| Previous | Next |
| NS_E_WMP_DRM_LICENSE_NOTACQUIRED | NS_E_WMP_DRM_LICENSE_UNUSABLE |
NS_E_WMP_DRM_LICENSE_NOTENABLED
Failure scope
For NS_E_WMP_DRM_LICENSE_NOTENABLED, the failed contract is that the license exists but its start condition has not yet become true. 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 trusted time and any first-use/start-date condition with the current action.
Data worth retaining
The object graph behind this result includes content KID and header, license-store entry, requested action, acquisition URL, user/store context, secure clock and DRM component generation. A it trace should retain the content KID, requested action, license-state query, acquisition callback sequence, server response category and the first lower-level DRM HRESULT.
A later generic error must not replace this evidence: the original condition remains that the license exists but its start condition has not yet become true.
The transition to retest
A useful failure model for it links cause and recovery: the license exists but its start condition has not yet become true. Verify that model when you compare trusted time and any first-use/start-date condition with the current action, then make the smallest change needed to wait for the valid interval or obtain a license with an appropriate start condition. This distinction prevents a license-policy result from being hidden by a later Player dialog and keeps the test attached to the original object generation.
Verification inputs
| Field | Value |
|---|---|
| Owner | operation, API/callback, object or session identifier, and component/device version associated with this result |
| Direct check | compare trusted time and any first-use/start-date condition with the current action |
| 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 |
Different owners, similar dialog
| Result | Why it points elsewhere |
|---|---|
NS_E_WMP_DRM_LICENSE_EXPIRED | the matching Player license is outside its permitted usage interval |
NS_E_WMP_DRM_LICENSE_NOTACQUIRED | the Player completed or abandoned acquisition without installing a usable matching license |
NS_E_WMP_DRM_LICENSE_UNUSABLE | a located license cannot be applied to this content/action despite being present |
Separate cause from wrapper
The established fact is that the license exists but its start condition has not yet become true. 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.
Test without erasing evidence
- Preserve it and
0xC00D1205before cleanup, fallback or another media item changes the context. - Apply the narrow correction for it: wait for the valid interval or obtain a license with an appropriate start condition.
- Associate it with its current Windows Media Player rights processing object and the requested action.
- Run the direct check for it: compare trusted time and any first-use/start-date condition with the current action.
- Compare the failure with a known-good case that changes only the property named by this condition: the license exists but its start condition has not yet become true.
- Repeat the same action with the same content/device identity and verify that it is not replaced by another policy or trust failure.
When a retry is valid
Recovery should change the failed precondition by choosing to wait for the valid interval or obtain a license with an appropriate start condition. 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 it 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.
Final verification
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 — documents the protocol or API boundary behind it.
- Acquiring licenses — provides the normative workflow relevant to it.
- Licenses and the local license store — lists the security and state transitions used to interpret it.
- Windows Media Format SDK error codes — defines the platform objects used when diagnosing it.
Looking for a different code? Search another status or error code.