Sometimes we can mount a VHDX that had its checkpoints saved on another location. When trying to boot the VM we will have a “Property ‘MaxInternalSize’ does not exist in class ‘Msvm_VirtualHardDiskSettingData’.”
This is because the disk properties has changed and the VM is linking the checkpoint back to its parent, making the chain corrupted.
To remediate this, we will use the Set-VHD powershell snippet
Set-VHD "D:\path\Disk_CHECK2.avhdx" -ParentPath "D:\path\Disk_CHECK1.avhdx" Set-VHD "D:\path\Disk_CHECK1.avhdx" -ParentPath "D:\path\Disk.vhdx"
Here we are stitching the newest checkpoint (Disk_CHECK2) to (Disk_CHECK1); then Disk_CHECK1 to the main Disk.VHDX.
Now, its very likely that you will receive a mismatch error:
“There exists ID mismatch between the differencing virtual hard disk and the parent disk. “
For this we will use the –
Set-VHD "D:\path\Disk_CHECK1.avhdx" -ParentPath "D:\path\Disk.vhdx" –ignoreidmismatch
And now you will have a booting VM again!
Just wanted to let you know, you post 100% saved me from a ton of work needed to rebuild a production VM with a corrupted virtual hard disk (my fault). Thank you so much for taking the time to post this with such clean and concise detail.
Cheers!
Thank you!
Thank you for this manual! You saved me lot of time
Thank you so much for this. You saved me hours of frustration and a lot of stress.
Hi Sebastián
Great post, thank you very much, you just saved my life !!
Thank you!!! Saved me a ton of work!!!