VMware Communities
TomNT
Contributor
Contributor

Unable to open file "/Users/NT-Technics/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk.vmdk": What to do?

Hello,

I have a problem with launching my Windows 10 in vmware Fusion. I tried to fix it in Terminal but I saw no activity after entering my pswd.

Can I try some other things?

Thanks

7 Replies
a_p_
Leadership
Leadership

Which files does the .vmwarevm package contain?

... but I saw no activity after entering my pswd.

Which password are you referring to? Please clarify.

André

0 Kudos
a_p_
Leadership
Leadership

0 Kudos
TomNT
Contributor
Contributor

After entering the following line in Terminal:

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -R /Users/yourusername/Documents/Virtual\ Machines.localized/Windows\ XP.vmwarevm/Windows\ XP.vmdk

and confirming it with Enter, I had to answer with a password. I used the standard installpassword of my Mac.

0 Kudos
a_p_
Leadership
Leadership

The command you posted seems to be for another VM (XP rather than WIn10).

Anyway, assuming that the issues is with the Windows 10 VM, open the "Virtual Disk.vmdk" in a text editor to see whether all of the "...-s###.vmdk" files which are listed in this file exist.


.André

0 Kudos
TomNT
Contributor
Contributor

I am missing "Virtual Disk-s016.vmdk". Is a solution for this issue available?

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=f585ff1f

parentCID=ffffffff

isNativeSnapshot="no"

createType="twoGbMaxExtentSparse"

# Extent description

RW 8323072 SPARSE "Virtual Disk-s001.vmdk"

RW 8323072 SPARSE "Virtual Disk-s002.vmdk"

RW 8323072 SPARSE "Virtual Disk-s003.vmdk"

RW 8323072 SPARSE "Virtual Disk-s004.vmdk"

RW 8323072 SPARSE "Virtual Disk-s005.vmdk"

RW 8323072 SPARSE "Virtual Disk-s006.vmdk"

RW 8323072 SPARSE "Virtual Disk-s007.vmdk"

RW 8323072 SPARSE "Virtual Disk-s008.vmdk"

RW 8323072 SPARSE "Virtual Disk-s009.vmdk"

RW 8323072 SPARSE "Virtual Disk-s010.vmdk"

RW 8323072 SPARSE "Virtual Disk-s011.vmdk"

RW 8323072 SPARSE "Virtual Disk-s012.vmdk"

RW 8323072 SPARSE "Virtual Disk-s013.vmdk"

RW 8323072 SPARSE "Virtual Disk-s014.vmdk"

RW 8323072 SPARSE "Virtual Disk-s015.vmdk"

RW 983040 SPARSE "Virtual Disk-s016.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "7832"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "eec4142c30c823b47e0e98c3f585ff1f"

ddb.uuid = "60 00 C2 9e 16 e8 b3 75-c1 71 86 cb d3 87 22 73"

ddb.virtualHWVersion = "12"

0 Kudos
a_p_
Leadership
Leadership

In order to fix this issue, we need a replacement for the missing file.

As a first step, please check whether the file is in the the trash, or lost+found folder.

If you cannot find it, create another (temporary) VM with the exact same virtual disk size (ensure that the numbers in the descriptor file match), and then copy the missing "...-s016.vmdk" to the non-working file's folder (rename it is necessary). With the file in place, I'd recommend that - before powering on the VM - you create a snapshot, so that the current .vmdk files won't get modified, i.e. there's a way back if required.

Depending on which data had been stored in the missing file, you will end up with more or less data loss, or file corruption in the guest OS. What you should after powering on the VM, is to to run chkdsk for the guest's partitions. Once everything works as expected, don't forget to delete the snapshot.


André

TomNT
Contributor
Contributor

I think everything is working again....

Thanks

0 Kudos