-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Run At Startup - Option to start minimized #26507
Comments
Settings is only supposed to appear if you try to run PowerToys while PowerToys is already running. Do you for example have both the Task Scheduler and another run at startup method for PowerToys at the same time? What window is actually opening every time for you? |
Hi,
This issue was happening on my work PC which is currently being fixed and I can't check it. I do remember manually adding it to the startup folder. This PC has PowerToys installed and it works to use the fancy Zone, but it doesn't appear to be running at all (not in the system tray).
When the work PC is fixed I will play around a bit (remove it from the startup apps folder) and try to report back. I think I added it to the startup folder because it wasn't starting up, but even when the main interface comes up on bootup it would disable FancyZones (the only thing I use) every 10th boot or so.
I will attach the window that pops up on bootup...
Hope that helps,
Edd
…________________________________
|
/needinfo i'm betting they put PowerToys in startup and we have our startup process as well. this would cause settings to pop up. |
sorry, /reportbug |
Description of the new feature / enhancement
It would be nicer for the application to start minimized as currently I have to close it each time I start up my machine. If there was an option for this it would be fine, but it would also be fine for it to default to not bring up the PowerToyys Settings window every time I boot up the machine
Scenario when this would be used?
Always
Supporting information
No response
The text was updated successfully, but these errors were encountered: