What the Outlook for Mac Conversation Bug Does
The Outlook for Mac conversation bug is a software defect in Outlook version 16.110, build 26061317, that removes the original message from reply and forward windows, causing email thread context and conversation history to disappear for users composing responses. After installing the recent update, Outlook no longer shows the previous email in the reply area, leaving a blank compose pane instead of the referenced conversation. According to The Register, one user said, “It makes it impossible to have a proper email thread because the recipient can’t see the conversation history.” This flaw affects one of the most basic email features and disrupts normal workflows for anyone who depends on readable reply chains. Forwarded emails suffer the same problem, undermining the very purpose of forwarding messages for shared context and documentation.
Who Is Affected and Why It Matters
The bug appears in Outlook for macOS starting with version 16.110, build 26061317, released on June 16. Users who updated to this specific build are affected whenever they reply to or forward messages. Instead of including earlier emails in the thread, Outlook opens an empty compose window, so recipients no longer see the conversation history below the response. This hits productivity for people who rely on long-running threads for projects, approvals, or support cases. The Register notes that shipping a client with a bug that breaks reply content “says more about Microsoft’s approach to quality than anything else.” Individual users can be confused by vanishing context, while IT admins managing fleets of Macs can expect a spike in helpdesk tickets as staff discover their replies no longer contain the prior conversation.
Step-by-Step Outlook Mac Bug Fix: Roll Back and Lock Version
Until Microsoft releases an official patch, the current Outlook Mac bug fix is to revert to an earlier version and prevent auto-updates. A Microsoft Learn moderator says the only stable option now is to roll back to version 16.109.3 or earlier. First, quit Outlook and uninstall version 16.110 from your Mac. Next, download and install Outlook 16.109.3 or another earlier stable build from your organization’s software portal or Microsoft’s official distribution channel. Once installed, open Outlook and confirm that replies and forwards now include the original email thread. Then disable auto-updates: go to the Help menu, choose Check for Updates, and clear the checkbox labeled Automatically keep Microsoft apps up to date. This locks you on the working version until Microsoft confirms a fix and you decide to re-enable updates.
Special Cases: Managed Devices and Recovering Conversation History
If your Mac is managed by an employer or IT department, you might not be able to uninstall Outlook or block updates yourself. In that case, contact your helpdesk and share the known workaround so administrators can evaluate whether to roll back the affected version across devices or apply configuration changes centrally. For emails already sent without conversation history, full threads remain in your mailbox, but your recipients receive only your latest reply text. To avoid confusion while the bug persists, manually copy key parts of the previous message into your reply body so the recipient has enough context. This is less convenient than automatic threading but prevents misunderstandings. Remember to monitor internal announcements or Microsoft Learn for notice of an official fix, and plan with IT for when it’s safe to restore automatic updates.
What This Bug Reveals About Outlook on macOS
The Outlook Mac email thread deletion issue highlights ongoing stability concerns for users who depend on Microsoft’s latest builds. When a core function like including conversation history in replies and forwards breaks, the impact is immediate: lost context, messy inboxes, and extra manual work to reconstruct threads. The Register points out that disrupting user workflows without warning is “undoubtedly a bad thing,” and this incident reinforces the risk of installing every new build on day one. For organizations, it underlines the need to test key applications on macOS before broad rollout, especially when updates affect essential tools like email. For individual users, this bug is a reminder to keep an eye on version numbers, maintain backups of critical correspondence, and know how to revert when a new release harms, rather than helps, everyday work.
