RESOLVED: Explorer crashing on right click

Anonymous
2023-09-04T10:51:57+00:00

Explorer.exe keeps crashing when I right click in a window or on the desktop. This seemed to start happening randomly and not after a Windows update or anything in particular.
I have tried the following:
-Disabled antivirus

-Disabled context menu's using ShellExView

-Booting into safemode
-Updating Windows
-Reinstalling the graphics driver

-sfcscan

-DISM repair
-Clear file explorer history
-Disable credential Guard in regedit
The same problem continues to happen, even in safemode.

Eventviewer displays the following when explorer crashes due to a right click:

Faulting application name: explorer.exe, version: 10.0.22621.2215, time stamp: 0xb9c28810

Faulting module name: Windows.UI.FileExplorer.dll, version: 10.0.22621.2215, time stamp: 0xaaa66d5d

Exception code: 0xc0000005

Fault offset: 0x000000000004e730

Faulting process ID: 0x0x1918

Faulting application start time: 0x0x1D9DF1AA34B61BA

Faulting application path: C:\WINDOWS\explorer.exe

Faulting module path: C:\WINDOWS\SYSTEM32\Windows.UI.FileExplorer.dll

Report ID: 9e3a2452-7da8-457c-a92d-d1db4f58f23a

Faulting package full name: 

Faulting package-relative application ID: 


I'm stumped and don't know what else I can do. Any suggestions?

Windows 11 Home 22H2 (OS Build 22621.2215)

Windows for home | Windows 11 | Performance and system failures

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
Answer accepted by question author
Anonymous
2023-09-04T14:45:47+00:00

Hello again,

I just fixed the issue without the need to run a repair.

I used the following command to disable the new context menu.
reg.exe add "HKCU\Software\Classes\CLSID{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32" /f /ve

The problem is now resolved.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

63 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-04-23T09:34:02+00:00

    Hi.

    I have the problem here with Windwos 11 23H2 up to date

    The new registry entry does NOT make any change.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-03-06T10:00:22+00:00

    It was a totally fresh install from Microsoft and I didn’t use back up.

    Will certainly check if all ok before installing AMD GPU drivers when I do my Windows 10 and 11 test installs.

    Cheers Reticzeta

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-03-05T12:22:17+00:00

    Of course we can't be sure but I'm pretty sure that this is not hardware related. In that case I guess it would be more random. For me it's consistently

    reporting

    Faulting application name: Explorer.EXE, version: 10.0.22621.3155, time stamp: 0x3fb2d7a4

    Faulting module name: SHELL32.dll, version: 10.0.22621.3085, time stamp: 0x4e9c34b7

    Exception code: 0xc0000005

    Fault offset: 0x000000000008774b

    Same application, same module, same offset.

    I've seen many people write that this is caused by a shell extension, which I'd like to believe. But even with ALL extensions disabled it still crashes. I think I've tried just about every suggested solution, except a complete Windows re-install which I am always hesitant to do - but perhaps it's the only way out. Something in Windows seems to be buggered up beyond repair.
    I'll be interested to hear how you will get on with your planned installations.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-01-30T12:43:46+00:00

    Yes it does. It disables the new context menu which has caused some people problems. If it didn't do anything then it wouldn't have fixed my problem and the other guy who posted here to say thanks for solving his issue.

    So it simple does do something. It fixes the issue with the new context menu.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments