Share via

Win7 Windows Explorer crashing when I right-click

Anonymous
2019-05-13T22:56:46+00:00

I've recently run into a weird problem.  When I'm in Windows Explorer and I try to right-click on a folder in the left window (the file system tree) Windows Explorer immediately crashes and restarts.  The menu doesn't even pop up.  Just *boom*.  Dead.

I can left-click okay in the file system tree, and if I right click on the exact same folder when it's in the right window, it works fine.

I'm running Windows 7 Pro with SP1.

Recent changes to my computer:  I added a 2-port USB 3.0 internal card, and a 10 TB external drive connected to that card maybe six weeks ago.

The problem seemed to crop up when I finally got around to organizing my files over the weekend on the 10 TB drive.  I moved a bunch of stuff, consolidated, removed duplicates, reorganized, etc., and that's when the problem became apparent.

I followed the advice from the MS tech here, and it still happens. 

https://answers.microsoft.com/en-us/windows/forum/windows\_7-performance/windows-explorer-in-windows-7-keeps-crashing-and/c6fddc14-7649-4334-ac9a-6d049fd503bd

I've also noticed that sometimes Windows Explorer takes a really long time to look at something on the 10 TB drive... not sure if it's related or just the size of the drive.

Thanks.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2019-05-14T04:24:10+00:00

    What is your system make and model?

    When you right click from Explorer Windows (should) offers the right click menu of things that come with Windows and perhaps some other things that have been added to the right click menu from other programs you have installed (scan this file, play this file, etc.) and those offerings are Explorer Extensions.

    When Explorer crashes on a right click the cause is usually an out of date or incompatible extension that has been added - not one of the right click options that comes with Windows.

    Using a program called ShellExView you can view all the Explorer extensions and perhaps using a process of elimination zero in on the afflicted extension by disabling all the non MS extensions and see if the problem is resolved.  If the problem is resolved then one of the non MS extensions would be suspicious.

    Next you can enable the non MS extensions one at a time or in little groups until the problem returns and through a process of elimination zero in on the one extension that when enabled causes Explorer to crash on right click.

    Here are some instructions that have helped on certain systems and then some general instructions about how to isolate an afflicted Explorer extension:

    If you mean you are seeing something like this:

    ![](https://learn-attachment.microsoft.com/api/attachments/f12de01e-7245-409c-b87f-ee7d870bdc50?platform=QnA)

    If that is the case, read this:

    Perhaps you have an afflicted Explorer Shell Extension.

    Explorer Extensions make up the list/menu of things you see when you right click something.  

    An afflicted Explorer Shell extension can cause Explorer to crash - especially when using copy/paste and/or drag/drop and often to/from an external USB attached drive or device.

    Several recent incidents involving Acer and ASUS systems and MyWinLocker from EgisTec (which is already known to include some troublesome Explorer shell extensions) which may have come preinstalled on your system.

    ** Note:  You may see this issue after the installation of Windows Update KB4038777 but the Windows update is not the problem - the update patches security holes that bring the real problem to the surface.

    Even if your system is not from Acer or ASUS it may have MyWinLocker installed and since there have been many reports of it contributing to Explorer crashes it seems a good place to start looking.

    If you look in your Installed Programs and find MyWinLocker or anything from EgisTec and you don't know what it is or why it is there consider just uninstalling it, rebooting and then see how things work.  You can always reinstall it again later if needed, right?

    If you have determined that MyWinLocker or any other EgisTec programs are involved follow the general purpose instructions below so you will be able to see all the Explorer shell extensions and figure out which one is afflicted.

    After using The following program suggestion if you see any extensions from EgisTec, PSD Security Software, eDataSecurity, DragDropProtect (they will be some of the pink extensions) start with those first.

    If none of those things are present, continue:

    When Windows Explorer (not Internet Explorer) is misbehaving (especially when right clicking), start to suspect third party Explorer extension add-ons.  You may also see Data Execution Prevention (DEP) errors.  DEP errors are reported when Windows feels threatened by a program and Windows will shut down the threatening program.  Windows should never feel threatened by Windows Explorer (or Internet Explorer) unless some add-on is the cause.

    Those would be Explorer extensions that do not belong to Microsoft.  That means extensions that you added.  Explorer extensions are usually okay and installing some applications will install Explorer extensions for you, give you a choice and sometimes they can be added without your knowledge when you install new software.

    Explorer extensions are sometimes added as a new right click option you see on folders and files (like scan this file, open this file, play this song).

    If there is a particular thing you do when Exploring that you know will cause the problem, that will help zero in on the problem and help you know for sure when you have found and fixed it.

    If you can make it happen anytime you want, make an adjustment and then there is no message the next time you do whatever it is you do, you have found and fixed it.

    First you need a way to see what Explorer add-ons you have installed now and a way to disable them (not uninstall them) so you can figure out which one is causing the problem.  You may have lots of non Microsoft extensions installed you don't even know about.

    Download ShellExView from here to see which Explorer extensions you have loaded:

    http://www.nirsoft.net/utils/shexview.html

    ShellExView doesn't install anything on your computer, it just runs and displays.

    After you launch ShellExView (double click shexview.exe) and acknowledge the security warning, adjust the column widths so you can see everything clearly.  Under Options, choose to "Mark Non-Microsoft Extensions" and the non Microsoft extensions will be in light pink, but on some systems that is a hard color to see, so click View, Choose Columns and move up or move down the Microsoft column so it is closer to the top (Move Up) so you can see it on your screen without having to scroll left and right.

    Next, click the column header called Microsoft (it may be way out on the right side of the screen) to sort the display (by clicking the Microsoft column header) so all the non Microsoft extensions are at the top and easy to see.  They will say "No" and be marked in pink since they are not Microsoft extensions, something like this:

    The non Microsoft extensions would be things you have added (non Microsoft) and are what you need to be suspecting.

    If you see extensions that do not have anything listed under Description, Product Name, Version, Company or have peculiar names that looks like they might be just random numbers and  letters, you might want to look at those first.

    You can also Google the name of a suspicious add-on and see if there are any hits regarding Explorer crashes or DEP errors and what other people have done about it.

    You might Google something like:

    <my-suspicious-add-on>  windows explorer crashing

    You have to fill in the name of your suspicious add on.

    See what kind of search results hits you get and look for solutions or situations that sound like yours.

    I am not a trial and error advocate, but I can't think of another way to do this...

    Right click and disable the non Microsoft extensions one at a time (or perhaps in little groups of 3-5) keeping a list so you can enable them again later if desired. The result of the change is immediate and no reboot is required.  Test your (right click) failure condition.  If Explorer starts to act normally, you will know that some extension you just disabled in that group of 3-5 is the culprit so you can start to enable them one at a time until explorer fails again.

    One user reported that there was a need to restart Explorer after each adjustment so to do that press Ctrl-E from within ShellExView.

    If you recognize any extensions that may have been added or downloaded recently, start with those first.

    Disabling an extension does not uninstall the extension - it is just disabled.  You can always enable it again later, so keep track of things by writing them down.

    Disable them one at a time or in little groups (to make things go faster) until your right click does not generate an error, then reboot and test again to be sure.   That last extension you disabled would be the suspicious one.

    You can also just disable all the non Microsoft extensions, reboot, test your failure condition and enable them one at a time until you find the one that generates the failure condition.

    If you have a lot of extensions, you could disable them is little groups, 3-5 at a time instead of 1 at a time until your system starts to behave.  

    When it does behave, you will know that the problem is one of the extensions in that little group and you can enable those in the group one at a time until the problem comes back, then the problem will be with the last extension you enabled.

    The hope is that you will find the one extension that causes the problem and then you can figure out what to do about it - either uninstall it or see if you can get an update from the maker of the extension from their web page.

    I don't have your issue but I can when you disable/enable the extensions, the extension is immediately disabled, so disabling an extension does not seem to require a reboot but if you think you found the problem, I would reboot and retest anyway to really be sure the problem is gone.

    If you post up a list of your non Microsoft extensions, maybe someone will recognize it as a potential problem.

    If you find the offending extension that is the problem, please let us know what it is so I can add it to my list!

    7 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-05-13T23:09:37+00:00

    Oh, forgot to mention that it also occurs in Safe Mode.

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-05-15T04:00:16+00:00

    You may have just skeered it into behaving - sometimes threatening the computer seems to work.

    Isolating a faulty extension can be tedious but I'm glad you understood how to do it.

    There is a list of known problematic extensions on the nirsoft site and I don't know how up to date it is.

    There are indeed several/some Spybot S&D problems in there (no dates though).

    http://shellfix.nirsoft.net/shell_problems_list.html

    0 comments No comments
  4. Anonymous
    2019-05-15T01:41:35+00:00

    ElderN, thank you very much for the help.

    I did what you suggested about the WinEx shell extension.  I found the non-Microsoft extensions and began disabling them in groups of 5.  After the 3rd group (#'s 11-15) the problem went away.

    So I began enabling the 3rd group one at a time... and after enabling all of them, the problem did not re-occur!

    I don't have an explanation as to how that works.  But now all my extensions are on, and it's working fine.  The most recent one that I had installed in that 3rd group was Spybot S&D (maybe 3 months ago), so maybe that is causing the problem.  Or rather, was.

    If this happens again (perhaps after a reboot) I will try to disable just that one extension and see if that fixes it.  I took a screen capture so I don't forget anything.

    Again, thank you!

    0 comments No comments