SimonJMBrown's Posts

Thanks for attempts to help, nothing worked so now having to go back to old backup and take consequences. Workstation caused this problem simply using built in defragrmentation option decided I had a virus (pretty **bleep** sure wasn't, dev machine with VS, Postman, Node.JS etc). That is what removed the slice. @wila diskmanager was tried much later in the process to try and recover, it was not the cause. The slice replace didn't work either. Started to load VM but then errors and windows options to repair appeared, tried all the options but none would work Not first time had workstation "utilities" cause problems. Its great when working as intended, awful when a problem.  Lession learn't, make more frequent backups and DEFINATELY dont use any of the VMWare tools until a backup done as well.  

Tried repair line, comes back instantly. Trying to load VM again I get a new error; /edit All new to me this, not finding much on how to resolve a parent-child issue mentioned. I tried the -e option to diskmanager and it gives more info, but I don't see a way of correcting the problem. Seems good at telling me the issue but not at pointing in right direction to resolve, better still a tool to fix! C:\Program Files (x86)\VMware\VMware Workstation>vmware-vdiskmanager.exe -e "C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev-000004.vmdk" Failed to open the disk 'C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev-000004.vmdk' : The parent virtual disk's capacity is not the same as child's capacity (0x3ec3). Disk link C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev-000004.vmdk successfully opened. Disk link C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev-000001.vmdk successfully opened. Cannot establish parent(C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev-000001.vmdk) - child(C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev-000004.vmdk) relationship: The parent virtual disk's capacity is not the same as child's capacity (0x3ec3). Parent link description Name: C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev-000001.vmdk Create Type: twoGbMaxExtentSparse Capacity: 85899345920 Content ID: 2832678526 Parent Content ID: 2859411184 Child link description Name: C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev-000004.vmdk Create Type: twoGbMaxExtentSparse Capacity: 81637933056 Content ID: 1428822893 Parent Content ID: 870683872 Disk link C:\Users\simon.brown\Documents\VMWare\Windows 10 Dev\Windows 10 Dev.vmdk successfully opened. Disk chain is not consistent: The parent virtual disk's capacity is not the same as child's capacity (0x3ec3).

Ok, so even though says file missing, it is there and I can browse to it and starts VM but then get warning.   Looking at the 000004 file I notice that one entry is physically missing; RW 8323072 SPARSE "Windows 10 Dev-000004-s017.vmdk" I had earlier removed a snapshot through snapshot manager. I can only assume S017 was that file.  I did try removing that entry from the .vmdk but still fails. I looked at parent .vmdk referenced in 000004 file and that one, and its parent files all exist. To your questions: No -tmp file in folder There is a lck file, i have seen this before, renaming it aside and trying to load VM again made no difference. files output attached and the .vmx renamed to allow attaching here. Thanks for assistance so far, my backup is older than I thought /edit Added 000004 file as requested

I had checked there, nothing in history. Does not look like windows/Anti virus determined this error message. Feels like VMWare has and deleted file. I am not sure if others have been, not got past this one yet. Is there any type of audit log of these activities to understand what Workstation has done?

Eventually after trying other options. I uninstalled and installed 16.0, which still didn't work. Then upgraded to 16.1.1 and (thankfully) my VMs load again. Day lost with it all. I will not be performing upgrades so quickly in future!

edit 2 Uninstalled, installed 16.0 (VMs still failed to run with internal error). Then upgraded to 16.1.1 and back working. Lost a day to this poor upgrade. /edit Reverted to old version, still not working and backups don't work either? Really need to get a fix for this, I now have 12 VMs that are dead!   Happened to me as well, most of my VMs now show Internal error on starting. Tried old remove lck files approach, no good. Tried backup VMs, same problem. 3 of my main VMs do start but 7 others don't so far. Not trying uninstall to go back to previous version in hope it works.. and the 3 that did work don't suddenly stop working. Not a happy customer, lost most of day on this now and still not in working state. How can a bug like this get through QA?