Skip to content
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 no longer allow snapping elevated (admin) applications #1513

Closed
LukaszMendakiewicz opened this issue Mar 9, 2020 · 5 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@LukaszMendakiewicz
Copy link

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.657]
PowerToys version: 0.15.1
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

  1. Create zones.
  2. Launch elevated process (e.g. Win+X > Windows PowerShell (Admin))
  3. Hold Shift and drag the window into the zone.

Expected behavior

Window snaps to the zone.

Actual behavior

Window does not snap to the zone.

Notes

This used to work before updating to 0.15.1. I believe the previous version I was on was 0.14.1.

@LukaszMendakiewicz
Copy link
Author

It works OK if PowerToys are launched elevated too. Did the mode PT launch in as the default changed between the versions?

@enricogior
Copy link
Contributor

@LukaszMendakiewicz
yes, the default has changed.
You can set it back to the old behavior using the general settings option "Always run as administrator".

@LukaszMendakiewicz
Copy link
Author

Thanks for clarifying. The release notes do mention:

Removed requirement to always 'run as admin'

But I don't think it communicates clearly enough that the default changed from running as admin to not, and it can affect the observed behavior.

@enricogior
Copy link
Contributor

We are planning to add a notification when we detect that an elevated window is moved while PT is running non elevated. We just didn't have the time to do it in 0.15.x

@crutkas
Copy link
Member

crutkas commented Mar 9, 2020

#1015 is the tracking issue, going to close this since we are tracking there. @LukaszMendakiewicz it is better for us to take this route so we aren't always running elevated (also most people don't use elevated processes (but we 100% know this is a scenario we must support))

@crutkas crutkas closed this as completed Mar 9, 2020
@crutkas crutkas added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants