Users of the legacy Outlook application on Mac computers woke up last week to a frustrating surprise. An automatic update to version 16.110 quietly removed the ability to see previous messages when composing a reply or forwarding an email. The compose window now sits blank. Only the new text appears. Context vanishes. Recipients receive messages stripped of the thread they need to understand the discussion.
This bug surfaced shortly after the June 16, 2026 release. CNET first highlighted the problem, noting that the area where users once reviewed the full conversation history now displays nothing. Before the update, replying or forwarding pulled in the entire prior exchange. After, it does not. The change affects HTML-formatted emails most severely. Plain text sometimes shows the body but with awkward gaps.
But the issue runs deeper than a simple visual glitch. Professionals who rely on threaded email conversations for project coordination, client negotiations, or internal approvals suddenly found themselves copying and pasting old messages manually. That extra labor adds up fast across dozens of emails a day. One user on Microsoft’s forums captured the exasperation. “This is an extremely frustrating bug in this last update, and I hope a fix is on the way,” wrote Stephan. He added, “This is frankly quite disappointing that something major like this completely evaded the software testing process before it was being rolled out.”
Microsoft acknowledged the defect within days. A moderator on the company’s Q&A platform stated plainly, “Microsoft has confirmed that this is a known issue affecting Legacy Outlook for Mac. Specifically, the issue impacts the retention of conversation history when replying to or forwarding messages. The product team is currently investigating this behavior, and a fix will be released once it becomes available.” The admission appeared in multiple threads, including this detailed discussion thread.
Reports poured in quickly. On Reddit’s r/Outlook community, users described the same sudden failure. Yesterday it worked. Today the original message stamp appears but the body below stays empty. Forwarding suffers equally. The entire purpose of the feature disappears. Enterprise administrators managing fleets of Macs braced for help-desk calls. Many corporate devices block users from easy rollbacks. They depend on centralized update policies.
The timing feels particularly awkward. Microsoft has spent years nudging Mac users toward its redesigned New Outlook client. That version uses a different architecture built on web technologies. Most users have already migrated. Legacy Outlook remains available through a toggle for those who prefer the older interface or need specific add-ins and Exchange on-premises compatibility. The bug hits exactly that shrinking but vocal group still committed to the classic experience.
Recent coverage adds color. Windows Report detailed the version specifics on June 23, confirming the defect in 16.110 and the absence of any immediate patch. Windows Central reported the confirmation one day earlier, quoting frustrated users and outlining the business impact. The bug does not delete actual emails from the inbox or sent folders. It simply fails to quote them into new messages. Still, the effect feels like deletion to anyone trying to maintain clear communication chains.
So what can affected users do right now? Microsoft and community moderators recommend two paths. The fastest fix involves downgrading. Users must first disable automatic updates inside any Office application by going to Help, selecting Check for Updates, and clearing the box for automatic maintenance. They quit all Office apps, drag the current Outlook from the Applications folder to the trash, then install version 16.109.3 or 16.108 from Microsoft’s update history archive. The direct package links live on the company’s support site.
That approach works for individual machines. It carries risks for managed environments. Once downgraded, users must remember to re-enable updates after the eventual patch arrives. Otherwise they miss security improvements and other fixes. A preview build numbered 16.110.1 has shown promise for some testers in the Current Channel, though results vary.
The alternative pushes users toward the New Outlook entirely. Microsoft promotes this modern client as the future. It handles conversation threading differently and avoids the bug. Yet many professionals resist. They cite missing features, slower performance on large mailboxes, or broken compatibility with certain corporate plugins. Apple Mail offers another escape hatch, but it introduces its own headaches with embedded images and Teams integration.
This episode exposes broader tensions in how Microsoft maintains its Mac software. The legacy app receives updates less frequently than its Windows counterpart. When changes do arrive, they sometimes carry unintended consequences. Quality and performance improvements appeared in the 16.110 release notes. Nothing hinted at broken email quoting. That silence left users blindsided.
Conversation history in email clients exists for good reason. It provides immediate context. It reduces miscommunication. It saves time. Removing it without warning forces every participant to reconstruct the narrative. In fast-moving industries such as finance, law, or technology consulting, those seconds and minutes matter. They accumulate into hours of lost productivity.
Industry observers note that Microsoft has improved its response speed. The company acknowledged the problem within a week of widespread reports. Contrast that with past Mac Outlook outages that lingered for months. Still, the absence of a concrete timeline frustrates power users. No one knows whether the repair arrives in days, weeks, or as part of the next monthly bundle.
And the workaround instructions themselves reveal the awkward state of the product line. Throwing the application in the trash and manually installing an older package hardly qualifies as an elegant enterprise solution. Administrators in large organizations now face the choice between widespread disruption or asking employees to tolerate broken threading until the fix lands.
Outlook on Mac has traveled a long road since its early days. Once criticized for lagging far behind the Windows edition, it gained ground through steady updates and better cloud integration. This regression serves as a reminder that even mature software carries hidden dependencies. A seemingly minor alteration to how quoted text renders can cascade into major workflow pain.
Users who have already rolled back report immediate relief. The original messages reappear. Threads behave as expected. They simply must stay vigilant against the next automatic update. Others experiment with copy-and-paste routines or shift their primary work to Outlook on the web. That browser version continues to function normally.
The incident also revives debate about the wisdom of maintaining two parallel Outlook experiences on macOS. The New Outlook receives the bulk of development attention. Legacy support feels increasingly like an afterthought. Yet for certain power users the older interface remains indispensable. Microsoft must balance the desire to simplify its codebase against the real needs of those holdouts.
Until the patch arrives, the practical advice stays straightforward. Check your version number. If you see 16.110 and rely on conversation history, consider the downgrade path immediately. Document the steps. Test thoroughly on a non-critical machine first. And keep an eye on Microsoft’s support channels for any new preview builds that might resolve the matter without forcing a full switch.
The company built its reputation on dependable productivity tools. Moments like this test that trust. How Microsoft communicates the fix, how quickly it ships, and whether it prevents similar surprises in future releases will determine how quickly users forgive the lapse. For now, many Mac professionals find themselves manually reconstructing email context they once took for granted. The blank compose window stares back. The history they need is gone. At least until the next update changes everything again.
WebProNews is an iEntry Publication