Rem0o
All sensors & controls disappeared after updating to V231, except for GPU ones.
Screenshot:
All sensors & controls disappeared after updating to V231, except for GPU ones. Did LibreHardwareMonitor just die for some reason? I assume the GPU bits are still up bc it's the only thing using a different API...
log.txt file: log.txt
Specs: Gigabyte B550 Aorus Pro Ryzen 5700X RTX 3070Ti
I had the same thing happen to me when I enabled "secure boot" so I could play the Battlefield 6 open beta. Seems like LibreHardwareMonitor won't run with secure boot enabled?
Edit: PC specifications added: Gigabyte B550 Aorus Pro AMD 5900X Nvidia RTX 3080
I had the same thing happen to me when I enabled "secure boot" so I could play the Battlefield 6 open beta. Seems like LibreHardwareMonitor won't run with secure boot enabled?
Interesting. I did the same, but this didn't happen until today when I updated to V231. I've been playing the BF6 beta for a few days now but only today did I get this.
Seems like a recurring issue dating back to 2020, possibly earlier with IT8792E -- which both of these complaints seem to use on their Gigabyte B550 boards. Hell, people have complained about IT8792E having issues with Fan Control since 2021. It appears to be a well documented issue though, with some people claiming that LHM is persistent about not wanting to function with IT8792E, thus requiring you to use Gigabyte's silly proprietary software. These sources are a bit outdated, but fairly recently this discussion about IT8792E not wanting to cooperate has resurfaced. The solutions proposed in that thread are... not ideal. They basically boil down to "run an older version of LHM that IT8792E will work nicely with", or "plug all your fans into headers not controlled by IT8792E". GLHF.
I had the same thing happen to me when I enabled "secure boot" so I could play the Battlefield 6 open beta. Seems like LibreHardwareMonitor won't run with secure boot enabled?
Edit: PC specifications added: Gigabyte B550 Aorus Pro AMD 5900X Nvidia RTX 3080
Update: I updated the motherboard BIOS from F14 to F17, re-enabled secure boot and now FanControl is working fine. Not entirely sure what the issue was, but it's fixed now for me.
Same issue here, i lost everything minus GPU controls. I went as far back as V220, no avail, program doesnt want to see the fans, tried setting everyting to PWM, didnt work. I have had secure boot on for ages, dont know what changed recently, everything broke for me on V230 and i cant get it back.
MSI X670E Tomahawk AMD 7800X3D Nvidia 4090
Seems like a recurring issue dating back to 2020, possibly earlier with IT8792E -- which both of these complaints seem to use on their Gigabyte B550 boards. Hell, people have complained about IT8792E having issues with Fan Control since 2021. It appears to be a well documented issue though, with some people claiming that LHM is persistent about not wanting to function with IT8792E, thus requiring you to use Gigabyte's silly proprietary software. These sources are a bit outdated, but fairly recently this discussion about IT8792E not wanting to cooperate has resurfaced. The solutions proposed in that thread are... not ideal. They basically boil down to "run an older version of LHM that IT8792E will work nicely with", or "plug all your fans into headers not controlled by IT8792E". GLHF.
Its not just Gigabyte Motherboards now, its MSI ones too, im getting the same issue as stated above, i have done literally everything, including turning off Secure Boot and turning it back on. Im convinced this is probably some change in Windows at this point because none of my MB BIOS settings changed until i saw all the sensors were gone.
Its not just Gigabyte Motherboards now, its MSI ones too, im getting the same issue as stated above, i have done literally everything, including turning off Secure Boot and turning it back on. Im convinced this is probably some change in Windows at this point because none of my MB BIOS settings changed until i saw all the sensors were gone.
I'm not sure where I gave the impression this was limited to Gigabyte motherboards. IT8792E is, in extremely oversimplified terms, a chip that gets slapped onto motherboards. I don't know whether IT8792E is limited to one manufacturer, and so I make no claim about that. It just seems like the overwhelming majority of people who complain about IT8792E use Gigabyte boards. I'm also not sure why you're so confident that it is an OS related issue just because you checked some BIOS settings -- all the replies thus far have actually been very conclusive that manually entered BIOS settings are irrelevant; the person who originally made the claim that it was related to secure boot literally commented again in the same day to say that it works fine with secure boot enabled after updating BIOS.
If anything, I think the only viable conclusions to be made are: (1) using an outdated BIOS may be related, backed by the claim above about updating BIOS resolving the issue; and/or (2) there is specifically a problem with how LHM is trying to retrieve information from IT8792E (and/or other 'chips slapped onto motherboards'), which is supported by all the references linked in my previous reply that literally complain about LHM not being able to retrieve sensor information from IT8792E. To further back this claim, here's someone complaining 2 weeks ago that their MSI board also fails to report some information to LHM.
I don't doubt that an OS-induced issue could be relevant, but so far there's not exactly a whole lot of evidence for that besides you saying "i tried everything, so it must be the OS". The only concrete step you've listed as trying is toggling secure boot. Can you list what else you have tried that leads you to believe this is an issue rooted in the OS? Do you know other people using the exact build of Windows you are using who experience the same problem, and also a group of people using an older build who are not experiencing this problem?
I think it'd be helpful to try 2 things here to help truly rule out the two problems that you've so quickly rejected:
- To rule out BIOS revision related issues: update BIOS, or at the very least mention what BIOS revision you are using.
- To rule out LHM specifically being the problem: try running with the HWInfo plugin and using the HWInfo sensors rather than the builtin LHM dependency. I can't be certain that HWinfo and LHM pull sensor data in different ways, but this will at least help identify whether the problem is isolated to the LHM dependency.
I'm not sure where I gave the impression this was limited to Gigabyte motherboards. IT8792E is, in extremely oversimplified terms, a chip that gets slapped onto motherboards.
You didnt, its just interesting thats an obvious pattern. This particular MSI board uses a chip called NCT6687D.
HWInfo is fine, im getting accurate readings. The reason im pushing OS is because its the ONLY THING that has been consistently changing over the last few weeks for me.
Timeline: 5 months ago, rebuilt OS, complete wipe. BIOS, Chipset, overall complete update, bios revision 7E12v1H. SecureBoot Enabled. FanControl working great.
Jump forward to a week ago or so: v230 hits, updates, lose everything except GPU sensors, start to search here. SecureBoot still enabled. Updated BIOS to latest stable (7E12v1J), nothing, turned secure boot off, nothing, turned secureboot back on, nothing. Set all fans to PWM, nothing, turned off all smart fan settings, nothing. Downgrading to V229, V225, V220, nothing. No changes to hardware configuration at all during this time.
HWInfo plugin does not apply controls but sees the sensors
No I dont know anyone else using this latest OS build and FanControl. I let Windows auto-update on this machine for specific reasons i wont get into.
Windows build is 11 Pro, 26100.
Logically, the only thing that makes any sense at this point is something in the OS is causing this at this point. I dont know what, im not sure what, i guess i am simply just reporting this at this point. I have already set curves in my BIOS. Im just trying to help at this point, there is alot of "Works on my machine" posts going around all over and its been frustrating finding a solution.
I appreciate the detailed response @SpaceballsTheGithubName -- it helps narrow it down a lot. Seeing that your board uses NCT6687D gave me some quick flashbacks to when I reported similar (albeit not identical) fan issues with my Z790 Edge Ti, and what a happy little coincidence that my board shares that same chip. Considering HWInfo is able to see the fans whereas LHM is not, it really sounds to me that there's something off with how LHM is trying to pull sensor info. Adding some degree of confirmation to that, someone has reported that readouts for MSI boards no longer functions with 'blanket logic', meaning the fundamental issue falls on LHM.
So, the good news is that I don't think this is a Windows issue which means I don't have to suggest you performing a clean OS install! Yay! The bad news is that it's becoming increasingly likely that this is a problem with LHM which places the responsibility of finding a solution in the hands of developers for LHM, not FanControl.
The bad news is that it's becoming increasingly likely that this is a problem with LHM which places the responsibility of finding a solution in the hands of developers for LHM, not FanControl.
If this is the case who knows how long its going to take, shame really. BIOS adjustments for me until its working again i guess.
Edit: i disabled the HWinfo plugin and got this from the next bootup
Unless i am mistaken, its finding the sensors, but not adding them to the program in this particular case.
I had a similar problem as described here and noticed that Windows defender seems to have quarantined the FanControl.sys file because it contains the Winring0 driver (https://github.com/GermanAizek/WinRing0) that has some problems (https://gamersnexus.net/features/insecure-code-vs-entire-rgb-industry-winring-0-driver-ft-wendell-level1-techs as a writeup) with security. After reinstalling FanControll and actively unquarantining the file i was able to see my sensors again.
Whether this is a library that comes with FanControll or with LHM i do not know, but I hope this information helps in finding a fix.
I had a similar problem as described here and noticed that Windows defender seems to have quarantined the FanControl.sys file because it contains the Winring0 driver (https://github.com/GermanAizek/WinRing0) that has some problems (https://gamersnexus.net/features/insecure-code-vs-entire-rgb-industry-winring-0-driver-ft-wendell-level1-techs as a writeup) with security. After reinstalling FanControll and actively unquarantining the file i was able to see my sensors again.
Whether this is a library that comes with FanControll or with LHM i do not know, but I hope this information helps in finding a fix.
Thank you so much my fan control is working again!
I had a similar problem as described here and noticed that Windows defender seems to have quarantined the FanControl.sys file because it contains the Winring0 driver (https://github.com/GermanAizek/WinRing0) that has some problems (https://gamersnexus.net/features/insecure-code-vs-entire-rgb-industry-winring-0-driver-ft-wendell-level1-techs as a writeup) with security. After reinstalling FanControll and actively unquarantining the file i was able to see my sensors again.
Whether this is a library that comes with FanControll or with LHM i do not know, but I hope this information helps in finding a fix.
Mine started working after restoring the quarantined file. Thank you.
I had a similar problem as described here and noticed that Windows defender seems to have quarantined the FanControl.sys file because it contains the Winring0 driver (https://github.com/GermanAizek/WinRing0) that has some problems (https://gamersnexus.net/features/insecure-code-vs-entire-rgb-industry-winring-0-driver-ft-wendell-level1-techs as a writeup) with security. After reinstalling FanControll and actively unquarantining the file i was able to see my sensors again.
Whether this is a library that comes with FanControll or with LHM i do not know, but I hope this information helps in finding a fix.
upvoting this as a solution to the same problem! thanks a lot! remember to backup your config before doing anything, its a hassle to re setup everything
Just updating here as well.
I set my curves in my MOBO settings and ignored FanControl, kept it installed and controlling my GPU fans to see if it would resolve eventually. After the latest or previous windows update (not sure which), i am not sure if this is a FanControl thing or potentially a LHM update, the most recent FanControl update popped up on startup and all my sensors came back. I did not put an exception in Defender, i did not make any significant changes, but the problem seems to have fixed itself. Not sure whats going on here, someone more savvy in both LHM and Windows updates might be able to shed some light.