-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
PowerToys Run crashed and blue screened PC #33896
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
Exception
Environment
Assemblies - PowerToys.PowerLauncher
|
Looks a lot like #30507, but it shouldn't blue screen the PC. Is there a chance this happened at the same time as some graphical update? We've never been able to repro. Did it happen just once or it keeps happening? /needinfo |
Unfortunately, it crashed again today.
|
/dup #31226 |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Microsoft PowerToys version
0.82.1
Installation method
Other (please specify in "Steps to Reproduce")
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
Installed via Intune Company Portal.
✔️ Expected Behavior
To work as it always has without crashing.
❌ Actual Behavior
PC hung briefly, then a window opened to say PowerToys had run into a problem, and before I could make a screen capture the PC blue screened and then restarted.
PowerToysReport_2024-07-18-07-24-01.zip
Other Software
Windows 11 Pro 23H2, Build 22631.3880, Windows Feature Experience Pack 1000.22700.1020.0
Dell Precision, 13th Gen Intel(R) Core(TM) i7-13850HX 2.10 GHz, 32.0 GB
Azure AD joined
The text was updated successfully, but these errors were encountered: