Upgraded to 0.16.0 and FancyZones not working neither can I uninstall
See original GitHub issueEnvironment
Windows build number: [run "ver" at a command prompt] [Version 10.0.18362.657]
PowerToys version: PowerToysSetup-0.16.0-x64
PowerToy module for which you are reporting the bug (if applicable):
Steps to reproduce Editing
After editing Zones, applied layout selected (doesn’t mater if predefined or custom) nothing happens. Tried to uninstall PowerToys via Programms and features, runs through the steps and explorer restarts before it completes - PowerToys never gets removed
Expected behavior
Actual behavior
Screenshots
Issue Analytics
- State:
- Created 3 years ago
- Comments:26 (10 by maintainers)
Top Results From Across the Web
PowerToys Fancy Zones Custom Template not showing ...
I've just installed Powertoys(preview) v0.69.1 directly from Github. When I create a custom template it it shows in the list custom ...
Read more >PowerToys FancyZones utility for Windows
A window manager utility for arranging and snapping windows into efficient layouts.
Read more >Windows 10 PowerToys - A Cheat Sheet - TechRepublic
What can Windows 10 PowerToys do? Here is a list of available Windows 10 PowerToys with a brief description of what each toy...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Currently having the same issue with FancyZones not working with this update. I’ve created my zones and hold shift when dragging but instead of the zone lighting up, my window I’m dragging just goes transparent.
@vohzi it’s confirmed, you had a similar problem as in https://github.com/microsoft/PowerToys/issues/1821 even if in your case it wan’t the remote desktop but the receiver (different devices generating a similar device id that we were not processing correctly)
@MannyQED I’m assuming something similar was also happening to you, so I’m closing this issue for now as a duplicate of https://github.com/microsoft/PowerToys/issues/1821 (as explained above, the bug is the same for different scenarios)
Thank you for helping identifying the problem and sorry for the regression.