| Previous | Next |
| NS_E_DRM_NEEDS_INDIVIDUALIZATION | NS_E_DRM_ACTION_NOT_QUERIED |
NS_E_DRM_ALREADY_INDIVIDUALIZED
The exact DRM condition
0xC00D2729 maps to NS_E_DRM_ALREADY_INDIVIDUALIZED. Read it as a result from DRM individualization and security-component upgrade: you already have the latest security components.
No upgrade is necessary at this time. Keeping the “already individualized” boundary intact prevents a later playback message from hiding the original DRM failure.
A useful investigation order
- Prove the boundary by ensuring you can record the exact API, object state, input identity and first lower-level result associated with this failure.
- After you correct the producing DRM state or input and retry with a fresh operation object, verify both the requested right and the final store/device state.
State to capture before retry
- Protected identity: whether the application is already individualized for the required level.
- Persistence or transport: security-component version before and after the attempt.
- Security context: download/service response and signature validation result.
Nearby results with different meanings
| Result | Different condition |
|---|---|
NS_E_DRM_NEEDS_INDIVIDUALIZATION | A security upgrade is required to perform the operation on this media file. |
NS_E_DRM_INDIVIDUALIZING | A security-component individualization operation is already in progress. |
NS_E_DRM_INDIVIDUALIZE_ERROR | The security upgrade failed. Try again later. |
Technical references
- DRM individualization.
- Performing DRM individualization.
- Enabling DRM support — API and state rules for the DRM operation described here.
- DRM client structures.
Looking for a different code? Search another status or error code.