Information about Windows Defender warning "HackTool:Win32/Winring0" (AquaComputerService.sys)

This is an appropriate response on Microsoft's part.

No unsigned organization should have access to Ring0.

WinRing0 should have been killed 15+ years ago.

As far as for Aquacomputer goes, the best way to set it up in a build is to use only sensors controlled on the aquaero, so that the control is completely separate from the OS and the system.

For over a decade now, I have blocked the AquaSuite service from loading using services.msc, and instead used only sensors attached to my two Aquaero's for any and all control.

If you want to use the temperature sensors built into the PC itself, you should probably also be using the fan headers on the motherboard directly, as those operate independently of the OS.

My perspective is that this then becomes independent of the OS and works no matter what the PC is running.

Having cooling control that depends on the OS is probably always going to be a bad idea. What happens if you boot to a Linux live image from a USB stick, for instance? Or what if you boot in safe mode and none of the services load? Is it OK to overheat when you do this? Cooling control should be completely independent of the OS such that it works no matter what OS is running on the PC. Thats the main reason why I bought an Aquacomputer product in the first place :p

As soon as you pull the OS into the control loop you are asking for trouble.

Not all temperature sensors are available to the motherboard. Most CPU temps readings on motherboards are socket temperatures and not CPU ones, and the GPU is flat out unavailable without an OS running.
Not everyone wants to hook up NTC thermistors everywhere

For cooling when the OS isn't loaded, or when using non windows OSes, that's what fallback values are for, on controllers that can't manage virtual sensors onboard.

Even Aquaeros can't do as much standalone as Aquasuite can do. But If you need basic cooling like a simple one curve per sensor, no need for a service.But then... maybe no need for an Aquacomputer controller if you mean to completely bypass Aquasuite.

Citation de "Remayz"

Even Aquaeros can't do as much standalone as Aquasuite can do. But If you need basic cooling like a simple one curve per sensor, no need for a service.But then... maybe no need for an Aquacomputer controller if you mean to completely bypass Aquasuite.

I see Aquasuite as a simple "setting tool" to program the settings I want into my Aquaero's, so that they can then proceed to work independent of the host. That - apart from the occasional pretty charts and graphs - is the only thing I use it for. The service is always disabled, and Aquasuite itself rarely runs unless I need to change something.

And the Aquaeros are amazing in their own right without Aquasuite.

Most motherboards are not able to hook up temperature sensors or flow sensors to them, and are unable to properly control pump speed.

Another ace the Aquaero has up its sleeve is to be MUCH More efficient than a traditional temperature curve, by being programmed like a PID controller in what Aquacomputer calls a "setpoint controller". A traditional temperature curve will in all conditions other than max temp apply more fan and/or pump speed than is necessary to maintain your target temp. A PID controller does not have this problem. That feature alone makes the Aquaero worth its weight in gold.

In my case I spend maybe 90% of my time in Linux (where there is no Aquasuite software anyway) and I have a large and complex loop that cools multiple machines, so relying on any one OS to provide sensor input would not be effective.

I am constantly dual booting or booting from external media to test things, and I want my loop control to work as intended (and not hit a failsafe speed) when I do.

I also tend to not like software or services constantly running on my machines. The less going on at any given moment, the better. None of my hardware companion software is ever installed or running other than initial setup. Too many of these vendors software are just poor excuses for spyware looking to "monetize data".

I bought my Aquaeros exactly because they could operate independently of the OS. That's why they were worth the money to me. If I just wanted to control PWM speeds based on software sensor outputs, I'd probably use some open source freeware program to do so.

As far as I am concerned OS independence is the Aquaeros biggest selling point!

(I just wish I could configure it from other operating systems than just Windows. Something like a virtual Ethernet interface over USB, and the ability to point my browser to it and configure it using a webpage (or even via SSH using a terminal), much like an IPMI/BMC system on a server would be amazing)

spin a windows VM just to do setup :p that's what i did for a few Qadros in the rack.

Citation de "Remayz"

spin a windows VM just to do setup :p that's what i did for a few Qadros in the rack.

I have done that as well.

I have also used some USB-A to USB header adapters to plug in Aquaero devices to laptops in order to manage them separately from the system they are cooling.

would it be too much to expect aquacomputer to make an official statement (or have I missed it?) especaily given Aquasuite is a subscription based service (yes I know you can use it subscription free as well with an older version but I'm currently subscribed).

My understanding is they would need to write drivers from scratch to replace WinRing0

EDIT : I missed it, link further up

I can't post in the other thread so i'll ask it here. Why am I paying for software updates when you aren't updating when it matters? Isn't this the sole reason you charge for updates? Now you've dicked around for so long i'm past my license period and have to give you more money when and if you fix it.

Since 2025/09/11 Microsoft activated that ban as part of the antivirus software built-in windows 11.

The default behavior of that anti virus is to block AquaComputerService.sys and move it in quarantine.
It is detected as "VulnerableDriver:WinNT/Winring0.G"

That renders Aquasuite non operational.

Can we expect an update soon ?

Information about Windows Defender warning "HackTool:Win32/Winring0" (AquaComputerService.sys)

more detailed in german:
Informationen zu Windows Defender Warnung "HackTool:Win32/Winring0" (AquaComputerService.sys)

To sign a driver, you must be verified in the Microsoft Partner Center. This process was changed in 2024 and is still completely broken today.
They try to perform verification using some kind of AI tools, there is no support, and you can only start the whole process over again from the beginning.
The entire process is very slow, with long waiting times and no feedback at all.

Here is an excerpt of how others are doing:
https://community.osr.com/t/how-to-submi…ft/59448?page=1

Until there is a solution, you can completely disable monitoring in the settings and use other tools such as HWINFO or Aida.