Windows 10: File Explorer not responding when browsing one specific drive

Hello, I have several drives on my Windows 10 computer.
But when I'm browsing through one of these drives, E:, it get's incredibly laggy.
Sometimes it gets unresponsive or takes up to one minute to just rename a folder.
I have no problem with File Explorer in any other HDD nor on my SDD.

I find it weird because most of my programs are installed on this drive and they run smoothly, but it is only when I'm using File Explorer to browse, say, my music folder, that it stops working.

Passed SMART test by the manufacturer tool.
sysdm.cpl is also set to run at best performance

I'm at my wits ends already.

:)

 

File Explorer Not Responding

Hi,

I am following very clear instructions online in order to fix File Explorer Not Responding on my brand new computer. Instructions I am following are at this link: https://www.****/knowledge/windows-10-file-explorer-wont-open-solved/

I can get as far as Step 4 where I try to right click on Quick Access within the File Explorer but because it is Not Responding this action does not work and I have to close File Explorer.

Does anyone have suggestions for how to get around this when File Explorer is Not Responding?

Alternatively, should I consider storing larger files in a different drive of the computer?

A little background: I have had this computer that came loaded with Windows 10 for about 1 month. The File Explorer would not respond when I first started using it (transferring in new files), and again recently when I have tried saving several (large) design
files from Illustrator. This may be the culprit for it's bogging down; either that or perhaps because I just deleted 1000's of emails off of gmail? My text display size is at 100%.

Thank you.

ps I am not very computer savvy so please dumb down your responses!

 

Explorer stops responding when browsing network share.

I have a bunch of Windows 10 computers where explorer stops responding once I browse to a network share on a Server 2008r2 box.

It seems to happen on specific folders within the share.

It happens if browsing via IP, UNC or a mapped drive.

Computers are all attached to a domain.

Path is under 20 characters.

I've taken a new W10 install on a different computer, left it off the domain, with no software installed and try to browse the files the same thing happens.

I can browse the affected server from other clients (Win7, Server2008, even XP!) with no issues.

I've looked at the following:

Explorer.exe crashes when searching inside mapped drive

If I browse to the location from notepad, for example, it crashes notepad.

I've turned on "Always show thumbnails, never icons" in the explorer options and setting "Details" view as the default.

 

File explorer not responding

Hi Sue,

After an update, your PC can sometimes cause software conflicts. We would like to know more about the File Explorer not responding. Please provide answers to the questions:

• Can you please tell us if this update was a regular security update or the Fall Creators update?
• When you saw a dialog box, did you see a particular error message? If yes please send a screenshot.
  
• Did you perform any troubleshooting steps to resolve the concern?

We'll wait for you response to our queries.