microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
108.19k stars 6.39k forks source link

Fancyzones stops working randomly, and starts working again after I deactivate and then activate the feature in PowerToys #32698

Closed oes25 closed 4 days ago

oes25 commented 3 months ago

Microsoft PowerToys version

0.80.1

Installation method

Microsoft Store

Running as admin

Yes

Area(s) with issue?

FancyZones

Steps to reproduce

✔️ Expected Behavior

For fancyzones to work as expexted. For blue recangles to appear over the areas of my layout that contains different windowsizing presets

❌ Actual Behavior

Nothing. It is as if Fancyzones is turned off it seems.

Other Software

No response

github-actions[bot] commented 3 months ago

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:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

oes25 commented 3 months ago

And, as said in the title. It starts working again after I turn Fancyzones off and then on again in the app

sjwk commented 3 months ago

I'm having the same intermittent issue since upgrading to the latest version. I'd guess that issue #32585 is connected too - I first also wondered if it was something to do with sleep or disconnection from monitors, but I am seeing it happen when connected and no screen lock or sleep occurring.
As a wrinkle, I'm using Fancyzones inside a fullscreen RDP session, and I'm also using virtual desktops inside the RDP session. But neither of those seem to match with it stopping working. Like you, the only fix seems to be to go into PowerToys and switch Fancyzones off and on again.

nguyen-dows commented 4 days ago

/dup #16683

microsoft-github-policy-service[bot] commented 4 days ago

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!