0XC00D2773

NS_E_DRM_UNABLE_TO_GET_SECURE_CLOCK (0XC00D2773): What It Means and How to Fix It

Windows Errors Intermediate 👁 2 views 📅 May 28, 2026

This error pops up when Windows Media Player or a DRM app can't sync the device's secure clock, often after a fresh install or system reset.

When This Error Hits

You're playing a protected media file—maybe a purchased movie or a subscription download—through Windows Media Player (WMP) or a PlayReady-based app on Windows 10 or 11. Suddenly, playback stops and you get: NS_E_DRM_UNABLE_TO_GET_SECURE_CLOCK (0XC00D2773). The message reads: "A problem has occurred in obtaining the device's secure clock."

This usually happens right after a fresh OS install, a system restore, or when you move your hard drive to a different machine. Sometimes it shows up after a major Windows update. The core issue: your system's DRM subsystem lost its trusted time reference.

Why It Happens

Windows Media Player and other PlayReady-based apps rely on a secure clock—a cryptographic counter inside a special folder called %PROGRAMDATA%\Microsoft\PlayReady. This clock is tied to your hardware's unique signature. When you reinstall Windows or change hardware, the existing secure clock data becomes invalid. The DRM server refuses to hand out licenses because it can't verify your device's clock hasn't been tampered with.

What's actually happening here is the secure clock counter is stale or missing. The 0XC00D2773 code means the client failed to fetch a fresh secure clock from Microsoft's licensing servers. It's not a network problem—it's an identity crisis. Your PC forgot how to prove its clock is real.

The Fix

Skip the generic advice about reinstalling WMP or running sfc /scannow. That won't touch the PlayReady folder. You need to reset the secure clock data manually. Here's how:

Step 1: Stop the Windows Media Player Network Sharing Service

Open an elevated Command Prompt (run as administrator). Type:

net stop WMPNetworkSvc

Press Enter. This stops the service that might be locking PlayReady files.

Step 2: Delete the PlayReady Folder

In the same Command Prompt, run:

rmdir /s /q "%PROGRAMDATA%\Microsoft\PlayReady"

This removes the entire secure clock cache and license store. Don't worry—Windows will recreate a fresh folder next time you play DRM content. The reason step 3 works is that playback triggers a new clock sync from Microsoft's servers.

Step 3: Restart the Service and Reboot

Run:

net start WMPNetworkSvc

Then restart your computer. After the reboot, open the DRM-protected file again. WMP will attempt to sync its secure clock from scratch. This time it should succeed because there's no stale clock data to confuse the handshake.

Step 4: If It Still Fails—Check Date and Time

Make sure your system clock is synced to internet time. Go to Settings > Time & Language > Date & time. Turn on "Set time automatically" and "Set time zone automatically." Then manually sync:

w32tm /resync

A skewed system clock can cause the DRM server to reject the handshake even after a fresh sync.

Step 5: Reinstall the DRM Component (Advanced)

If the error persists, you might have a corrupted PlayReady runtime. Download the Windows Media Player DRM reset tool (drmreset.exe). Run it as administrator, then reboot. This tool wipes all DRM data, including the secure clock, and triggers a full reinitialization. I've only needed this once in five years of fixing this error.

What to Check If It Still Fails

If none of the above works, you're looking at a hardware change issue. Secure clock data is tied to CPU and motherboard IDs. If you replaced either, the DRM server sees a new machine. Microsoft's licensing servers may need to be contacted manually. Run slui 4 to reactivate Windows online—this sometimes refreshes the hardware binding. Also check if your firewall or proxy blocks licensing.mp.microsoft.com and playready.microsoft.com—those are the servers WMP talks to for clock sync.

In rare cases, a third-party antivirus like Avast or Norton interferes with PlayReady's ability to write to %PROGRAMDATA%. Temporarily disable real-time protection and retry step 2. If that fixes it, add an exclusion for the %PROGRAMDATA%\Microsoft\PlayReady folder.

One last thing: don't bother with the "Repair Windows Media Player" option in Programs and Features. It doesn't touch the secure clock. The empty folder trick is the real fix.

Was this solution helpful?