Controlling administrator windows #403
Replies: 1 comment 1 reply
-
Hello @vertigo220, Thanks for the feedback. Actually, a workaround is possible and already implemented, though I can't find a working workaround for this specific hotkey at the moment. The existing workaround allows WindowTop to handle elevated/admin windows seamlessly. When you attempt to use one of its features on an elevated/admin window, WindowTop prompts a confirmation request via the OS, asking for permission to run as admin. Behind the scenes, WindowTop launches a secondary helper process with admin privileges. This process communicates with the main application whenever an elevated/admin window is detected. On the first attempt to enable a feature like Always On Top, the secondary process isn't running yet. At this point, the OS prompts you with a confirmation request (via UAC). Once approved, the secondary process starts, and subsequent commands for elevated/admin windows are sent directly to this process with admin permissions. You can read more about it here: #241 (comment) This is how it works. PowerToys does not implement a similar mechanism. In fact, WindowTop is more sophisticated than PowerToys in many ways. Just because PowerToys carries the "Microsoft" name doesn't make it inherently better. Their developers don't have access to any exclusive internal OS details or APIs. |
Beta Was this translation helpful? Give feedback.
-
Regarding this statement from the releases page:
you may find this useful:
https://learn.microsoft.com/en-us/windows/powertoys/administrator
I don't think a workaround is possible. I've struggled with this issue myself in one of my own projects, and even Microsoft's own app is pretty clear that it can't be done. So probably not worth the time trying to figure it out.
Beta Was this translation helpful? Give feedback.
All reactions