| Previous | Next |
| NS_E_DRM_MUST_REGISTER | NS_E_DRM_MUST_REVALIDATE |
NS_E_DRM_MUST_APPROVE
Failure scope
For NS_E_DRM_MUST_APPROVE, the failed contract is that the receiver is registered but lacks the user approval required before content transfer. This result comes from WMDRM for Network Devices, whose state machine implements 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.
The investigation becomes concrete when you read the approval flag independently of registration and validation state.
Verification inputs
| Field | Value |
|---|---|
| Direct check | read the approval flag independently of registration and validation state |
| 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 |
Data worth retaining
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.
A later generic error must not replace this evidence: the original condition remains that the receiver is registered but lacks the user approval required before content transfer.
The transition to retest
It should be modeled as a failed precondition, not as an arbitrary media exception. Demonstrate the precondition by choosing to read the approval flag independently of registration and validation state, and remove it by choosing to obtain user approval and persist it on the registered-device object. The result model is suitable for a regression fixture because its expected state change is observable without weakening the DRM policy.
Separate cause from wrapper
The receiver is registered but lacks the user approval required before content transfer.
Test without erasing evidence
- Preserve it and
0xC00D28A6before cleanup, fallback or another media item changes the context. - Run the direct check: read the approval flag independently of registration and validation state.
- Compare the failure with a known-good case that changes only the property named by this condition: the receiver is registered but lacks the user approval required before content transfer.
- Apply the targeted fix: obtain user approval and persist it on the registered-device object.
- Associate it with its current WMDRM for Network Devices object and the requested action.
Different owners, similar dialog
| Result | Why it points elsewhere |
|---|---|
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_REGISTER | the receiver has no valid entry in the transmitter registration database |
NS_E_DRM_MUST_REVALIDATE | the receiver registration exists but its proximity validation is stale or no longer acceptable |
When a retry is valid
Recovery should change the failed precondition by choosing to obtain user approval and persist it on the registered-device object.
- Preserve the evidence before making changes.
Technical references
Looking for a different code? Search another status or error code.