Windows 10: Windows 10 Explorer is not responding for downloads folder

Yesterday suddenly Windows Explorer stopped working for the Downloads folder. Clicking on it just gives the Not responding message forever. Tried the solution of restarting Windows Explorer, then restarting the computer; did this repeatedly.

I can still access the contents of the Downloads folder from within apps, though. Also, I can use Windows Explorer to look at 'This PC', and it shows the Downloads folder as normal. Clicking on it, though just hangs.

Anyone?

Thanks, Ron

:)

 

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.

 

How to make vista display same icon size for all opened folders in explorer ?

Some suggestions

 

Share folder related "not responding" in Explorer

20 years ago when you access some shared folder on other PCs that is unaccessible will render your Explorer not responding for a long time, like 10+ seconds.

For Windows 10 the above problem is solved, but there are still problems related to shared folder.

(1) If you access some unaccessible shared folder then go to other locations in Explorer, although Explorer won't get not responding, it will pop up unaccessible messages later when you are doing other unrelated things. If the user goes away, the access
should be canceled.

(2) When you add some shared folder to quick access list, then when you drag some items in list to reorder them, Explorer becomes not responding again. When I remove all the shared folders from the list, the problem disappears. So I assume this is again
due to unaccessible shared folders in the list.

There may be other related problems. The solution is to change all the code to deal with shared folder to an asynchronous way with cancellation.