Outlook Mac email bug: a basic feature suddenly disappears
The current Outlook Mac email bug is a software defect in Outlook for macOS where replies and forwards no longer include the original email, effectively deleting visible conversation history from the composition window and breaking standard email thread behavior for updated users. This is not a minor glitch; Microsoft has managed to break a very basic Outlook function – the ability to include the previous email in a reply. The issue afflicts Outlook for Mac in version 16.110, build 26061317, which launched on June 16. Before the update, the original message appeared in the reply window; after the update, nothing. The area where a response is composed is now left blank, no longer showing the original email. For an app that dominates corporate inboxes, shipping a build that makes email thread history missing is a self‑inflicted productivity wound.
Why broken conversation threads are more than an annoyance
Losing conversation history in replies and forwards isn’t cosmetic; it changes how teams work. One affected user put it plainly: “It makes it impossible to have a proper email thread because the recipient can't see the conversation history”. Another called it “an extremely frustrating bug” and questioned how something so major evaded testing before rollout. When Outlook conversation threads are broken, context evaporates: recipients must hunt through separate messages or guess what a reply refers to. This undermines one of the most basic things an email client needs to do, and shipping a product with a bug that breaks this functionality says more about Microsoft's approach to quality than anything else. In workplaces that live in their inbox, this isn’t a minor update hiccup; it is a direct hit to trust in updates and in the product itself.
Who is affected: from individual users to IT teams
The Outlook Mac email bug hits anyone who updated to version 16.110, build 26061317 on macOS. Power users, freelancers and small businesses with full control of their devices can at least respond quickly, but administrators with fleets of Macs running Outlook should brace for helpdesk tickets. Every broken reply and forward where the email thread history is missing becomes an IT support problem, especially for teams that rely on long, detailed chains. And if your device is managed by an employer, you may have to wait for Microsoft to roll out an official fix, because policy may block manual rollback. In theory, users can temporarily copy and paste salient parts of the message they are responding to. In practice, forcing people to manually reconstruct context on every email is a clumsy workaround that slows down already busy inboxes.
The only real Outlook macOS workaround right now
There is no official fix from Microsoft yet; representatives have not responded to requests for comment, and the tech behemoth has yet to provide its take. For now, the only meaningful Outlook macOS workaround is rolling back. A Microsoft forum moderator and an external staff representative say the solution is to revert to version 16.109.3 or earlier. That means 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 doesn’t update back to the version that contains the bug. In Outlook for Mac, go to the Help dropdown, click Check for Updates, and uncheck Automatically keep Microsoft apps up to date. This protects conversation threads but leaves you stuck on older code until Microsoft finally ships a competent patch.
What this incident reveals about Microsoft’s update culture
Breaking conversation threads on Outlook for Mac is more revealing than any marketing campaign. It shows that Microsoft is willing to ship an update where email thread history is missing from replies and forwards, even though this is one of Outlook’s most basic and essential functions. In isolation, bugs happen. But in the context of recent decisions—such as Office 2019 on Apple hardware entering a reduced functionality mode soon, nudging users toward upgrades—this fiasco reinforces a pattern: “latest and greatest” isn’t always safer or better for users. The lesson for Outlook users on macOS is blunt: treat updates as change management, not routine housekeeping. Delay rapid adoption, keep a rollback plan, and demand clearer testing standards. Until Microsoft releases a fix for Outlook conversation threads broken by 16.110, staying on older versions is the most reliable option.
