For what it's worth, in our particular situation applying the new Windows 10 202H update fixed the issue.
Mapped Drive will not connect after reboot
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
After a recent windows update I have had multiple issues with my network drives on my home network. Some of these were caused by my router which I have replaced. Now I have all but one drive working correctly. I cannot figure out the one remaining problem.
If I map the drive by the name (\MyBookWorld\Public) the map works OK until I reboot. After reboot, I get the error of "The Specified network name is no longer available". I cannot connect to drive via start>>run either. If I try to access the drive by IP address using start>>run, it works.
If I disconnect the map drive and reboot, I can connect from start run to the drive after every reboot.
If I map the drive by IP address, reboot and then try to use the drive, I get "Microsoft Windows Network: The local device name is already in use". Net use shows the drive disconnected and has an entry to the unc name. It works if I use start>>run to the UNC name.
I have verified that smb is enabled on the machine. I have made sure the services of "comptuer browser", "LanmanServer", and "LanmanWorkstation" are set to automatic start.
I have removed the mapping, made sure that it was not in the net use list in the command prompt and made sure the registries at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 for this drive have been removed.
I have added the mapping to the Hosts file.
I tried mapping to a different drive letter and get the same problem. Any ideas on what in Windows is messing this up?
Windows for home | Windows 10 | Internet and connectivity
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
52 answers
Sort by: Oldest
-
Anonymous
2020-11-19T13:54:06+00:00 -
Anonymous
2020-11-19T14:33:11+00:00 Adding the following Registry Entries solved my problem.
HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>CurrentVersion>Policies>System
add DWord(32bit): EnableLinkedConnctions
Set Value Data to 1
HKEY_CURRENT_USER >Network>Drive Letter
add DWord(32 Bit): ProviderFlags
Set Value Data to 1
-
Anonymous
2020-11-30T08:59:21+00:00 Adding the following Registry Entries solved my problem.
HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>CurrentVersion>Policies>System
add DWord(32bit): EnableLinkedConnctions
Set Value Data to 1
HKEY_CURRENT_USER >Network>Drive Letter
add DWord(32 Bit): ProviderFlags
Set Value Data to 1
Hi!
What if the folders does not exist. Can I create them? Right clicking and chosing new does not allow for a folder to be created.
I am missing CurrentVersion>Policies>System and >Drive Letter
-
Anonymous
2020-11-30T12:44:51+00:00 Hi,
Looks like with latest updates of version 2004 the HKLM may not be necessary. I just noticed I don't have this entry either after installing the latest updates.
The HKCU is still there and the NAS drives still correctly map.
Thx
-
Anonymous
2020-11-30T13:01:16+00:00 Roger!
Then this will not help me, as this is still a issue for me.
I am on windows version 20H2.
I did try a lot of tips when I googled this, adding things to task manager or startup folder running scripts and what not without luck. Some of them worked, but slowed down windows explorer, and it did not work ones I fixed that. It was so slow it was faster to just disconnect and reconnect everytime.
Kind of annoying to reconnect everytime I boot up my PC though.
The search for an solution contiunues.