Recovering HDD space screws up the Windows 10 VM

Discussion in 'Windows Virtual Machine' started by RodrigoG1, Nov 22, 2016.

  1. RodrigoG1

    RodrigoG1 Bit poster

    Messages:
    7
    Hello,

    Last week, after shutting down the Win 10 (anniversary edition) VM I went and click on the "Recover space" (Recuperar in spanish, I'm not sure if it's "Recover" or "Compress" in English). After that I took a Snapshot of the VM, as I was going to update some stuff.

    After that, I started the VM and I was never able to boot up Windows again. It always went into "Diagnosing" and "Trying to repair", never able to repair anything. I blamed the Snapshot, as I had been doing the Compressing for ages without problems, and had to go back to a backup.

    Today I did the Compress again (no Snapshot), on that same VM. And boom! I can't boot it up again. The same behavior. As I write this I am copying the backup I made yesterday. Not going to waste a whole day trying to recover this.

    I am guessing that something is wrong on the new version (I have version 12.1.1 (41491)), which I installed last week before doing the previous Compress. I haven't used that on any other VM, and seeing that it has screwed up my VM 2 out of 2 times, I wont use it again.

    Has anybody seen something similar?
     
  2. TroutDeep

    TroutDeep Junior Member

    Messages:
    14
    I observed this today.

    After shutting down the Windows 10 (fully updated) VM, I manually reclaimed space. Strangely, after that completed, it still reported that about 500 MB was still reclaimable. After reclaiming again, it still reported that the same amount (about 500 MB) was available to be reclaimed. At that point, I tried booting the VM again and go the symptoms reported above. Windows tried to repair the disk, but failed. So, there appears to be a bug that results in incorrect space reclamation, resulting in some degree of disk corruption.
     
  3. RobT

    RobT Bit poster

    Messages:
    2
    Just got badly bitten by the same bug. Any suggestions?
     
  4. RodrigoG1

    RodrigoG1 Bit poster

    Messages:
    7
    I had a VM that I could keep doing this without problems. I didn't do this anyway for several weeks. I updated to the latest version (12.1.2 build 41525) some weeks ago and today I tried.. and boom! The VM is screwed. It's a different error in Windows, but it is still starting up and I can't do anything at all.

    Parallels needs to fix this ASAP, or at least investigate and tell us why this is happening.
     

Share This Page