| Previous | Next |
| NS_E_DRM_LICENSE_UNAVAILABLE | NS_E_DRM_UNABLE_TO_VERIFY_PROXIMITY |
NS_E_DRM_DEVICE_LIMIT_REACHED
The exact DRM condition
This HRESULT is specific: NS_E_DRM_DEVICE_LIMIT_REACHED appears because the transmitter has reached the number of network devices allowed by policy or implementation. 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.
Confirm the producer by doing one thing first: enumerate open/registered devices and distinguish active sessions from stale records.
Fields for a reproducible report
| Field | Value |
|---|---|
| Temporal state | trusted/system time, validity interval, request sequence and retry number when they influence this result |
| Direct check | enumerate open/registered devices and distinguish active sessions from stale records |
What to log
The important objects are device certificate and serial number, registration-database entry, approval flag, validation timestamp, network session, protocol message and transcrypt policy. Evidence should correlate the exact WMDRM-ND message type, device identifier, certificate chain, registration state, round-trip timing and the first protocol HRESULT.
A later generic error must not replace this evidence: the original condition remains that the transmitter has reached the number of network devices allowed by policy or implementation.
Expected state change
It should be modeled as a failed precondition, not as an arbitrary media exception. Demonstrate the precondition by choosing to enumerate open/registered devices and distinguish active sessions from stale records, and remove it by choosing to close or remove obsolete devices through the registration API. The result comparison should preserve content and device identity so success cannot be attributed to testing a different asset.
Scope and consequences
The transmitter has reached the number of network devices allowed by policy or implementation.
Troubleshooting order
- Preserve it and
0xC00D28A3before 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: enumerate open/registered devices and distinguish active sessions from stale records.
- Compare the failure with a known-good case that changes only the property named by this condition: the transmitter has reached the number of network devices allowed by policy or implementation.
- Apply the targeted fix: close or remove obsolete devices through the registration API.
Related codes, different contracts
| Result | Why it points elsewhere |
|---|---|
NS_E_DRM_CERTIFICATE_REVOKED | the WMDRM-ND peer certificate is explicitly revoked |
NS_E_DRM_LICENSE_UNAVAILABLE | no license available to the transmitter authorizes the requested WMDRM-ND action |
NS_E_DRM_UNABLE_TO_VERIFY_PROXIMITY | the timed proximity exchange did not prove that the receiver is sufficiently near the transmitter |
Change the rejected precondition
A matching correction is to close or remove obsolete devices through the registration API.
Technical references
Looking for a different code? Search another status or error code.