-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ep_taskbar crashes Explorer when receiving notifications #3605
Comments
I have read this #3398 |
What version of EP are you running? |
Thank you for reporting this. I will check soon. |
Would be great if you can send your explorer.exe with its file extension renamed to .txt. |
We have warned for this issue to happen in the 3rd point in its Warning section. |
Yes, hello Amrsatrio, EP is version "22621.3880.66.4" from august 1, "Windows 11 Pro 24H2 26100.1586" and "Windows Feature Experience Pack 1000.26100.18.0". So two days ago the application crashed the explorer 6 times, so I restarted the PC and switched to taskbar style "Windows 11 (default)" (really not liking this one); after that, the whole day nothing crashed. Conclusion is, it's random, can't force the crashing, but it's definitely "Windows 10 (ExplorerPatcher)" style crashing it.
You mean the one found in "C:\Windows"? Okay, done it, while "Windows 10 (ExplorerPatcher)" was active, nothign crashed yet. |
ApplicationErrorExplorerPatcher.evtx to txt |
Update: Have a nice day |
if you enabled the option register as shell extension, disable it by opening up the EP properties application, go to File Explorer, and untick Register as shell extension. Here's why: https://github.com/valinet/ExplorerPatcher/wiki/Using-ExplorerPatcher-as-shell-extension |
Were the crashes happening when you were receiving a flurry of notifications? I know that continuous notifications from Telegram crashes Explorer. |
Yeah just checked it, the error happened in the handler for notifications. I kept getting these crashes too if I have Telegram open and keep getting messages. Seriously I don't know what went wrong in here... but I could compromise the little app icon sliding animation in the notification center button to prevent this from happening altogether. |
@Amrsatrio okay, switched back to "Windows 10 (ExplorerPatcher)" and disabled that "register as shell extension".
You're the boss. so I won't argue against what you found, but define what you mean with "receiving".
Because I'm very, very sure sure that most of the crashes did not happen when 1) or 2) were occuring. Additional information: Thanks, Have a nice day |
Investigated further. I noticed that a struct used by the private APIs for notifications grew by 8 bytes in 22621.3296 when compared to 22621.1992. Simply there is no easy way to get around this without making complex code matching patterns. I may have to axe the app icon sliding thingy from the notification center button for good. |
@Amrsatrio Everything worked without crashes for the last 5+ days; now it crashed again for the first time. This time the explorer crashed and restarted exactly (00:51) when I switched the proton-vpn server and the notification displayed in the notification-center. |
May it has something to do with this? #3600 (comment) |
No, different issue. Anyways I edited the code on my phone to disable the notification gleams feature. The taskbar DLL is building right now and once it's done I'll share you the link. |
Good day @Amrsatrio Would it be possible to have a copy of that taskbar DLL as well? I am also on the 22621.3880.66.6 release and ep_taskbar5.dll is crashing as well. I'd like to try it out and report if it alleviates the problem. Regards |
No it is not a duplicate. Instead it is a sign that I should hurry up with other bug fixes. |
@pyrates999 @Amrsatrio |
@1kartafal4 lol oh no, sorry :D |
Fixed in 66.7. |
Really sorry for taking this long. 🙇 |
Good day to the developers,
thanks a lot for this good program.
I use it together with TranslucentTB (both latest version) and on Windows 11 23H2 it worked fine.
After now installing the latest Release Preview build 26100.15xx (new clean install, no windows-insider program), the program keeps crashing the windows explorer, which then automatically restarts.
As you can see in the screenshot, 3 times in 5 minutes.
I can send a copy of the .evtx file of the windows event viewer if needed, and/or are there log files from ExplorerPatcher itself that can be send?
Can you fix it, or is it Windows specific? I'm using the Windows 10 (ExplorerPatcher) taskbar style.
Greetings
![error1](https://private-user-images.githubusercontent.com/111880217/362648796-62a1ad37-14a0-4751-ba73-6d45f6d7dc65.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1ODcxNTgsIm5iZiI6MTczOTU4Njg1OCwicGF0aCI6Ii8xMTE4ODAyMTcvMzYyNjQ4Nzk2LTYyYTFhZDM3LTE0YTAtNDc1MS1iYTczLTZkNDVmNmQ3ZGM2NS5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNVQwMjM0MThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kOWU1MzczYmEwODJmMTE5YmQzMDAyOTQ4NGU5OThjMDE2NmU5ZTY1ZjY4ZDJlNzkyZWZkMzZjNTYxZGZhM2VjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.F6nsFDvNmwrXdA37y3WzePy1Zg2Y0PHBgHRu8tAZZSA)
![error2](https://private-user-images.githubusercontent.com/111880217/362648820-f364df82-e45a-464b-83cb-2cfdb59d311b.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1ODcxNTgsIm5iZiI6MTczOTU4Njg1OCwicGF0aCI6Ii8xMTE4ODAyMTcvMzYyNjQ4ODIwLWYzNjRkZjgyLWU0NWEtNDY0Yi04M2NiLTJjZmRiNTlkMzExYi5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNVQwMjM0MThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04NmM0MWE2YzQ4ZThhZjIxNTVkMWQyZWRlOGE1YzVlZGVmMWFjMTRjODU5NzkxNWVhMTQxZDk5OWUzODc5ODA0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.-Qj7G0stN2mK8wJlRTQIaByOlOlcPwTr7HuNysxDmlg)
The text was updated successfully, but these errors were encountered: