What does HRESULT 0xC00D11DB (NS_E_WMP_DRM_NO_SECURE_CLOCK) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

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.%0

Previous	Next
NS_E_WMP_DRM_GENERIC_LICENSE_FAILURE	NS_E_WMP_DRM_NO_RIGHTS

NS_E_WMP_DRM_NO_SECURE_CLOCK

The state behind the HRESULT

NS_E_WMP_DRM_NO_SECURE_CLOCK belongs to the point where a device-dependent license requires trusted time but the target device has no usable secure clock state. This result runs inside Windows Media Player rights processing, where the implementation handles the Player layer that opens protected media, queries the local license state, performs silent or interactive rights acquisition, validates DRM components and applies play, burn or sync restrictions.

The shortest path to a defensible diagnosis is to query the device DRM status and secure-clock flag before starting transfer.

Build a useful incident record

The important objects are content KID and header, license-store entry, requested action, acquisition URL, user/store context, secure clock and DRM component generation. Evidence for this HRESULT should correlate the content KID, requested action, license-state query, acquisition callback sequence, server response category and the first lower-level DRM HRESULT.

The scope stays narrow: a device-dependent license requires trusted time but the target device has no usable secure clock state. Other content or actions may still be valid.

Reconstruct the decision

Reconstruct the transition from the requested action to the rejected condition. The proof step is to query the device DRM status and secure-clock flag before starting transfer; the repaired transition must then perform the supported device data/clock update while online, then re-evaluate the license. Record the first lower-layer status beside this result because wrapper HRESULTs can otherwise conceal the producing component.

State table

Field	Value
Temporal state	trusted/system time, validity interval, request sequence and retry number when they influence this result
Lower result	the earliest store, network, cryptographic, driver or provider status preceding the final it wrapper
Owner	operation, API/callback, object or session identifier, and component/device version associated with it
Direct check	query the device DRM status and secure-clock flag before starting transfer
Policy input	requested action plus the exact license, certificate, profile, output or registration property evaluated by it

Focused verification

Preserve it and 0xC00D11DB before cleanup, fallback or another media item changes the context.
Apply the narrow correction for this HRESULT: perform the supported device data/clock update while online, then re-evaluate the license.
Associate it with its current Windows Media Player rights processing object and the requested action.
Run the direct check for this HRESULT: query the device DRM status and secure-clock flag before starting transfer.
Compare the failure with a known-good case that changes only the property named by this condition: a device-dependent license requires trusted time but the target device has no usable secure clock state.
Repeat the same action with the same content/device identity and verify that it is not replaced by another policy or trust failure.

Interpretation limits

The established fact is that a device-dependent license requires trusted time but the target device has no usable secure clock state. That fact does not independently establish damaged media bytes, a missing decoder, a generally broken network, or invalid rights for every other action.

If the Player, encoder, setup program or device layer later emits a broader error, retain it as the first specific result. The object and operation attached to it are usually more diagnostic than a later cleanup or user-interface summary.

Neighboring security decisions

Result	Why it points elsewhere
`NS_E_WMP_DRM_CANNOT_RESTORE`	the Player restore service rejected another restore within its rate or policy limit
`NS_E_WMP_DRM_GENERIC_LICENSE_FAILURE`	the Player wrapper could not reduce a rights-validation failure to a more specific public result
`NS_E_WMP_DRM_NO_RIGHTS`	none of the available media usage rights authorizes the requested Player operation

Repair criterion

Repair the owner of the check: perform the supported device data/clock update while online, then re-evaluate the license. Success means that the same requested action is accepted after that precise state change, not merely that another file or device happens to work.

A broad reset is not the first step for this HRESULT; Do not reset the local DRM store before recording the content KID and license-state result; a reset can turn a precise rights or signature failure into a generic missing-license condition.
Do not alter trusted time, revocation enforcement, certificate validation or output policy merely to suppress it; that bypasses the decision instead of correcting its input.
Retain one failing artifact and one corrected artifact so the resolution of it can be regression-tested.

Acceptance condition

For the final it test, keep the content KID or file hash, requested action, user/account, device identity and output route unchanged wherever they apply.

Technical references

Windows Media DRM overview — defines the platform objects used when diagnosing it.
Acquiring licenses — documents the protocol or API boundary behind it.
Licenses and the local license store — provides the normative workflow relevant to it.
Windows Media Format SDK error codes — lists the security and state transitions used to interpret it.

Looking for a different code? Search another status or error code.