Mapped Drive will not connect after reboot

I have exactly the same problem and have tried everything that you have. If you disconnect the mapped NAS drives initially the NAS cannot be connected using UNC, but after a short while it will connect and then mapped drives can be reconnected. There is no need to reboot first.

This has happened with more than 1 Windows 10 computer but not all on the network.

I have been searching for an answer for months.

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?

I have had the same problem with all my mapped drives, on a Synology NAS, I think  since the last Windows update, a few days ago. I haven't found any way to stop it happening, but I have found an easy way to restore the drives. Go to the command prompt, and type in the following instruction:  **net use * /delete.**after this, the drives can be remapped in File Explorer. Obviously not ideal, especially if you have a lot of drives, but an easy way to get up and running again. Hopefully, Microsoft will identify the bug and stop it happening.

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

Hi

I have the same experience as MalcolmSmith2, also on a Synology NAS, and his solution works for me. I quote:

 Go to the command prompt, and type in the following instruction:  net use * /delete. after this, the drives can be remapped in File Explorer. 

This doesn't stop it happening, but at least it gets you up and running again fairly quickly.

unfortunately not a solution, but a work around. not ideal.

Hi

I have the same experience as MalcolmSmith2, also on a Synology NAS, and his solution works for me. I quote:

 Go to the command prompt, and type in the following instruction:  net use * /delete. after this, the drives can be remapped in File Explorer. 

This doesn't stop it happening, but at least it gets you up and running again fairly quickly.