Outlook Classic Update Causes Encrypted Email Failure Bug

A recent security update for Microsoft’s classic Outlook email client has introduced a significant bug that prevents users from opening encrypted emails. This issue, confirmed by Microsoft, has caused considerable disruption for businesses and individuals who rely on email encryption for sensitive communications and data protection. The unexpected failure to decrypt and access these messages has led to workflow interruptions and potential security concerns.

The problem specifically affects recipients using the classic Outlook desktop client. When attempting to open “Encrypt Only” messages, users encounter an error or find the email content replaced by an unreadable attachment, typically named “message_v2.rpmsg.” This behavior occurs even after users attempt to verify their credentials, indicating the issue lies within Outlook’s decryption process rather than user authentication.

Root Cause and Triggering Event

Microsoft has identified the root cause of the encrypted email failure bug. The issue began after users installed Current Channel Version 2511 (Build 19426.20218) of the classic Outlook application. This specific update, intended to enhance security, inadvertently disrupted the email decryption mechanism.

The problem is directly linked to how Outlook handles the decryption of emails encrypted using the “File > Encrypt” dialog. When users encrypt messages through this specific path, recipients on affected versions of classic Outlook are unable to access the content. Instead of viewing the email body, they are presented with a credential verification prompt, followed by the unreadable .rpmsg attachment.

It is important to note that this bug does not appear to affect all users or all types of encrypted emails. However, for organizations that frequently exchange sensitive data, such as contracts, financial information, or proprietary trade secrets, this disruption can significantly impede daily operations and communication flow.

Symptoms and User Experience

Users encountering this bug typically experience a series of frustrating symptoms. Upon trying to open an encrypted email, they may be prompted to verify their credentials, even if their login information is correct. Following this prompt, the email does not display its intended content.

Instead, the email appears as an unreadable attachment, often labeled as “message_v2.rpmsg.” This attachment contains the encrypted data but cannot be deciphered by the affected Outlook client, rendering the message inaccessible. This situation creates a significant barrier for users needing to access critical information promptly.

The issue can manifest in the Reading Pane, where a message might appear stating, “This message with restricted permission cannot be viewed in the reading pane until you verify your credentials. Open the item to read its contents and verify your credentials.” Even opening the message in a new window does not always resolve the problem, as the core issue lies in Outlook’s decryption capabilities after the update.

Impact on Businesses and Security

The inability to access encrypted emails has a direct and substantial impact on businesses. Encrypted emails are often a requirement for regulatory compliance, protecting intellectual property, and maintaining client trust. When this functionality is broken, it can lead to delayed responses, missed business opportunities, and potential security risks if employees resort to unapproved workarounds.

For organizations that handle confidential contracts, financial data, or sensitive internal credentials via email, this disruption can slow down daily operations considerably. The integrity and non-repudiation of S/MIME signed messages can also be compromised in some scenarios, as discussed in relation to other Outlook encryption issues.

Furthermore, the bug could indirectly increase security risks if users begin seeking alternative, potentially less secure, methods to share information. This undermines the very purpose of using encrypted communication channels in the first place.

Microsoft’s Response and Acknowledgement

Microsoft has publicly acknowledged the bug affecting encrypted emails in classic Outlook. The company confirmed the issue in an update posted on January 6, 2026, and is actively working on a permanent fix.

The issue is specifically documented on Microsoft’s support pages, where they provide updates on the investigation and potential resolutions. While a timeline for the permanent fix has not been provided, Microsoft’s acknowledgement signals their commitment to addressing the problem.

Microsoft has also emphasized that the problem is limited to classic Outlook and specific encryption methods, particularly those using the “File > Encrypt” option. This targeted nature helps in diagnosing and resolving the issue more effectively.

Workarounds for Affected Users

While Microsoft works on a permanent solution, several workarounds are available to help users access encrypted emails. These temporary measures aim to minimize disruption to daily workflows.

One recommended workaround involves using an alternative encryption path. Instead of using “File > Encrypt,” users can select the “Options” ribbon, then “Encrypt,” and choose “Encrypt or Do Not Forward.” This alternative method appears to bypass the bug introduced by the recent update.

Another workaround suggests saving the encrypted email as a draft after applying encryption via “File > Encrypt” and before sending it. This intermediate step may allow the email to be processed correctly. Additionally, accessing encrypted emails through Outlook on the web (OWA) has been reported as a functional alternative, as OWA is unaffected by this specific desktop client bug.

For those comfortable with system modifications, reverting to a previous build of Outlook is also an option. Specifically, rolling back to build 19426.20186, which predates the problematic update, can resolve the issue. This process typically involves closing all Office applications and running a specific command in an elevated Command Prompt.

Technical Details of the Bug

The bug stems from a regression in Outlook’s message rendering or protection-handling code following the update. When the “File > Encrypt” path is used, the client’s mechanism for recognizing the encrypted package or acquiring the necessary license to render the message content appears to be impaired.

This impairment leads to Outlook incorrectly packaging the encrypted content as an .rpmsg attachment rather than rendering it as readable text. The issue is particularly notable when dealing with “Encrypt Only” messages, which are designed for maximum confidentiality.

The problem is considered a high-impact but narrowly scoped client regression, meaning it affects a critical function but is confined to specific scenarios within the classic Outlook client. The interaction between different protection schemes, such as S/MIME and Office Message Encryption (OME), can sometimes create complex rendering paths, and this update seems to have introduced a fault in one of these paths.

S/MIME and OME Interaction Issues

While the primary bug concerns “Encrypt Only” messages, related issues have been reported concerning S/MIME-signed and Office Message Encryption (OME) protected emails. In some instances, opening a message that is both S/MIME signed and OME protected could trigger a dialog box warning users that they have changed the message and that saving the changes would remove the digital signature.

This prompt, intended for ordinary editing actions, could lead to the unintentional stripping of S/MIME signatures if users select to save changes. The loss of a digital signature fundamentally undermines the non-repudiation and integrity guarantees of S/MIME, posing a significant risk in legal and regulated communications.

Microsoft has documented and provided fixes for these specific S/MIME and OME interaction problems in certain Outlook builds. Users experiencing such issues should verify their Outlook build number and ensure they are running a patched version that addresses these composite protection scenarios.

Reverting to Previous Builds

For users facing persistent issues with encrypted emails, reverting to a prior, stable build of Outlook is a viable workaround. The problematic update was Current Channel Version 2511 (Build 19426.20218). The build that preceded this and is known to work correctly is 19426.20186.

To revert, users must first close all Microsoft Office applications. Subsequently, they need to open an elevated Command Prompt and execute a specific command. The command provided by Microsoft is: “%programfiles%Common FilesMicrosoft SharedClickToRunofficec2rclient.exe” /update user updatetoversion=16.0.19426.20186.

This process effectively rolls back the Office Click-to-Run client to the last known working version in that build family. While effective, this method requires administrative privileges and careful execution to avoid unintended consequences. It is a more intrusive solution compared to using alternative encryption methods.

Outlook on the Web as an Alternative

Outlook on the web (OWA) has emerged as a reliable alternative for accessing encrypted emails while the classic desktop client bug is being addressed. OWA utilizes different rendering and decryption flows, often server-side, which are unaffected by the desktop client’s specific regression.

Users who cannot open encrypted messages in classic Outlook can successfully access them by logging into their account via Outlook on the web. This provides immediate continuity for critical communications.

This workaround is particularly useful for end-recipients who may not have control over their Outlook client version or the ability to implement build rollbacks. It ensures that essential encrypted communications remain accessible during the period of the classic Outlook bug.

Future Outlook and the Transition to New Outlook

It is important to note that Microsoft is actively transitioning users from classic Outlook to the new Outlook experience. While classic Outlook is still supported, its end-of-life is scheduled for Q2 2029, with support ending in April 2029. This phased retirement means that while classic Outlook will continue to receive updates for critical issues like the encryption bug, its long-term future is limited.

The ongoing development and support for classic Outlook, even as it approaches its end of life, highlights the critical nature of email encryption for businesses. Microsoft’s commitment to fixing this bug underscores the importance of secure communication channels.

Users are encouraged to stay informed about Microsoft’s updates regarding this issue and to consider the transition to the new Outlook, which may offer a more streamlined and secure experience in the long run.