Hello everyone! Last night I was working on a virtual machine when the power suddenly went out. After this unexpected shutdown, I can no longer start my Parallels virtual machine with the Windows 10 operating system. It contains important files for my work. When I launch Parallels, my virtual machine is not listed. And when I try to open "Windows 10 work.pvm" an error appears, as shown in the screenshot. Has anyone encountered a similar problem and knows how to get the virtual machine to work or, at least, retrieve the data from it? Unfortunately, I didn't manage to make any backups and never thought something like this could happen... I would be very grateful for any advice or help.
Hello @DarranB , We have created a ticket 54***23 with our Support team and we will be contacting you shortly to assist you. Thanks!
Don't you have even Apple's Time Machine backuping which exist in last version even this feature gonna be no more supported? You can backuping this way even to SD-card if not other HDD... I know "everyone is general after the war" but having a Backup is an easy things nowadays... I have that Time Machine to more places plus Acronis also to more places... I'm mentioning Time Machine because Parallels especially supports it. Keep going m8. K
I tried numerous solutions, including rebuilding the virtual machine with the same configurations. After the rebuild, the error disappeared, but the virtual machine still wouldn't start. The launch window would open for a moment and then immediately close. However, I found a way online to recover the files using Hetman Partition Recovery. I mounted the "windows 10 work.hdd" virtual disk in the program, scanned it for files, and successfully saved them to a flash drive. After that, I immediately created several backups and uploaded them to cloud storage. P.S. Always make backups - anyone can find themselves in a similar situation. Thanks to everyone who responded and tried to help! For those who are interested, here is the article that helped me: https://hetmanrecovery.com/recovery...ver-files-from-damaged-parallels-on-macos.htm
It may be an issue with a "Lock" file. Go to the location of the VM - right-click (control-click) and "show package contents" - look for a file with the extension .LOCK. Delete it and try to restart the VM. In VMs - lock file happen when memory is in use. If you do an unexpected shutdown (power off) then those lock files sometimes don't clean up and will prevent the machine from starting. This can happen sometimes if you move machines improperly as well.
