windows 10 version 2004 mapped drive issue

Kevin Rampersad 1 Reputation point

I would like to report that all mapped networking drives on all computers fail to connect consistently after this update in our company. The servers are 2003 servers. While we were able to roll back some computers to 1909 and fix the issues, others would not let us roll back and we had to wipe them and put version 1909 back on them. I would like to mention that these updates were pushed to the computers without any input even though MS states that it is optional and you have to manually upgrade to it. Why on earth would they force this on you?

After the format, several computer auto updated again to 2004. right now my only workaround it to set the adapter in metered connection mode to stop the updates.

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,172 questions
{count} votes

9 answers

Sort by: Most helpful
  1. Candy Luo 12,646 Reputation points Microsoft Vendor

    Hi ,

    Based on my understanding, the mapped network drives are not automatically reconnected at Windows startup. After logging you will see the following scenes:

    • In Windows Explorer, a red X appears on the mapped network drives.
    • Mapped network drives are displayed as Unavailable when you run the net use command at a command prompt.
    • In the notification area, a notification displays the following message: Could not reconnect all network drives.

    Is it right? Please feel free to correct me if my understanding is wrong. If yes, you can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device.

    For more details about scripts, you could refer to the following article:

    Here is a similar thread discussed before, you could have a look:

    ---Please Accept as answer if the reply is helpful---

    Best Regards,

  2. ITWorker4545 1 Reputation point

    I am experiencing the same issue posted by JuergenFleck-6603.

    All systems are on 2004 and have verified connection to the mapped drive's UNC path.

    Mapped drives show as connected with Get-PSDrive, but do not appear in File Explorer at all. No red X's, just gone.

    When File Explorer is reset through Task Manager the drives appear as expected.

  3. MEH 1 Reputation point

    Enable SMB1 on Windows workstations:

    1. Search in the start menu for ‘Turn Windows features on or off’ and open it.
    2. Search for ‘SMB1.0/CIFS File Sharing Support’ in the list of optional features that appears, and select the checkbox next to it.
    3. Click OK and Windows will add the selected feature. Restart your computer as part of this process
    0 comments No comments

  4. Aungkana K 1 Reputation point

    I want to give more information to help @Candy Luo reproduce the problem in her lab.

    1. Background Information
      My PC has mapped drive to 2 file servers.
      a) NAS IP with drive Q.
      b) Windows 2000 Server IP with network drive S, W, X, Y

    The problem happen to only windows 2000 server not NAS. My network drive Q has no problem at all.

    1. Every day after logon to my PC and try to connect to my network drive at Windows 2000 Server. Two type of error message.
      a) The error message on drive S shown "S:\ is not accessible. The specified network name is no longer available.
      b) The error message on drive W shown "An error occurred while reconnecting W: to \\working$ Microsoft Windows Network: The local drive name is already in use. This connection has not been restored."
      c) The error message on drive X and Y are similar to W.
      1. I disconnect only drive S: while drive W, X, Y stilled mapped but inaccessible.
      2. I map network drive S: again and the error shown "The mapped network drive could not be created because the following error has occurred: The specific network name is no longer available."
      3. I have to disconnect all network drive that connect to Then I can reconnect network drive S, W, X, Y.

  5. Anonymous

    Hello all, I just found the lifesaver ;-) (for Synology NAS but probalby also useful for others)

    I had exactly the same issues with build 2004 and our office Synology NAS ; searching 2 days for a solution...

    Make sure you have the latest DSM update installed (important).

    Controle Panel
    File Services
    Enable WS-Discovery !!

    For those using SMB1 : (I was, due to some former incompatibility issues):

    Change to min SMB= SMB1 and max SMB = SMB3 (also under file services)
    Reboot NAS
    Reboot PC + re-map the NAS network drive
    Reboot PC to check if the network drive is still intact and here you go...

    0 comments No comments