Forum Discussion
Disk2VHD problem on Windows 10 20H2?
Hi is anyone else having a problem creating a VHD of Windows 10 using Disk2VHD? When I try to create a VHD of a Windows 10 machine using Disk2VHD I get an error saying 'Error snapshotting volumes: the parameter is incorrect.'. It can see 3 drives SYSTEM_DRV, WINRE_DRV and the C: drive. If I deselect the first two it will let me create the VHD but then it doesn't work in HyperV. I have tried this on two different Windows 10 machines and get the same error on both.
Thanks
I noticed the same problem on Windows 10 version 1909 (Codename 19H2 / Build 18363), so it may be the same issue for later versions of Windows 10.
What I found is Disk2VHD could not P2V the recover volume (around 500MB in my case) and the EFI volume (around 100MB in my case) at the same time using volume shadow copy.
After much troubleshooting and attempting to fix the underlying VSS issue with no luck, I discovered it was the above issues what was preventing the P2V'ing from working with VSS and was generating all the VSS related errors in the event log.
I simply then excluded the 500MB recovery volume and the P2V process completed fine using VSS. Also boots fine in 2016 Hyper-V. (Hyper-V VM rebooted once or twice before windows loaded, but that may have been because my P2V was a password protected bitlocker enabled laptop)Regards: Elliott.
2 Replies
I noticed the same problem on Windows 10 version 1909 (Codename 19H2 / Build 18363), so it may be the same issue for later versions of Windows 10.
What I found is Disk2VHD could not P2V the recover volume (around 500MB in my case) and the EFI volume (around 100MB in my case) at the same time using volume shadow copy.
After much troubleshooting and attempting to fix the underlying VSS issue with no luck, I discovered it was the above issues what was preventing the P2V'ing from working with VSS and was generating all the VSS related errors in the event log.
I simply then excluded the 500MB recovery volume and the P2V process completed fine using VSS. Also boots fine in 2016 Hyper-V. (Hyper-V VM rebooted once or twice before windows loaded, but that may have been because my P2V was a password protected bitlocker enabled laptop)Regards: Elliott.
My problem was a little more simple and basic to fix. I was using an older version of the Disk2VHD software, not sure how I even had an old copy still on any devices?!?! Once I switched to using the most current version it worked perfectly. So embarrassingly it was a rookie mistake on my part.
Thanks for the help! Much appreciated.
