| Previous | Next |
| NS_E_DRM_UNSUPPORTED_PROTOCOL_VERSION | NS_E_DRM_CERTIFICATE_SECURITY_LEVEL_INADEQUATE |
NS_E_DRM_UNSUPPORTED_ACTION
Locate the failing contract
NS_E_DRM_UNSUPPORTED_ACTION is the result to preserve when the WMDRM-ND endpoint or policy does not implement the requested operation. Within WMDRM for Network Devices, this result is raised while processing 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.
A decisive test is to record action identifier and endpoint capability/policy structures.
One-attempt evidence
| Field | Value |
|---|---|
| Temporal state | trusted/system time, validity interval, request sequence and retry number when they influence this result |
| Lower result | the earliest store, network, cryptographic, driver or provider status preceding the final this result wrapper |
| Owner | operation, API/callback, object or session identifier, and component/device version associated with it |
| Direct check | record action identifier and endpoint capability/policy structures |
| Policy input | requested action plus the exact license, certificate, profile, output or registration property evaluated by it |
Evidence from one operation
Do not separate it from its owning state: device certificate and serial number, registration-database entry, approval flag, validation timestamp, network session, protocol message and transcrypt policy. The diagnostic record for it is the exact WMDRM-ND message type, device identifier, certificate chain, registration state, round-trip timing and the first protocol HRESULT.
This evidence matters because the rejected condition is specifically that the WMDRM-ND endpoint or policy does not implement the requested operation.
Model the rejected precondition
The transition that returns it begins with record action identifier and endpoint capability/policy structures. If that observation matches, the next state cannot be reached until the implementation can select a supported action or a receiver implementing the required one. 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.
Avoid a false conclusion
The established fact is that the WMDRM-ND endpoint or policy does not implement the requested operation. 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.
A defensible test
- Preserve it and
0xC00D28ADbefore cleanup, fallback or another media item changes the context. - Associate it with its current WMDRM for Network Devices object and the requested action.
- Run the direct check for it: record action identifier and endpoint capability/policy structures.
- Compare the failure with a known-good case that changes only the property named by this condition: the WMDRM-ND endpoint or policy does not implement the requested operation.
- Apply the narrow correction for it: select a supported action or a receiver implementing the required one.
- Repeat the same action with the same content/device identity and verify that it is not replaced by another policy or trust failure.
Other boundaries in the same family
| Result | Why it points elsewhere |
|---|---|
NS_E_DRM_DEVICE_ALREADY_REGISTERED | registration attempts to create a duplicate record for the same device identity |
NS_E_DRM_UNSUPPORTED_PROTOCOL_VERSION | the transmitter and receiver do not share a supported WMDRM-ND protocol version |
NS_E_DRM_CERTIFICATE_SECURITY_LEVEL_INADEQUATE | the peer certificate is valid but its security level is below the operation’s minimum |
Resolution test
Repair the owner of the check: select a supported action or a receiver implementing the required one. 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 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.
Verify without changing the question
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 — defines the platform objects used when diagnosing it.
- Device registration — documents the protocol or API boundary behind it.
- Using the WMDRM-ND protocol — provides the normative workflow relevant to it.
- MS-DRMND protocol specification — lists the security and state transitions used to interpret it.
Looking for a different code? Search another status or error code.