glazewm
glazewm copied to clipboard
[Bug] GWM Rules Do Not Properly Target Elevated Processes
So, I've been doing a bit of testing, trying to get GWM to always ignore CMD run as Admin, and literally no rule works until you reload the GWM config with the elevated window open.
Things I've tried:
- command: "ignore"
match_title: "<title>"
- command: "ignore"
match_process_name: "cmd"
match_title: "<title>"
For title:
"/Administrator/"
"/^.*Administrator.*$/"
"/.*Administrator.*/"
"/Administrator.*/"
And just for giggles:
"Administrator"
I bring this up since I've encountered a couple modern games that also run as elevated processes, following a similar mismanagement pattern, though this is a bit more expected since I push games to a different workspace rather than outright ignoring them.
Successfully ignored Admin CMD:
Fresh Admin CMD window before refreshing GWM config:
Fresh Admin CMD window after refreshing GWM config:
I don't know why this is still a thing, but I'm beginning to wonder if there's some kind of weird pollution effect going on within GWM's temp files, as there were similar anomalous effects that purging helped with before.
+1 i wonder that too kind of annoying when using non + elevated windows
The application is now signed and uiAccess is enabled 🎉 Admin windows can finally be managed without running the WM as admin