# Diagnose an invalid Change ID in the VM Conversion preview

> What evidence should be collected when VM Conversion synchronization cannot validate a disk Change ID?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-048-diagnose-an-invalid-change-id-in-the-vm-conversion-preview/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:23+00:00
- Modified: 2026-09-08T18:17:14+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What evidence should be collected when VM Conversion synchronization cannot validate a disk Change ID?

## Potentially affected

Use this review only for the documented preview extension and matching synchronization symptom.

## DSE recommendation

Preserve the failed operation details and the disk identifiers before attempting recovery.

## Article

## Source facts

Microsoft labels the Windows Admin Center VM Conversion extension as a preview product. Its troubleshooting guide identifies a synchronization failure in which the extension cannot retrieve or validate the Change ID for one or more disks on the source VMware VM. One documented recovery path regenerates Changed Block Tracking and includes powering the source VM off and back on before retrying synchronization. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/use/troubleshoot-vm-conversion-extension).

## Applicability

Use this review only for the documented preview extension and matching synchronization symptom. Identify the extension version, source VM, affected disks, and exact error. Review current preview limitations before planning further migration work.

## DSE recommendation

Preserve the failed operation details and the disk identifiers before attempting recovery. Have the VMware owner examine the Changed Block Tracking state and confirm whether the documented path applies. Treat its power transition as an interruption requiring workload approval. Record the intended recovery sequence and the approved retry point rather than repeatedly restarting synchronization without evidence.

## Verification

After an authorized corrective action, record the source VM and disk state and retry the selected synchronization. Compare the result with the original Change ID failure. Verify application readiness after any power transition through the agreed guest checks. Escalate a continuing failure with the retained extension, VM, and disk details before proceeding with conversion.

## Official references

[Microsoft Learn: Troubleshoot the VM Conversion Extension in Windows Admin Center (Preview)](https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/use/troubleshoot-vm-conversion-extension). Source reviewed September 8, 2026.

## Primary reference

- Name: Troubleshoot the VM Conversion Extension in Windows Admin Center (Preview)
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/use/troubleshoot-vm-conversion-extension
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Diagnose an invalid Change ID in the VM Conversion preview,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-048-diagnose-an-invalid-change-id-in-the-vm-conversion-preview/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.