NS_E_DRM_UNABLE_TO_CREATE_INMEMORYSTORE_OBJECT (0XC00D2784) Fix

1. Corrupt DRM data store — reset it

What's actually happening here is your Windows DRM system has a file that's broken. When you play protected content (like a purchased video or an old WMA file), the DRM component tries to build an in-memory object from that file. If the file is corrupt, it throws 0XC00D2784. This shows up most often in Windows Media Player or any app that uses the old DRM APIs.

The real fix is to delete the DRM data store and let Windows rebuild it. Don't worry — this won't break your system, it'll just regenerate a clean version next time you need DRM.

1. Close all programs that might use DRM — browsers, media players, anything.
2. Open File Explorer and type %USERPROFILE%\AppData\Local\Microsoft\DRM into the address bar. Hit Enter.
3. You'll see a folder with a few files. Delete everything inside. You might get a permission error on some files — that's fine, delete what you can.
4. Reboot your PC. This clears any cached DRM objects.
5. Try playing the protected content again. Windows will recreate the DRM store from scratch.

The reason step 3 works is the DRM service reads from that folder each time. If the files are gone, it builds fresh ones from the license data. No more corruption.

2. Missing permissions on DRM folder

Another common cause: your user account doesn't have full control over the DRM folder. This happens after a big Windows update (like 22H2) or if you migrated a profile. The DRM service can't write to the folder, so the memory object creation fails.

Here's how to check and fix:

1. Go to %USERPROFILE%\AppData\Local\Microsoft\DRM again.
2. Right-click the DRM folder, go to Properties → Security tab.
3. Click Advanced. Look at the owner — it should be your username. If it's SYSTEM or something else, click Change and type your username, then click Check Names and OK.
4. In the Permissions list, make sure your user has Full control. If not, click Add, type your username, set Full control, and save.
5. Check the box Replace all child object permissions and click OK.
6. Restart your PC and test.

Skip this step if you already deleted the folder contents — permissions won't matter if the folder is empty. Only do this if the folder still has files but you can't delete them.

3. Windows Media Player DRM reset

If the above didn't work, the problem might be in the WMP-specific DRM cache. WMP has its own copy of DRM data, separate from the system store. This error can pop up when that cache is stale.

Try this:

1. Close WMP completely.
2. Open Command Prompt as administrator (right-click Start → Command Prompt (Admin)).
3. Run: net stop drmsvc (stops the DRM service).
4. Then: del /s /q "%USERPROFILE%\AppData\Local\Microsoft\Media Player\*" (deletes WMP's cache).
5. Run: net start drmsvc (restarts the service).
6. Open WMP, try the file again.

The reason step 4 is key: WMP stores temporary DRM objects inside its own folder. Deleting those forces WMP to request fresh licenses from the server. If your original file is properly licensed, this fixes it.

Quick-reference summary