-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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 x64 Workspaces Crashes when opening Workspaces to edit a workspace #35422
Comments
/bugreport |
Hi @Bubblegendut |
Ok thanksI will delete the .json file see if that works.I have never modified my monitor layout or unplugged them. I shut down my pc each day with the power still on. If ids change then it must be win 11 or Nvidia driver that assign them! Sent from my iPadOn 17 Oct 2024, at 15:11, Laszlo Nemeth ***@***.***> wrote:
Hi @Bubblegendut
There is a recently discovered issue which occurs when you change your monitor setup. Thanks for the bug report file, the issue is in your case also an "old" monitor info. So your workspaces.json contains monitors with ids 6 and 7, and also with 1 and 2. If you change the monitor layout or unplug, re-plug a monitor those ids might change. Our next PT release will contain a fix for this issue, but you can manually modify the monitor id in your workspaces,json file, or remove some workspaces or remove some appa. Maybe deleting the workspaces.json file is the quickest solution. The workspaces.json file can be found in your app local folder, typically in
c:\Users\ XXX \AppData\Local\Microsoft\PowerToys\Workspaces
Sorry for the inconvenience!
Hope it helps!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Please retest with PT 0.86 and if the issue persist send a bug report/ Thanks! |
Workspaces Crashes
Worked fine for 1 day
next day after new Pc Start always get "stopped Working" Dialogue
Win 11 Pro 23H2
Power Toys v0.85.1
14 Oct 2024
The text was updated successfully, but these errors were encountered: