valinet / valinet/ExplorerPatcher

Make ExplorerPatcher Shut Up about crashs because it's still working

Open
#5,085 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C
Stars
33.9k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

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

Some clients have their computers infected with Windows 11 and so part of restoring a usable GUI is using ExplorerPatcher. The thing is: it keeps complaining that it crashes, all the time. If it crashed the Open-Shell start menu fix would be at the center of the screen however it's still at the bottom-left where it belongs.

Having a crash notice appear all of the time (except literally never when I'm viewing their computer) is really starting to annoy my clients many of whom have no idea the nightmare normal users like them have to deal with when they don't have a competent technical professional like me helping them. That being said we've got things to do. Please give us a simple option to make ExplorerPatcher shut up about crashes. They are either not actually happening or not having any actual effect but the error messages are the only actual problem.

Repro Windows Versions

Client PC not accessible at this time.

Third-party tweak software installed

OpenShell, Waterfox, AnyDesk

Describe the bug

.

Expected outcome

To not be obnoxious while working.

Actual outcome

Working but being obnoxious.

Additional info

No response

Crash Dumps

No response

Media

No response

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No source file, test, Windows version, or crash dump is provided. Start by reproducing the recurring ExplorerPatcher crash notification and determining whether ExplorerPatcher is still functioning; done would be a documented option that suppresses the notices without disabling working behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.