-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
PowerToys Run crashes when using with Program plugin #37254
Comments
We've found some similar issues:
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
|
How can i generate a full dump |
One way of achieving this would be by creating an entry in the Registry Editor ( It should look something like this in the end (but for PowerLauncher) and dump type should be 2 instead of 1: After that, please replicate the bug, navigate to /needinfo |
I tried again after deleting the files that gives the exception using the dumps, but it still kept happening with other different files/paths. I also remember these files were working previously with the power launcher, they have been there since before the 0.87.0 update. Since the size of the dumps are large github won't let me upload them here, I am sharing them using google drive. |
Pretty weird 🤔 Something we've done is update from .NET 9.0.0 to .NET 9.0.1 . Wonder if something came from there. Can you try uninstalling PowerToys 0.88.0, install 0.87.1 and see if there's still an issue? (Double checking if it's an actual PowerToys change or something that happened to the link files that might have started causing it) |
Thanks for sending the dumps, by the way! 😄 @theGuiltyMan |
I think this is the grabber.lnk: https://github.com/Bionus/imgbrd-grabber
|
@theGuiltyMan I've made a version that should no longer crash https://github.com/mantaionut/PowerToys/releases/tag/fix_GetThumbnail |
Unfortunately powertoys run still crashes when the program plugin is active. |
@theGuiltyMan I have updated the binaries https://github.com/mantaionut/PowerToys/releases/tag/fix_GetThumbnail with some extra logs that could help us identify what is the problem. |
Here is the log with the latest binary |
@theGuiltyMan thanks for the logs. I've also made a change from using System.Drawing.Icon.ExtractAssociatedIcon to SHGetFileInfo which could fix your issue since the problem code is in ExtractAssociatedIcon https://github.com/mantaionut/PowerToys/releases/tag/custom_getThumbnail. Can you retest those 2 binaries and let me know if any of them fixes your issue? |
The shortcut for ALVR is: Unfortunately neither of the binaries resolved the issue. |
Can you give me the crash dump for the alternative binary? |
Thanks, right now I am not sure if this crash is caused by a bug in PowerToys or a Windows API bug. |
Browse button crashes too? |
Yes |
What is the call stack for the browse button crash? Since that button only opens a window to select a file
|
Were you building it yourself or using the executable? |
The stack trace is from when I build myself, but the executable itself also crashes the same way |
That is really weird. Can you rebuild it using .net8 instead of .net9 and see if that crashes too? |
.net8 works flawlessly for all the buttons |
Can you open an issue in dotnet repository since this issue a .net9 bug? |
The new binary works perfectly. |
Can you test a build I've made with their suggestion of disabling CETCompat https://github.com/mantaionut/PowerToys/releases/tag/disable_cetcompat? |
It works |
Microsoft PowerToys version
0.88.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
Since version 0.87.0 whenever I try to use PowerToys Run it crashes.
I saw a few issues caused by thumbnail generation, but the program still crashes when the option is off and thumbnail files are deleted.
PowerToysReport_2025-02-02-23-35-53.zip
PowerToys.PowerLauncher.exe.36024.dmp.zip
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response
The text was updated successfully, but these errors were encountered: