Property ‘MaxInternalSize’ does not exist in class ‘Msvm_VirtualHardDiskSettingData’ – VHDX on Hyper-V

on

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 have 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 –ignoreidmismatch command:

Set-VHD "D:\path\Disk_CHECK1.avhdx" -ParentPath "D:\path\Disk.vhdx" –ignoreidmismatch

And now you will have a booting VM again!

Was this helpful?

17 thoughts on “Property ‘MaxInternalSize’ does not exist in class ‘Msvm_VirtualHardDiskSettingData’ – VHDX on Hyper-V

  1. 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!

    1. How do you know which one is the latest AVHDX and what it’s linked to?
      I restored an entire folder so they all have the same date.

  2. You just saved my day! I was looking at two days work down the drain since I had mounted a drive with checkpoints…

Leave a Reply

Your email address will not be published. Required fields are marked *