Rem0o / FanControl.Releases

This is the release repository for Fan Control, a highly customizable fan controlling software for Windows.
Other
14.54k stars 453 forks source link

Not launching on startup #2838

Open bagwetty opened 2 weeks ago

bagwetty commented 2 weeks ago

Love the app btw, it just wont launch on startup. This is consistent for both my machine and my partner's. Can provide more information if necessary. There are no errors in the log that I can see. I have tried delaying the launch at startup by several different values, all with the same end results. I have also tried manually adding it as a startup application w/in task manager It's honestly not a big deal, just something I figured I would point out.

My machine; https://pcpartpicker.com/b/Ydy48d

Rem0o commented 2 weeks ago

Do into task scheduler, try and run the "Fan Control" task manually: image

This is basically what gets fired when you log in.

Also, you need to user log in for the program to start. It won't run on "startup" without a login.

bagwetty commented 2 weeks ago

image Yah I already went through all of that and it still will only launch upon user input. As mentioned before, its honestly not a huge deal and it still works perfectly fine otherwise. Just a weird thing with seemingly only my system.

BrandonXue commented 1 week ago

I had a similar issue, where no amount of delay made it launch, and even manually clicking "Run" as seen the screenshot from @Rem0o didn't launch.

What fixed it for me is changing from "run only when user is logged on" to "run whether user is logged on or not" as well as checking "run with highest privileges". On Windows 11, select the FanControl task in the task scheduler, go to the right side panel and click "Properties", then you can change the setting under the "general" tab.

Screenshot 2024-11-20 233715

I think the reason for this issue is that I am using a non-admin account as my daily account. When you run FanControl in a non-admin account, it requires admin credentials to open. The task that gets created in Task Scheduler ends up having the admin account set as the author, so the task never runs under the default properties.