Rem0o
"Fail to initialise" keeps popping up after upgrading to v224
I was running v223 portable and updated to v224 when the prompt appeared. All was well immediately after the update.
I then turned my PC off to touch some grass. Came back to turn my system on and was greeted with the "Fail to initialise" popup from FanControl which you sometimes get when starting the system cold. The issue this time is that it doesn't seem to go away even after doing multiple restarts. I don't think it affects FanControl's functionality notwithstanding the prompt, as it seems to carry on working after clicking "OK" to make the prompt go away. But I haven't checked thoroughly since, after multiple restarts to make that prompt go away, I have given up for now and reverted back to v221 which is the latest version of FanControl I have in my backup.
I guess I'm just posting here to see if anyone else is having similar issues as mine.
As an aside, is there a recommended way to update to a version that is not the latest offered in the automatic prompt? v223 was working fine for me so I would rather go back to v223 instead of staying on v221 but obviously v224 is the one offered in the automatic update right now.
I'm staying with 217 for a very long time. I finally managed to make it work as I should, so no need for any upgrade in any near future. I'm sure with new version I will have lots of issues again, like missing sensors and settings all ramps for all the 7 fans manually again! I did that too many times in last couple of months, and I have enough of this.
"Fail to initialise" means there is a log. Please provide it so I can take a look.
I've attached the log.txt file as per your advice. Perhaps I should provide some additional descriptions for clarity.
After the initial v224 update and subsequent PC startup from cold, when I double-clicked on FanControl in the System Tray and the FanControl window popped up, nothing seemed amiss. But when I clicked the X on the top right to close the window, a prompt would come up and asked to the tune: "you made changes, do you want to save?" even when I hadn't made any change. If I then clicked Discard in this popup, everything would remain normal, and I wouldn't notice anything amiss even after subsequent restarts (i.e. no error popup when starting system). However if I clicked Save for the popup, at first nothing would be amiss until the very next system startup, at which point the "Initialisation fail" prompt would popup every time.
Upon looking at log.txt for events after the update to V224, the entries seem to suggest the HWiNFO plugin for FanControl is to blame. I have the latest version of that plugin (v1.4) in the Plugins folder.
06.05.2025 11:05:13: Open - HidSharp.Exceptions.DeviceIOException: Failed to get info. at HidSharp.Platform.Windows.WinHidDevice.RequiresGetInfo(GetInfoFlags flags) at HidSharp.Platform.Windows.WinHidDevice.GetProductName() at LibreHardwareMonitor.Hardware.Controller.Razer.RazerGroup..ctor(ISettings settings)
The Razer device access is what's failing. I believe this will faill if synapse runs at the same time. You can disable it from the sensor source section in the settings (controller checkbox).
I went into Edit Sources under Settings but the "Controller (various third parties)" is already unchecked? Please advise.
I have never own Razer stuffs so not sure why this has been triggered.
I had this popup as well and discovered v224 wasn't remembering the status of the HWinfo plugin between reboots. I had disabled it as CorsairLink plugin handles that duty now and a little smoother. Every reboot it's enabling it and saying it can't initialize because HWinfo isn't running on my system anymore. Side note, when I uncheck HWinfo it removes it from the plugins list entirely.
I had this popup as well and discovered v224 wasn't remembering the status of the HWinfo plugin between reboots. I had disabled it as CorsairLink plugin handles that duty now and a little smoother. Every reboot it's enabling it and saying it can't initialize because HWinfo isn't running on my system anymore. Side note, when I uncheck HWinfo it removes it from the plugins list entirely.
Images of the above:
The error it throws on startup.
Showing no sensors and enabled.
Showing enabled again.
Here I've unchecked and hit save
It saves and for some reason HWinfo disappears from the list of plugins on both screens.
I can then hit save manually or just close and it asks to save the config, I confirm. If the program is closed out entirely and reopened the Initialization retry failed message pops up again and HWinfo is once again loaded and enabled.
Edit: Removing the HWinfo plugin files resolves this issue for me.
i have the same problem, and after i removed HWinfo plugin and save the config, error doesn't show again
This issue seems to have been resolved in V225: I haven't encountered this issue since updating to V225.
I've been getting the same, only mine is referencing ADLX in the log. Issue seems to be that disabling ADLX is not persisent (I'm using ADLXWrapper). I can disable ADLX, refresh sensors and everything is good. Restart the system and ADLX plugin is re-enabled and throws the error.
27/05/2025 5:28:13 PM: ADLX plugin: ADLXWrapper.ADLXEception: ADLX was not initialized before getting system services at ADLXWrapper.ADLXWrapper.GetSystemServices() at FanControl.ADLX.ADLXPlugin.Initialize()
27/05/2025 5:28:20 PM: Try refresh failed. Retry count (6) exceeded. ADLX could not initialize or has no sensors.
Edit: just saw the comment re: v225 - mine hadn't prompted for update. Checked manually and updated so will see how it goes.
