The Outlook failure that transforms encrypted messages into .rpmsg files after December update

If in the last few weeks you have found encrypted messages in Outlook that only show an attachment called message _ v2.rpmsg And they don't let you see the content, you're not the only one. An error introduced by a December update caused certain emails protected with the "Encrypt Only" permission option to stop opening properly in Microsoft 365's classic Outlook version, leaving recipients with an incomprehensible file instead of the text of the message.

The "Encrypt Only" protection is the most basic form of encryption that Microsoft offers within its family of secure messaging solutions: numbers the content of the mail without blocking functions such as sending, printing or copying. When the decryption process failed in the affected Outlook client, the application showed a file with .rpmsg extension - a protected message container - rather than presenting the mail in readable text. That file is the equivalent of a card within a sealed envelope, but without the key to open it in the Outlook version that had the failure. To understand what that extension is you can see a technical reference on .rpmsg in FileInfo.

Microsoft confirmed that the origin was in a concrete compilation of the Current Channel channel: version 2511 (Build 19426.20218) deployed in December. After receiving reports, the company worked on a correction that has first been published on the Beta channel and will begin to reach users of the Current Channel and the Current Channel Preview with the Build 19725.20000 during February. This phased deployment is the usual way of Microsoft to validate the solution before a mass distribution.

As the update comes to solve the problem, Microsoft offered two alternatives for those affected. The first requires changing the way the encrypted messages are sent: instead of using the encryption option from the file dialog, the senders must choose the "Encrypt" function that is available on the option tape under the Options tab. Microsoft documents how to send encrypted messages in its help center; it explains the recommended flow to ensure that the mail is accessible to the recipient, and you can consult it at the official guide.

The second alternative is more technical: to return to a version of Office that is not affected by error. This requires closing all Office applications and running a command from a system symbol with high privileges. The command that Microsoft provided strength to Click-to-Run to reverse the installation to a specific compilation that did work. The command is as follows:

"% programfiles%\\ Common Files\\ Microsoft Shared\\ ClickToRun\\ officec2rclient.exe" / update user update = 16.0.19426.20186

When running this instruction, Office will download and install the indicated version, which returns the expected behavior for encrypted messages until the official correction is reached. It is important to keep in mind that forcing a reversion of build involves interrupting recent updates and may therefore not be the ideal option in corporate environments without the supervision of the IT team.

This incident is not an isolated fact: in recent months the Outlook team has had to deal with several problems that affected the classic experience on Windows. Among them there have been failures that prevented the drag-and-drop of emails after certain Windows 11 24H2 updates, CPU usage peaks while writing messages, unexpected application closures when opening emails and related file-related errors. Sometimes Microsoft came to launch off-schedule updates to mitigate serious blockages in Outlook. To review the history of Microsoft 365 Apps versions and technical notes it is useful to consult the update documentation in Microsoft Learn.

If this failure affects you, the most prudent thing is, first, to check which channel and version of Outlook you are on and, if possible, to apply the correction when it appears on your channel. If you depend on the option to receive encrypted emails normally, ask the emitters to use the alternative encryption route from the option tape or consult with your support team to temporarily reverse the building that does not present the problem. To follow the media and technical coverage of the arrangement and how the correction is deployed, specialized means such as Bleeping Computer have collected the information and provide updates on the status of deployment: BleepingComputer.

The practical lesson for administrators and users is clear: encryption adds an indispensable layer of protection, but also depends on the correct fit between customers, servers and formats. When a piece of that gear changes - as with quick updates - unexpected incompatibilities can arise. Maintaining backup, controlled update policies in corporate environments and open communication channels with the sender and Microsoft support helps minimize interruptions while software companies deploy patches and validate solutions.

If you need help checking the Outlook version, running the temporary version or evaluating the best option for your organization, I can detail the steps and precautions to follow according to your environment (home user, professional user or corporate system management).