Windows 10: mapped drive disconnects after reboot in windows 2004

after windows 2004 update from 1909 mapped drive is disconnecting all the time after reboot.

:)

 

Mapped drive disconnected after reboots

Since fall creators update I am seeing one of my mapped NAS drives always in a disconnected state after a reboot. It’s easily fixed by clicking the drive displaying the red x in explorer to establish the connection. But it seems strange that this has only started after fall creators and is the only one of three mapped drives doing this. And this same mapped drive is mapped in identical state to another machine running fall creators with no such issue. Any ideas on how to fix this? Or why it is happening. It’s only a minor niggle and can live with it as there are no pressing dependencies on the mapped drive but would be nice if there was an easy quick fix

thanks, Wayne

 

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?

 

Mapped drive is disconnected after reboot

Hello,

I have a computer that runs Windows 10, I have a mapped drive to a network share, after I reboot my PC Windows Explorer display a red "X" on the icon of the mapped drive. However, if I try to access or
browse the mapped drive, it reconnects quickly. It is not a big problem for me but I do have backup software running and when drive is disconnected I get an error message. What can I do to prevent my network drive from disconnecting?