Quoted from "Speedy-VI"

Quoted from "Remayz"

It won't be backported, that you can be sure of

I agree with Remayz on this one. I have never seen Aquacomputer say yes to anyone who wants to roll back to an earlier version of Aquasuite for whatever reason. Since X.79 there have been 2 firmware updates for the D5 Next and 1 for the Leakshield. If you have either of these devices and you update Aquasuite and the device firmware (which is usually required to work with the Aquasuite update), there is no going back. I have no idea what is going on with the new driver, but I suspect the limited engineering resources Aquacomputer has have been totally focused on getting the Ampinel released.

This has been going since September 2025 already and we're just getting completely ignored though. That's the biggest problem, at least give us some form of update or response.

That's basically what Aquacomputer tells Microsoft for making the signing process so long and broken, on the first message of the thread.
An update would be welcome, but i'm not sure i'd be much different. We'll see.

Quoted from "Remayz"

That's basically what Aquacomputer tells Microsoft for making the signing process so long and broken, on the first message of the thread.
An update would be welcome, but i'm not sure i'd be much different. We'll see.

I did some more research on this and Aquacomputer's claim that they are stuck at the verification of their company may be true, but it may also be their own fault.

Microsoft did start using AI in their company verification process, which has caused a spike in "verification loops". Companies like HWINFO and RH Software (SIV) completed their company verification years ago, so they are considered "Trusted" by the Microsoft Partner Center. They can get kernel mode drivers Attestation Signed in minutes. Conversely, Aquacomputer apparently never went through the verification process before for a kernel mode driver, which requires an Extended Validation Certificate and enrollment in the Windows Hardware Developer Program. Their problem is they based Aquasuite's hardware polling around an unsigned kernel mode driver (WinRing0), which started getting flagged as a severe threat by Defender. This gets reported to Microsoft and affects the company's rating in Microsoft Defender SmartScreen and Intelligence Services.

To make matters worse, Aquacomputer then moved the offending WinRing0 code into their Aqua Computer Service, which caused Defender to start flagging the Service. This would change their rating in Microsoft's system from a company using "Legacy/Vulnerable" code to "Obfuscation/Evasion", which is a primary indicator of Malware. Including a Defender Exception (which are reported to Microsoft) in the Aquasuite installer raises their risk rating even higher. When the AI reviews their application, it generates a Risk Exception which requires investigation by a human, and that is what is causing the massive delay in getting the company verified. If Aquacomputer had written their own kernel mode driver and gotten it signed in the beginning rather than using WinRing0, they would not be stuck in this loop. Moving the offending unsigned code into their Service and adding a Defender Exception in their installer just made things worse because the Exceptions are reported to Microsoft every time someone installs Aquasuite and the Defender Exception.