PowerToys crashes on startup due to ExplorerPatcher.amd64.dll conflict (Access Violation 0xC0000005)

[fnfontana]

Before reporting your issue

• I have confirmed that this issue does not happen when ExplorerPatcher is not installed
• I do not have "register as shell extension" enabled
• I have tried my best to check existing issues

Repro ExplorerPatcher versions

ExplorerPatcher 26100.4946.69.4

Repro Windows Versions

Windows 11 23H2 22631.5909 x64

3rd party tweak software installed

Microsoft PowerToys version 0.94.0.0

Describe the bug

Microsoft PowerToys crashes immediately after startup with an access violation error caused by a conflict with ExplorerPatcher.amd64.dll. The application terminates within seconds of being launched, making it completely unusable.

Steps to reproduce:

1. Install ExplorerPatcher version 26100.4946.69.4
2. Install PowerToys version 0.94.0.0
3. Try to launch PowerToys from Start Menu or directly from executable path: C:\Program Files\PowerToys\PowerToys.exe
4. Observe that PowerToys terminates immediately with access violation

Error Details:

• Exit Code: -1073741819 (0xC0000005)
• Exception Code: 0xc0000005 (Access Violation)
• Faulting Module: ExplorerPatcher.amd64.dll
• Faulting Application: PowerToys.exe

Expected outcome

PowerToys should launch normally and remain stable when ExplorerPatcher is installed, allowing both utilities to coexist without conflicts.

Actual outcome

PowerToys crashes with access violation immediately upon startup, making it unusable. The crash is consistent and reproducible on every launch attempt. Windows Event Log shows multiple crash events (Event ID 1000) with ExplorerPatcher.amd64.dll as the faulting module.

Additional info

Windows Event Log Details:

Faulting application name: PowerToys.exe, version: 0.94.0.0, time stamp: 0x68b21430
Faulting module name: ExplorerPatcher.amd64.dll, version: 26100.4946.69.4, time stamp: 0x68df7bc6
Exception code: 0xc0000005
Fault offset: 0x000000000000d43b
Faulting process id: 0x1858
Faulting application start time: 0x1DC37E405093960
Faulting application path: C:\Program Files\PowerToys\PowerToys.exe
Faulting module path: C:\Program Files\ExplorerPatcher\ExplorerPatcher.amd64.dll

---

Workaround tested:
Temporarily renaming ExplorerPatcher.amd64.dll allows PowerToys to function normally, confirming the DLL conflict.

Environment:

• Architecture: x64
• PowerShell Version: 7.5.3
• .NET Runtime: Present and functional (verified)
• Both applications installed in default Program Files locations

Impact:
This prevents users from using PowerToys functionality while ExplorerPatcher is installed, forcing them to choose between the two utilities. Both applications work fine independently when the other is not present.

Crash Dumps

Multiple crash offsets observed:

• 0x000000000000d43b
• 0x000000000001bc60
• 0x000000000001bf31
• 0x000000000000d555

Media

No response

[pyrates999]

if you enabled the option register as shell extension, disable it by opening up the EP properties application, go to File Explorer, and untick Register as shell extension.

Here's why: https://github.com/valinet/ExplorerPatcher/wiki/Using-ExplorerPatcher-as-shell-extension

duplicate of: #4272

please close this.

[fnfontana]

Thank you for the quick response and solution!

I followed your instructions and disabled the "Register as shell extension" option in the ExplorerPatcher Properties under File Explorer settings. After applying this change, PowerToys now launches successfully without crashing.

Confirmation:

• ✅ PowerToys no longer crashes on startup
• ✅ No more access violations (0xC0000005)
• ✅ Both ExplorerPatcher and PowerToys now coexist properly

The solution worked perfectly. I understand now that the shell extension feature injects ExplorerPatcher into all processes, which was causing the compatibility conflict with PowerToys. Since I don't specifically need the classic Open/Save dialogs functionality, keeping this option disabled is the ideal solution for my use case.

Thank you for maintaining such a responsive project and providing clear documentation about the risks and benefits of the shell extension feature.

Closing this issue as resolved.