Fix DRM error 0XC00D276C on Windows 10/11

You're trying to play a protected video or music file, and Windows throws that 0XC00D276C error. It's a Digital Rights Management (DRM) hiccup that stops media playback dead. I've seen this on Windows 10 and 11, often after a Windows update or when you switch between media apps.

The main fix: Reset the DRM store and re-register the component

This is the fix that works in about 90% of cases. It clears out the corrupted DRM data and forces Windows to rebuild it fresh.

Close all media apps. That means Windows Media Player, Movies & TV, any browser tabs playing protected content, and Silverlight-based players. You don't want them locking the DRM files.
Open Command Prompt as admin. Click the Start button, type cmd, right-click Command Prompt, and pick "Run as administrator." Click Yes if User Account Control asks.
Stop the DRM service. Type this and press Enter:
```
net stop drmservice
```
You should see "The DRM service was stopped successfully." If it says it's not running, that's fine — move on.
Delete the DRM data store. Type or paste this, then press Enter:
```
del /f /s /q %windir%\ServiceProfiles\LocalService\AppData\Local\Microsoft\DRM\*.*
```
This deletes everything in that folder. It's safe — Windows rebuilds it when needed.
Delete the MSDRM folder. Some systems also have this. Run:
```
rmdir /s /q "%ProgramData%\Microsoft\Windows\DRM"
```
If it says "The system cannot find the file specified," don't worry. That just means your system doesn't have that folder.
Clear the Media Foundation cache. This is often overlooked. Run:
```
del /f /s /q %USERPROFILE%\AppData\Local\Microsoft\Media Foundation\*.dat
```
Again, if it says "file not found," it's okay.
Re-register the DRM component. Run these two commands one after another:
```
regsvr32 drm.dll
regsvr32 msdrm.dll
```
Each should pop up a message saying "DllRegisterServer in ... succeeded."
Restart the DRM service. Type:
```
net start drmservice
```
You'll see "The DRM service was started successfully."

Now close the Command Prompt and try playing your media again. The error should be gone. If it's not, reboot and try again — sometimes Windows needs a clean slate.

Why this works

The DRM component stores a machine-specific key that ties your media license to your PC. When that key gets corrupted — often from a botched Windows update, a crash while playing protected content, or installing a different media player — Windows can't create the registration object the error mentions. Deleting the DRM store removes that corrupted key. The re-registration step makes sure the DLLs that handle DRM are properly registered in Windows. Starting the service again kicks it all off fresh. It's like clearing a clogged pipe.

Less common variations of this error

If the main fix didn't do it, try these in order.

Variation 1: Silverlight-specific DRM issue

Some older streaming services still use Silverlight. If you're getting this error in a browser that supports Silverlight (Edge in IE mode, or Firefox with the plugin):

Open the Control Panel and go to Programs and Features.
Find Microsoft Silverlight, right-click it, and choose Change.
In the Silverlight setup, choose "Repair." Let it finish, then restart your browser.

This resets Silverlight's own DRM store without touching Windows Media Player's.

Variation 2: Corrupted Media Foundation pipeline

Sometimes the issue isn't DRM itself but the entire Media Foundation stack. To fix this:

Open PowerShell as admin (right-click Start, choose Windows Terminal (Admin) or PowerShell (Admin)).
Run this command to re-register all Media Foundation transforms:
```
mftrace -reinstall
```
That forces Windows to re-register every Media Foundation codec and transform. It can take a minute.

Variation 3: User profile corruption

If the error only happens under one user account, the user profile's DRM data might be messed up. Create a new user account and test there. If it works, you're looking at a profile-specific issue. Migrate your data to the new profile.

How to prevent this from coming back

Once you fix this error, you can keep it from returning with a few habits.

Don't force-close media apps. When you close Windows Media Player or a browser playing DRM content, let it finish writing to the DRM store. Hitting End Task in Task Manager while media is playing is a common cause.

Keep Windows updated. Microsoft pushes DRM-related fixes through Windows Update. I've seen cumulative updates directly address this error on Windows 10 version 21H2 and Windows 11 version 22H2.

Stick to one media player for DRM content. If you bounce between Windows Media Player, VLC with DRM plugins, and a browser, you're asking for conflicts. Pick one and use it.

Back up your DRM licenses. If you've purchased protected content (yes, some people still do), back up the DRM store folder. Copy C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\DRM to a safe place after you've licensed your files. If this error comes back later, you can restore those files instead of re-downloading everything.

That's it. You should be back to watching your protected movies and listening to your purchased music without that error code in your face.