Trojan:Win32/Vigorf.A DETECTED

[ToXiCEngel]

I've used FanControl for years without issue until today. Thia morning Windows Security notified me that it detected Trojan:Win32/Vigorf.A in FanControl (v234, .net 8). Is this a legitimate threat or something I should allow? Blocking the threat prevents FanControl from detecting all sensors.
I found it odd that I've used v234 since its release without issue and only today did I get this notification. I checked the Microsoft Security changelog for the release it installed this morning but this particular threat wasn't on the list of new threats. So I'm left wondering what the heck is going on. Anyone else encounter this?

[MaterialJason]

I'm actually looking into this now I think it might be a false positive because windows detected it and immediately said it wasn't a threat right after.

[MaterialJason]

So from what I see so far it looks like windows has decided to SMITE Fan Control after it perceived the threat. My Fan Control can no longer see any sensors and claims the threat has been blocked. I've also been using v234 since its release so I'm thinking windows just over reacted to something trying to read hardware sensors but we'll see here soon enough. I'd keep it blocked for now until the devs come in and tell us whats going on.

[ToXiCEngel]

I checked the more detailed description in the MS Security threat history and it flagged this as the culprit
driver: R0FanControl
file: FanControl.sys

[MaterialJason]

I just checked the issues tab and someone said the same thing. I uninstalled it for the time being but I hope the devs get to this soon. Looks like everyone's getting in pinged.

[olinapa]

I just checked the issues tab and someone said the same thing. I uninstalled it for the time being but I hope the devs get to this soon. Looks like everyone's getting in pinged.

i also have this issue like thousands people. how do you actually formally uninstall Fancontrol?

[Rem0o]

See #3410