Windows 10: Mapped Drive not reconnecting after Windows 10 / 2004 uptate

My network typically has 3 to 4 Windows 10 computers connected and 6 or more from time to time. Also there are 3 D-Link NAS Mapped. Two are DNS-323 and these are working fine and one Sharecenter DNS-345, the one I am having issues with.


All the computers were working without network issues when they were all version 1909, but two were updated to version 2004. Here is where the problem started. Windows 1909 computers do not have this problem When the computers with version 2004 boot up, they do not re-connect to the Sharecenter DNS-345, but do re-connect to both of the DNS-323 NAS. I have found that I need to disconnect the unconnected NAS in Windows and re-add it. This in itself is an issue, because it typically is seen in the network connection window, but it is not accessible. I then use the IP address and sometimes when the window opens the address is there and sometimes it is not. But then the NAS might be accessible though the name or not. Trying again might have the address show up and then the network name might be accessable, but for sure I am able to connect via the IP address.


Unfortunately, no matter whether I connect via IP address or Network Name, upon reboot of both of the computers with version 2004, they do not re-connect to the Sharecenter DNS-345. Back to square one and removing the mapped network drive and re-mapping it. My network was bullet proof and I haven't had any issues since the issues with the Windows release from a couple of years ago. That I got around easily. This is frustrating me and I don't find any web chatter about this problem. If I could go back to version 1909 I would, but I believe that option is off the table. Can you help?


Thanks, Gary .

:)

 

windows 10 forgetting mapped drives after reboot after 2004 update

Windows 10 32bit 2004
After update all my mapped drives lost connections, I disconnected each drive and re mapped andI can access all drives
normally. After a reboot all connections fail , i can remap drives and they all work until the next reboot all all are marked to reconnect. Ran SFC and Dism no problems . I ended up reverting back to 1909 and everything working ok.
I have a couple other Pc's 64bit that have not been updated and now I am afraid of the same issue with them .
Any Advice?

 

Hard drive/ OS issue

a guy suggested :

• shutdown
• unhooked HDD
• restarted
• yay !!
• reconnected HDD
• restarted
• yay !!

also , try method 3
How do I unlock the drive where Windows 10 is installed?

 

Map Network Drive in Windows 10


Hello cognus,

I find the best way to keep a mapped drive always available is to use OPTION ONE and select Reconnect at sign-in at step 5.

The (Remains connected after next logon) command in the other options should work for you as well though.

It's normal for the mapped drive to have a red X on it after not being used for a while, but clicking on the drive should have it be automatically connected again after a short wait sorta like waiting for a HDD to spin back up after being turned off when idle.

I'm not aware of a way to keep a mapped drive to always stay active.