A critical bug in the latest Outlook for Mac update is driving users to frustration as every reply or forwarded email arrives with a completely blank message body, eliminating the original thread and leaving recipients with no context. Microsoft has acknowledged the issue, which affects the legacy version of Outlook for Mac, and has already begun deploying a fix through version 16.110.1.

The bug, introduced in Outlook for Mac version 16.110 (build 26061317), landed in the Microsoft 365 stable channel in mid-June 2026. Within hours of its release, reports flooded community forums and social media with users describing replies and forwards that stripped all content from the original message, showing only the newly typed response—or nothing at all if the user hadn’t added their own text.

“I thought I was going crazy,” said one IT administrator who manages a fleet of Macs for a midsize law firm. “A partner forwarded a contract to me, and the email was completely empty. We almost missed a deadline because I had to chase down the original message.”

The Blank Body Bug: What Happens and Who Is Affected

The bug manifests in the legacy Outlook for Mac interface, not the new Outlook for Mac that Microsoft has been encouraging users to adopt. When a user clicks Reply, Reply All, or Forward, the composer window opens with the original message body missing or invisible. Any inline text, images, or formatting disappears, though attachments remain intact if forwarded. The problem occurs regardless of the email account type—Exchange, IMAP, or POP—and affects both plain text and HTML messages.

Technical analysis points to a regression in how the legacy Outlook client processes the message body when generating reply content. In build 26061317, the rendering engine appears to fail to copy the original body buffer into the new draft, resulting in an empty composition space. The issue is purely visual; the original message data isn’t lost, but it isn’t displayed or transmitted in the reply.

Microsoft confirmed the problem in a support article published on June 18, 2026, two days after the initial reports. The article read: “After updating to Outlook for Mac version 16.110 (build 26061317), users may see that the body of the original email is blank when replying to or forwarding messages in legacy Outlook. We are investigating and will provide an update when a fix is available.” The article quickly became a rallying point for affected users.

A Timeline of Trouble: From Release to Fix

Version 16.110 arrived on June 14, 2026, as part of Microsoft’s regular monthly update cadence for Office for Mac. It included several new features for the new Outlook interface, such as improved search relevance and calendar peek improvements, but also carried routine security patches and performance fixes. The release notes made no mention of any change that would have foreshadowed the reply blanking bug.

Within a day, the first complaints appeared on Microsoft’s Answers forum: “All my replies are empty since updating Outlook this morning. Anyone else?” By June 16, the thread had over 200 replies, with users sharing workarounds and expressing disbelief that such a fundamental flaw could pass testing. “How do you break the most basic email function?” one user posted.

Microsoft’s engineering team identified the root cause as a component mismatch in the legacy rendering pipeline and began testing a fix internally. Rather than wait for the next monthly update, the company opted for an out-of-band hotfix. On June 20, 2026, Outlook for Mac 16.110.1 (build 26061425) began rolling out through the Microsoft AutoUpdate tool.

The Fix: Version 16.110.1 and How to Install It

The hotfix, Outlook for Mac 16.110.1, specifically addresses the blank body issue and contains no other changes. Users can install it manually by opening any Office application, going to Help > Check for Updates, and allowing Microsoft AutoUpdate to download and apply the latest build. For managed environments, the update package is available through standard software distribution channels, including Jamf and Microsoft Intune.

Microsoft’s updated support document confirmed the fix: “This issue has been resolved in version 16.110.1 (build 26061425). After installing this update, the original email body will appear correctly when replying to or forwarding messages.” The document also noted that the bug did not affect the new Outlook for Mac, and encouraged users still on legacy Outlook to consider switching to the new experience.

Early adopters of the fix report that functionality returns to normal immediately after the update. No restart or database repair is required.

Community Reaction: Anger, Relief, and Insistence on Better Testing

User sentiment on forums and social channels was swift and sharp. While many expressed relief that Microsoft delivered a fix within a week, the outrage over the initial slip-up was palpable. The bug had real-world consequences: businesses missed threaded conversations, legal teams lost important context in email chains, and customer service reps accidentally sent blank replies to customers.

“We had to tell our entire department to stop replying to any external email until the fix came out,” said an IT director at a university. “It was either that or risk looking incredibly unprofessional.”

Others pointed out that the legacy Outlook for Mac client has felt neglected, with many features lagging behind the Windows version. The blank reply bug felt to some like the final straw. “Microsoft is clearly prioritizing the new Outlook, and that’s fine, but they can’t let the old one rot while we’re still using it,” wrote a commenter on a prominent Mac admin blog.

The incident also reignited discussion about Microsoft’s testing practices. With over 800 million Office 365 users, even a 1% impact translates to millions of affected individuals. Several community members called for a public post-mortem, though Microsoft rarely releases such documents.

Workarounds That Users Discovered (and Shared)

While waiting for the official fix, users developed several stopgap measures:

  • Copy and paste the original message: Before replying, users could open the original email in a separate window, copy its contents, and paste them into the reply window. Cumbersome but effective.
  • Use the new Outlook for Mac: Microsoft’s new Outlook client, which is available via a toggle in the top-right corner of the legacy app, was not affected. However, some users resist the new interface due to missing features like PST file support or third‑party add‑ins.
  • Reply from a mobile device or the web: Outlook on iOS, Android, or the Outlook Web App (OWA) worked correctly, so some users temporarily shifted their workflow to those platforms.
  • Roll back to version 16.109: Advanced users downloaded the previous installer from Microsoft’s update history repository and reinstalled, though this was not officially recommended.

None of the workarounds were ideal, especially for those in tightly managed environments where the new Outlook toggle is disabled or software installation is locked down.

Why Legacy Outlook Matters: The Divide Between Old and New

Microsoft has been pushing its new Outlook for Mac since 2020, with a revamped interface built on Microsoft’s React Native-based architecture. It offers faster performance, a cleaner design, and features like ignore conversation and better calendar integration. However, the legacy client remains the default for many users due to its broader compatibility with Exchange public folders, certain third‑party integrations, and some accessibility tools.

As of 2026, Microsoft has not announced an end-of-support date for the legacy Outlook for Mac, but the writing is on the wall. Features are no longer being added to the legacy version; only security and stability fixes are delivered. The blank reply bug is a stark reminder of the risks of running an application in maintenance mode—regressions in core functionality can slip through because the test matrix may favor the newer client.

Analysts suggest that the incident might accelerate migration to the new Outlook, but not without resistance. “Every time Microsoft forces a change, there’s an uproar,” said an independent Office consultant. “But the longer users stay on legacy, the more these kinds of bugs will happen.”

Microsoft’s Larger Update Strategy for Mac Office

Outlook for Mac follows the same update cadence as the rest of the Office suite. Major updates typically arrive on the second Tuesday of each month, with hotfixes released as needed. The version 16.110 mishap is part of a broader pattern where monthly updates occasionally introduce regressions; earlier in 2026, an Excel for Mac update broke Power Query refreshes, and a Word update caused frequent crashes when opening documents from OneDrive.

Unlike Windows, where administrators can defer updates via Group Policy, Mac users have fewer granular controls. Microsoft AutoUpdate can be configured to manual mode, but many users keep it on automatic to ensure they receive security patches promptly. The blank reply bug illustrates the trade‑off: early access to fixes also means early exposure to new bugs.

Microsoft’s response time—six days from initial report to fix rollout—was relatively fast by industry standards. The company credited its automatic crash reporting and the detailed reproduction steps provided by the community for speeding the diagnosis. In a brief statement, a Microsoft spokesperson said, “We appreciate the patience of our customers and the community’s help in flagging this issue. We are reviewing our testing processes to help prevent similar regressions in the future.”

What the Bug Meant for Microsoft’s Reputation

Perception matters in the productivity software market. For many Mac users, Outlook is a necessary evil—mandated by their employer but often compared unfavorably to Apple’s Mail or third‑party alternatives like Spark. A bug that makes replies unreadable reinforces the stereotype that Microsoft doesn’t care deeply about the Mac experience.

Yet, the quick fix also demonstrated that Microsoft can still react effectively when a fire is lit. Some users even praised the outcome: “They broke it, they fixed it in under a week. That’s better than a lot of software companies,” commented a Reddit user in the r/Office365 community.

The incident arrived at an awkward time for Microsoft, which was in the middle of its “Modern Work” campaign promoting the new Outlook and Teams. The bug risked undermining confidence in the very tool that underpins enterprise communication.

Moving Forward: Lessons and Recommendations

For IT administrators and end users alike, the blank reply bug offers several takeaways:

  • Set Microsoft AutoUpdate to “Let Me Check”: Gaining a few days before installing new updates can allow early‑adopting community members to surface issues.
  • Test updates on a pilot group: Organizations should deploy updates to a small set of users first, especially for critical communication tools.
  • Know your legacy/new toggle: If the bug reappears, switching to the new Outlook (if enabled) can be a lifesaver.
  • Monitor Microsoft’s health dashboard: Microsoft maintains a service health page in the Microsoft 365 admin center that now includes known issues for Outlook for Mac. Subscribing to updates can shorten your response time.
  • Keep a backup installer handy: For mission‑critical environments, retaining the previous version’s installer can enable a rapid rollback without waiting for a fix.

Microsoft is expected to release a full post‑incident summary in the coming weeks, but in the meantime, the takeaway is clear: even mature software can stumble, and the difference between a minor hiccup and a headline‑grabbing disaster often lies in how quickly the fix is delivered.

The Bottom Line

The Outlook for Mac blank reply bug of June 2026 was a serious but short‑lived crisis. In less than a week, Microsoft diagnosed and deployed a hotfix that restored full functionality for legacy Outlook users. The incident exposed the fragility of dual‑client strategy and served as a wake‑up call for organizations that had not yet tested updating to the new Outlook.

For those still on legacy Outlook, the question now is whether this bug will be the nudge they need to switch—or whether they’ll cling to the familiar a little longer, accepting the occasional blank reply as the cost of stability.