The Outlook Mac email bug that wipes your conversation history
The Outlook Mac email bug is a flaw in Microsoft Outlook for macOS where replying or forwarding no longer includes the previous message, causing the email conversation history to appear blank and breaking normal threaded communication. 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 launched on June 16 and rolled out to users shortly after. Before the update, the original message appeared in the reply window; after the update, nothing shows where the prior email should be. The area where a response is composed is now left blank, no longer showing the original email. In other words, your reply box has turned into a memory hole.
Why this bug is a serious break in Outlook’s core usability
This is not a minor annoyance; it strikes at one of email’s most basic promises: threaded conversations. One affected user summed it up: “It makes it impossible to have a proper email thread because the recipient can't see the conversation history”. When forwarding a message, users expect the original message to travel with it; when the original message is not included, it defeats the purpose of forwarding. Shipping a product with a bug that breaks this functionality “is, after all, one of the most basic things an email client needs to do” and raises fair questions about Microsoft’s approach to quality. Disrupting user workflows without warning is a bad move even when everything else works; doing so while gutting reply and forward behavior is worse.
Who should be worried: individual users, managed devices, and IT
If Outlook is central to your email workflow on macOS, you should treat this Outlook Mac email bug as a critical risk. Administrators with fleets of Macs running Outlook should brace for helpdesk tickets as confused users discover their email conversation history deleted from replies and forwards. The only current workaround requires control over the software version, which is great for users in full control of their devices – not so good for anyone with a managed device. If you use a device managed by an employer, you may have to wait for Microsoft to roll out an official fix, because rolling back is often blocked by policy. Meanwhile, every reply you send from the broken version risks confusing clients, breaking audit trails, and forcing people to reconstruct context from scattered messages.
The Outlook thread bug fix: rollback and disable auto-updates
Here is the uncomfortable reality: there is no in-place Outlook thread bug fix right now. A moderator labeled as Microsoft external staff says the only current solution is to revert to version 16.109.3 or earlier. 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. 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 means going to the Help dropdown, choosing the update tool, and unchecking the option to automatically keep Microsoft apps up to date. You will need to remember to re-enable updates after Microsoft ships a repaired build.
Stopgap email workarounds and why you should act before it hits
Until an official fix lands, the only email workaround inside the broken version is manual and fragile: copy and paste the important parts of the email you are responding to into your reply. In some instances, having a user copy and paste the salient bits might not be such a bad thing, because it forces people to think about what they actually need to include. But as a long-term answer, this is not acceptable; it turns every reply into a manual editing task and makes mistakes likely. Users should be aware of this issue before it affects their email workflows, because once messages go out without history, the damage is done. The lesson is blunt: running the latest and greatest Outlook build can carry its own risks, and when quality slips, your daily tools can undermine you instead of helping.
