0XC00D2735

Fix DRM Error 0XC00D2735: Can't Create Backup Object

Windows Errors Intermediate 👁 7 views 📅 Jun 17, 2026

This DRM error stops you from backing up or restoring media licenses. It's usually Windows Media Player settings, corrupted data, or permissions.

1. Corrupted DRM Data Store (Most Common Fix)

The number one reason you see this error is a corrupted DRM data store. Windows Media Player (WMP) stores your license info in a folder called C:\ProgramData\Microsoft\Windows\DRM. If a file in there gets mangled—say from a power failure, a crash, or an interrupted backup—you can't create a backup object.

Here's the fix. It's safe, and you won't lose your media files.

  1. Close Windows Media Player completely. Check Task Manager if you're unsure.
  2. Open File Explorer and type %PROGRAMDATA%\Microsoft\Windows\DRM into the address bar. Hit Enter.
  3. You'll see a folder full of files. Look for a subfolder called DRMStore. Right-click it and rename it to DRMStore_old.
  4. Now open WMP again. It will create a fresh DRM store automatically.
  5. Try the backup again. Go to Tools > Manage Licenses (or search for “Back up licenses” in Start). Click Back Up Now.

What you should see: After renaming the folder, WMP should start clean. The backup should complete without the error. If you get a different error, check step 2.

2. Permission Issues on the DRM Folder

If the first fix didn't work, the DRM folder itself might have wrong permissions. This happens after a Windows update or if you migrated from an older PC. WMP needs full control of that folder to write backup objects.

  1. Open File Explorer again. Browse to %PROGRAMDATA%\Microsoft\Windows\DRM.
  2. Right-click the DRM folder (not the store subfolder) and select Properties.
  3. Go to the Security tab.
  4. Click Advanced. In the new window, look at the owner. If it's not SYSTEM or Administrators, click Change next to the owner name.
  5. Type SYSTEM in the box and click Check Names. It will underline it. Click OK.
  6. Back in Advanced Security, check the box that says Replace owner on subcontainers and objects.
  7. Click Apply, then OK.
  8. Still in Properties > Security, select Users (your account). Under Permissions for Users, make sure Full control is checked. If not, check it and click Apply.
  9. Close everything, restart WMP, and try the backup again.

Real-world trigger: This happens a lot after upgrading from Windows 7 to Windows 10 or 11. The old DRM data retains permissions from the previous OS version, and the new WMP can't write to it.

3. Windows Media Player Configuration Reset

Sometimes it's not the data or permissions—it's WMP's own configuration. It might be stuck in a bad state. The fix is to reset WMP completely.

  1. Close WMP.
  2. Press Win + R, type regedit, and hit Enter.
  3. Go to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer.
  4. Right-click the MediaPlayer key and select Export to back it up somewhere safe (in case you need to undo this).
  5. Delete the MediaPlayer key. Yes, delete it. Don't worry—WMP rebuilds it on next launch.
  6. Close Registry Editor.
  7. Open WMP. It will act like it's the first time running—you'll see the setup wizard. Let it finish.
  8. Now try the backup again.

Important: Deleting this registry key will remove your WMP library settings (play count, ratings, saved playlists). Your actual media files are untouched. If you need those settings, use the export you made earlier.

Quick-Reference Summary Table

CauseSignsFix Steps
Corrupted DRM storeError on backup; DRM folder exists but has junk filesRename DRMStore to DRMStore_old; let WMP rebuild it
Permission problemError on backup; Access Denied in logsSet owner to SYSTEM; grant Users full control on DRM folder
WMP config corruptionError persists after first two fixes; WMP acts glitchyDelete MediaPlayer registry key; re-run setup wizard

One last thing—if you're backing up to a network drive or external USB, make sure that drive has write permissions for your user account. WMP doesn't always give a clear error when the target drive is the problem. Run the backup to your local desktop first to rule that out.

Was this solution helpful?