I followed Parallels' suggestion to reclaim 45GB of disk space and ended up with a corrupted Parallels Data File that cost me upwards of GBP 350 to have fixed. If I felt I had a chance of recouping that from Parallels, I would. In the meantime, I urge company to withdraw that faulty reclaim disk space function - and users should avoid it at all costs. (Latest MBP running Mojave and Parallels 15)
You know what...all my problems started when I clicked on Reclaim Disk Space about 2 weeks ago. This was when I was running Mojave and PD15. Upgrading to latest Catalina did not solve the problem. Unbelievable...
I was able to use Time Machine and thankfully I had a backup from October 1. I had to copy the entire VM from an external drive to my internal drive. I will never touch the reclaim disk space button again unless Parallels makes it clear it is safe to do so...
Hi, it's a well known problem (and very very dangerous bug) since months and no new from Parallels... S.
Hi, no it's months before and I don't keep old emails when I don't have any answer from the receiver. As you can see easily in your forums , we are a lot who have this problems and for some lose virtual machines or time to restore them. So a ticket number is not necessary... you have all the infos on forums. Regards S.
Hi, of course! Hopefully I've backups... I'm a IT professionnal since 40years. the problems is not that! the problem is the BUG! who destruct Virtual Machine who is inaceptable for a software as this and the lack of answe from Parallels
Bump. Oh man oh man I wish I had referred to this forum before deciding to Reclaim ~30GB of space on my Windows 10 install. BOTH my Windows 10 Guest hard drive and my Mac OS HOST hard drives are now corrupt. The Mac OS install is virtually unusable and I can't find any way to repair this. How in the world has this feature not been fixed or just completely REMOVED from Parallels?! This is horrendous for a paid piece of software.
I wish I found this thread earlier so that I don't need to waste a day waiting and it's still running. Had to find ways to reduce the size of my Win10 VM as its size grew at least 2GB every time I switched it on and Microsoft run its update. It's ballooning to a size that is choking and impossible to run. I tempted to force quit the process however I'm fearing that it may corrupt not only the VM but the drive that it is stored on. Awh.... Hoping that this will push it to the top of the thread in the forum so that everyone could aware of the risk.
