0XC00D2793

Fix NS_E_DRM_MIGRATION_INVALID_LEGACYV2_SST_PASSWORD (0XC00D2793)

Windows Errors Intermediate 👁 1 views 📅 May 27, 2026

This error hits when migrating old Windows Media DRM files. The password you're using doesn't match the one stored in the legacy V2 Secure Storage file. Here's how to fix it.

Getting hit with error 0XC00D2793 when trying to move your old Windows Media DRM licenses? It's frustrating — especially when you know you typed the password right. Let me walk you through the fix that actually works.

The Short Fix: Run the DRM Migration Tool with the Correct Password

The root cause is simple: the password you're using for the DRM migration doesn't match what was stored in the Legacy V2 Secure Storage (SST) file. Maybe you changed it years ago and forgot. Or maybe you're entering it with Caps Lock on. Either way, here's how to fix it.

  1. Close Windows Media Player and any other app that uses DRM content.
  2. Press Windows Key + R, type cmd, and hit Enter to open Command Prompt.
  3. Navigate to the Windows Media Player folder. The exact path depends on your OS version:
    • Windows 10/11 64-bit: cd C:\Program Files\Windows Media Player
    • Windows 10/11 32-bit: cd C:\Program Files (x86)\Windows Media Player
  4. Run this command:
    DRMv2mig.exe -source "C:\Users\YourUsername\Documents\My Music\DRM" -destination "C:\Users\YourUsername\Documents\My Music\DRM_Migrated" -password YourOldPassword
    Replace YourUsername with your actual Windows username, adjust the source folder path to where your old DRM files are, and replace YourOldPassword with the exact password you used when first setting up DRM on that old PC.
  5. After running it, you should see "Migration completed successfully" with no errors. If you still get 0XC00D2793, move to the next section.

Why This Error Happens

The Legacy V2 SST file stores your DRM licenses in an encrypted format. That encryption uses a password — one you picked when you first used Windows Media Player to buy or rent content. If you've changed Windows passwords, reinstalled the OS, or moved the SST file from another computer, the password stored inside that file won't match what you're typing now.

The DRM migration tool (DRMv2mig.exe) decrypts the old SST file using the password you provide. If the decryption fails, you get this error. It's not a bug — it's a password mismatch.

Less Common Variations of This Error

Password Reset from a Backup

If you copied your DRM files from an old backup but can't remember the original password, you're stuck — unless you have the user profile that created it. The password is tied to the user account, not the file. If you still have access to that old user account (even on a different PC), log into it, open Windows Media Player, and go to Tools > Options > Privacy > DRM to see if the password is saved there.

Corrupted SST File

Sometimes the file itself is damaged. If you get this error with what you're 100% sure is the right password, the SST file might be corrupted. In that case, you'll need to re-acquire the licenses. That means re-downloading the media from the store you bought it from — which isn't always possible for older content.

Wrong File Version

The error can also pop up if you're trying to import a Legacy V2 SST file into a newer DRM system that expects V3 format. Check the file extension: V2 SST files end in .sst. If you renamed one or mixed versions, rename it back.

How to Prevent This Error in the Future

Prevention here is tricky because Microsoft deprecated Windows Media DRM years ago. But if you still have content that uses it:

  • Write down the DRM password when you first set it up. Store it in a password manager.
  • Back up the entire DRM folder — not just the SST file — from C:\Users\YourUsername\AppData\Local\Microsoft\DRM.
  • Migrate licenses before reinstalling Windows. Run DRMv2mig.exe while your old OS still works, so you can test the password immediately.

If you've exhausted all options and still can't migrate, your only choice is to strip the DRM from your files using third-party tools (where legal) or accept the loss. That's the harsh reality of old DRM systems.

Was this solution helpful?