Your posts indicates that Aquasuite X.85 was able to poll your mobo sensors and X.86 cannot. This suggests that either Aquacomputer changed/broke something in the X.86 update or something changed on your end. Have you recently updated the Chipset drivers and/or BIOS? What is the strange behavior you are observing with X.86?

Years ago, Aquacomputer based their sensor polling on the unsigned WinRing0 Kernel mode driver. About 6 months ago, they said they wrote a new driver since Microsoft started flagging the WinRing0 unsigned Kernel mode driver as a severe threat. There are several threads about this on the English and German forums.LINK-1 LINK-2 LINK-3 LINK-4 (German) There are also a lot of posts about this mixed into other threads. Aquacomputer claims that they have completed writing a new driver and have submitted it to Microsoft for certification, but that was several months ago. They blame Microsoft for the delay in deploying this new driver. In the meantime, they have apparently moved the unsigned driver code into AquaComputerService.sys, but Windows Defender continued to flag it. They now include an option to add a security exception for it as a stop-gap measure.

Until they get their new driver signed, I decided to disable all Aquasuite direct sensor polling and import sensor data from HWINFO via its Shared Memory feature. HWINFO reports far more sensor data than Aquasuite, and it is updated far more often. The import of sensor data from HWINFO via it's Shared Memory feature works great. The only downside is that HWINFO imposes a 12-hour time limit on Shared Memory being enabled in the free version of the program. I have a lifetime Pro license which has no time limit for Shared Memory, so the time limit is not an issue. I suggest checking if HWINFO can poll your mobo sensors. It is extremely likely that it can, and if it can't because of a recent BIOS or Chipset driver update, if you post on the HWINFO forum, it will be fixed in the next Beta release within a few days. Aquacomputer usually takes much longer to address this type of thing.

I also use delta-T as the control source for my fan curves. It is strange that your Virtual Software Sensor for delta-T is working, but the delta-T value is not appearing at the top like it should. The only thing I can think of that could cause what is happening is if the Aqua Computer Service is not running, or maybe if Aquasuite went into Maintenance Mode. If the Aqua Computer service is not running, you should see a message in the Aquasuite Service Tab, or just check it in Windows Services.

I always leave all Aquasuite direct sensor polling disabled and import everything I need from HWINFO, and not just because Aquacomputer is still using unsigned WinRing0 code to poll sensors. I think HWINFO is far superior to Aquasuite for sensor polling, and the author of HWINFO is very good about updating it when new hardware is released, or driver updates require changes to polling methods. Aquacomputer usually takes a lot longer to add new CPUs. GPUs, and chipsets to their polling. My view is that Aquasuite is best at monitoring and controlling Aquacomputer devices, and HWINFO is best at system-wide sensor polling. I also know that it uses a fully signed Kernel model driver while AquaComputer is still claiming that they are waiting for Microsoft to sign their new driver. I have trouble believing that Microsoft is the problem because new drivers can be Attestation Signed by the developer without passing full Hardware Lab Kit (HLK) testing. You just enroll in the Microsoft Hardware Developer Program, prepare a CAB file containing the driver binaries, .inf file, symbols, and catalog file, obtain an Extended Validation (EV) Code Signing Certificate, then upload the package to the Microsoft Hardware Dev Center. Microsoft usually processes the request within 30 minutes and provides an Attestation signed package. The whole process is automated. Once the driver is written, the Attestation Signing process should take at most a few hours, not days, and certainly not months!

I have updated one computer to Aquasuite X.86 but that computer only has an Octo attached. My main rig with a D5 Next, High Flow Next, Octo, Leakshield, and 2 x Farbwerk 360s has not been updated yet because I shut it down to do some work on the loop. I will put it back together enough to boot it up, update Aquasuite to X.86, update the D5 Next firmware, and see what happens. I don't know what the D5 Next firmware update actually does, because the Aquacomputer Change Logs are extremely vague, but they must have had a good reason to update the firmware. I say this because they told me that the D5 Next flash memory is maxed out, and they don't like messing with the firmware code unless they absolutely have to,

Ah. .NET Framework. I did not think of that. Good to know, so thanks for reporting what the problem was.