A basic Outlook function is broken—and it’s not a small glitch
The Outlook Mac bug is a recent flaw in version 16.110, build 26061317 that stops replies and forwards from including email thread history, leaving the reply window blank and breaking the normal flow of Outlook conversation threads for many users who rely on contextual email communication.
Microsoft has managed to break a very basic Outlook function – the ability to include the previous email in a reply. Before this update, Outlook for Mac users replying to an email could see the original message thread in the compose area; after installing version 16.110, that space is now blank and no longer shows the original email. In practice, this means every reply looks like a brand-new message, stripped of past exchanges and context. For tools designed around productivity, this is not a cosmetic annoyance; it cuts into how people understand, audit, and trust long-running conversations.
The problem launched with version 16.110, build 26061317 on June 16, and Mac users who updated to this newest Outlook release lost the feature. Until Microsoft delivers an official fix, the experience of replying or forwarding in Outlook for Mac is fundamentally incomplete.
How the Outlook Mac bug destroys conversation context
When replying to an email, it's often helpful to include the conversation history for context. That is not a nice-to-have; it is the backbone of modern email. One affected user put it bluntly: "It makes it impossible to have a proper email thread because the recipient can't see the conversation history." With the reply area blank, multi-message exchanges get severed midstream, and everyone involved is forced to reconstruct context from memory or sift through their inbox manually.
The area where a response is composed is now left blank, no longer showing the original email. This hits both replies and forwards. As one user noted, when forwarding a message, the entire point is to forward the message; if the original content is missing, forwarding is defeated. The result is broken Outlook conversation threads and fragmented email thread history that make it harder to track decisions, commitments, and previous instructions.
You can technically work around this by copying and pasting parts of the original mail into your reply, but that shifts the burden onto users to manually rebuild context message by message. For anyone handling long, detailed chains, this bug does more than slow things down; it erodes confidence that their email record is complete and reliable.
Who is affected and why this is worse on managed devices
The bug afflicts Outlook for Mac users who installed version 16.110, build 26061317, which rolled out in mid-June. If you or your team rely on Outlook conversation threads to manage projects, approvals, or support cases, this is not a niche corner-case. It hits one of Outlook’s most basic and essential functions, and shipping an update that breaks it raises uncomfortable questions about Microsoft’s quality priorities.
For users in full control of their devices, the situation is annoying but manageable. They can decide whether to roll back and freeze updates. For anyone using a device managed by an employer—where updates are pushed centrally—the story is harsher. If you use a device managed by an employer, you may have to wait for Microsoft to roll out an official fix, and no timeline for that has been announced.
Administrators with fleets of Macs running Outlook should brace for helpdesk tickets. Every user who depends on email thread history will suddenly find their daily workflow broken. While some might welcome shorter, less scroll-heavy chains, disrupting user workflows without warning is a bad trade-off when it collapses fundamental email behavior.
The only real email reply fix right now: roll back and freeze updates
Microsoft has not yet released an official fix or communicated a public timeline. The Register asked Microsoft for its take on the matter, but the company has yet to respond, and a representative also did not immediately respond to another request for comment. In the meantime, users are left with a single meaningful email reply fix: revert to a known-good version.
According to a Microsoft forum moderator, the solution is to roll back to a previous version and turn off auto-updating until a fix is released. Official guidance says the only current solution is to revert to version 16.109.3 or earlier, which requires removing Outlook version 16.110 and installing an earlier build. Once you have version 16.109.3 or earlier, you must turn off automatic updates so that Outlook does not update back to the broken release.
It is an inelegant workaround and, for managed devices, sometimes impossible without IT intervention. Still, if you own your Mac and have the option, rolling back is the only way to restore normal email thread history and make replies and forwards behave the way Outlook promises.
What this Outlook Mac bug says about trust in everyday tools
This Outlook Mac bug is not a quirky edge-condition; it strikes at one of the core expectations users have of an email client: that replies and forwards will carry conversation history. Microsoft has already acknowledged through its moderators that the only email reply fix today is to revert to older builds and disable updates, which is a stark admission of how far this release missed the mark.
In some cases, encouraging people to copy and paste only the salient parts of a message might lead to cleaner chains; long, epic threads are a common complaint. But forcing this change through a silent bug rather than a deliberate feature shows a disregard for the workflows people have built around Outlook conversation threads. It also underlines a simple truth: running the latest version of a product is not always the safest choice, especially when essential functions can break overnight.
Until Microsoft ships a fix and restores confidence, the best you can do is decide whether the risk is worth it. If email is critical to your work—and for most people it is—pinning Outlook to a stable version and keeping a close eye on future updates is the more cautious move.
