FanControl.Releases
FanControl.Releases copied to clipboard
Rem0o
Not Starting with WINDOWS
FanControl doesn't start automatically with windows even if it is configured in the program itself and also added to the shell:startup.
With the next windows start the configuration tick of the program "Start with Windows" changes to "Not Selected" automatically
Just checking that you're a local admin of the PC? I tried everything I could to get auto-start working as a standard user, but nothing helped. Ended up having to change my user to Admin as found FanControl so useful!
Can confirm last 3 or 4 versions do not start automatically with Windows when previous versions did.
If you take a look in the Task Scheduler for the task named "Fan Control", it is created properly? Can you run it manually?
Sure -- running it manually does not start FanControl. Here's what it looks like in situ (I've had FanControl installed for about 14 months now):
Wait, how can it has never run?
Also, can you just run the command line in the FanControl folder and see what's wrong?
That’s what I was wondering. Also, I’m in the office now so won’t be able to check the command line until later...
Sent from my iPhone
On Jan 25, 2022, at 6:43 AM, Rem0o @.***> wrote:
Wait, how can it has never run? Also, can you just run the command line in the FanControl folder and see what's wrong?
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.
Also, can you just run the command line in the FanControl folder and see what's wrong?
Sorry, do you mean Unregister_Startup_Task.cmd?
If I run the command ( start /B FanControl.exe) from a prompt in the program folder without the /c switch, it starts FanControl OK.
Thought this was odd, though.
Huh. Tried to change it to Windows 10 and save the task and got an error message:
I am using admin account from the beginning and I cannot make the FanControl start with windows, no matter what I've tried.
I'm asking because I see "Medium Mandatory Level" as a user account, thought that was a strange name and it might not be the admin one.
Well I'm really out of ideas here. The task is there, its command work, admin rights and everything. Sorry 🤷♂️
Something seems misconfigured in the task scheduler item, though, right? I mean if it won't let me save the item after opening it (even if I make no changes other than add a period to the end of the description phrase)...
You can't change the Windows Vista thing. That's basically the versioning of the task, saying how far back it is retro-compatibility. That was fine don't change it.
I am using Avira antivirus and malwarebytes which quarantined FanControl.exe after my first use of the software. I don't know whether it has something to do or not.
You can't change the Windows Vista thing. That's basically the versioning of the task, saying how far back it is retro-compatibility. That was fine don't change it.
That's not what I'm saying - what I mean is you can't alter anything, even a label (see screenshot) without it refusing to save the task again. So something's not right there, clearly.
Try deleting it all together, go back in FanControl and tick the box again, it will recreate it from scratch.
Will do when I get home from work and will report back...
Sent from my iPhone
On Jan 26, 2022, at 6:52 AM, Rem0o @.***> wrote:
Try deleting it all together, go back in FanControl and tick the box again, it will recreate it from scratch.
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.
OK, so I
- deleted the Task Scheduler entry.
- Ran Fan Control manually, set it to start with Windows, saved config.
- Checked that new Task had been created - it had.
- Rebooted.
- No autostart still.
Just to see if anything had changed, I added a couple of characters to the description of the task item as above, and it once again would not save, and threw the same error message.
I am using Avira antivirus and malwarebytes which quarantined FanControl.exe after my first use of the software. I don't know whether it has something to do or not.
Just now I found that Malwarebytes had quarantined some tasks related to FanControl (most of the quarantine list didn't include "fancontrol" in the name, but were also needed so be careful allowing some of those quarantined items).
Un-quarantining those items within Malwarebytes brought back the Start with Windows function for me.
FWIW I use no antivirus other than Windows built-in.
What I did do was manually add my user account with the 'Change User or Group' button to the task scheduler task definition, and that seems to have fixed it. Not sure why it used to work and stopped for me a few versions back (nothing else has changed on my machine, other than I think an update to Win10 21H1 maybe).
I am using Avira antivirus and malwarebytes which quarantined FanControl.exe after my first use of the software. I don't know whether it has something to do or not.
Just now I found that Malwarebytes had quarantined some tasks related to FanControl (most of the quarantine list didn't include "fancontrol" in the name, but were also needed so be careful allowing some of those quarantined items).
Un-quarantining those items within Malwarebytes brought back the Start with Windows function for me.
I have also un-quarantined FanControl, but even it is not starting automatically :(
But I need to find out the other FanControl relevant files and un-quarantine them. Let's see whether it works or not.
I have un-quarantined the FanControl folder, but it still doesn't start with windows :(
I solved the issue by changing these task settings:
- Change the user to your usual account name in security options
- Make sure to only execute if the user is logged in
- Change the trigger from any user to your usual account
I have this problem too. I do have Malwarebytes, but it isn’t eating any task or files for FanControl. Anyone got it working? Very awesome tool, hope I get it working again.
Edit: Apologies, commented too early, I ended up changing the command and directing the task to run the .exe. Seems to have worked for now.
