question

JohnCartwright-7308 avatar image
0 Votes"
JohnCartwright-7308 asked GaryNebbett answered

Why wont Windows 10 Pro 2004 reconnect my network drives on restart?

I am running Windows 10 Pro 2004 build 19041 on a "Dell XPS 15 7590" laptop.
On restart, or after sleep, my Dlink network drives never reconnect, however my WD MyCloud drive usually, (but not always), does reconnect.
To recover the situation I have to disconnect the affected drives, but can not remap them without first restarting the laptop.

windows-10-network
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.


Just checking in to see if the information provided was helpful.

Please let us know if you would like further assistance.

0 Votes 0 ·

Please Accept as answer if the reply is helpful.

0 Votes 0 ·
didier3001 avatar image
0 Votes"
didier3001 answered

Hi @JohnCartwright-7308

The bug itself listed in the article below is for an older version of Windows 10 but the workaround should still work:
Mapped network drive may fail to reconnect in Windows 10, version 1809

And here with more details on the steps: link

3 other things you could try / check:
1. Can you also try if configuring the "always wait for the network at computer startup and logon" policy in Computer Config\Administrative Templates\System\Logon affects the problem?
2. If you have mounted these network drive with FKDN, can you try to mount them with IP address instead?
3. Do you have any third party firewall enabled?

Regards,
Didier3001

--I hope this helps. Please Accept it as an answer and "Up-Vote" the answer or message(s) that helped you so that it can help others in the community looking for help on similar topics


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JuergenFleck-6603 avatar image
0 Votes"
JuergenFleck-6603 answered CandyLuo-MSFT commented

I have the same issue in a customers network. All new HP ProBooks, upgraded to build 2004 and the network drives disappear or do not connect at startup. When I check with "net use" the drives are mapped but in the windows explorer they do not show up at all (no red cross).

Before the new laptops came, I connected with a GPO and changing the GPO to "replace" mode does not help. I deactivated the mapping by GPO and manually mapped the drives (from windows explorer and with "net use v: \\server\share /persistent:yes). Same issue.

Then I did the number 2 of the post of @didier3001 , mapping the drives not with FQDN, but with IP adress, did not help too.

My customer is very disappointed and I can only help him with some creepy workarounds ... :-(

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Based on my understanding, the network drives disappear in GUI (windows explorer) but you can check the drives are mapped with "net use" command. Is that right? Please feel free to let me know if my understanding is wrong.

If yes, I will try to reproduce this phenomenon in my windows 10 2004 and will get back to you as soon as possible. I appreciate your patience.

If you have any updates during this process, please feel free to let me know.

0 Votes 0 ·
MKLKMKLK-5328 avatar image
0 Votes"
MKLKMKLK-5328 answered MKLKMKLK-5328 edited

We have a same problem, but this opinion totally wrong:
" the network drives disappear in GUI (windows explorer) but you can check the drives are mapped with "net use" command. Is that right? P"

The truth is, that network drives are present in GUI with red X sign, and when I click on it to try rebuild the connenction, a window appears with a message something like this: "Error to reconnect G: - Microsoft Windows Network: the local device name is already in use. The connection failed."

I connected a share earlier - before a restart - with \\IP\share_name format. When we tried to change it to \\FQDN\share_name , on some windows instances it worked till the first restart: after that FQDN connections all failed, and when we retried with \\IP\share_name format, it worked. After that, after a restart some shares are OK by IP, some by FQDN name, but when one is OK with IP it definiatelly fails with FQDN and vica versa.

Nothing changed at share(s), and all is totally OK when we try to connect either from a Windows 10 earier builds or Windows 7 clients, so the problem surely connects to a Windows update happened in august.

My Windows 10 2004 version now is: 19041.450.

Any help or advide would be appreciated!

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JohnGalloway-4565 avatar image
0 Votes"
JohnGalloway-4565 answered

Edition Windows 10 Pro
Version 20H2
Installed on ‎11/‎07/‎2020
OS build 19042.630
Experience Windows Feature Experience Pack 120.2212.31.0

Netgear ReadyNas Duo with 3 mapped shares.
On initial boot, 2 of the 3 display Red X in File Explorer. None will reconnect. Says 'Local device name is already in use' or 'Specified network names is no longer available' (varies)
Net Use lists all 3 drives as Disconnected.

If I 'Restart', then the drives either re-connect properly, or if displayed with Red X, reconnect when clicked on.

Have tried the workaround for version 1809. And enabled "always wait for the network at computer startup and logon" policy.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

CharlesSampson-2731 avatar image
0 Votes"
CharlesSampson-2731 answered

Same problem here with Windows 10 Pro Ver. 20H2 @CandyLuo-MSFT. I have a login script that runs from my Domain Controller and connects a number of Network Drives, but will not connect any when the user logs in.

Even if I go to the local computer and try and Map Network Drive, the default drive letters I use for these drives are not available.

I cannot use the work around suggested as Power Shell is disabled on all of my computers as this is a very easy utility for viruses to access computers and the network.

Any other help would be appreciated.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Frode-5147 avatar image
0 Votes"
Frode-5147 answered JohnGalloway-4565 commented

Same problem here with Win10 P 2004 and 20H2. I have seen this problem since we accidentally got 2004 on some PCs when 2004 first came out. So far I have circumvented the problem by installing version 1909 for the unlucky users (downgrading). Now I got a new batch of laptops with 20H2 pre-installed, and I'm trying to fix this problem, without luck. All our users have at least 2 drive-mappings to shares on a Qnap NAS, most have 3, and some have 4 or 5 shares mapped. This works fine in Win10 P 1909 (and in Win7p). In Win10 p 2004, it works fine to map new drives, but reconnecting after reboot doesn't work.

Our windows PCs don't have any passwords, and no profiles are stored. We do not have any domain, no MS accounts and no stored passwords. All computers are common or non personal, with no user files stored on the local HDD. All our files, and log-in security, are on the NAS.

When mapping drives for the first time, I tick the box for "Reconnect at Logon" (my windows is in Norwegian, so the wording might be a bit off). This works fine on 1909 - When users start their PC, they open the filemanager, click on the stored share name, and is prompted for the username and password for the NAS. After doing this for the first share, the other shares for the same NAS open without additional password entry.

On 2004, it works OK with one mapping, to one share, but if you store 2 or more shares, there is no way to use those share-mappings next time you start the PC. Error messages like: Local device name is already in use' or 'Specified network names is no longer available' or (something like) 'Cannot log in with different user accounts' (varies).
If I then delete the stored drive mappings to NAS shares, I can recreate them just fine, but for most users it is a big hassle having to enter the network path and share names. This is in a school, and most of the teachers have only 5 minutes to log in on any available PC to get hold of their stuff, and have no time to recreate drive mappings first.

It has become more and more difficult to use windows in an open, mixed network environment over the years. It looks like Microsoft wants to make it difficult to use any other service or solution other than their own. I hope that is not the issue in this case, but so far I have not been able to solve this problem. Any help is welcome.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Bizarrely, I've found that the inital logon of the day doesn't map any of the 3 shares on my Netgear ReadyNas, but then Start | Power | Restart brings the system back with everything as it should be.

0 Votes 0 ·
AlanBarker-6977 avatar image
0 Votes"
AlanBarker-6977 answered

I've also had the same problem since updating my 3 systems to 2004. On reboot I have to re-connect them to my Buffalo NAS drive.
I now have all systems on 20H2 but still the same problem.
Surely Microsoft should have solved this problem by now.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HGRitticuss avatar image
0 Votes"
HGRitticuss answered

Why is it good practice to use Net Use? The connection can be added in the GPO so when is Microsoft expecting to fix this obvious issue?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GaryNebbett avatar image
0 Votes"
GaryNebbett answered

Hello All,

It is probably a bit late to be useful in this thread, but I think that I have an explanation for what happens. I am maintaining and updating the explanation here: http://gary-nebbett.blogspot.com/2021/06/mapped-network-drive-reconnection.html

Gary


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.