FanControl.Releases icon indicating copy to clipboard operation
FanControl.Releases copied to clipboard

Autostart works only for the system user who enabled the setting

Open kamild1996 opened this issue 2 years ago • 6 comments

Fan Control creates a scheduled task to make itself start automatically on boot. The problem is that the task is setup to use the currently logged in user for running the task, which has the side effect of the task not starting properly when other system accounts are used.

This seems easily fixable within the created task by changing the user account used for running the task to "Users".

kamild1996 avatar Feb 28 '23 18:02 kamild1996

How would that play out with the run as admin requirement?

Rem0o avatar Feb 28 '23 19:02 Rem0o

How would that play out with the run as admin requirement?

It plays along, "Run with highest privileges" option is still respected, so it runs with admin rights on any system account as long as that account is in the "Administrators" group. I did test that task change with Fan Control, seems to work without any hiccups on Windows 11.

kamild1996 avatar Feb 28 '23 19:02 kamild1996

The task it create now seems for any user and at highest privileges but this does not support limited access accounts..

IslandJohn avatar Mar 16 '23 22:03 IslandJohn

I'm running into this with my personal and work user accounts. Both user accounts have administrator capabilities.

I installed and enabled "Start at user log on" on my personal account. This works fine when logging in as personal, however, FanControl does not start automatically for my work user.

Edit: Windows 11 Home

ecd0011 avatar Oct 15 '24 14:10 ecd0011

Hi, if you want auto-start on 2 different users, you'll need to duplicate the scheduled task in task scheduler and run it on that new user. Should do the trick.

Rem0o avatar Oct 15 '24 14:10 Rem0o

Thanks @Rem0o! That did the trick.

For future reference, the issue was that the task was set to run as my "personal" account but only when that account is logged in.

I also tried @kamild1996's solution of setting to run as "Users" instead of a specific user. I didn't know where I needed to do this, hence my first comment, but this change also worked for me after trying it.

If anyone wants to try this:

  1. Open Task Scheduler.
  2. Find the FanControl task.
  3. Right-click. Open Properties to change the user. Export and import to duplicate.

ecd0011 avatar Oct 15 '24 15:10 ecd0011

Thanks @Rem0o! That did the trick.

For future reference, the issue was that the task was set to run as my "personal" account but only when that account is logged in.

I also tried @kamild1996's solution of setting to run as "Users" instead of a specific user. I didn't know where I needed to do this, hence my first comment, but this change also worked for me after trying it.

If anyone wants to try this:

  1. Open Task Scheduler.
  2. Find the FanControl task.
  3. Right-click. Open Properties to change the user. Export and import to duplicate.

I tried this and Fan Control still doesn't start on logon for non-Admin users. Is it the elevated privileges that causes an issue?

AnloWho avatar Feb 16 '25 19:02 AnloWho

Is it the elevated privileges that causes an issue

Yes

Rem0o avatar Feb 16 '25 19:02 Rem0o

From a user point of view, the esisest way would be to go to the scheduled task, look for FanControl and then change the settings as shown here: Image Basically this means that it's gonna run as soon as the computer boots using the saved Administrator credentials regardless on which user is logging on. I've put "Administrator" as an example, but it needs to change according to what your administrative user account is. Anyway, please note that you will NOT see the icon on the bottom right when you login with a different user, let's call this User1, as it will only be visible when Administrator logs in, however this will allow FanControl to start in background with the administrative credentials all the time, which means that the user profile is turned on.

I've personally checked this on my GPU which would otherwise idle at 65°C and it's now idling at 49°C, so it works.

FranceBB avatar Feb 17 '25 14:02 FranceBB