Microsoft Acknowledges Outlook Encryption Issue, Offers Temporary Workaround

If you’ve been struggling to reply to encrypted emails on Microsoft Outlook, you’re not alone. Users have reported frequent issues since the release of Current Channel Version 2402, encountering an error message that leaves them stuck. The error, stating "Microsoft Outlook was not able to create a message with restricted permission," has been a significant hindrance for many. Microsoft has acknowledged this bug but is still working on a permanent solution. Meanwhile, they’ve provided some temporary fixes to help users manage their encrypted emails.

In a recent support document, Microsoft outlined the problem and offered some advice. When you attempt to reply to an OMEv2 encrypted email from the Outlook desktop client, you might see the frustrating error message. This issue has been noted in builds starting with version 2402 (Build 17328.20142) and continues to affect users. Rather than leaving everyone in the lurch, Microsoft has suggested a couple of ways to circumvent the issue. While not a permanent solution, these workarounds can help maintain your workflow.

The first workaround is quite simple: use Outlook Web Access (OWA) or the new Outlook interface to reply to encrypted emails. These platforms do not experience the same issue and can be a quick alternative for those who need immediate access to their encrypted communications. While it might be inconvenient for users accustomed to the desktop client, OWA and the new Outlook are fully functional and free from this bug. This temporary solution keeps business moving without too much disruption.

For users who must use the desktop client and need an urgent fix, Microsoft offers a more technical workaround. By reverting to a previous, working build of Outlook, you can bypass the current issue. This involves using Command Prompt to run a couple of specific commands. First, you need to navigate to the ClickToRun directory. Then, you’ll input a command to update Outlook to an earlier version, specifically 16.0.17231.20236. This rollback should restore functionality until a more permanent fix is rolled out.

The good news is that Microsoft is actively investigating the issue and promises updates as more information becomes available. While it’s frustrating to deal with these kinds of bugs, the company’s acknowledgment and temporary solutions provide some relief. Users are encouraged to follow the company’s updates for news on a permanent resolution. In the meantime, switching to OWA or the new Outlook, or rolling back to a previous build are your best options to maintain smooth email communication.

In conclusion, it’s clear that Microsoft is aware of the problem and is working towards a permanent fix. The temporary solutions offered might not be perfect, but they do provide a way to continue working without too much disruption. If you’re facing this issue, try using OWA, the new Outlook, or rolling back to a previous version of the desktop client. Stay tuned for updates from Microsoft as they work to resolve this and provide a seamless email experience once more.