Rem0o
V236 NET 8.0 sensors getting lost after every reboot.
With startup shows error of all sensors, used to work reloading configuration, but this stopped working. The only sensor recognized - is my AMD graphics card. Reloading Fan Control after the startup with admin rights does help after some time.
I'm getting this same issue. Just installed the latest Nvidia drivers for my GPUs, restarted and Fan Control not can't find any of my case fans, only the GPU fans. Updated to the latest FC version and tried to reload the configuration, also copied over a backup config and still no fans show. Tried to refresh the sensors and it says that LibreHardwareMonitor could not initialize or has no sensors. Is it possible that Libre isn't running after my restart? Is this baked into the app or do I need to launch it as a separate process? Any help would be appreciated!
Edit: Uploaded my FC log.txt log.zip
Edit 2: I exited FC then opened the LibreHardwareMonitor.exe, then reopened FC and now it seems to work without issue. I set the LHM app to open minimized when Windows starts.
I experienced this issue this morning after a Windows Update ran last night; looks like windows defender started blocking a driver, detecting it as VulnerableDriver:WinNT/Winring0.G. I was able to find the entry in Windows Defender's Protection History, clicked "allow", restarted my system, and then the missing Sensors and Controls were restored.
This just happened to me as well. I was able to restore FanControl functionality by allowing the 'malicious' file from Windows Defender
has been happening to me on the net4.8 version consistently whenever i use the alternate LHM. PawnIO is installed, instructions followed exactly to the letter, and both Vigorf.A from before and the new Winring0 flag above are allowed in windows defender. app works fine when using the stock LHM.
I had the same issue which seems to have been fixed temporarily by rolling back upgrade from .NET 8.0.20 to 8.0;19: https://builds.dotnet.microsoft.com/dotnet/WindowsDesktop/8.0.19/windowsdesktop-runtime-8.0.19-win-x64.exe
winget.exe install --id "Microsoft.DotNet.DesktopRuntime.8" --exact --source winget --accept-source-agreements --disable-interactivity --version "8.0.19" --silent --accept-package-agreements --force
still using PawnIO and patched LHM.dll but my fans are now found on boot without error
Commenting to say that I had the same issue, and like @jsonu26a1 it was Windows Defender blocking it after a Windows Update. Except in my case I had to create a C:\DefenderRecovery empty directory first before I could force Windows Defender to allow it. Once I was able to restore the sys file and allow it, everything works as expected.
Same issue with the sensors on startup. Although my windows defender do not seems to be the culprit, as I cannot find anything related to this in his history.
Also even my curves stops showing, even though if I check the config file, they are still in it. could it be just trouble reading the userconfig file ?
Last night I manage to get it back by completely unistaling fancontrol and doing a all new fresh install, which broke this morning...
Same issue I guess, I updated setup with the alternate LHM and PawnIO is installed, but When I open FC Fans dont have my curves assigned and I see too many Fans. :( Also GeForce Fans just dont show anything, they are detected but there is no info about RPM or % FC was such a good software now I need to find new one
Just had this pop up again after a Windows update. @jsonu26a1, thanks for the suggestion to allow the vulnerability in Windows Defender. That worked immediately and didn't require a system reboot, just had to restart FanControl 🙏
I've been getting the same issue on V236 and V237. Try using V235, works for me.
I'm having the same issue. Except I can't "allow" the drivers through Defender for some reason--maybe because they're listed as a 'Severe' threat?
@rhomble
I'm having the same issue. Except I can't "allow" the drivers through Defender for some reason--maybe because they're listed as a 'Severe' threat?
I had this same exact issue. It was listed as a severe threat on mine as well, with no ability to perform any actions on it. It wasn't until I created an empty folder in C:\DefenderRecovery (and a reboot) that allowed me to take some kind of action on it. Maybe that'll work for you too, assuming you don't have that directory. I can't tell you why that works, but somehow discovered that with varying Google searches.
I'm having the same issue. Except I can't "allow" the drivers through Defender for some reason--maybe because they're listed as a 'Severe' threat?
Not sure if we had the same problem, so I'll be verbose:
I went into Windows Security -> Virus & threat protection -> Protection History (bottom of the "Current threads" section). There were several reports of the driver, named "Threat blocked" or "Threat removed or restored", all listed as Severe. Only the first report - lowest in the list and called "Threat quarantined" - had an "Actions" button, which allowed me to restore it.
(this all being Windows 10, i don't know if it looks different in 11)
There was no mention of Windows defender blocking this file in my notifications. Thanks for the post and fix, the fan errors were driving me crazy thinking something was wrong on my end when it was Windows Defender blocking fancontrol.sys
