valinet / valinet/ExplorerPatcher
[29634+] ep_taskbar crashloops explorer.exe due to ABI change
Nobody has claimed this yet.
- 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
70.3, 70.4
Repro Windows Versions
29634.1000 x64 & ARM64
Third-party tweak software installed
None
Describe the bug
- Install EP 70.4
- Windows 10 (ExplorerPatcher) taskbar aka ep_taskbar is configured to be used by default.
- Observe explorer.exe crashlooping and getting the repeated crashing dialog.
Expected outcome
Desktop and ep_taskbar shows normally and functional.
Actual outcome
explorer.exe crashlooping.
Additional info
This is part of the taskbar ABI changes that were initially introduced in 26xxx.8474, then 28000.2298, and finally landed in Canary/Experimental Future Platforms channel in build 29634.
I will fix this in due time along with making a more robust detection for incompatible taskbar ABIs.
Crash Dumps
No response
Media
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the crashloop with ExplorerPatcher 70.4 on Windows build 29634, then inspect ep_taskbar's handling of taskbar ABI compatibility. Done means explorer.exe no longer crashloops and the Windows 10 taskbar works on both x64 and ARM64.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100