| Previous | Next |
| NS_E_WMP_DRM_LICENSE_UNUSABLE | NS_E_WMP_DRM_LICENSE_NOSAP |
NS_E_WMP_DRM_LICENSE_CONTENT_REVOKED
Start with the producing object
The useful reading of NS_E_WMP_DRM_LICENSE_CONTENT_REVOKED is narrow: the issuer has revoked authorization for the protected content or license. The subsystem producing this result is Windows Media Player rights processing, not the media decoder; it performs 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 preserve the revocation result and content identity; do not interpret it as local-store damage.
Relevant runtime state
A complete incident ties together content KID and header, license-store entry, requested action, acquisition URL, user/store context, secure clock and DRM component generation; the minimum correlation set for this HRESULT is 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: the issuer has revoked authorization for the protected content or license. Other content or actions may still be valid.
One-variable comparison
A useful failure model for this HRESULT links cause and recovery: the issuer has revoked authorization for the protected content or license. Verify that model when you preserve the revocation result and content identity; do not interpret it as local-store damage, then make the smallest change needed to obtain a replacement version or new rights only through the content provider. Record the first lower-layer status beside this result because wrapper HRESULTs can otherwise conceal the producing component.
Trace requirements
| Field | Value |
|---|---|
| Policy input | requested action plus the exact license, certificate, profile, output or registration property evaluated by this result |
| Temporal state | trusted/system time, validity interval, request sequence and retry number when they influence it |
| 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 | preserve the revocation result and content identity; do not interpret it as local-store damage |
What another code would mean
| Result | Why it points elsewhere |
|---|---|
NS_E_WMP_DRM_LICENSE_NOTENABLED | the license exists but its start condition has not yet become true |
NS_E_WMP_DRM_LICENSE_UNUSABLE | a located license cannot be applied to this content/action despite being present |
NS_E_WMP_DRM_LICENSE_NOSAP | the Player environment cannot provide the Secure Audio Path required by the license |
Do not diagnose the wrong layer
The established fact is that the issuer has revoked authorization for the protected content or license. 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.
Practical diagnostic path
- Preserve it and
0xC00D1207before cleanup, fallback or another media item changes the context. - Associate it with its current Windows Media Player rights processing object and the requested action.
- Run the direct check for this HRESULT: preserve the revocation result and content identity; do not interpret it as local-store damage.
- Compare the failure with a known-good case that changes only the property named by this condition: the issuer has revoked authorization for the protected content or license.
- Apply the narrow correction for this HRESULT: obtain a replacement version or new rights only through the content provider.
- Repeat the same action with the same content/device identity and verify that it is not replaced by another policy or trust failure.
What success looks like
The appropriate operational response is to obtain a replacement version or new rights only through the content provider. Success means that the same requested action is accepted after that precise state change, not merely that another file or device happens to work.
- While investigating it, keep this restriction: 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.
Regression check
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 — provides the normative workflow relevant to it.
- Acquiring licenses — lists the security and state transitions used to interpret it.
- Licenses and the local license store — defines the platform objects used when diagnosing it.
- Windows Media Format SDK error codes — documents the protocol or API boundary behind it.
Looking for a different code? Search another status or error code.