A Core Outlook Mac Function Has Been Broken
The current Outlook Mac bug is a defect in version 16.110, build 26061317 that stops replies and forwards from including the original email conversation history, leaving users with blank response windows and no visible thread context. This is not a cosmetic annoyance but a direct hit on one of the most basic expectations of any modern mail client: that a reply contains what you are replying to. Before this update, Outlook for macOS displayed the previous message in the reply window; after the update, the field is empty. The result is broken email threads and confused correspondents who can no longer see how a conversation evolved, and that deserves more than a quiet shrug from Microsoft.
Why Losing Email Conversation History Is Such a Big Deal
Email conversation history is the backbone of how teams remember decisions, promises, and context. With Outlook for Mac now omitting the previous message in replies, recipients “can't see the conversation history,” making “it impossible to have a proper email thread.” The reply area is instead “left blank, no longer showing the original email,” turning every response into a context-free note. That undermines both replies and forwards, where “when the original message is not included, then it defeats the purpose of forwarding.” In theory, users can copy and paste what they think matters, and some may welcome less endless quoted text. In practice, forcing people to re-create context by hand is error‑prone, time‑consuming, and guarantees inconsistent records across long-running conversations.
The Outlook Reply Issue Exposes a Quality Problem
What makes this Outlook reply issue so disappointing is how fundamental the broken feature is. Microsoft has “managed to break a very basic Outlook function – the ability to include the previous email in a reply.” This is not an edge case; it is “one of the most basic things an email client needs to do,” and shipping a version where that fails “says more about Microsoft's approach to quality than anything else.” One user calls it “an extremely frustrating bug” and is “frankly quite disappointing that something major like this completely evaded the software testing process.” The bug landed in version 16.110, build 26061317, released June 16, without warning to end users. That kind of disruption to everyday workflows erodes trust and raises fair questions about how aggressively updates are tested before they are pushed out.
The Only Real Email Thread Fix Right Now: Roll Back Outlook
Microsoft has not yet provided an official fix or timeline, and a representative has not responded to requests for comment. Instead, the only reliable email thread fix comes from moderators on Microsoft’s own platform: users must uninstall Outlook 16.110 and revert to version 16.109.3 or earlier. After downgrading, they have to turn off automatic updates so Outlook does not quietly reinstall the broken build. According to that guidance, “the solution… is to roll back to a previous version and turn off auto-updating until a fix is released.” This workaround is workable for individuals who control their own Macs, but anyone on a managed device may be stuck until an official patch arrives. For IT teams, that means preparing for a wave of helpdesk tickets and deciding whether to block or reverse the update fleet‑wide.
What Outlook for Mac Users and Admins Should Do Next
Given how central email conversation history is to everyday communication, treating this Outlook Mac bug as optional is a mistake. Individuals who have the option should follow the moderators’ advice: remove Outlook version 16.110, install 16.109.3 or earlier, and disable automatic updates until Microsoft publishes a repair. Those stuck on managed devices can only escalate the issue and press for a rollback, while carefully copying and pasting relevant context for critical replies in the meantime. Administrators “with fleets of Macs running Outlook should brace for helpdesk tickets” and proactively brief users on the problem and the interim workaround. Bugs happen, but breaking a core email function without a fast, visible response invites frustration. The message to Microsoft is simple: fix Outlook for Mac quickly, and treat thread integrity as sacred going forward.
