Windows 10 file explorer crash, won't open

I am having problems with my file explorer on Windows 10.  I used to have Windows 7 which worked flawlessly until I upgraded.  If I double click file explorer to open, it loads, freezes, (not responding) and closes.  This also happens from any other location on the system I try opening it at.  The only place it works is when I am in a program, Excel, Word, etc. 

Microsoft has tried to fix my issue Twice.  The only thing that works temporarily is reinstalling windows 10.  First time it worked for about 6 months, last time a week.  They've played around with graphics card, opened another test user to see if it only did on my account.  I spent 5 hours on tech support last time. 

Not sure where to take it from here...New machine at this point.  Without file explorer it makes it tough to operate a computer.

Start with this free tool:  http://www.nirsoft.net/utils/shexview.html

Disable (DO NOT DELETE) all non-Microsoft shell extensions

Reboot for the changes to take effect.

See if that fixes the problems.

If it does, then re-enable things a few at a time, reboot and see if the problem comes back

Eventually you'll figure out what's to blame - and then you can uninstall the program that's associated with it.

If it doesn't fix things, post back with these 2 sets of reports:

 

Let's try looking at these 2 sets of reports:

Report Set #1)  Please run this report collecting tool (even though you may not be experiencing BSOD's) so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

Report Set #2)  Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504

While waiting for a reply, please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:
You may not need to log temps - if uncertain, please ask.

To make it work (log the temps to a file) you have to do BOTH of the below:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.

 

usasma,

Downloading shellexview did the trick.  I only had about 10 non microsoft shells.  Turns out it was Norton 360 shell that was causing the problem.  It is amazing that you are willing to share your knowledge with general public.  I greatly appreciate your help.  It has been a frustrating situation especailly spending countless hours with Microsoft tech support.  30 minutes and I am back into all my desktop icons and file explorer.  Amazing.

Thanks Again,

James

Edited by james209, 14 December 2016 - 01:27 AM.

I'm glad to hear that this helped you out.

Just FYI - disabling the Norton extension may have stopped the problem - but that hasn't fixed it (and any other problems that may be present)>

I suggest uninstalling Norton and then installing a fresh copy of it to ensure it's nice and squeaky clean!

Good luck!