Office files that have RMS protection seem to crash
Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. For more information about this change, read this blog post.
When you try to open a Microsoft Office document that has Information Rights Management (IRM) protection, the document seems to crash and does not respond. This behavior occurs after you install either of the following:
2687297 Description of the Office 2010 hotfix package (Mso-x-none.msp): June 26, 2012
2553260 MS12-057: Description of the security update for Office 2010 (MSO): August 14, 2012
ImportantThis section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in WindowsTo resolve this issue, follow these steps:
Delete all files in the following folder:
Close all Office programs.
Click Start, click Run, in the Open box, type regedit, and then click OK.
Locate the following subkey and remove the CachedCorpLicenseServer value from the subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\DRM
Delete all entries under the following subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\DRM\ServiceLocations
For an automated solution, execute a batch file to update your system automatically.
Note We recommend that you back up the registry before you follow these steps:
Start Notepad, and paste the following in a new text file:
del %localAppData%\Microsoft\DRM*.* /q /f /s
reg delete hkcu\Software\Microsoft\Office\14.0\Common\DRM /v
Save the file, and change the file name extension from .txt to .bat.
Run the .bat file that you created in step 2. To do this, double-click the file to run it.
Microsoft has confirmed that this is an issue in the Microsoft products that are listed in the "Applies to" section.