tinyapps.org / blog

"Could not reconnect all network drives" #

is an all-too-common startup error in Windows. I used to work around it with a simple batch file:
   REM delay execution for 10 seconds (wait for networking to load)
   REM see http://www.robvanderwoude.com/wait.php#PING for more info
   ping -n 11 >NUL 
   REM disconnect all existing mapped drives
   net use * /delete /yes
   REM map x: drive to \\server\share
   net use x: \\server\share
saved to the All Users Startup folder as map_x.bat or what have you (it can also be launched via Task Scheduler).

Recently, I've taken to using the "Always wait for the network at computer startup and logon" policy instead:

Enable it here:

gpedit.msc > Local Computer Policy > Computer Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon

If your Windows version does not include Group Policy Editor, use regedit to create or edit the following value name:

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\WinLogon\SyncForegroundPolicy

and set the value data to 1:


Speaking of the Windows Registry, sometimes it's not clear if a path is referencing a key or a value name, as Jerry Honeycutt points out in his Microsoft Windows Registry Guide:
When looking at a key's fully qualified path, you have to figure out whether the path includes a value or not. Usually, the text is clear about whether the path is to a key or includes a value, but sometimes it isn't. For example, does HKCR\txtfile\EditFlags refer to a key or a value? In this case, it refers to a value, and I prefer to use explicit language, such as "the value HKCR\txtfile\EditFlags," to make the reference clear. Sometimes, paths that don't include a value name end with a backslash (\). If there is no backslash, pay particular attention to the context to make sure you know whether the path is just a key or includes a value. Sometimes a bit of common sense is all you need.

/windows | May 11, 2012

Subscribe or visit the archives