-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Windhawk in non-administrator account? #260
Comments
Mods aren't launched. Mods are injected into processes. If a process runs as administrator, the mod code which runs inside it runs as administrator.
The Taskbar Styler that's injected into the explorer.exe instance of Guest runs in Guest's environment, and if the theme isn't adjusted properly, it means that something's wrong with the style, or that the style is just designed for dark mode.
It's not clear what exactly you want. If you want different users to have different mods, or different configurations of mods, then the standard Windhawk installation doesn't support that, and you can try the portable version. If you want the styler mod to adjust to the theme, you need to improve your style definitions. |
Maybe the mod follows the first logged on account because previous explorer is still running so still hooked by the mod |
Each mod is independent, mods don't communicate with one another. But sure, test it and post back. |
I have 2 accounts, one is administrator, and other one is not. I'll call this Guest
Windhawk and its mods are launched always as Administrator or SYSTEM (although no UAC prompt) and when I logged on those 2 accounts, the mods in Guest still work baed on Administrator
e.g. Taskbar Styler works as Dark Mode, but guest is Light Mode
Can I get the portable or current user only-Windhawk? I want to run 2 parallel instances or mods—I want the latter more—in diffrent accounts/privileges
+another best option is prevent running on Guest and let running only in 1 account. on or in anyways idk whichs correct sry for my english
The text was updated successfully, but these errors were encountered: