Winring0 Driver being used(banned by windows 10/11 and virtually all anti-cheats)

[Raxisphasmatis]

Describe the bug
Programs\Turing System Monitor\main.sys is using WinRing0 driver

To Reproduce
Steps to reproduce the behavior:

1. Load Windows 11
2. Install and run the Turing System monitor
3. Windows and anti-cheats detect Programs\Turing System Monitor\main.sys and block it
4. certain functions such as cpu temp don't work after that

Expected behavior
Cpu temps as normal

Additional context
Windows detects and blocks WinRing0 drivers now, but adding an exclusion no longer works as windows stops it again, additionally most anti-cheat programs now also won't let you play games while anything using WinRing0 drivers are loaded(RGB, Fan controllers, keyboards etc).

[mathoudebine]

The WinRing0 driver is loaded by LibreHardwareMonitor library. If main.sys is blocked, then the LibreHardwareMonitor library will not work properly.
The only alternative is to select "Python libraries" as Hardware Monitoring from the config. window.
Can you check and see if it solves your issue?

[Raxisphasmatis]

Python libraries work without triggering the winring0 witch-hunt from every virus scanner and anti-cheat on the system, and seem to work with everything on the display excluding CPU temps(CPUuse %, freq, GPU use/temp/vram use all work)

[goofyhsk]

Are there any workarounds to get CPU Temp (intel 14600K in my case) working with the python libs?
EDIT: I think the CPU Freq is stuck at stock

[obiwan-bartek]

Got the same problem.
Maybe using some hardware detection app (like Aida64, HWInfo, CPUID, etc) as an underlying layer for CPU data? Just like many OSD apps for monitoring does.

[c0ldJS]

It appears that LHM committed a change semi-recently that ditches WinRing0 for PawnIO.

Some anti-cheat mechanisms don't like PawnIO either so it's maybe a Band-Aid commit.