Microsoft Fixes Outlook Bug Blocking Access to Encrypted Emails

Why It Matters

The fix restores access to encrypted communications essential for compliance‑sensitive workflows, preventing potential data‑access disruptions for Microsoft 365 enterprises.

Key Takeaways

• Outlook bug blocked “Encrypt Only” emails after Dec update
• Fix released to Beta, rolling to Current Channel Feb
• Workaround: use Encrypt option via Options ribbon
• Alternate: revert to prior build using ClickToRun command
• Issue impacted Microsoft 365 users, risking data access

Pulse Analysis

Classic Outlook’s “Encrypt Only” feature lets senders protect content without restricting forwarding, printing or copying. A December 2025 update (Current Channel Version 2511, Build 19426.20218) introduced a regression that replaced the encrypted payload with a message_v2.rpmsg attachment, rendering the email unreadable in both reading pane and full‑screen view. The problem surfaced across Microsoft 365 tenants, prompting support tickets from finance and legal teams that rely on encrypted communications. Microsoft confirmed the defect three weeks ago and began engineering a fix. The issue highlighted how minor code changes can cascade into compliance risks.

The quick release of a Beta Channel fix, followed by a February rollout to Current and Current Preview channels (Build 19725.20000), demonstrates Microsoft’s commitment to maintaining compliance‑critical features. In the interim, administrators can mitigate risk by directing users to the “Encrypt” command on the Options ribbon or by rolling back to the pre‑bug build with a Click‑To‑Run command line. Both workarounds preserve message confidentiality while avoiding service disruption, a crucial consideration for regulated industries that must meet data‑privacy mandates. These steps also reduce the likelihood of missed deadlines in audit cycles.

This incident adds to a series of recent Outlook stability issues, including drag‑and‑drop failures, CPU spikes, and outright crashes after Windows 24H2 updates. The pattern underscores the importance of a disciplined update cadence and thorough testing in enterprise environments. IT leaders should monitor Microsoft’s release notes, maintain a staged deployment pipeline, and keep fallback images ready, ensuring that critical email functionality remains available even when a patch is delayed. Proactive communication with end‑users further smooths the transition and preserves productivity. It also reinforces confidence in the Microsoft 365 ecosystem.