What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Yes—you can use Microsoft Sysinternals Disk2vhd to capture a running Windows PC and attach its VHD disk to a VirtualBox VM. But creating the image is only half the job: the VM must include the source system’s boot partitions, use the right BIOS or UEFI mode, and expose a storage controller Windows can boot from. Start with an IDE/PIIX controller, preserve the original disk and image, and troubleshoot according to the screen or stop code you see.
This is a physical-to-virtual (P2V) migration, not a hardware-neutral reinstall. Windows, drivers, activation, networking and some applications may react to the change. The instructions below are for preserving or testing an existing Windows installation; they do not guarantee that every source PC or Windows license can be moved.
Before you start: check the source PC
Do not begin by selecting only C:. Windows may keep its boot files on a separate System Reserved partition or EFI System Partition, and a PC may depend on more than one physical disk. First record how the source is configured and make a backup you can restore.
Outdated 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 matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Back up the PC. Keep the original physical installation untouched while you capture and test the VM. A VHD is not a substitute for a verified backup.
- Check encryption. Disk2vhd does not support converting BitLocker-enabled volumes as a directly bootable image. Fully decrypt the relevant volume and let decryption finish before capture. See Microsoft’s Disk2vhd documentation.
- Record firmware mode and Windows details. Run
msinfo32and note BIOS Mode (Legacy or UEFI), Windows edition/version, and System type (x86 or x64). In Disk Management, note which partitions are on the system disk. - Check disk layout. Open an elevated Command Prompt and run
diskpart,list disk,list volume, thenexit. An asterisk in the GPT column oflist diskindicates a GPT disk. Usebcdedit /enum allto inspect boot entries if needed. - Check for multiple disks or unusual storage. Identify separate boot, application and data disks, and note dynamic disks, Storage Spaces, RAID or vendor storage drivers. These layouts may need all disks and their original order, or a different migration plan.
- Plan for identity and licensing. A clone can share the physical PC’s name, domain identity, IP settings, application identity or security-agent registration. Keep the VM’s network disconnected on first boot. Check the license terms for your exact Windows edition, purchase channel and intended use.
Disk2vhd is Microsoft’s volume-to-VHD capture utility. It uses Volume Shadow Copy (VSS) to capture a running Windows system, but it does not reproduce the source PC’s physical hardware as virtual hardware. Disk2vhd is designed primarily around Microsoft virtualization products; using the resulting VHD in VirtualBox adds a compatibility step. Microsoft’s page lists Disk2vhd 2.02, last updated October 12, 2021; check the official page for the current download and instructions.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Which partitions should you capture?
- Legacy BIOS/MBR: select the System Reserved partition if present, the Windows volume (usually
C:), and any separate boot partition required by that installation. Include recovery partitions if you want to preserve their recovery function. - UEFI/GPT: include the EFI System Partition (ESP) as well as the Windows volume. The Microsoft Reserved partition (MSR) has no ordinary drive letter and may not appear as a selectable volume; do not mistake that for the EFI partition. Include the recovery volume if desired.
Disk2vhd’s list is volume-oriented, while bootability depends on the disk’s partition layout and matching firmware. Review Disk Management and the DiskPart output rather than assuming a volume list alone explains the boot arrangement. Disk2vhd can create one VHD for each physical disk containing selected volumes, so capture every disk needed to start Windows and access required data.
Capture Windows with Disk2vhd
- Download Disk2vhd from the Microsoft Sysinternals page and run it as administrator.
- Enable Use Volume Shadow Copy so Disk2vhd can capture the running Windows volumes through VSS.
- Select the boot-critical and required Windows/data volumes identified above. Do not select only
C:unless you have confirmed that it contains everything needed to boot and operate the installation. - Choose an output location on a different physical disk or a suitable network location. Avoid writing the image onto a busy source volume when another destination is available; ensure the destination has room.
- Start the capture and wait for it to finish. Keep the original installation available, and copy the finished VHD safely before experimenting with conversions or repairs.
The documented command-line form is:
disk2vhd <drive: [drive:]...|*> <vhdfile>For example, to request all volumes and save the result to another disk:
disk2vhd * D:P2Vsource-pc.vhdCheck the downloaded build’s syntax and available options before using a command in a production environment. A completed file is not proof that all required partitions were captured or that the image will boot. Do not attach or mount the new VHD in the same Windows installation that you plan to virtualize: Microsoft warns that doing so can change the disk signature and leave the VM’s boot configuration unable to locate its boot disk.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Create the VirtualBox VM for the captured disk
Create a new VM manually; do not create a blank virtual hard disk and expect it to replace the captured installation automatically.
- In VirtualBox, create a VM using the matching Windows family and architecture. An x64 image needs an x64 guest configuration; do not treat an x86 image as interchangeable.
- Allocate enough RAM for the source Windows installation while leaving adequate memory for the host. Start with one virtual CPU (especially for older Windows) and increase resources after a stable boot.
- Match the firmware mode: start with BIOS for a Legacy/MBR source, and enable EFI for a UEFI/GPT source. A mismatch can prevent the boot manager from finding Windows.
- Attach the captured VHD as the primary hard disk. For the first boot, use an IDE/PIIX controller and make sure the disk is on the first hard-disk port. Microsoft’s Disk2vhd instructions specifically recommend attaching the resulting disk as IDE. This is a compatibility-first starting point, not a promise that IDE fixes every boot problem.
- Check the VM boot order so it tries the hard disk. If using Windows installation media for recovery, temporarily put the optical drive first, then restore the disk-first order afterward.
- Leave the network adapter disconnected for the first boot if this clone might overlap with the live PC, a domain machine, or managed infrastructure.
VirtualBox accepts VHD media. You can attach the VHD directly; conversion to VDI is optional and changes the disk container, not the guest’s boot files or drivers. To retain the original VHD as a rollback copy, convert a copy to VDI using the installed VirtualBox version’s VBoxManage command:
VBoxManage clonemedium disk "D:P2Vsource-pc.vhd" ^
"D:VirtualBox VMsSource-PCsource-pc.vdi" ^
--format VDIOn Linux or macOS, use the same command with the appropriate paths and line continuation, for example:
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
VBoxManage clonemedium disk "/path/source-pc.vhd"
"/path/Source-PC/source-pc.vdi"
--format VDIOracle documents clonemedium and the current VBoxManage command reference; supported output formats include VDI, VMDK, VHD and RAW, subject to the installed version and command. A clone receives a new medium identifier, and keeping the source VHD gives you a recovery path. See the VirtualBox documentation for version-specific UI and VM settings. Oracle’s download page showed VirtualBox 7.2.14 on August 18, 2026; that is a dated observation, not a permanent “latest version” claim.
First boot: change as little as possible
Start the VM with the initial controller, firmware and disk placement unchanged. Give Windows time to detect virtual hardware and install drivers; it may take longer than an ordinary start or require a restart. Do not change the storage controller, firmware mode, disk port and boot order all at once, because that makes a failure harder to diagnose.
If Windows reaches the desktop, verify that important applications, services, scheduled tasks, data volumes and device-dependent features work. Then install the matching VirtualBox Guest Additions package from the VM’s Devices menu or the Guest Additions ISO and follow the Windows installer prompts. Guest Additions provide integration and guest-device drivers; they do not normally repair a VM that cannot get past a pre-boot storage error such as 0x0000007B. Oracle’s Guest Additions documentation covers Windows guests.
Once boot and data integrity are confirmed, reconnect networking only after checking for duplicate identity or address conflicts. Expect a new virtual NIC and MAC address, and potentially a new Windows network profile. Activation may require reactivation because Windows sees substantially different hardware; it is not guaranteed to happen automatically. Check the applicable license terms, particularly for OEM installations, rather than assuming that a technically bootable VM is licensed for the intended use. Historical transfer notes on Microsoft’s Disk2vhd page should not be generalized to every current edition.
Keep the source PC and VHD until the VM has passed application, boot, licensing and data checks. Make an independent backup or a snapshot only after confirming the disk is stable. Do not run the physical PC and its clone simultaneously on the same production network without resolving duplicate hostname, domain, IP, application and endpoint-management identities. Sysprep is not a routine cure for a P2V boot problem: it alters machine-specific state, can fail, and may complicate recovery. Use it only as an intentional deployment step with a backup and a clear reason.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsTroubleshoot by the symptom
| What you see | First checks |
|---|---|
| “No bootable medium found” | Disk attached, boot order, BIOS/UEFI match, captured boot partition, image readability |
0x0000007B / INACCESSIBLE_BOOT_DEVICE |
Storage controller and boot-critical driver; start with IDE/PIIX |
| Automatic Repair loop or disk read error | Firmware mode, boot files, partition capture, filesystem and BCD |
| Windows blue-screens after starting | Storage and filter drivers, filesystem, old physical-hardware utilities |
| VHD missing, rejected or UUID collision | Output completeness, paths, VirtualBox media registration and duplicate image IDs |
| Windows boots but devices or network do not work | Guest Additions, stale physical-device drivers, new NIC/profile and identity |
“No bootable medium found”
- Power off the VM. In Settings > Storage, confirm that the intended VHD is attached and appears on the expected controller and port. Confirm the disk file exists and VirtualBox can read it.
- In Settings > System > Boot Order, put Hard Disk ahead of an empty optical drive or other device.
- Match the source firmware: disable EFI initially for Legacy/MBR; enable EFI for UEFI/GPT. Do not toggle firmware at random—record the original setting and test one change at a time.
- Check that the image contains the System Reserved or EFI boot partition as appropriate. If a separate physical disk held the boot files, capture and attach that disk too.
- If the image is readable and settings match, boot matching Windows installation media and choose recovery tools. Use DiskPart to inspect the disk and volumes rather than guessing partition numbers.
For a Legacy BIOS/MBR installation only, the system partition may need to be marked active. In a recovery Command Prompt, identify the correct disk and partition first:
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
diskpart
list disk
select disk 0
list partition
select partition <number>
active
exitDo not mark an EFI System Partition active as a general fix; UEFI does not use the MBR active-partition mechanism in the same way. Microsoft’s VM boot troubleshooting guidance distinguishes legacy active-partition repair from UEFI startup.
0x0000007B or INACCESSIBLE_BOOT_DEVICE
This usually indicates that Windows cannot access the system disk early in boot. Microsoft lists controller changes, moving a disk to different hardware and storage/filter-driver problems among possible causes in its 0x7B troubleshooting guidance. In a P2V, the source may have used SATA, RAID, NVMe or a vendor controller while the VM exposes a different one.
- Power off. Confirm the VHD is attached as the boot disk, then try IDE/PIIX as the initial controller. Make only this controller change before testing again.
- Verify the VM firmware mode and disk position. Changing VHD to VDI will not fix a missing controller driver.
- If the stop code remains, boot Windows recovery media. Try Startup Repair once or twice if the problem is a damaged startup configuration, but do not assume it can supply a missing storage driver.
- In recovery, identify the Windows volume letter before running checks; it may not be
C:. You can usediskpartthenlist vol, followed byexit. Runchkdsk C: /fonly after substituting the confirmed Windows volume letter. - Inspect boot entries with
bcdedit /enum all. If boot files need rebuilding, use the appropriate BIOS or UEFI procedure below, after identifying the correct Windows and system partitions.
Do not start by editing storage-driver registry Start values from another installation. The correct service and repair method vary by Windows version, and an ill-judged change can make the image harder to recover. Prefer a compatible controller, proper boot-file repair, or offline driver injection by a technician familiar with that Windows release.
Automatic Repair loop, disk read error or suspected BCD damage
These symptoms can come from mismatched firmware, omitted boot partitions, damaged boot files, a disk-signature/BCD mismatch or filesystem corruption. Boot from matching Windows installation media and select Repair your computer rather than installing over the image. In Command Prompt, run diskpart and list vol to identify the Windows volume and (for UEFI) the EFI volume. Letters in recovery are often different from normal Windows.
For a BIOS/MBR installation, Microsoft’s traditional boot repair commands are:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcdUse these only after confirming the installation is Legacy/MBR and that recovery tools see the intended system disk. For UEFI, assign a temporary letter to the EFI System Partition in DiskPart (select the correct volume, then assign letter=S) and rebuild the boot files using the verified Windows volume letter:
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
bcdboot C:Windows /s S: /f UEFIHere C: and S: are examples, not assumptions. Replace C: with the Windows directory’s actual recovery-environment letter, and S: with the EFI partition letter you assigned. A wrong target can update the wrong boot configuration. Run chkdsk <Windows-letter>: /f only after identifying the intended volume; do not run repairs against a guessed drive letter.
Recommended Free Tools
Windows starts, then blue-screens or behaves badly
If Windows gets further than the boot manager but crashes, the issue may be a storage driver, third-party storage filter, filesystem corruption, obsolete physical GPU/chipset/RAID utility, security software, or other hardware-tied service. If possible, try Safe Mode. Remove obsolete OEM hardware utilities only when you understand their role; do not remove unknown drivers indiscriminately. After a stable desktop boot, install Guest Additions and check Device Manager and Event Viewer. Review relevant crash and setup logs, including C:WindowsMinidump, C:WindowsPanther and C:WindowsSystem32LogFiles (paths or available logs can differ). If the image is unstable or the source disk is damaged, recapture or restore from a known-good backup rather than repeatedly applying speculative repairs.
VHD is missing, inaccessible or “too small”
Check whether the output path was full or disconnected, whether capture was interrupted, whether all required volumes were selected, and whether the source spans multiple physical disks. A dynamically sized VHD’s file size on the host is not the same as its virtual capacity or the used data inside Windows:
- Virtual capacity is the maximum disk size the guest sees.
- Host file size is the space the VHD currently consumes on the host.
- Used data is the data occupied inside the Windows volumes.
Do not judge image health by file size alone. Ask VirtualBox to inspect the medium:
VBoxManage showmediuminfo "D:P2Vsource-pc.vhd"
VBoxManage list hdds
VBoxManage showvminfo "Source-PC"These commands help establish whether VirtualBox recognizes the disk, how it is registered, and how it is attached to the VM. A recognized medium can still have incomplete contents or a non-bootable partition layout.
“VHD is already attached” or UUID collision
This commonly occurs after copying a VHD or registering more than one VM against the same medium identity. Use VBoxManage list hdds to inspect registered media. If you need a separate VM disk from a copy, create a new image with VBoxManage clonemedium disk source.vhd destination.vdi --format VDI, using real paths and retaining the source file. Avoid manually editing VirtualBox XML files unless normal media-management commands have failed and you understand the consequences.
Best Value
- [Upgraded Version] - This external hard drive features a mirrored logo stripe combined with a striped anti-slip design, and the rounded corners of the casing make it easier to grip. The stripes also have a heat dissipation function, ensuring stable and fast data transfer.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
Windows boots, but mouse, display, network or time is wrong
These are commonly post-boot integration issues, not evidence that the P2V capture failed. Install Guest Additions after Windows is stable. Windows may retain hidden adapters for the old physical NIC; the virtual NIC has a new MAC address and can create a new network profile. Reconfigure networking carefully, especially if the source has a static IP or is domain managed. Applications that depended on a physical device may still need their own drivers or may not function in a VM.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When to recapture instead of keep repairing
- BitLocker was enabled: decrypt completely and capture again rather than treating the encrypted image as a normal bootable VHD.
- A boot partition or required physical disk was omitted: recapture the missing volume/disk if possible. Boot-file reconstruction may work, but it is not a substitute for understanding the original layout.
- VSS capture failed or the output was interrupted: start a fresh capture to a reliable destination.
- The source filesystem is unhealthy: repair or back up the source first; a hot capture of a damaged system may simply preserve its problems.
- Storage Spaces, dynamic disks, software RAID or vendor RAID are involved: do not assume a volume-level VHD has reproduced the underlying storage arrangement. Plan a separate migration or recovery strategy, including required disks, order and drivers.
- Sysprep or repeated repairs changed the installation: preserve logs and a copy before further action. Microsoft notes that some Sysprep failures may require recreating an image; see its Sysprep troubleshooting guidance.
Older Windows versions such as XP, Server 2003, Vista and Windows 7 can be more sensitive to controller and hardware changes. Start with Legacy BIOS where appropriate, IDE/PIIX3 and one virtual CPU, but do not assume a modern VirtualBox setup or an older VirtualBox release will work without testing the exact guest.
On an Apple-silicon Mac, an x86/x64 Windows P2V image is not a straightforward equivalent of an ARM guest. Oracle lists an Apple-silicon VirtualBox host package, but host architecture does not convert an x64 physical installation into an ARM Windows guest. Confirm architecture and current product capabilities before planning a cross-architecture migration.
Should you use another conversion route?
If Disk2vhd produced a sound VHD and VirtualBox recognizes it, try attaching it directly before adding another converter. Converting VHD to VDI with VBoxManage can give you a VirtualBox disk container, but it does not fix omitted partitions, firmware mismatch, BCD damage or missing drivers.
StarWind V2V Converter is an alternative when you specifically need format interoperability; its vendor advertises VHD/VHDX, VMDK, QCOW2 and IMG support and VirtualBox-related conversion workflows. It is not mandatory when VirtualBox already accepts a healthy VHD, and another conversion step still needs validation. Hyper-V may suit a Windows-to-Windows workflow more naturally because Disk2vhd is documented for Microsoft virtualization use. For complex storage, repeatable disaster recovery or a damaged source, use a migration/backup approach designed for that situation. If the old setup is unstable or hardware-dependent and preserving its exact environment is not essential, a clean Windows VM with application and data migration may be more supportable than P2V.
Quick Recap
Final checklist
- Source backup exists; original physical disk remains untouched.
- BitLocker decryption is complete; BIOS/UEFI mode, architecture, partition layout and all required disks are recorded.
- Disk2vhd ran as administrator with VSS enabled; boot-critical volumes were selected; output went to another disk.
- VirtualBox guest architecture and firmware match the source; VHD is attached first as IDE/PIIX and boot order is correct.
- First boot is isolated from production networking; controller and firmware are not changed simultaneously.
- After stable boot, Guest Additions, applications, data, activation, domain identity and networking are checked.
- A separate validated backup exists before retiring the original or relying on the VM.
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.
