Does ExplorerPatcher work on your Windows version?
ExplorerPatcher 71.1 supports Windows 10 1809 and newer and Windows 11 22H2 through 25H2, and its release notes list 26H2 and 26H1 builds as tested. Windows 7, 8 and 8.1 are not on the project's list. Type your build into the checker above. Our own tests ran on Windows 11 25H2 (Arm64), Windows Server 2025 and Windows Server 2022.
Checked against ExplorerPatcher 71.1 (26100.9711.71.1) on Windows Server 2025 (24H2 shell) 26100.33674 and Windows 11 Enterprise 25H2 26200.9725 and Windows Server 2022 (Windows 10 21H2 shell) 20348.5773 · Nov 6, 2026On this page
Not sure? Press Win+R, type winver, press Enter, and copy the line that says "OS Build".
Type a build to see which taskbar ExplorerPatcher uses on it, whether it was tested, and what users reported.
How to read your build number
Press Win+R, type winver and press Enter. The line “OS Build” shows a number such as 26100.9711. The first part (26100) decides which row below applies. The part after the dot is the monthly update level, and it matters only for known breakages on the status page.
| Windows version | Build number starts with |
|---|---|
| Windows 10 1809 to 22H2 | 17763 to 19045 |
| Windows 11 22H2 and 23H2 | 22621 and 22631 |
| Windows 11 24H2 | 26100 |
| Windows 11 25H2 | 26200 |
| Windows 11 26H2 (Dev) | 26300 |
| Windows 11 26H1 | 28000 |
Why the build matters
ExplorerPatcher patches code inside explorer.exe and the Start menu hosts, and it finds that code by reading Microsoft’s public symbol files for your exact build (according to upstream’s symbols page). When Microsoft changes the code, ExplorerPatcher needs a new release. That is why one Windows update can break it while the next release fixes it.
Microsoft also removed the Windows 10 taskbar from Windows 11 in the 24H2 generation. From there on, ExplorerPatcher draws its own taskbar. The chart shows which strategy applies to which build family.
Support table
This table comes from upstream’s compatibility wiki and the release notes of 71.1. “Supported” is upstream’s word, not ours. Our own results are in the notes under each row and in the next section.
| Windows version | Build | EP support | Taskbar implementation | Windows 10 Start menu | NT Alt+Tab |
|---|---|---|---|---|---|
| Windows 10 1507, 1511, 1607 | 10240, 10586, 14393 | Not supported | Not supported | n/a | n/a |
| Windows 10 1703, 1709, 1803 Listed in the wiki table as loadable but without ExplorerPatcher support. | 15063, 16299, 17134 | No EP support (use the ep_taskbar_loader Windhawk mod) | ep_taskbar.0.dll | n/a | n/a |
| Windows 10 1809 to 22H2 Our Server 2022 run (20348.5773, Windows 10 21H2 shell code) installed and uninstalled cleanly; taskbar stayed the stock 40 px one in every style. | 17763 to 19045 | Supported | Windows 10 shell: stock taskbar (EP adds settings) | Native Start menu | n/a |
| Windows 11 21H2 The stock Windows 10 taskbar is available. | 22000 | On request only | ep_taskbar.1.dll | Windows 10 Start menu available | Yes |
| Windows 11 22H2 and 23H2 Last Windows version with the stock Windows 10 taskbar. | 22621.1343+, 22631, 22635 (Beta), 23403 to 23620 (Dev) | Supported | ep_taskbar.2.dll or the stock Windows 10 taskbar | Windows 10 Start menu available | Yes |
| Windows 11 22H2 before 22621.1343 | < 22621.1343 | Not supported | n/a | n/a | n/a |
| Windows 11 24H2 Option "Windows 10" for the taskbar does nothing; use "Windows 10 (ExplorerPatcher)". | 26052 to 26090, 26100, 26120 (Dev) | Supported (EP 66.4 and later) | ep_taskbar.5.dll (renamed ep_taskbar.ge.dll) | Works with EP 71.1 (our test: 26100.33674) | Removed by Microsoft (our test: the NT option shows no switcher; Windows 10 and Simple Window Switcher work) |
| Windows 11 25H2 Same files as 24H2 (shared servicing branch). Builds 26220.8474 and later broke EP 69 and earlier (issue 4957); fixed in 70.1. | 26200, 26220 (Dev) | Supported | ep_taskbar.ge.dll | Works with EP 71.1 (our test: 26200.9725 Arm64) | Removed by Microsoft (our test, Arm64: the NT option shows no switcher; Windows 10 and Simple Window Switcher work) |
| Windows 11 26H1 | 27686 to 27982 (Canary), 28000 (Release), 28020 (Canary) | Listed in EP 71.1 notes as tested (28000.3231, 28120.3302) | ep_taskbar.ge.dll | Works per the 71.1 notes | Removed by Microsoft |
| Windows 11 26H2 | 26300 (Dev) | Listed in EP 71.1 notes as tested (26300.9711, 26340.9767) | ep_taskbar.ge.dll | Works per the 71.1 notes | Removed by Microsoft |
| Canary and Dev builds 25115 to 25309 | 25115 to 25309 | On request only | ep_taskbar.3.dll | Varies | Varies |
| Canary builds 25314 to 26040 The stock Windows 10 taskbar was removed from builds 26002 and later. | 25314 to 26040 | On request only | ep_taskbar.3.dll / ep_taskbar.4.dll | Varies | Varies |
| Newest Canary builds Upstream does not recommend ExplorerPatcher on Canary. | 29531 and later | EP 71.1 notes list 29695.1001 as tested | ep_taskbar.ge.dll | See notes | Removed by Microsoft |
Upstream’s 71.1 notes say the release was tested on builds 22621.4317, 22631.7652, 26100.8037 (Arm64), 26100.33650, 26300.9711, 26340.9767, 28000.3231, 28120.3302 and 29695.1001, and that the other builds in the list are x64.
What we tested ourselves
We ran the same script on three throwaway GitHub-hosted machines on 6 Nov 2026. None of them is a physical PC.
| Machine | Windows | Build | CPU | Role |
|---|---|---|---|---|
win11arm | Windows 11 Enterprise 25H2, Arm64 | 26200.9725 | Arm64 (Cobalt 100), 4 cores, 16 GB | The only real Windows 11 client image GitHub offers. Defender real-time and tamper protection on; Smart App Control off. |
win2025 | Windows Server 2025 (24H2 shell), x64 | 26100.33674 | x64 (EPYC 7763), 4 cores, 16 GB | x64 build 26100 with the same shell code as Windows 11 24H2. Defender service on, real-time off. |
win2022 | Windows Server 2022 (Windows 10 21H2 shell), x64 | 20348.5773 | x64 (Xeon 8370C), 4 cores, 16 GB | The Windows 10 code path (settings10.reg); Windows 10 shell. |
Results by Windows version:
- Windows 11 24H2: see the 24H2 page. Evidence comes from Windows Server 2025, which shares the 24H2 shell.
- Windows 11 25H2: see the 25H2 page. Evidence comes from a real Windows 11 client image, on Arm64.
- Windows 10: see the Windows 10 page. Evidence comes from Windows Server 2022, which has the Windows 10 21H2 shell.
- Arm64: see the Arm64 page.
One result worth knowing for both Windows 11 rows: the Alt+Tab styles. On 24H2 (Server 2025) and 25H2 (Arm64) the Windows 10 style and Simple Window Switcher worked, and the Windows NT style showed no switcher at all. See Alt+Tab styles.
What we did not test: physical PCs and laptops, an x64 Windows 11 Home or Pro edition, multiple monitors, Smart App Control switched on, third-party antivirus, and any Insider build.
Windows 7, 8 and 8.1
ExplorerPatcher does not list Windows 7, 8 or 8.1. The compatibility table in its wiki starts at Windows 10 1507 and marks that release, 1511 and 1607 as not supported. We have not run it on any of these systems, and we cannot tell you what would happen. Because ExplorerPatcher works by patching the shell of specific Windows 10 and 11 builds, there is no reason to expect it to do anything useful on an older shell.
If you run Windows 7 or 8.1 and want a different interface, look at the alternatives instead.
Windows Server
Server editions work, with a caveat. We installed 71.1 on Windows Server 2025 (24H2 shell, build 26100.33674) and Windows Server 2022 (Windows 10 21H2 shell, build 20348.5773). Both installed in about 5 seconds, and both uninstalled with only the settings key left behind. Servers are not clients, though: the Start menu, edition features and update channel differ from a Windows 11 PC. Read our Server results as “the same shell code works”, not as “your Windows 11 PC will behave the same”.
Insider builds
We do not recommend it. Upstream’s table lists some Dev builds as supported, and the 71.1 notes name one Canary build (29695.1001) as tested, but the wiki marks the newest Canary builds (29531 and later) as “TBD”. Microsoft usually publishes no symbol files for Beta and Release Preview builds, or for the optional “C” and “D” preview updates (upstream’s symbols page), so ExplorerPatcher cannot always load the features that depend on them. We have not tested any Insider build.
The most visible example: Windows build 26220.8474 (a Beta channel build from 15 May 2026) removed the engine behind the Windows 10 Start menu and made ExplorerPatcher 69.6 crash Explorer in a loop. Version 70.1 stopped the crashes four days later. See Start menu not working for the history.
Before you install on any build
- Check your build in the box at the top of this page.
- Read the status page for known problems with your Windows update.
- Learn the recovery step first: black screen after ExplorerPatcher.
- Switch off Smart App Control before installing, as the project’s release notes ask.
- Do not use the reimplemented taskbar on a work PC. Upstream’s wiki says it is for personal machines only.
Then download from GitHub.
More short answers are in the ExplorerPatcher FAQ.
Common questions
Does ExplorerPatcher work on Windows 11 25H2?
Yes. Version 71.1 installed and ran on Windows 11 Enterprise 25H2 build 26200.9725 (Arm64) in our test, and upstream supports 25H2. We have not tested a 25H2 Home or Pro PC with an Intel or AMD chip.
Does ExplorerPatcher work on Windows 7, 8 or 8.1?
The project does not list them. Its compatibility table starts at Windows 10 1507, and even that version is marked as not supported. We have not tested Windows 7, 8 or 8.1, so we cannot say what would happen.
Can I use ExplorerPatcher on Insider builds?
We do not recommend it. Upstream's table lists some Dev builds as supported and marks the newest Canary builds as to be decided, and Microsoft usually publishes no symbol files for Beta and Release Preview builds. We have not tested any Insider build.
What should I do after a Windows update breaks it?
Start Explorer without ExplorerPatcher with Ctrl+Alt+Shift (see the black screen page), then check the status page and the project's releases for a fix. Fixes for a new Windows build usually arrive as a new release.