I have a similar problem on win7 32 bit..
When I run vmware-mounter or vdk.exe from a cmd window (admin). I can see the mounted volume via dir from the cmd window and cd to it and operate on it.
If I try to invoke explorer drive: from the cmd window, it complains that the drive isn't available.
If I try mounting from a .bat file running it as admin, the mount fails.
In no case can I access the files on the 'mounted drive' from win7.
I CAN access the drive if I mount it as a drive on a virtual machine using workstation 5.
Microsoft seems to have royally messed up the interface to 'mounted' hard drives and ended up with two different, independed, file systems.
How can we straighten this out? The author of VDK doesn't seem to have released any recent updates but the source code is published. Someone might be able to 'fix' it so it works with win7.
Perhaps someone can get vmware and microsoft to cooperate on fixing this problem. I hope so. Win7 has some nice features, but it also has some major frustration points.
HELP!