Attempting to map an .vmdk file as writeable via File / Map Virtual Disks fails with "there was a problem trying to map the virtual disk volume" if the directory of the .vmdk has a (direct child) subdirectory named ".vmx" (and a 0-byte file named ".vmsd" is left behind following the error). Mapping works fine if said subdirectory is either renamed or removed prior. Sighted in Workstation 10.0.4 under Win7 x64, completely repeatable.
Is there an official list of reserved file/directory names that one should avoid using while around VMware? Some are long known and pretty obvious, like .lck's, but this .vmx one was new to me.