| Previous | Next |
| NS_E_WMP_DRM_UNABLE_TO_ACQUIRE_LICENSE | NS_E_WMP_PROTECTED_CONTENT |
NS_E_WMP_LICENSE_REQUIRED
Start with the producing object
The useful reading of NS_E_WMP_LICENSE_REQUIRED is narrow: the Player found no media usage rights for the requested play, burn or sync action. 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.
A decisive test is to record the content KID, requested action and whether silent acquisition was attempted.
Practical diagnostic path
- Preserve this result and
0xC00D120Abefore cleanup, fallback or another media item changes the context. - Compare the failure with a known-good case that changes only the property named by this condition: the Player found no media usage rights for the requested play, burn or sync action.
- Apply the narrow correction for this HRESULT: sign in to the issuing service and acquire rights for that action.
- Associate this result with its current Windows Media Player rights processing object and the requested action.
- Run the direct check for this HRESULT: record the content KID, requested action and whether silent acquisition was attempted.
- 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
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.
That observation distinguishes it from file corruption because the Player found no media usage rights for the requested play, burn or sync action.
One-variable comparison
It should be modeled as a failed precondition, not as an arbitrary media exception. Demonstrate the precondition by choosing to record the content KID, requested action and whether silent acquisition was attempted, and remove it by choosing to sign in to the issuing service and acquire rights for that action. Keeping the result transition intact also shows whether a retry reused stale state or actually reevaluated the corrected input.
Trace requirements
| Field | Value |
|---|---|
| Policy input | requested action plus the exact license, certificate, profile, output or registration property evaluated by it |
| 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 | record the content KID, requested action and whether silent acquisition was attempted |
What another code would mean
| Result | Why it points elsewhere |
|---|---|
NS_E_WMP_DRM_LICENSE_NOSAP | the Player environment cannot provide the Secure Audio Path required by the license |
NS_E_WMP_DRM_UNABLE_TO_ACQUIRE_LICENSE | the Player could not complete the license-acquisition transaction at this time |
NS_E_WMP_UDRM_NOUSERLIST | user-scoped DRM cannot verify the activated-user list associated with this computer |
Do not diagnose the wrong layer
The established fact is that the Player found no media usage rights for the requested play, burn or sync action. 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 appropriate operational response is to sign in to the issuing service and acquire rights for that action. 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.