Physical-to-virtual conversion creates a virtual disk image from an existing computer so it can be tested in a virtual machine. It is useful for migration experiments, legacy software or a controlled lab, but it is not a substitute for a backup. The resulting system can have activation, driver, encryption and boot issues. Confirm that you have a valid Windows license for the intended virtual use before proceeding; licensing rights depend on how Windows was purchased and the agreement that applies.
Prepare the source PC
- Back up important files independently and verify that the backup opens.
- Record the Windows edition, firmware mode and disk layout. Make sure the destination has enough free storage for the virtual disk and working space.
- If BitLocker is enabled, save the recovery key. Microsoft’s Disk2vhd documentation says encrypted BitLocker volumes are not supported for conversion unless they are fully decrypted first.
- Download Disk2vhd only from Microsoft Sysinternals. Review the current documentation and choose the system volumes required for boot; selecting only a data volume will not create a bootable Windows VM.
- Save the virtual disk image to a separate drive where possible, then wait for the snapshot operation to finish before disconnecting anything.
Create and test the VM
Use Hyper-V on a Windows edition that supports it, or another compatible hypervisor that supports the generated VHD format. Create a new virtual machine with a compatible generation and firmware configuration, attach the VHD, and give the VM enough memory and disk space. The first boot may detect virtual hardware and install drivers. If startup fails, use the hypervisor’s recovery options and keep the original physical PC intact.
Test network access, storage, applications and required data before relying on the virtual copy. Do not boot the VHD on the same physical system in ways that cause disk-signature conflicts; Microsoft’s Disk2vhd guidance warns against attaching a bootable VHD to its source system if it will later be booted in a VM. Keep the VM isolated from sensitive networks until it is patched and you have confirmed its security settings.
Plan for activation and licensing
A cloned Windows installation may ask to reactivate because the virtual hardware differs from the physical computer. A successful image conversion does not transfer a license automatically. Check Microsoft’s current Windows license terms or contact the license provider for your specific retail, OEM or organization license. Do not run both the original installation and a cloned copy if your license does not permit it.
After testing, maintain separate backups of the virtual disk and its data. A virtual machine is still a computer: install updates, use strong account credentials and protect it with the same care as physical hardware.
Official references
Microsoft Sysinternals: Disk2vhd · Microsoft Learn: create a virtual machine in Hyper-V
