The Outlook Mac email bug that broke basic email
The Outlook Mac email bug is a flaw in version 16.110, build 26061317 of Microsoft Outlook for Mac that removes the original message from reply and forward windows, wiping visible conversation history and undermining one of the most basic expectations of any email client.
Microsoft has managed to break a very basic Outlook function – the ability to include the previous email in a reply. The issue, which afflicts Outlook for Mac, was introduced in version 16.110, build 26061317, which rolled out to users last week and launched on June 16. Before the update, when Outlook for Mac users replied to an email, they could see the original message thread; after the update, this was no longer the case, and the area where a response is composed is now left blank, no longer showing the original email. That means email conversation history is effectively missing every time you hit Reply or Forward.
This is not a cosmetic glitch. It makes it impossible to have a proper email thread because the recipient cannot see the conversation history. When forwarding a message, users expect the original content to be included; when the original message is not included, then it defeats the purpose of forwarding. For an email client, that is the equivalent of a word processor suddenly refusing to show previous paragraphs.
Why this bug hurts productivity and trust
One of the most basic things an email client needs to do is preserve context in replies and forwards, and shipping a product with a bug that breaks this functionality says more about Microsoft’s approach to quality than anything else. The update effectively turns every reply into a blind message, forcing users to reconstruct context manually or risk confusing, incomplete threads.
Disrupting user workflows without warning is undoubtedly a bad thing. In workplaces where Outlook is a daily tool, this Outlook Mac email bug does not just annoy; it undermines trust in automatic updates. Administrators with fleets of Macs running Outlook are told to brace for helpdesk tickets, and users on managed devices may have to wait for Microsoft to roll out an official fix, with no timeline announced.
Microsoft has already delivered a kicking to Apple hardware users in recent weeks, and this bug reinforces a harsh lesson: running Microsoft’s latest and greatest carries its own risks. When a core feature like email conversation history goes missing, the supposed benefit of staying current starts to look like a liability.
The main Outlook Mac workaround: downgrade and freeze updates
There is no official Microsoft Outlook fix yet. A representative for Microsoft did not immediately respond to a request for comment, and no timeline for a patch has been announced. For now, the only reliable Outlook Mac workaround is blunt but effective: downgrade and lock your client in place until a repaired build appears.
The solution, according to one of Microsoft’s forum moderators, is to roll back to a previous version and turn off auto-updating until a fix is released. The representative said the only current solution is to revert to version 16.109.3 or earlier; to do so, you have to remove the current Outlook version 16.110 and install an earlier version. Once you have version 16.109.3 or earlier, you must turn off automatic updates so that Outlook does not update to the version that contains the bug.
That is fine for users in full control of their devices; they can downgrade, disable auto-updates, and carry on. It is not so good for anyone with a managed device, where policies may block manual installation or freezing of update channels. Those users are effectively stuck waiting while their email conversation history remains missing.
Temporary coping tactics if you cannot downgrade
Not everyone can rip out Outlook 16.110 on demand. If your Mac is managed by an employer, you may have to wait for Microsoft to roll out an official fix. In that limbo, you either adapt or switch tools. And yes, that may mean falling back on the kind of manual workarounds that email clients were supposed to make obsolete decades ago.
One option is to copy and paste the salient bits of the email you are responding to into your reply. In some instances, having a user copy only what matters might not be such a bad thing; it forces people to think about what they actually need to include. But as a long-term habit, this is a productivity tax and a source of human error, not a feature.
For critical threads, you might compose in a different mail client, use webmail for replies, or keep a backup of key emails outside Outlook. None of these are elegant, but when the core reply function is broken, the priority shifts from elegance to keeping conversation history intact by any means.
What this bug tells us about updates—and what to do next
This Outlook Mac email bug is more than an isolated glitch; it is a reminder that automatic updates can break things that users assumed were sacred. When a release makes it impossible to have a proper email thread because the recipient cannot see the conversation history, it betrays a blind spot in testing and a disregard for the workflows that keep teams running.
Until a formal Microsoft Outlook fix arrives, the pragmatic path is clear: if you can, downgrade to version 16.109.3 or earlier, turn off automatic updates, and protect your email conversation history. If you cannot, adopt temporary workarounds or alternative clients and push your administrators to prioritize a rollback. The real lesson is this: do not assume that the latest build is the safest; for now, stability beats novelty, especially when the novelty is an empty reply window.
