Contact us
Email hello@explorerpatcher.dev about mistakes on this guide, a broken tool or an outdated page. We cannot give support for ExplorerPatcher itself. Bugs, crashes and feature requests belong on the project's GitHub issues page, where the developers read them.
Checked against ExplorerPatcher 71.1 (26100.9711.71.1) · Nov 6, 2026On this page
What to write to us about
Our address is hello@explorerpatcher.dev. We answer about things on this site:
- a factual mistake, an unclear step, or a page that is out of date;
- a tool that gave a wrong answer (tell us your Windows build and what you typed or dropped, but never send us your files);
- a screenshot or measurement you think is wrong, with your reason;
- a lookalike site you found, so we can check it for our table;
- credit or wording about a person or project we named.
Every page ends with Report a problem with this page. It opens an email with the page address filled in, which is the fastest way to get a correction.
We aim to fix a factual error within 7 days and record the change on the corrections page. We read every message but cannot promise a personal reply to each.
What we cannot help with
We are an independent guide, not the ExplorerPatcher developers. We do not run the project, we cannot change the program and we have no access to your PC. So we cannot:
- fix a crash, a black screen or a failed install for you;
- accept bug reports or feature requests for ExplorerPatcher;
- tell you whether a particular Windows update will break it;
- recommend that you use it on a work PC.
If something is broken right now, open the black screen guide or troubleshooting first. They have steps you can follow without waiting for an answer.
Where ExplorerPatcher bugs go
Report them upstream:
- Issues: github.com/valinet/ExplorerPatcher/issues. Upstream’s wiki says to use Issues, and asks for your Windows build from
winverand your ExplorerPatcher version. - Chat: the project’s README links a Discord server, discord.gg/gsPcfqHTD2, for support and discussion.
- Documentation: the project’s wiki.
Check that the problem does not happen with the stock taskbar before you report it, as upstream asks. Antivirus detections are better reported to the antivirus vendor; upstream’s release notes say issues about detections will be closed.
Your email
If you write to us, we use your message and address only to answer you and to fix the page. We do not add you to a list. More in the privacy page.