HRESULT 0xC00D1B90 (NS_E_DUPLICATE

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The profile ID is already used by a DRM profile. Specify a different profile ID.%0

Previous	Next
NS_E_DRM_PROFILE_NOT_SET	NS_E_INVALID_DEVICE

NS_E_DUPLICATE_DRMPROFILE

Interpret the security decision

At 0xC00D1B90, NS_E_DUPLICATE_DRMPROFILE records that a new encoder DRM profile reuses an identifier already present in the profile store. The owner is Windows Media Encoder DRM profiles; its working contract covers encoder-session configuration that selects a stored DRM profile and uses its identifier, policy and secret while packaging live or file-based protected output.

To prove this boundary rather than infer it from a dialog, enumerate stored profile IDs and compare the exact normalized identifier.

Do not lose object identity

The object graph behind this result includes encoding session, DRM profile identifier, profile store, password, selected audience/output and profile-count limit. A trace should retain the profile ID supplied to the session, profile enumeration result, profile-store location, password length and the point at which the encoder binds the profile.

The scope stays narrow: a new encoder DRM profile reuses an identifier already present in the profile store. Other content or actions may still be valid.

How the operation should advance

A useful failure model links cause and recovery: a new encoder DRM profile reuses an identifier already present in the profile store. Verify that model when you enumerate stored profile IDs and compare the exact normalized identifier, then make the smallest change needed to choose a unique profile ID or deliberately update the existing profile.

Values to compare

Field	Value
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
Direct check	enumerate stored profile IDs and compare the exact normalized identifier

Distinguish from nearby results

Result	Why it points elsewhere
`NS_E_DRM_PROFILE_NOT_SET`	the encoder session reached protected output without a DRM profile bound to it
`NS_E_DRM_PASSWORD_TOO_LONG`	the supplied legacy DRM profile password exceeds the accepted field length
`NS_E_DRMPROFILE_NOTFOUND`	the encoder cannot resolve the requested DRM profile identifier

Keep the scope narrow

A new encoder DRM profile reuses an identifier already present in the profile store.

From HRESULT to cause

Preserve it and 0xC00D1B90 before cleanup, fallback or another media item changes the context.
Apply the targeted fix: choose a unique profile ID or deliberately update the existing profile.
Associate it with its current Windows Media Encoder DRM profiles object and the requested action.
Run the direct check: enumerate stored profile IDs and compare the exact normalized identifier.
Compare the failure with a known-good case that changes only the property named by this condition: a new encoder DRM profile reuses an identifier already present in the profile store.

Fix and verify

Correct this layer directly and choose a unique profile ID or deliberately update the existing profile.

Preserve the evidence before making changes. Do not recreate every encoder profile at once; preserve the original profile ID and compare one known-good profile so a lookup problem is not confused with a policy or password problem.

Technical references

Looking for a different code? Search another status or error code.