Skip to Main Content

Uh-oh! Internet Explorer is out of date.

You are currently running an old version of Internet Explorer that does not support some of the features on this site. For a better experience upgrade to Microsoft Edge.

Update to Microsoft Edge

Or try an alternative browser:

Chrome Firefox

Look for Backing.FileName – that shows the exact child VMDK in use.

Connect-VIServer vcenter.company.com $vm = Get-VM "troubled-vm" $snap = Get-Snapshot -VM $vm -Name "broken_snapshot" $snap.ExtensionData.Config.Hardware.Device | Where $_.DeviceInfo.Label -eq "Hard disk 1"

If a VM won't start due to a "broken pipe" or disk error, you may need to manually repair the snapshot chain:

Since the phrase can refer to two very different scenarios, this review breaks down the process, tools, and risks for both.

Vmdk Snapshot Recovery Updated Jun 2026

Look for Backing.FileName – that shows the exact child VMDK in use.

Connect-VIServer vcenter.company.com $vm = Get-VM "troubled-vm" $snap = Get-Snapshot -VM $vm -Name "broken_snapshot" $snap.ExtensionData.Config.Hardware.Device | Where $_.DeviceInfo.Label -eq "Hard disk 1"

If a VM won't start due to a "broken pipe" or disk error, you may need to manually repair the snapshot chain:

Since the phrase can refer to two very different scenarios, this review breaks down the process, tools, and risks for both.