| Previous | Next |
| NS_E_DRM_CERTIFICATE_REVOKED | NS_E_DRM_DEVICE_LIMIT_REACHED |
NS_E_DRM_LICENSE_UNAVAILABLE
Start with the producing object
The useful reading of NS_E_DRM_LICENSE_UNAVAILABLE is narrow: no license available to the transmitter authorizes the requested WMDRM-ND action. The subsystem producing this result is WMDRM for Network Devices, not the media decoder; it performs the transmitter/receiver protocol that registers a network playback device, approves it, validates proximity, opens a protected session and transcrypts licensed content for that receiver.
The investigation becomes concrete when you query the content KID and action before transcryption starts.
Relevant runtime state
The security decision represented by this result depends on device certificate and serial number, registration-database entry, approval flag, validation timestamp, network session, protocol message and transcrypt policy. Record the exact WMDRM-ND message type, device identifier, certificate chain, registration state, round-trip timing and the first protocol HRESULT from the same it attempt.
The producing layer has not made a claim about every media operation; it has only established that no license available to the transmitter authorizes the requested WMDRM-ND action.
Practical diagnostic path
- Preserve this result and
0xC00D28A2before cleanup, fallback or another media item changes the context. - Run the direct check for it: query the content KID and action before transcryption starts.
- Compare the failure with a known-good case that changes only the property named by this condition: no license available to the transmitter authorizes the requested WMDRM-ND action.
- Apply the narrow correction for it: acquire or install a license granting network-device playback.
- Associate it with its current WMDRM for Network Devices object and the requested action.
- Repeat the same action with the same content/device identity and verify that it is not replaced by another policy or trust failure.
One-variable comparison
It should be modeled as a failed precondition, not as an arbitrary media exception. Demonstrate the precondition by choosing to query the content KID and action before transcryption starts, and remove it by choosing to acquire or install a license granting network-device playback. The result model is suitable for a regression fixture because its expected state change is observable without weakening the DRM policy.
Do not diagnose the wrong layer
The established fact is that no license available to the transmitter authorizes the requested WMDRM-ND 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.
Trace requirements
| Field | Value |
|---|---|
| Owner | operation, API/callback, object or session identifier, and component/device version associated with it |
| Direct check | query the content KID and action before transcryption starts |
| 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 |
What another code would mean
| Result | Why it points elsewhere |
|---|---|
NS_E_DRM_INVALID_CERTIFICATE | the WMDRM-ND peer certificate is malformed, corrupted or fails signature validation |
NS_E_DRM_CERTIFICATE_REVOKED | the WMDRM-ND peer certificate is explicitly revoked |
NS_E_DRM_DEVICE_LIMIT_REACHED | the transmitter has reached the number of network devices allowed by policy or implementation |
What success looks like
A matching correction is to acquire or install a license granting network-device playback. 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 delete the complete device-registration database before preserving the failing device record and certificate chain; that removes the distinction between registration, approval, validation and session failures.
- 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 10 for Network Devices — provides the normative workflow relevant to it.
- Device registration — lists the security and state transitions used to interpret it.
- Using the WMDRM-ND protocol — defines the platform objects used when diagnosing it.
- MS-DRMND protocol specification — documents the protocol or API boundary behind it.
Looking for a different code? Search another status or error code.