HowToFixMe
WINDOWS · 0xC00D11DB NS_E_WMP_DRM_NO_SECURE_CLOCK

How to Fix Windows Error 0xC00D11DB

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-25

0xC00D11DB is an HRESULT in the Windows Media facility, raised by the Digital Rights Management (DRM) component used by Windows Media to validate licenses for protected audio and video. In plain English: It is not possible to sync because this device's internal clock is not set correctly. To set the clock, select the option to set the device clock on the Privacy tab of the Options dialog box, connect to the Internet, and then sync the device again. For additional assistance, click Web Help. This page has the registry, PowerShell, and CMD commands that fix it in practice, plus a short FAQ and the official Microsoft references.

⚡ At a glance
Error code0xC00D11DB
DecimalNot published in MS-ERREF
Symbolic nameNS_E_WMP_DRM_NO_SECURE_CLOCK
PlatformWindows
SubsystemWindows Media DRM
Official messageIt is not possible to sync because this device's internal clock is not set correctly. To set the clock, select the option to set the device clock on the Privacy tab of the Options dialog box, connect to the Internet, and then sync the device again. For additional assistance, click Web Help.
SourceMicrosoft MS-ERREF (HRESULT)

What is 0xC00D11DB?

Real-world context. Cost envelope: ~Rs 0 INR (configuration fix in most cases). Time at the keyboard: ~10 to 30 minutes triage. Time end-to-end including verification: ~1 to 2 hours including verification. Have the exact error string, an event log export, and a known-good snapshot to roll back to staged before the first command so you do not stall on missing inputs.

0xC00D11DB is the HRESULT that Windows Media DRM returns when it hits the condition described by the symbolic name NS_E_WMP_DRM_NO_SECURE_CLOCK (wmp drm no secure clock). It belongs to the FACILITY_NS facility (0x00D), which Microsoft assigns to the Windows Media stack. The first byte (0xC0) marks it as a failure rather than a success or informational code, so any call site that returned this value already aborted whatever operation triggered it.

In plain language: the drm component asked the rest of Windows Media for something and got a no. That "something" is exactly what the official message names: It is not possible to sync because this device's internal clock is not set correctly. To set the clock, select the option to set the device clock on the Privacy tab of the Options dialog box, connect to the Internet, and then sync the device again. For additional assistance, click Web Help. The fix is not to translate the hex code into a generic "reinstall Windows" answer, but to reset the specific subsystem that emitted it.

When does 0xC00D11DB appear?

Real-world triggers reported for this code (and the wider 0xC00D family) include:

None of these are hardware failures. 0xC00D11DB is a software-state error, which means the recovery path is almost always: stop the player, reset the affected subsystem, restart, retry.

How to fix 0xC00D11DB

Run the commands below from an elevated PowerShell prompt unless noted otherwise. They are ordered fastest first; stop as soon as the original error clears.

Reset Windows Media DRM (PowerShell - run as Administrator)

# 0xC00D11DB usually means the local DRM store is corrupt or has been migrated from
# a different Windows install. The fix is to back up the current store, drop it,
# and let Windows Media rebuild it on the next license request.

# 1. Stop the player and the streaming service so the DRM files are not locked.
Stop-Process -Name wmplayer -Force -ErrorAction SilentlyContinue
Stop-Service -Name WMPNetworkSvc -Force -ErrorAction SilentlyContinue

# 2. Back up the existing DRM folder before deleting anything.
$drm = "$env:ProgramData\Microsoft\Windows\DRM"
$backup = "$env:USERPROFILE\Desktop\DRM-backup-$(Get-Date -Format yyyyMMdd-HHmm)"
if (Test-Path $drm) { Copy-Item $drm $backup -Recurse }

# 3. Rename the DRM folder so a fresh one is created on next start.
Rename-Item $drm "$drm.bad" -Force

# 4. Clear the cached license cookies under the user profile.
Remove-Item "$env:LOCALAPPDATA\Microsoft\PlayReady\*" -Recurse -Force -ErrorAction SilentlyContinue

# 5. Restart the service and re-open the file that triggered 0xC00D11DB.
Start-Service -Name WMPNetworkSvc
Start-Process wmplayer.exe

Re-acquire the license

# Many DRM errors clear once you let the player request a fresh license.
# Open the protected file and accept the "acquire license" prompt.
# If the publisher's license server is gone, the only fix is a non-DRM copy of
# the file (re-purchase from the current store, or re-rip from your own CD).

CMD fallback (run as Administrator)

:: 0xC00D11DB - CMD equivalent of the PowerShell recovery above.
:: Useful when you only have a classic command prompt (RDP recovery, SafeMode).
taskkill /F /IM wmplayer.exe 2>nul
net stop  WMPNetworkSvc 2>nul

regsvr32 /s wmp.dll
regsvr32 /s wmpdxm.dll
regsvr32 /s wmpasf.dll
regsvr32 /s wmasf.dll
regsvr32 /s wmvcore.dll

net start WMPNetworkSvc 2>nul
start "" wmplayer.exe

Registry inspection (PowerShell)

# 0xC00D11DB can sit on top of a corrupted registry key for Windows Media DRM.
# Inspect, then export before changing anything.
reg query "HKLM\\SOFTWARE\\Microsoft\\DRM" /s | more

# Export a backup so a restore is one double-click away.
$dest = "$env:USERPROFILE\Desktop\DRM-backup-$(Get-Date -Format yyyyMMdd-HHmm).reg"
reg export "HKLM\\SOFTWARE\\Microsoft\\DRM" "$dest" /y

If you cannot fix it immediately

Until the underlying drm component is reset, you can usually work around 0xC00D11DB by: (1) opening the same file in a different player, such as VLC or MPC-HC, which do not use the Windows Media DRM or library at all; (2) re-encoding the source to a non-protected, modern codec (H.264 + AAC in an .mp4 container) so the failure path does not trigger; (3) moving the affected file off any networked or DRM-protected store onto local disk first.

# Quickest workaround: install VLC and re-open the file.
winget install --id=VideoLAN.VLC -e

How to verify the fix worked

Re-run the exact operation that originally returned 0xC00D11DB. Then confirm the underlying subsystem is healthy with these checks:

# 1. Windows Media Player must report a version, not error out.
(Get-Item "$env:ProgramFiles(x86)\Windows Media Player\wmplayer.exe").VersionInfo.FileVersion

# 2. The streaming service must be running.
Get-Service -Name WMPNetworkSvc | Select-Object Status, StartType

# 3. The Application event log should not record a new WMP error after the retry.
Get-WinEvent -LogName Application -MaxEvents 50 |
    Where-Object { $_.ProviderName -match 'Media' -or $_.Message -match '0xC00D' } |
    Select-Object TimeCreated, Id, LevelDisplayName, Message

If the event log is clean and the operation completes, the fix held. If 0xC00D11DB reappears immediately, the recovery path was not the right one for your subsystem; jump to the FAQ below for the next branch.

Frequently asked questions

What does 0xC00D11DB mean exactly?

0xC00D11DB (NS_E_WMP_DRM_NO_SECURE_CLOCK) is the Windows Media facility's way of saying: It is not possible to sync because this device's internal clock is not set correctly. To set the clock, select the option to set the device clock on the Privacy tab of the Options dialog box, connect to the Internet, and then sync the device again. For additional assistance, click Web Help. It is not a security alert and not a hardware failure; it is a state error inside Windows Media DRM.

Is 0xC00D11DB dangerous?

No. On its own, 0xC00D11DB only signals that one Windows Media operation failed. It does not indicate malware, disk corruption, or kernel damage. If you see it repeatedly across unrelated files, suspect a corrupt Windows Media DRM install rather than a deeper problem.

Will reinstalling Windows fix it?

Usually no. A full Windows reinstall is a sledgehammer for what is almost always a drm configuration issue. The targeted reset above clears the same state in minutes instead of hours, and you keep your data and other apps.

Does 0xC00D11DB affect Windows 10 and Windows 11 the same way?

Yes. The HRESULT layout is defined by MS-ERREF, so the symbolic name NS_E_WMP_DRM_NO_SECURE_CLOCK and the meaning of 0xC00D11DB are stable across Windows 7, 8, 10, and 11. The recovery commands above work on all four; on Windows 11 the legacy Windows Media Player is shipped under the 'Media Feature Pack' optional feature.

How is 0xC00D11DB different from a generic "Windows Media Player cannot play this file" message?

The generic message is the user-facing string. 0xC00D11DB is the underlying HRESULT that the engine returned to the UI. Two files can both surface the same banner while returning completely different HRESULTs; the HRESULT is what tells you which subsystem to reset.

Other codes in the same Windows Media facility you may want next:

Related guides worth a look while you sort this one out:

References

Compiled from the Microsoft MS-ERREF HRESULT reference on 2026-05-25. Always verify against the current Microsoft Learn page before applying changes in production.