ExplorerPatcher problems and fixes

Decode a message

Paste the text of a dialog, notification or error. The decoder matches it against the messages we found in ExplorerPatcher’s source and in our test runs, and tells you what it means and which page to open.

Paste the message, or part of it

Pick your symptom

First aid

Work down this list and stop when Explorer behaves.

1. Start Explorer without ExplorerPatcher. Press Ctrl+Shift+Esc, choose Run new task, type explorer.exe, hold Ctrl+Alt+Shift, press Enter, and keep holding until the taskbar shows. ExplorerPatcher stays off for that session. If it fails, use the other methods on the black screen page.
2. Dismiss the crash dialog. It is expected after step 1. Click Dismiss.
3. Check the status page. If a Windows update broke ExplorerPatcher, a newer release may already exist.
4. Update ExplorerPatcher. Run the newest setup file from GitHub over the old install. In our test the update kept our settings.
5. Switch the taskbar style back. Search Start for “Properties (ExplorerPatcher)”, open Taskbar, and set Taskbar style to Windows 11.
6. Uninstall. See the uninstall guide. Your settings stay in the registry unless you remove them.

Smaller problems

Each entry names its source: upstream’s FAQ or wiki, an upstream issue, or our own test. Issue numbers link to the project’s tracker on GitHub. Upstream issues listed here are reports we have not reproduced.

The search box disappears when Start or Search opens

Cause (upstream FAQ): Microsoft changed how Search works on Windows 11, so Search always behaves as if the box were turned off. Fix: use the search icon on the taskbar, or hide the search button. The FAQ names no other fix.

“Pin to Start” does nothing in the Windows 10 Start menu

Cause (upstream FAQ): Microsoft changed internal code and ExplorerPatcher must be updated for each change. Fix: update. Upstream issue 3984 (closed 21 May 2025) covered builds 22631.4541 and 26100.2454, and the 71.1 notes list further Pin to Start fixes for Arm64. See Start menu not working.

The taskbar menu has no “Properties” entry

Cause: the advanced option “Do not change the taskbar context menu” is on, which hides the entry (upstream’s advanced settings wiki). In our test the entry was there by default. Fix: open Start and search for “Properties (ExplorerPatcher)” (we saw that entry in Start after installing), or use the Win+X option, or press Win+R and run:

rundll32 "C:\Program Files\ExplorerPatcher\ep_gui.dll",ZZGUI

Upstream’s wiki gives the same command with C:\Windows\dxgi.dll as the file.

The taskbar looks broken or has the wrong size

Cause (upstream FAQ): the option “Enable advanced mitigations for correct rendering using classic theme” is on while you do not use the Classic theme. It applies to Windows 10 and Windows 11 21H2 to 23H2 with the stock Windows 10 taskbar. Fix: turn it off in Properties and restart File Explorer.

The “Windows NT” Alt+Tab style does nothing

Cause (upstream FAQ): Microsoft removed that switcher in 24H2, so it displays nothing. We saw the same on Windows Server 2025 and Windows 11 25H2: no switcher appeared. Fix: choose Windows 10 or Simple Window Switcher; both worked on our machines. See Alt+Tab.

“Windows 11 Command Bar (classic Address Bar)” changes nothing

Cause (upstream FAQ): Microsoft removed the toggle behind it on newer builds. We saw no difference on build 26100 (Windows Server 2025). Fix: use the Windows 10 Ribbon or the Windows 7 Command Bar, which both worked. See the ribbon page.

7+ Taskbar Tweaker or a Windhawk mod stopped working

Cause (upstream wiki): 7+ Taskbar Tweaker works inside the Windows 10 taskbar code in explorer.exe, so it cannot work with ExplorerPatcher’s reimplemented taskbar. The wiki lists a few Windhawk mods as compatible, for example Taskbar Volume Control and Taskbar Clock Customization, and says other tweak tools are not guaranteed to work. Related upstream issue: 3769 (closed 16 Oct 2024). Fix: use only the listed mods, or keep the Windows 11 taskbar style. See the alternatives.

Taskbar toolbars (Quick Launch, Links) stop working after an update

Upstream reports: 4542 (toolbars no longer open since build 26100.5074, closed 5 Oct 2025), 5093 (a Windows update broke Links toolbar folder menus, closed 5 Jul 2026) and 4831 (Quick Launch after KB5074109, still open). We have not tested toolbars after an update. Check the status page and update ExplorerPatcher first.

“This PC” keeps opening, or File Explorer jumps around

Upstream reports: 1817 (“This PC” keeps randomly opening, closed 20 Nov 2023) and 2543 (File Explorer opens after an app exits full screen, still open). We have not tested this and do not know a cause. If it matters to you, read both threads before you change settings.

The volume or brightness slider is not visible

Upstream reports from 2023, for example 1692 (build 22621.2134, KB5029263, closed 23 Sep 2023). Issue 1802, about the same update, had “Fix available” in its title. Our test machines have no audio device, so we could not test the volume flyout. If you see this now, update first, then report it with your build number.

A grey screen after an interrupted ExplorerPatcher update

Upstream issue 5230 (open, 3 Nov 2026) is titled “Interrupted upgrade leaves C:\Windows\dxgi.dll zero-filled (grey screen)”. We have not reproduced it. If you see a grey screen after an update was interrupted, follow the black screen recovery, in particular Method 4.

Uninstall is blocked, or settings are still there afterwards

The 71.1 release notes warn that SentinelOne can hold ExplorerPatcher’s files and block uninstalling. We did not test SentinelOne. In our uninstall test the settings key stayed behind on all three machines, which is by design. See the uninstall guide.

How to report a bug upstream

Report bugs on the project’s GitHub Issues page. The top of upstream’s “Reporting problems” wiki page says to use Issues. This site cannot fix the program and is not affiliated with the developers. What upstream asks for:

• The Windows version from winver (for example, 22621.1992) and the steps to reproduce the problem (taskbar wiki).
• Confirmation that the problem does not happen with the stock taskbar (taskbar wiki).
• Complete details such as your OS version and the tweak software you have installed (FAQ), for example Open-Shell, Start11, StartAllBack or 7+ Taskbar Tweaker.
• For crashes, the older reporting guide in the wiki (now struck through) asked for the faulting module name from Event Viewer, when it is shown.

From us, as practical advice: also give your ExplorerPatcher version (for example 26100.9711.71.1), whether your PC is x64 or Arm64, which taskbar style you use, and whether the problem stays when you start Explorer without ExplorerPatcher using Ctrl+Alt+Shift. Search the open issues first, because many problems already have a thread. Our contact address handles corrections to this website only, not bug reports.

More short answers are in the ExplorerPatcher FAQ.