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

Fan Control Don`t launch at startup

Open Chicora470 opened this issue 2 years ago • 14 comments

After the last update the program does not start at launch, i need to start manually, even if i set the startup and in windows startup section

Chicora470 avatar Nov 25 '23 19:11 Chicora470

I'm having the same issue except I can't even run it manually. I run it, get the UAC prompt, then nothing after that. No FanControl.exe task in the task manager either.

sparkymark75 avatar Nov 26 '23 14:11 sparkymark75

Hello,

I have the same problem.

I also tried to run the Updater.exe file and I got this error.
error-updater-fancontrol
The error can be translated to "Access to the access path 'C:\Program Files\FanControl\FanControl.Releases-120\de\Microsoft.Win32.TaskScheduler.resources.dll' is refused."

The error occurs when applying update for v174 so maybe something's up with it ? I got no clue.

MBoutray avatar Nov 26 '23 15:11 MBoutray

I also found the crash dumps when i tried running the program. I tried opening it with Notepad++ and nothing was readable. FanControl.exe.15448.dmp

MBoutray avatar Nov 26 '23 15:11 MBoutray

I just took a copy of my config, deleted the install, downloaded the latest version (v174) and then copied my config back across. Seems to be working okay now.

sparkymark75 avatar Nov 26 '23 15:11 sparkymark75

I just took a copy of my config, deleted the install, downloaded the latest version (v174) and then copied my config back across. Seems to be working okay now.

It worked for me too

Ccipo1998 avatar Nov 26 '23 18:11 Ccipo1998

Same here, but the first install wouldn't even start manually anymore. Reinstalled -> wont launch on startup again, however I can manually start it now.

Frenzaih avatar Nov 27 '23 08:11 Frenzaih

I just took a copy of my config, deleted the install, downloaded the latest version (v174) and then copied my config back across. Seems to be working okay now.

This also worked for me. Remember any plugins you have installed too! Either copy them or install again before loading your config.

tomfclarke avatar Nov 27 '23 14:11 tomfclarke

I just took a copy of my config, deleted the install, downloaded the latest version (v174) and then copied my config back across. Seems to be working okay now.

Did that too afterwards, worked like a charm.

It's the first time I've had an issue with this software (or just the update).
Pretty good ratio for the amount of time I've been using it. 👌🏻

MBoutray avatar Nov 27 '23 14:11 MBoutray

FYI, you just need to rename Newtonsoft.Json.dll and run the updater to have it fixed.

Ekristoffe avatar Nov 27 '23 15:11 Ekristoffe

Hello i did a fresh install of the .net 8 and im still having the issue, i deleted everything except "Configurations" folder and then extracted the .net8 version

vegetagaru avatar Nov 29 '23 09:11 vegetagaru

Has the Same Problem, i fix it with Download the Netframework 4.8 Version and Copy over my Installation. After this my Fancontrol runs fine again. Think the Problem came from the Netframework 8 Version, maybe some in the Updater who select the wrong Version over the Installed.

Fix: Download - FanControl_net_4_8.zip

Unzip and Replace all Files with your Exist Installation.

( Updated FIle found in the Release Assets Section https://github.com/Rem0o/FanControl.Releases/releases )

Than you can Run the Programm fine again.

Holli82 avatar Nov 30 '23 14:11 Holli82

tbh i was on the 4.8 and started having problems then i switched to the 8 version and still had problems xD so dunno

vegetagaru avatar Nov 30 '23 23:11 vegetagaru

I'm having this issue on FanControl V194_net_4_8 and the October 2023 version. ~~I attempted the workaround of making it start at user login via Task Scheduler. Had to check the admin privileges box. It doesn't work consistently for some reason as sometimes the task just doesn't run.~~ The issue got fixed when I downloaded FanControl_194_net_8 Windows 10, 64 bit, latest update.

ars4l4n avatar Jul 02 '24 14:07 ars4l4n

FYI, you just need to rename Newtonsoft.Json.dll and run the updater to have it fixed.

???

ars4l4n avatar Jul 03 '24 09:07 ars4l4n