Unable to start VM as Parallels deleting Snapshot (for ever ;-)

History
I was unable to launch Parallels as the drive on which I host the VM was low on space.
To fix I initiated the deletion of a snapshot but the Mac got shut down and deletion was interrupted.

Issue
This morning Parallels automatically launched the Windows VM on launch but was unresponsive to key presses and gave me some message that I could not use the VM because the deletion was still in progress (would be good if a future Parallels app update could check that state before starting the VM ;-).
Now I'm unable to monitor the deletion which has been running for an hour (normally takes 10-15 mins). Nor am I able to start the VM. If I try to close parallels it says "Cannot close the XYZ virtual machine window. The operation of deleting a virtual machine snapshot is currently in progress. Wait until it is complete and try again." But with no progress bar I have no way of estimating how long I'll be impacted and I'm left unsure if the system is in a working or failed state. :-(

Anyone have any experience of this or suggestions please?

Cheers,
Jim

 

Hello Jim,
Make sure that you have a backup of the Virtual Machine and follow the steps provided in the link to remove all snapshot.
http://kb.parallels.com/111736

Thanks,
Padman

 

Hi,

I'm having the exact same problem on Parallels Desktop 10 but when I try to execute the actions in the link I get this error:
Unable to perform the operation because the virtual machine that uses this disk is not stopped. Shut down the virtual machine and try again.

I can't shut down the virtual machine because it is stuck deleting the snapshot.

 

Hi, and did you try to merge snapshots? Did you get any error during merging process?

 

Yes, when I try that I get the message:
"Unable to perform the operation because the virtual machine that uses this disk is not stopped. Shut down the virtual machine and try again."

 

Thanks a lot for your reply, could you please generate a problem report using this KB?
Please reply us back with the report ID.

 

It was resolved by a Mac restart. Thanks, regardless.

 

Thanks a lot for sharing the results!