| Previous | Next |
| NS_E_DRM_UNABLE_TO_VERIFY_PROXIMITY | NS_E_DRM_MUST_APPROVE |
NS_E_DRM_MUST_REGISTER
Interpret the security decision
At 0xC00D28A5, NS_E_DRM_MUST_REGISTER records that the receiver has no valid entry in the transmitter registration database. This result 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.
To prove this boundary rather than infer it from a dialog, look up the certificate and serial-number pair in the registration database.
Do not lose object identity
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 attempt.
The comparison is useful only if it preserves the fact that the receiver has no valid entry in the transmitter registration database.
From HRESULT to cause
- Preserve this result and
0xC00D28A5before 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: look up the certificate and serial-number pair in the registration database.
- Compare the failure with a known-good case that changes only the property named by this condition: the receiver has no valid entry in the transmitter registration database.
- Apply the targeted fix: process the registration request and create the device record.
How the operation should advance
When documenting it, state the rejected input and the expected successor state. The rejected input is demonstrated when you look up the certificate and serial-number pair in the registration database; the successor becomes reachable after you process the registration request and create the device record. This distinction prevents a license-policy result from being hidden by a later Player dialog and keeps the test attached to the original object instance.
Keep the scope narrow
The receiver has no valid entry in the transmitter registration database.
Values to compare
| Field | Value |
|---|---|
| Direct check | look up the certificate and serial-number pair in the registration database |
Distinguish from nearby results
| Result | Why it points elsewhere |
|---|---|
NS_E_DRM_DEVICE_LIMIT_REACHED | the transmitter has reached the number of network devices allowed by policy or implementation |
NS_E_DRM_UNABLE_TO_VERIFY_PROXIMITY | the timed proximity exchange did not prove that the receiver is sufficiently near the transmitter |
NS_E_DRM_MUST_APPROVE | the receiver is registered but lacks the user approval required before content transfer |
Fix and verify
Recovery should change the failed precondition by choosing to process the registration request and create the device record.
- Preserve the evidence before making changes.
Technical references
Looking for a different code? Search another status or error code.
