Windows 10: Mapped Drives hanging Windows 10 File Explorer

For the past month, File Explorer has crashed. They are not marked with a red X however when I click on them they do not open. Rather, File Explorer stops responding. I eventually have to restart File Explorer using Task Manager.What seems to work is unmap and remap. When I deallocate, it takes an ungodly amount of time. When I remap, it quickly remaps.

:)

 

Mapped Drives hanging Windows 10 File Explorer

I have several mapped drives on Windows 10. All have been for years. The past month or so, two of them have been hanging up File Explorer. They are not red-x'd out. Yet, when I click on them, they don't open. Rather, File Explorer becomes non-responsive.
I eventually have to Restart File Explorer using Task Manager.

What seems to work is unmapping and re-mapping. When I unmap, it takes an ungodly amount of time. When I re-map, it re-maps quickly.

Answers or suggestions?

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Mapped Drives Issues

To clarify .... the issue is the Windows 10 OS. It is with Windows File Explorer. The Mapped drives used to appear in File Explorer's left panel list of drives and folders. Two days ago File explorer stopped show the mapped drives. so not they don;t appear in the list of Drives and folders.

- - - Updated - - -

I did, it has no effect. I also check the NAS devices they support SMB 2.0. Also I have several other computers on my home network they work fine with the mapped drives and They do not have SMB 1 turned on. So it is something that happened to the computer in question.