-
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
FancyZones Editor doesn't open after update #19223
Comments
same error. log entries on trying to enter FansyZones Editor:
|
Stack trace from #19334 :
|
We've got a possible fix floating around, but we can't really test it since it we don't have the same conditions locally. Could you please try a debug build with the fix so we can validate it on your configuration? (It's an unsigned build , by the way) Please uninstall your current PowerToys installation, then install this debug build. Thank you, in advance. |
The fix didn't help
|
@ALERTua , so the FancyZones Editor still doesn't open? |
@jaimecbernardo, I uninstalled the production build, as you instructed, then installed the unsigned build using the link you gave, launched it, pressed FansyZones Editor hotkey, and saw the dialog window:
then copypasted the log in my post above. |
@ALERTua , A fuller /bugreport might be helpful here instead to check FZEditor logs instead of just the FancyZones logs. Thank you! |
Thank you!
|
To better explain the problem here, we expect a configuration that's able to get the DeviceID that represents the monitor that the display interface uses. This is an example from my PC. We're then able to match that with display information in WMI: Unfortunately, for the cases of this issue, it seems the display interface is not connected in the same way to the display, even though both are there:
|
@ALERTua , Thank you. This is the configuration when FancyZones isn't working. Wonder what changes for it to work. Could you please set it to work and send the new monitor_ids.txt for comparison? |
Hi @ALERTua @kellymenzel @eseinbinder We've got a possible new fix for this. This adds a fallback for those cases where there's no monitor associated to the display device. Could you please try a debug build with the fix so we can validate it on your configuration? (It's an unsigned build , by the way) Please uninstall your current PowerToys installation, then install this debug build. Thank you, in advance. |
@jaimecbernardo, I can confirm that the debug build works on my Cloud PC and fixes the problem introduced in 0.60.0 for me. |
Hi @ALERTua @kellymenzel @eseinbinder , This is the actual new fix. This adds a fallback for those cases where there's no monitor associated to the display device. With a cycle fix now too. Could you please try a debug build with the fix so we can validate it on your configuration? (It's an unsigned build , by the way) Please uninstall your current PowerToys installation, then install this debug build. Thank you, in advance. |
@jaimecbernardo, working configuration with 3 monitors enabled with the first test build without a fix I can confirm that the new test build https://github.com/jaimecbernardo/PowerToys/releases/tag/v0.0.1-test-fix-issue-19223-no-monitor-fallback-2 works for me in all monitor combinations! |
will try in a little bit. thanks for fixing so quickly! |
@jaimecbernardo The latest v0.0.1-test-fix-issue-19223-no-monitor-fallback-2 build also works for me. Just installed it, works on my Cloud PC. Thanks! |
Thanks everyone for helping debug and test this! |
Another affirmative on this fix from me on my afflicted machine. Thanks! |
works for me too. sorry for the delay in testing. |
so, ooc, for those of us who installed the fix to test it, should we leave it installed until v0.61.0 is released, at which time we uninstall, then install v0.61.0, or should we downgrade to 0.59.1 until 0.61.0 is released, and then just upgrade at that time? are there any advantages/disadvantages to either path? 🤔 |
The hot fix was released in 0.60.1: https://github.com/microsoft/PowerToys/releases/tag/v0.60.1 |
For those who installed the debug build, please uninstall it and install 0.60.1 instead, so you can continue receiving updates. |
Microsoft PowerToys version
0.60.0
Running as admin
Area(s) with issue?
FancyZones Editor
Steps to reproduce
Fancyzones doesn't work after install version 0.60.0. Starting the editor i've got a error pop-up
✔️ Expected Behavior
Starting editor
❌ Actual Behavior
error pop-up
Other Software
Windows 11 Pro build 22000.739
The text was updated successfully, but these errors were encountered: