| Previous | Next |
| NS_E_DRM_MIGRATION_TARGET_STATES_CORRUPTED | NS_DRM_E_MIGRATION_UPGRADE_WITH_DIFF_SID |
NS_E_DRM_MIGRATION_IMPORTER_NOT_AVAILABLE
How to classify this result
The symbolic result NS_E_DRM_MIGRATION_IMPORTER_NOT_AVAILABLE narrows 0xC00D278A to license and secure-state migration. In practical terms, the required migration importer component is unavailable; the producing layer is the controlled import/export path that packages legacy DRM state, validates the migration image and source identity, and commits eligible licenses to a supported target environment.
Record importer registration, module version and load error.
How to prove the condition
- Locate the earliest API return, callback or event containing this result and
0xC00D278A. - Identify the exact content, license, store, device or migration object instance involved in “migration importer not available”.
- Determine whether “migration importer not available” occurred before network exchange, during response validation, while enforcing policy, or while committing protected state.
- Perform the code-specific check: record importer registration, module version and load error.
- Make one targeted change — install or register the supported importer for this migration format — and repeat the same producing operation.
Which component owns the failure
Do not flatten this result into a generic DRM error. Migration is not equivalent to copying license-store files: the importer validates source state, target support and protected identities. The second relevant rule is that a migration image, target-state corruption and an already imported license are independent outcomes and should not be collapsed into one generic restore failure.
Diagnostic inputs that separate the causes
- Code-specific proof: record importer registration, module version and load error.
- Protected identity: migration image identity, hash and creation time.
- Operation state: legacy V2 secure-store entry and supplied password.
- Persistence or transport: importer plug-in availability and current operation state.
- Security context: per-license duplicate or import result.
- Correlation point: source and target OS versions and user SIDs.
Common but unsafe responses
- Avoid editing migration images or combining data from different source machines.
- Avoid running concurrent playback or DRM operations against the source while migration owns it.
- Do not reduce this result to “DRM failed” in telemetry; retain the HRESULT, symbolic name, operation and object identity.
What a supported fix should change
To correct this, install or register the supported importer for this migration format.
Representative case: A legacy V2 image is supplied on a system without its importer plug-in.
Do not merge these HRESULTs
| Result | Different condition |
|---|---|
NS_DRM_E_MIGRATION_UPGRADE_WITH_DIFF_SID | Migration or upgrade sees a different user SID than the protected source state expects. |
NS_E_DRM_MIGRATION_TARGET_STATES_CORRUPTED | Protected DRM state on the migration target is corrupt. |
NS_DRM_E_MIGRATION_SOURCE_MACHINE_IN_USE | The source DRM environment is busy with another operation during migration. |
How to know the fix is real
After the repair, recreate the WMDRM object and run the smallest reproducer. Confirm that 0xC00D278A no longer occurs, that the intended license action completes, and that no store, certificate, clock or migration warning replaces it.
Code-specific operational note
The user-facing message “A problem has occurred in the Digital Rights Management component during license migration. Contact Microsoft product support.” describes the visible condition but does not identify the producing API, object instance, or protected identity by itself.
Technical references
Looking for a different code? Search another status or error code.