Workstation Pro 12.5.5 running on Windows 7 Pro 64-bit
I've enabled shared folders in Virtual Machine Settings/Options as "Always enabled" and map as a network drive in Windows guests. The host path and share name are set in the Folders view and the Attributes are set as Enabled.
In a Windows 7 Pro guest, I've mapped the share as a drive.
Every time I start the guest (since release 12.5), the guest comes up with the "Could not reconnect all network drives" warning. If you click on the status bar icon for the network drives, the above created share shows as disconnected yet, if I click on it, the shared drive opens (kind of like kicking it to wake it up).
This behavior didn't happen in previous releases. How do I get the guest to reconnect to shared drives at startup automatically?
I had the same problem, I noticed as I loaded different VM's that the issue appeared to follow the upgrade of the client tools package.
I first tried a number of things none of which helped.
What did work was turning off auto-update of tools and uninstalling the VMware-tools-10.1.5-5055683
I tested a number of older versions and the problem remained I finally jumped all the way back to 10.0.0-3000743 and the problem was resolved.
(Don't forget to drag the older version into the VM before you uninstall the tools).
Note you can find older releases here:
Thanks. You saved my day!
Anyway I cannot understand why VMware didn't get this problem solved from so long time. I think we won't have this one solveved anymore. I'm frustrated by this behaviour.
I'm seeing this behavior too. My guest is running Windows Server 2008 R2 Enterprise with SP1. I'm running VMWare Tools 10.1.6, build-5214329.
What I'm seeing is that for some reason VMWare Tools is taking a long time to start running. So that when the OS starts coming up and connecting shares, VMWare Tools isn't running yet so there's no connectivity to shares on the host. I noticed this because I've also noticed that it takes a while for the Unity Mode button to enable.
When it's finished starting up, I have to bring up a folder explorer and click on my shares for them then to see that they can connect again. Applications that try to access those will fail until I bring up that folder explorer.
Uninstalling and reinstalling VMWare tools hasn't helped either.
I to have the same issue, but with Fusion 8.5.8 running various different windows versions.
Deeply disturbing that I see nary a word in the knowledge base about this problem.
I don't have the time or energy to revert to a previous version of Tools.
This issue STILL needs to be addressed...
I ran into this problem a long time ago and just used the old version of tools as advised by JHP99.
I recently upgraded to Workstation 14 and was frustrated to see the tools package included still did this and did some more digging.
The registry fix posted in this thread totally fixed it for me! I recommend anyone still experiencing this to try latest tools package with this registry tweak.
1) run regedit
2) navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmhgfs\
3) edit the registry value "Start" REG_DWORD which is currently 3 (DEMAND START) and change 1 (SYSTEM START).
4) exit regedit
5) reboot the Windows VM.
I continue to have this issue. I've tried several 'solutions', including uninstalling & reinstalling VMWare Tools, and the registry change.
When I start my VM, I get the 'Could not connect to all network drives' error message and below/attached is what I see in Computer.
Running under VMWare Workstation Pro 14
Guest: Windows 7 Home Premium SP1 x64
Host: Windows 10 Pro x64
jam3972's registry mod worked for me. Thanks! Saved me a lot of irritation. I only recently noticed the issue, but also haven't used VMware on this computer in a while. Running VMware Fusion 8.5.10, VMware Tools 10.1.6.5214329, MacOS 10.13.6 (High Sierra) on a mid-2010 13" MacBook Pro.