| Previous | Next |
| NS_E_WMP_DRM_LICENSE_NOTENABLED | NS_E_WMP_DRM_LICENSE_CONTENT_REVOKED |
NS_E_WMP_DRM_LICENSE_UNUSABLE
Start with the producing object
The useful reading of NS_E_WMP_DRM_LICENSE_UNUSABLE is narrow: a located license cannot be applied to this content/action despite being present. Within Windows Media Player rights processing, this result is raised while processing 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.
Before changing the machine, compare KID, machine binding, rights, security requirements and revocation state.
Practical diagnostic path
- Preserve this result and
0xC00D1206before cleanup, fallback or another media item changes the context. - Apply the narrow correction for this HRESULT: replace the unusable license with one issued for this content and environment.
- Associate this result with its current Windows Media Player rights processing object and the requested action.
- Run the direct check for this HRESULT: compare KID, machine binding, rights, security requirements and revocation state.
- Compare the failure with a known-good case that changes only the property named by this condition: a located license cannot be applied to this content/action despite being present.
- Repeat the same action with the same content/device identity and verify that it is not replaced by another policy or trust failure.
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.
This evidence matters because the rejected condition is specifically that a located license cannot be applied to this content/action despite being present.
One-variable comparison
It should be modeled as a failed precondition, not as an arbitrary media exception. Demonstrate the precondition by choosing to compare KID, machine binding, rights, security requirements and revocation state, and remove it by choosing to replace the unusable license with one issued for this content and environment. The result comparison should preserve content and device identity so success cannot be attributed to testing a different asset.
Trace requirements
| Field | Value |
|---|---|
| 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 | compare KID, machine binding, rights, security requirements and revocation state |
| Policy input | requested action plus the exact license, certificate, profile, output or registration property evaluated by it |
What another code would mean
| Result | Why it points elsewhere |
|---|---|
NS_E_WMP_DRM_LICENSE_NOTACQUIRED | the Player completed or abandoned acquisition without installing a usable matching license |
NS_E_WMP_DRM_LICENSE_NOTENABLED | the license exists but its start condition has not yet become true |
NS_E_WMP_DRM_LICENSE_CONTENT_REVOKED | the issuer has revoked authorization for the protected content or license |
Do not diagnose the wrong layer
The established fact is that a located license cannot be applied to this content/action despite being present. 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.
What success looks like
The next attempt becomes meaningful only after you replace the unusable license with one issued for this content and environment. Success means that the same requested action is accepted after that precise state change, not merely that another file or device happens to work.
- Evidence for this HRESULT is easy to destroy; 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.