| Previous | Next |
| NS_E_UNCOMPRESSED_DIGITAL_VIDEO_PROTECTION_LEVEL_UNSUPPORTED | NS_E_COMPRESSED_DIGITAL_AUDIO_PROTECTION_LEVEL_UNSUPPORTED |
NS_E_ANALOG_VIDEO_PROTECTION_LEVEL_UNSUPPORTED
Failure scope
For NS_E_ANALOG_VIDEO_PROTECTION_LEVEL_UNSUPPORTED, the failed contract is that the analog video output cannot apply the policy required by the license. Within Windows Media DRM output protection, this result is raised while processing license-policy evaluation that compares the content owner’s required output protection level or scheme with the active audio/video output path.
Before changing the machine, record analog connector type and available analog protection mechanism.
Data worth retaining
This result is meaningful only while the following state remains associated with one operation: license OPL fields, play or copy action, output connector type, compressed/uncompressed state, driver-reported protection capability and selected rendering path. Preserve the requested action, required OPL values, active connector, negotiated protection mechanism and whether the stream is compressed at that boundary for it.
A later generic error must not replace this evidence: the original condition remains that the analog video output cannot apply the policy required by the license.
The transition to retest
When documenting this result, state the rejected input and the expected successor state. The rejected input is demonstrated when you record analog connector type and available analog protection mechanism; the successor becomes reachable after you disable that output or use a permitted protected digital path. Record the first lower-layer status beside it because wrapper HRESULTs can otherwise conceal the producing component.
Verification inputs
| Field | Value |
|---|---|
| Direct check | record analog connector type and available analog protection mechanism |
| 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 |
Test without erasing evidence
- Preserve it and
0xC00D2907before cleanup, fallback or another media item changes the context. - Run the direct check for it: record analog connector type and available analog protection mechanism.
- Compare the failure with a known-good case that changes only the property named by this condition: the analog video output cannot apply the policy required by the license.
- Apply the narrow correction for it: disable that output or use a permitted protected digital path.
- Associate it with its current Windows Media DRM output protection 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.
Separate cause from wrapper
The established fact is that the analog video output cannot apply the policy required by the license. 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.
Different owners, similar dialog
| Result | Why it points elsewhere |
|---|---|
NS_E_COMPRESSED_DIGITAL_VIDEO_PROTECTION_LEVEL_UNSUPPORTED | compressed digital video leaves through a path below the required protection level |
NS_E_UNCOMPRESSED_DIGITAL_VIDEO_PROTECTION_LEVEL_UNSUPPORTED | the uncompressed video rendering path cannot enforce the license’s minimum protection |
NS_E_COMPRESSED_DIGITAL_AUDIO_PROTECTION_LEVEL_UNSUPPORTED | compressed digital audio output lacks the protection level demanded by the license |
When a retry is valid
Recovery should change the failed precondition by choosing to disable that output or use a permitted protected digital path. Success means that the same requested action is accepted after that precise state change, not merely that another file or device happens to work.
- A broad reset is not the first step for it; Do not treat every output-protection result as a missing codec; the decoder can be present while the connector or driver cannot enforce the license policy.
- 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
- Output protection levels — documents the protocol or API boundary behind it.
- Working with output protection levels — provides the normative workflow relevant to it.
- WMDRM output-protection structures — lists the security and state transitions used to interpret it.
- DRM actions and rights — defines the platform objects used when diagnosing it.
Looking for a different code? Search another status or error code.