Unfortunately, 64-bit Windows will restrict the ability to load 32-bit drivers, which is why the VMDK mounting utility is failing. I found that purports to be able to work around the problem by simply installing it in the Program Files directory instead of Program Files (x86), but it did not work for me; perhaps you will have better luck. You could also look for a third-party tool like, but alas, they too need to use a driver, which gets blocked—yes, even when installing/running as administrator (the for VDK is available, so someone may take up the task of updating and compiling it for 64-bits). Actually has a 64-bit version, but unfortunately it only supports read-only for VMWare disks. There are on the VMW boards about this and it seems that the just doesn't support 64-bit Windows and that a newer one is included as part of the developer tools (as though only devs would need such a utility). So your options are to use the vmware-mount utility from either the or the newer which contain a more recent copy of the mounting and disk management utilities. (Even these install as 32-bit by default and include a zip file with 64-bit versions of a few of the files including the disk management utility, but not the mounting utility.) You can mount a VMDK file with this, but note that it mounts as read-only by default; for write capability, you must use the /m:w switch, and even then, Windows keeps giving a path not found error when trying to change/delete files on the mounted volume.