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
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

63 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-01-30T13:21:23+00:00

    Well that's very different to it not doing anything.

    Obviously your issue is caused by a different problem. I advise you start off with an sfcscan and then a dism restore

    https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-01-30T13:35:09+00:00

    I tried those and disabling non ms shell items

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-01-30T13:44:31+00:00

    Well apart from not fixing my problem it did not do anything either, as far as I could see 😊
    Disabling that wretched new context menu was one of the first things I did back when I started out with Windows 11.

    You may be right in that my problem is something entirely different.
    Thanks for the tip. I had done SFC /scannow already, and it reported one corruption (bthmodem.sys) which it repaired.

    This is apparently a well known issue which can be ignored, so I did not think any other actions were needed.

    Running the DISM now. Maybe it helps.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-01-30T14:55:36+00:00

    The DISM command completed successfully, no errors or messages. Rebooted for good measure. The crash persists 😒

    Was this answer helpful?

    0 comments