| Previous | Next |
| NS_E_DRM_MUST_REVALIDATE | NS_E_DRM_INVALID_SESSION |
NS_E_DRM_INVALID_PROXIMITY_RESPONSE
What the caller learned
Read NS_E_DRM_INVALID_PROXIMITY_RESPONSE at the object boundary, where the receiver returned a proximity response that fails parsing or cryptographic verification. 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.
Confirm the producer by doing one thing first: preserve challenge, response, nonce/session association and signature result.
Narrow the failure
- Preserve this result and
0xC00D28A8before cleanup, fallback or another media item changes the context. - Associate this result with its current WMDRM for Network Devices object and the requested action.
- Run the direct check: preserve challenge, response, nonce/session association and signature result.
- Compare the failure with a known-good case that changes only the property named by this condition: the receiver returned a proximity response that fails parsing or cryptographic verification.
- Apply the targeted fix: fix receiver protocol/firmware or session correlation, then restart validation.
State that must remain correlated
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.
That observation distinguishes it from file corruption because the receiver returned a proximity response that fails parsing or cryptographic verification.
State transition
The before/after comparison has one controlled variable. Before correction, the receiver returned a proximity response that fails parsing or cryptographic verification; after correction, the same workflow can fix receiver protocol/firmware or session correlation, then restart validation. The result comparison should preserve content and device identity so success cannot be attributed to testing a different asset.
Capture before retry
| Field | Value |
|---|---|
| Direct check | preserve challenge, response, nonce/session association and signature result |
Similar symptoms are not identical
| Result | Why it points elsewhere |
|---|---|
NS_E_DRM_MUST_APPROVE | the receiver is registered but lacks the user approval required before content transfer |
NS_E_DRM_MUST_REVALIDATE | the receiver registration exists but its proximity validation is stale or no longer acceptable |
NS_E_DRM_INVALID_SESSION | the WMDRM-ND message refers to a nonexistent, expired or mismatched protocol session |
Do not overread the HRESULT
The receiver returned a proximity response that fails parsing or cryptographic verification.
A real fix
Correct this layer directly and fix receiver protocol/firmware or session correlation, then restart validation.
Technical references
Looking for a different code? Search another status or error code.