Windows 10: Explorer crashes after right clicking on MS Office files.

Hello,


I have a problem on my new HP laptop. Every time when I right-click on a MS Office file, explorer.exe crashes. It is important to note that this happens only with "new" file extension (happens for .xlsx but not for .xls). But I can open them when browsing from Excel or PowerPoint. With other files it works properly.


There was no such problem yesterday. My recent activities: I have installed some programs, including Google Drive Sync for PC and activated OneDrive. Also there is McAfee antivirus preinstalled on my PC. I suppose the reason could be one of the programs I have listed.


I have already tried solution with ShellExView. It showed McAfee as pink in the list, but disabling it appeared to be useless. What can you suggest?

:)

 

right click crashes explorer

It's a WIN 7 glitch, Registry problem. Could be caused by a lot of apps, especially AV/AS.

See here;
http://www.sevenforums.com/crashes-debugging/19169-right-click-causes-explorer-crash-fix.html
*Toast :toast:

 

File Explorer - Right click and crashing


Hello

Please see my You Tube Demo video - when I right click on a file within File Explorer on Windows 10 it crashes; here is a video demo of the crash - as you can see the Bar down the bottom is disappearing

Please can anyone suggest a fix.

 

File Explorer crashes after Right Click in Desktop


Download: ShellExView - Shell Extension Manager For Windows
NOTE: download version 1.97 or later, else Restart Explorer won't work in step 4

1. This program does not require installation, just right click and run as Administrator
2. From the menu, click on Options then click on Filter by Extension Type and select Context Menu. Also put check marks as shown
   
   
   
3. Click on the screen, Hold down CTRL Key+A to select all then click on the red button on top left corner to disable all.
4. Click on the Options again and select Restart Explorer
5. Now try to right click on desktop to see if it fixes your problem. If it does then start to enable one by one and repeat step 4 until the problem occurs again, that's the offending extension.