| Previous | Next |
| NS_E_DRM_DRMV2CLT_REVOKED | NS_E_OUTPUT_PROTECTION_LEVEL_UNSUPPORTED |
NS_E_DRM_RIV_TOO_SMALL
Read the code before the dialog
The producer of 0xC00D28B7 has determined that the revocation-information version available to the client is below the minimum required by policy. NS_E_DRM_RIV_TOO_SMALL runs inside WMDRM for Network Devices, where the implementation handles 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 compare installed RIV with the requirement from the license/protocol response.
Minimum evidence set
| Field | Value |
|---|---|
| Policy input | requested action plus the exact license, certificate, profile, output or registration property evaluated by this result |
| 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 | compare installed RIV with the requirement from the license/protocol response |
Correlate the owner and the policy
It is meaningful only while the following state remains associated with one operation: device certificate and serial number, registration-database entry, approval flag, validation timestamp, network session, protocol message and transcrypt policy. Preserve the exact WMDRM-ND message type, device identifier, certificate chain, registration state, round-trip timing and the first protocol HRESULT for it.
A later generic error must not replace this evidence: the original condition remains that the revocation-information version available to the client is below the minimum required by policy.
Why the first HRESULT matters
The transition that returns it begins with compare installed RIV with the requirement from the license/protocol response. If that observation matches, the next state cannot be reached until the implementation can perform the supported security/CRL update to raise the revocation-information version. Record the first lower-layer status beside it because wrapper HRESULTs can otherwise conceal the producing component.
The final dialog can be broader
The established fact is that the revocation-information version available to the client is below the minimum required by policy. 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 controlled reproduction
- Preserve it and
0xC00D28B7before 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: compare installed RIV with the requirement from the license/protocol response.
- Compare the failure with a known-good case that changes only the property named by this condition: the revocation-information version available to the client is below the minimum required by policy.
- Apply the narrow correction for it: perform the supported security/CRL update to raise the revocation-information version.
- Repeat the same action with the same content/device identity and verify that it is not replaced by another policy or trust failure.
Contrast with related results
| Result | Why it points elsewhere |
|---|---|
NS_E_DRM_INCLUSION_LIST_REQUIRED | the requested operation requires an inclusion list that the license does not contain |
NS_E_DRM_DRMV2CLT_REVOKED | a legacy DRM v2 client component required by the operation is revoked |
NS_E_DRM_INVALID_LICENSEBLOB | the Cardea request contains a license blob that fails format, integrity or binding checks |
Recovery at the right layer
Repair the owner of the check: perform the supported security/CRL update to raise the revocation-information version. 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 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.
Re-test the original case
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.