[German]Microsoft Outlook seems to have issues with encrypted emails. Reply emails that are encrypted can then no longer be read by the recipient. The problem seems to have existed since the beginning of May 2024, as I saw in a forum post. But there is a temporary solution from Microsoft for the problems with encrypted email replies.
A forum post on MS Answers
In the Microsoft Answers forum for Outlook Classic, there has been a post Outlook Encrypted Emails issues dealing with the problem since May 8, 2024. A user writes that one of the external partners uses encryption for emails. This encrypted communication has been possible for some time without any problems with the company's internal recipients.
ABut since the beginning of May 2024, there seems to be a massive problem when encrypted emails arrive. If an employee tries to reply to such an encrypted email, the error message appears:
"Microsoft Outlook was unable to create a message with restricted permission."
The thread starter writes that the company's employees can send emails (probably encrypted) to the external partner. The problem only occurs with the classic desktop version of Microsoft Outlook, while with Outlook Web App (OWA) it is possible to reply without any problems.
So it cannot be due to missing keys. However, the attempt to correct this by creating a new profile was unsuccessful and the error persists.
A workaround from Microsoft
The colleagues at Bleeping Computer have noticed that Microsoft has suggested a temporary workaround in a reply to the post, as it is probably a bug in the official Outlook build.
- Solution 1 is to switch to the Outlook Web App (OWA) to reply.
- Solution 2 is to go back to version 2401 with Office in the Current Channel if only classic Outlook is to be used.
The rollback can be done with the following instructions
cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
officec2rclient.exe /update user updatetoversion=16.0.17231.20236The commands must be executed in an administrative command prompt. Question: Is anyone affected by this bug?
