Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ExplorerPatcher incompatibility (explorer.exe crash loops)

Open
#1,015 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

No files, tests, or code entry points are named. Start by locating Windhawk's installation and crash-warning flows, then check how it could detect ExplorerPatcher; done means users are warned that the two tools are incompatible.

Written by the indexing model from the issue text.

Description

bug info-needed

Hi, just a quick suggestion, when crashes happen or even during WHawk's installation maybe try to detect C:\Program Files\ExplorerPatcher (default path) or idk, maybe in a more dynamic manner, to warn the user the apps are incompatible.

For many days I had issues with windhawk seemingly 'randomly' crashing explorer process in a loop. Somehow today I randomly found 1 random comment online mentioning ExplorerPatcher also modifies explorer process which makes them incompatible, no matter which windhawk mods you use. Beyond the crashes I also could not use 50% of the themes / they would load broken UI.

Some windhawk mods cause the crashes to happen more frequently (e.g the 'show folder sizes' mod) but even with very few mods it's still not usable due to crashing explorer constantly. And I didn't even remember I had installed ExplorerPatcher - it is a great tool - but I removed it and WHawk works fine now.

Dominant language
Rust
Stars
9.3k
Forks
246
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ramensoftware/windhawk

All issues in ramensoftware/windhawk

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.