Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Disk2vhd can capture a running Windows installation into a VHD or VHDX, but selecting only C: does not necessarily make a bootable disk. You must capture the partition that contains Windows Boot Manager as well: the System Reserved partition on BIOS/MBR systems, or the EFI System Partition on UEFI/GPT systems. Then create a Hyper-V VM with the matching generation and controller.
This guide covers physical-to-virtual conversion for Hyper-V. “Native boot,” where Windows starts directly from a VHDX on physical hardware, is a separate deployment method and is addressed near the end.
What Disk2vhd does
Microsoft Sysinternals Disk2vhd uses Volume Shadow Copy Service (VSS) to create a point-in-time virtual-disk representation while Windows is running. It copies only the volumes you select and preserves the source disk’s partitioning information. Microsoft’s download page currently lists version 2.02 and documents support beginning with Windows Vista and Windows Server 2008, including x64 systems.
Recommended Free Tools
The result is useful for a Hyper-V physical-to-virtual (P2V) migration, compatibility testing, or preserving an old Windows environment. It is not automatically a complete backup, application-consistent database image, or guarantee of activation and driver compatibility.
#1 Best Overall
Before you capture the computer
- Run Disk2vhd with administrator rights and verify that the source Windows installation boots normally.
- Prefer a different local or portable disk for the output. Microsoft warns that network-share destinations can cause timeouts; local storage is generally safer and faster.
- Close applications that are actively writing important data. For databases and other transactional workloads, use the vendor’s application-consistent backup procedure instead of treating an online VSS capture as sufficient.
- Record Windows edition and version, static IP settings, special storage drivers, application licenses, and activation status.
- BitLocker must be fully decrypted. Suspending protection is not the same as decrypting the volume. Confirm decryption has completed before imaging, and retain recovery keys separately.
- Keep the original machine unchanged until the VM has been tested and accepted.
Check BIOS/UEFI mode and partition style
Press Win+R, run msinfo32, and read BIOS Mode. Legacy normally corresponds to BIOS/MBR; UEFI normally corresponds to UEFI/GPT. To inspect disks and volumes, open an elevated command prompt:
diskpart
list disk
list volume
exitAn asterisk in the Gpt column indicates a GPT disk. Unusual layouts can break the normal correspondence, so use both the firmware mode and the actual partition layout when deciding how to build the VM.
Select every partition required for booting
| Source installation | Select in Disk2vhd | Initial Hyper-V choice |
|---|---|---|
| Legacy BIOS/MBR | System Reserved partition and Windows volume (usually C:) |
Generation 1, IDE boot disk |
| UEFI/GPT | EFI System Partition and Windows volume; Recovery partition is optional | Generation 2, SCSI boot disk |
BIOS/MBR: include System Reserved
The small System Reserved partition commonly contains Windows Boot Manager, the BCD store, recovery files, and sometimes BitLocker boot data. Omitting it can leave a complete-looking C: volume that fails with “Operating system not found,” “No boot device,” or a blinking cursor.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchUEFI/GPT: include the EFI System Partition
The EFI System Partition (ESP) is usually a small FAT32 partition without a drive letter. Temporarily mount it from an elevated command prompt:
mountvol S: /sChoose another unused letter if S: is already assigned. It will then appear as a selectable volume in Disk2vhd. In Microsoft’s Generation 2 conversion procedure, clear Use Volume Shadow Copy when the EFI partition is selected if VSS cannot handle that partition; this is a documented exception, not a general recommendation to disable VSS for every capture.
Multiple physical disks
Disk2vhd creates a separate output file for each physical disk containing selected volumes. Map every selected volume to its physical disk before starting. If boot files are on one disk and Windows or application data is on another, capture and later attach all required disks.
Create the image with Disk2vhd
- Download Disk2vhd from the official Microsoft page, extract it locally, and run
disk2vhd.exeas administrator. - Select the Windows volume and its System Reserved or EFI partition. Add other volumes required by applications.
- Choose a destination on a different physical disk where possible. Do not use a network share unless there is no practical alternative.
- Choose VHD or VHDX in the current interface. VHDX is generally the better choice for current Hyper-V; VHD may be needed for legacy virtualization software.
- Click Create, wait for completion, and verify that the output file exists and has a plausible size.
Disk2vhd can write to a local volume, including one being converted, but Microsoft notes that another disk usually gives better performance and reduces operational risk.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Command-line capture
The documented syntax is:
disk2vhd <[drive: [drive:]...]|[*]> <vhdfile>Examples:
disk2vhd * C:VHDfull-capture.vhd
disk2vhd C: S: F:VHDwindows-capture.vhdThe drive letters must match the source computer. The wildcard includes all volumes visible to Disk2vhd; that may produce multiple files when volumes span physical disks. In scripts, log the exit result and verify every expected output file.
Move the image safely
Close Disk2vhd, copy the VHD/VHDX to storage accessible by the Hyper-V host, and retain an untouched master copy. Avoid attaching the image to the same Windows installation from which it was created. Microsoft documents that Windows can change a duplicate disk signature when the image is mounted on its source system; the BCD may then refer to the old signature and the VM can fail to find its boot disk. Test from a separate Hyper-V host or recovery environment whenever possible.
Create the matching Hyper-V VM
Hyper-V generation is a firmware and boot-hardware choice, not a file-extension choice. Microsoft’s generation guidance explains the differences, and the generation cannot be changed after the VM is created.
Choose Generation 1 for BIOS/MBR
- Legacy BIOS firmware.
- Boot disk attached to an IDE controller.
- Typical choice for Windows 7 or older BIOS installations and BIOS-based Windows 10.
Choose Generation 2 for UEFI/GPT
- UEFI firmware.
- Boot disk attached to a virtual SCSI controller.
- Appropriate for supported 64-bit Windows installations using an EFI System Partition.
- Windows 11 requires Generation 2; Windows 10 64-bit supports both generations when the disk and firmware match.
If the source is unknown, inspect it before creating the VM. Changing .vhd to .vhdx does not convert BIOS boot files into UEFI boot files.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Hyper-V Manager procedure
- Select New > Virtual Machine in Hyper-V Manager.
- Assign a descriptive name and select Generation 1 or Generation 2 before continuing.
- Assign conservative startup memory and configure networking; you can refine both after the first boot.
- Use the existing virtual hard disk option when offered, or finish the wizard and attach the converted disk in Settings.
- For Generation 1, attach the boot disk to IDE Controller 0. For Generation 2, attach it to the SCSI Controller.
- Check the boot order. In a Generation 2 VM, the converted disk must be in the UEFI firmware boot list.
Generation 2 enables Secure Boot by default. Leave it enabled for a supported Windows guest initially. If the VM fails before Windows starts despite a correct disk and boot order, temporarily clear Settings > Security > Enable Secure Boot as a diagnostic step, then restore the appropriate security configuration.
You can also use PowerShell templates, adapting paths, memory, and switch names:
New-VM -Name "Converted-PC" `
-Generation 1 `
-MemoryStartupBytes 4GB `
-VHDPath "D:VMsConverted-PC.vhdx" `
-SwitchName "Default Switch"For a UEFI/GPT capture, change -Generation 1 to -Generation 2. The command does not solve partition, driver, activation, or licensing issues.
What to expect on the first boot
Windows may take longer than usual while it detects virtual storage, display, and network hardware. Expect a new virtual NIC and MAC address, driver installation, one or more restarts, changed firewall profiles, and possible Windows or application activation prompts. A static IP configured for the physical adapter will not automatically apply to the new virtual adapter. Do not generalize, rename, or heavily reconfigure the guest until it has booted reliably.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsTroubleshooting
“No operating system found” or “Boot device not found”
- Confirm the VM generation matches the source firmware mode.
- Confirm the System Reserved or EFI partition was captured.
- Check the controller: IDE for Generation 1, SCSI for Generation 2.
- Check Hyper-V boot order and that the VHD/VHDX is readable.
- Use a copy if the image was ever mounted on the original source computer.
Windows Boot Manager appears, but Windows will not start
Boot from Windows installation media or WinPE and identify drive letters, which often differ from normal Windows:
diskpart
list volume
exitAssuming Windows is C: and the system or EFI partition is S:, rebuild boot files with the matching firmware mode:
bcdboot C:Windows /s S: /f BIOS
bcdboot C:Windows /s S: /f UEFIRun only the command appropriate to the VM. For BIOS/MBR, the correct system partition may also need to be marked active; do not mark partitions blindly:
diskpart
select disk 0
list partition
select partition <system-partition-number>
active
exitGeneration 2 reports no UEFI-compatible filesystem
The source may actually be BIOS/MBR, the EFI partition may be missing or incorrectly captured, the disk may not be in the UEFI boot order, or Secure Boot may reject the loader. Verify the source layout, recapture the EFI partition if necessary, rebuild UEFI boot files, and try Generation 1 only when the source was genuinely BIOS-based.
Disk2vhd reports a VSS or snapshot error
Check Event Viewer for VSS and VolSnap errors. Retry to local storage, confirm BitLocker is fully decrypted, and capture fewer volumes to isolate the failing one. Complex storage filters, antivirus drivers, EFI handling, insufficient space, and network destinations can all contribute. Follow Microsoft’s EFI-specific instruction about clearing Use Volume Shadow Copy when that partition is selected.
Best Value
Windows crashes or restarts immediately
Physical RAID, vendor storage drivers, endpoint security, hardware-bound services, or damaged source files may not tolerate the virtual hardware. Use Safe Mode or Windows Recovery Environment and remove obsolete drivers only when you can identify them. Dynamic disks, hardware RAID, Storage Spaces, SAN volumes, and third-party filters warrant a vendor-supported backup-and-restore migration instead of assuming a simple Disk2vhd capture will work.
Networking, activation, and licensing problems
Install and configure the new virtual adapter, verify the Hyper-V switch, and check DHCP, static addressing, DNS, and firewall profile. Hardware changes can trigger Windows activation, OEM transfer restrictions, volume-license requirements, and application reactivation. Disk2vhd’s historical licensing notes are not a substitute for the current terms applying to your Windows edition or software.
Special cases that need extra planning
- Domain controllers: Never start a converted controller alongside the original without an isolated, domain-aware plan; duplicate identity, replication, and time issues can be serious.
- Servers and databases: Check vendor support, application-consistency requirements, backup agents, clustering, and hardware-bound licensing before conversion.
- Windows 7: Start with Generation 1 for a BIOS capture and expect greater sensitivity to IDE/SCSI drivers, activation, and Secure Boot.
- Multiple disks: Attach every disk needed for boot, paging, profiles, databases, and application data; a VM can boot while still missing essential data volumes.
Native boot is a different procedure
A native-boot VHDX starts Windows directly on physical hardware without Hyper-V. Microsoft’s native-boot documentation describes applying an image, preparing partitions, and adding a BCD entry. For Windows 10 and later, that procedure requires VHDX rather than VHD. A raw Disk2vhd capture may contain hardware-specific drivers, OEM configuration, encryption state, and activation dependencies, so it is usually more predictable as a Hyper-V guest. Do not mix native-boot commands into the ordinary P2V workflow.
Final validation checklist
- Correct VM generation and controller are used.
- System Reserved or EFI partition is present.
- Windows boots through at least two restarts.
- Network adapter, IP configuration, DNS, and firewall profile are correct.
- Device Manager has no unexplained storage or security-driver failures.
- Windows and application activation and licensing are verified.
- Critical applications, databases, scheduled tasks, backups, and monitoring are tested.
- The original machine and an untouched image copy remain available until acceptance.
Frequently Asked Questions
Can I select only C: in Disk2vhd?
Usually not. Include the System Reserved partition for BIOS/MBR or the EFI System Partition for UEFI/GPT, otherwise the image may contain Windows but lack its boot files.
Should a Disk2vhd image use VHD or VHDX?
VHDX is generally preferable for current Hyper-V and modern Windows. Use VHD when compatibility with older virtualization software specifically requires it.
Can I boot the image on the same computer that created it?
Avoid mounting it in the source Windows installation. Windows may change the duplicate disk signature, causing BCD and boot failures. Test from a separate host or recovery environment.
The Bottom Line
A Disk2vhd capture becomes a reliable Hyper-V boot disk only when it includes the correct boot partition and is attached to a VM whose firmware, generation, and controller match the source. Treat first boot as a migration test: validate drivers, networking, licensing, applications, and backups before retiring the physical system.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
