Think this has something to do with the whole winring0.g saga, but just came back from 2 week vaca, got the Windows Defender notice about winring0.g (which I think it now blocks), and then I noticed that in my config of Aquasuite, my Octo can map sensors (like water temp) from the high flow next, but it doesn't display the value (that is reported on the high flow next). I also have lost access to the HW Info data as being an option to tie to an Octo sensor.


I am trying to read through the forums here to see what I can do - can I ask defender to ignore the winring0.g, or are there other workarounds that someone can suggest, or do I potentially have a completely different issue that has nothing to do with the winring (and its just coincidence my Aqua profile fan curve stopped working cause it can no longer get a temp from the high flow next.

The HWinfo sensors is a separate issue - before when mapping sensors to the Octo, it would give me the option to select sensors from the HighFlow Next or from HWInfo - now only sensors from HighFlow Next are available, and while in the sensor selection the HighFlow Next reports in this case, the proper temperature, when I select it and go back to the main screen it does not display it there

(see attachment)

And what's interesting (I just checked) the HW Info sensor panel is showing all the data from the AquaComputer Octo and HighFlow Next devices - so it looks like it is something on the Aquasuite s/w that isn't working right anymore (again think it is tied to this winring0.g issue)

So turns out my Aquasuite support expired, and I just needed to re-purchase support for the next year - once that was done, the two Aquasuite sensors (Highflow Next and OCTO) started talking to each other (and HWInfo).

Still not sure how the whole winring0 saga fits in here - whether right or wrong, I excluded the Aquasuite service from Window's defender so I should be okay for now?