Share via

Error on Map Network Drives Build 2004

Alan Escobedo 1 Reputation point
2020-09-04T21:35:56.18+00:00

Hi Good Afternoon ... I've some problems with the new Build [2004]

After install this build, the maped network drives, it's not working ... I'll try with a ping, and it's working fine ...
But, not work on Explorer ...

After login on my username, appear the next Command Pront Message
22745-error.jpeg

And I'll try to connect and after seconds, the explorer, not responds...

And try to back the previous version, but, this options not appear on Windows Configuration / Update & Security / Recovery

Can you help me?

Thanks

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,033 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ramesh Srinivasan 176 Reputation points
    2020-09-05T02:51:48.34+00:00

    Many users are facing this issue after installing v2004. Here are some workarounds that can help.

    Mapped Network Drives don't work in Windows 10 v2004

    Mapped network drive may fail to reconnect in Windows 10, version 1809

    0 comments
  2. Kapil Arya 7,861 Reputation points MVP
    2020-09-05T08:15:57.41+00:00
    0 comments
  3. Sunny Qi 10,916 Reputation points Microsoft Vendor
    2020-09-07T07:23:00.117+00:00

    Hi,

    Thanks for posting in Q&A platform.

    Before we go further, I would like to confirm the following questions:

    1. May I know if the map drive was disappeared in GUI (Windows Explorer)?
    2. If the map drive was still in Windows Explorer, whether the issue is a red X appears on the mapped network drives?
    3. When you run the net use command at a command prompt, what's the status of the mapped network drive?
    4. How did you map the drive? Manually or via GPO?

    Best Regards,
    Sunny

    =======================================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  4. Anonymous
    2020-10-29T15:11:45.74+00:00

    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...
    (issue that mapped network drives can't reconnect after reboot)

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

    Controle Panel
    File Services
    Advanced
    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