What does HRESULT 0xC00D28B6 (NS_E_DRM_DRMV2CLT_REVOKED) mean?

 
Previous Next
NS_E_DRM_INCLUSION_LIST_REQUIRED NS_E_DRM_RIV_TOO_SMALL

NS_E_DRM_DRMV2CLT_REVOKED

The first reliable fact

The condition encoded by 0xC00D28B6 is not generic playback failure; it is that a legacy DRM v2 client component required by the operation is revoked. For NS_E_DRM_DRMV2CLT_REVOKED, the owner is WMDRM for Network Devices; its working contract covers 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.

Start by recording component identity/version and revocation-list entry.

Incident data

FieldValue
Owneroperation, API/callback, object or session identifier, and component/device version associated with this result
Direct checkrecord component identity/version and revocation-list entry
Policy inputrequested action plus the exact license, certificate, profile, output or registration property evaluated by this result
Temporal statetrusted/system time, validity interval, request sequence and retry number when they influence this result

The transaction to reconstruct

The security decision represented by it 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 attempt.

This evidence matters because the rejected condition is specifically that a legacy DRM v2 client component required by the operation is revoked.

A controlled before/after test

A useful failure model links cause and recovery: a legacy DRM v2 client component required by the operation is revoked. Verify that model when you record component identity/version and revocation-list entry, then make the smallest change needed to update to a non-revoked supported DRM client component. Keeping the result transition intact also shows whether a retry reused stale state or actually reevaluated the corrected input.

What the result does not prove

A legacy DRM v2 client component required by the operation is revoked.

Reproduce at the owning layer

  1. Preserve it and 0xC00D28B6 before cleanup, fallback or another media item changes the context.
  2. Compare the failure with a known-good case that changes only the property named by this condition: a legacy DRM v2 client component required by the operation is revoked.
  3. Apply the targeted fix: update to a non-revoked supported DRM client component.
  4. Associate it with its current WMDRM for Network Devices object and the requested action.
  5. Run the direct check: record component identity/version and revocation-list entry.

Do not merge these failures

ResultWhy it points elsewhere
NS_E_DRM_INVALID_LICENSEBLOBthe Cardea request contains a license blob that fails format, integrity or binding checks
NS_E_DRM_INCLUSION_LIST_REQUIREDthe requested operation requires an inclusion list that the license does not contain
NS_E_DRM_RIV_TOO_SMALLthe revocation-information version available to the client is below the minimum required by policy

Restore the required state

A matching correction is to update to a non-revoked supported DRM client component.

  • Preserve the evidence before making changes.

Technical references


Looking for a different code? Search another status or error code.