With the deleted files, and the fact that you've tried to run the VM from the base virtual disk (at least it has a modified CID), the best we can do is to try, and see whether we can restore the state form January, 24th.
To do this:
- close VMware Workstation
- backup the VMs folder/files unless already done (it's up to you, but I strongly recommend it)
- create a new, temporary sub-directory
- move all files except for "Windows 7 x64.vmdk", "Windows 7 x64-000001.vmdk", and "Windows 7 x64-000001.vmdk" to the newly created directory
- extract the three files from the attached .zip archive to the VM's folder
- inject the modified header data into "Windows 7 x64-000001.vmdk" using the utility that you've downloaded before
dsfi.exe "Windows 7 x64-000001.vmdk" 0 1536 "xxx-Windows 7 x64-000001.vmdk.bin"
- open VMware Workstation, and create a new snapshot for this VM to avoid modifications to the existing files
Depending on which data was modified when you tried to run the VM from the base disk, you may see some data corruption. In any case you should run chkdsk c: /f to have Windows check, and fix the file system if necessary.
Once the VM runs stable with the expected data, you may consider to delete the temporary directory with the now obsolete files, and delete the existing snapshots.
André
