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

John Cartwright 1 Reputation point
2020-08-01T10:13:31.5+00:00

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
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,274 questions

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Didier3001 971 Reputation points Microsoft Employee
    2020-08-01T10:32:13.847+00:00

    Hi @John Cartwright

    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

    1 person found this answer helpful.
    0 comments
  2. Juergen Fleck 6 Reputation points
    2020-08-27T09:25:29.053+00:00

    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 person found this answer helpful.
  3. MKLK MKLK 6 Reputation points
    2020-09-03T07:59:15.567+00:00

    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!

    1 person found this answer helpful.
    0 comments
  4. John Galloway 6 Reputation points
    2020-12-02T15:45:29.523+00:00

    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.

    1 person found this answer helpful.
    0 comments
  5. Charles Sampson 6 Reputation points
    2020-12-07T13:34:05.47+00:00

    Same problem here with Windows 10 Pro Ver. 20H2 @Candy Luo . 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.

    1 person found this answer helpful.
    0 comments