• 27.12.2025, 15:03
  • S’inscrire
  • Connexion
  • Vous n’êtes pas connecté.

 

sebastian

Administrator

jeudi 2 octobre 2025, 10:19

What i need to do for resolve this problem ?
https://forum.aquacomputer.de/weitere-foren/english-forum/114285-information-about-windows-defender-warning-hacktool-win32-winring0-aquacomputerservice-sys/

softlion2

Junior Member

jeudi 9 octobre 2025, 08:21

merci !

marko22

Junior Member

samedi 11 octobre 2025, 17:13

Hello. I have a question regarding the language version. Why are only the German and English versions available? I’ve been an Aquasuite user for over 5 years. It’s not a problem for me to use it in English. I know it’s possible to rename sensors, but when using the Polish language, the application reports errors with national characters. Admittedly, that’s not a big issue either. Some time ago, during an email exchange about purchasing a license key, I asked whether a translation could be made. I was told that it wasn’t possible. Is there any reasonable reason for this refusal? I’m willing to do it free of charge, and I believe many users would benefit from it. Thank you for your response.

KuraiShidosha

Junior Member

lundi 13 octobre 2025, 06:28

Nice to see recent update fixed my issue with the RGBpx right click menu being in German when I use English. Now if only the last used profile not being saved to the controllers on cold boot can be fixed then finally I'd have the peace I had before September update dropped.

** Update 2025/10/22
I have further proof that the profile switch on cold boot is broken and not functioning properly. My Farbwerk 360 will switch to Profile 1 and the RGBs will behave accordingly eg Profile 1 = Rotating Rainbow and Profile 2 = Off and even if I set it to Profile 2 then shut down, it will boot back up to Profile 1 and the RGBs will light up. My Quadro however has Profile 1 max fan and pump speed, and Profile 3 is low RPM for quiet functionality. When I shut down with the Quadro set to Profile 3, the fans and pumps will operate at the correct RPM settings as Profile 3 however opening up Aquasuite will show that it is set to a bugged Profile 1. I then have to click Profile 3, which does nothing to fan and pump speed, then click back to Profile 1 to get proper max speed setting to apply.

Clearly something is broken about how profiles are saved to the device and loaded on cold boots. Something should be done about this for those of us who don't use Global Profiles but rather the 4 individual profiles loaded to the device memory. I hope to see the next update improve this behavior so that the profile set to the device before last shutdown is what's loaded and reflected not only in the PWM/RGB settings but also what profile is selected in the device when opening Aquasuite instead of all reverting to Profile 1.

Ce message a été modifié 1 fois. Dernière modification effectuée par "KuraiShidosha" (23 octobre 2025, 04:01)

cool&quiet

Junior Member

vendredi 14 novembre 2025, 23:25

Quick question: I was thinking about treating myself with the latest aquasuite software update for a 10 €. I've had an Aquaero 6 Pro USB for, I think, now over a decade and still running the software that came bundled and was offered free to update to. The versions read: firmware 2009, aquasuite 2016-5.3.

It's running just fine. Never had any issues that I'm aware of. So is the update worthwhile? Is any updated or added functionality expected? I'm using it in tandem with the free versions of Open Hardware Monitor and HWiNFO64, running Windows 11 Pro.

Thanks! :thumbsup:

Speedy-VI

Senior Member

samedi 15 novembre 2025, 21:59

The versions read: firmware 2009, aquasuite 2016-5.3. It's running just fine. Never had any issues that I'm aware of. So is the update worthwhile? Is any updated or added functionality expected? :thumbsup:
There have been a huge number of updates since 2016, far too many to list. I don't know how many of them are relevant to an Aquaero 6 Pro. I suggest looking at the second post in this thread that contains the Change Log for recent updates going back to Aquasuite version X.78 and has links to the Change Logs going back to 2016. There have probably been some firmware updates for the Aquaero 6 Pro. Also, the current version of Aquasuite requires Microsoft .NET 8.0. I took a quick look and found significant updates for the Aquaero 5 and 6 in early 2017 which I have pasted below. Aquacomputer does a pretty good job of maintaining the Change Log, although technical details are often not fully described.

General changes for the aquaero 5 and 6 series
In the aquaero, the aquabus is checked for resource conflicts now. Problems are marked with a warning symbol and further information about a conflict will be displayed too. This helps to keep track of complex systems and to understand where a displayed sensor value is coming from. Devices are highlighted in red if they are not connected anymore. Devices that had a communication problem in the last 4 hours are highlighted in yellow.

In the aquaero firmware the aquabus administration has been completely revised. Devices get mapped much faster into the system now. In addition, we have already integrated upcoming devices. As already mentioned: make sure to update the firmware of devices that are connected via aquabus.

As of now it is possible to connect two aquaero slave devices to an aquaero master device. Since a slave device offers no USB communication the aquabus ID for a second slave device must be set by placing a jumper onto temperature sensor port 8. A slave device can also monitor a flow sensor now and transfer its value via aquabus to the master device.

Also new is that we moved the option to connect a second flow sensor from fan port 1 to the aquabus lowspeed port which had no function lately. This way fan port 1 can be still used for other stuff when connecting a second flow sensor.

In addition, a new status page has been programmed which shows the current profile, number of alarms/warnings and the current alarm level. To keep it simple we no longer display the 12V on/off messages.

Changelog for aquaero 5 and 6
Bugfix: some text and menu entries have been improved
Bugfix: non-connected temperature sensors with an offset are now automatically hidden
New: administration of aquabus resources and status information
New: the aquabus communication has become much more robust compared to previous implementations
New: two aquaeros with slave firmware can be connected to a master device
New: a second flow sensor will be connected to the aquabus lowspeed port now
New: status page for profiles, alarms, warnings, alarm levels
New: 12V on/off messages are no longer displayed

Changelog for aquaero 5 and 6 with slave firmware
New: improved aquabus communication
New: value of a connected flow sensor is transmitted via aquabus
New: up to two aquaero slave devices via aquabus
New: jumper on temperature sensor 8 selects aquabus address for second slave device

cool&quiet

Junior Member

samedi 15 novembre 2025, 22:51

The versions read: firmware 2009, aquasuite 2016-5.3. It's running just fine. Never had any issues that I'm aware of. So is the update worthwhile? Is any updated or added functionality expected? :thumbsup:
There have been a huge number of updates since 2016, far too many to list. I don't know how many of them are relevant to an Aquaero 6 Pro. I suggest looking at the second post in this thread that contains the Change Log for recent updates going back to Aquasuite version X.78 and has links to the Change Logs going back to 2016. There have probably been some firmware updates for the Aquaero 6 Pro. Also, the current version of Aquasuite requires Microsoft .NET 8.0. I took a quick look and found significant updates for the Aquaero 5 and 6 in early 2017 which I have pasted below. Aquacomputer does a pretty good job of maintaining the Change Log, although technical details are often not fully described.

General changes for the aquaero 5 and 6 series
In the aquaero, the aquabus is checked for resource conflicts now. Problems are marked with a warning symbol and further information about a conflict will be displayed too. This helps to keep track of complex systems and to understand where a displayed sensor value is coming from. Devices are highlighted in red if they are not connected anymore. Devices that had a communication problem in the last 4 hours are highlighted in yellow.

In the aquaero firmware the aquabus administration has been completely revised. Devices get mapped much faster into the system now. In addition, we have already integrated upcoming devices. As already mentioned: make sure to update the firmware of devices that are connected via aquabus.

As of now it is possible to connect two aquaero slave devices to an aquaero master device. Since a slave device offers no USB communication the aquabus ID for a second slave device must be set by placing a jumper onto temperature sensor port 8. A slave device can also monitor a flow sensor now and transfer its value via aquabus to the master device.

Also new is that we moved the option to connect a second flow sensor from fan port 1 to the aquabus lowspeed port which had no function lately. This way fan port 1 can be still used for other stuff when connecting a second flow sensor.

In addition, a new status page has been programmed which shows the current profile, number of alarms/warnings and the current alarm level. To keep it simple we no longer display the 12V on/off messages.

Changelog for aquaero 5 and 6
Bugfix: some text and menu entries have been improved
Bugfix: non-connected temperature sensors with an offset are now automatically hidden
New: administration of aquabus resources and status information
New: the aquabus communication has become much more robust compared to previous implementations
New: two aquaeros with slave firmware can be connected to a master device
New: a second flow sensor will be connected to the aquabus lowspeed port now
New: status page for profiles, alarms, warnings, alarm levels
New: 12V on/off messages are no longer displayed

Changelog for aquaero 5 and 6 with slave firmware
New: improved aquabus communication
New: value of a connected flow sensor is transmitted via aquabus
New: up to two aquaero slave devices via aquabus
New: jumper on temperature sensor 8 selects aquabus address for second slave device
Thanks. I might go with the update even though I don't have — nor unlikely will have — water cooling in my system, as it sounds like many of the updates have to do with its functionality. A tenner ain't that much for a fresh GUI and a firmware update, which is always welcomed. I wonder if I'm able to bring back the settings from such an old version, but I'll find out by latest should I snag it...

Ce message a été modifié 2 fois. Dernière modification effectuée par "cool&quiet" (16 novembre 2025, 19:31)

Jeff3F

Newbie

samedi 15 novembre 2025, 22:56

I have a feature request for Aquasuite -

I'm middle aged, so I have windows 11 scale my text to 150%. Aquasuite doesn't appear to like this so a lot of times text or stuff inside windows when configuring things isn't visible.

THank you, I'm in the (long) process of learning the complexities of Aquasuite so I can get my fans/pump to do exactly what I want!

Hopper64

Full Member

jeudi 18 décembre 2025, 19:41

Just updated my bios to 2107 for my asus MZ790A encore. Peculiar problem as many of my settings are not available. Can't figure out what is wrong. Ideas? It says no USB connection or device not recognized??




https://imgur.com/a/7eNC2LW
Asus Maximus Z790 Apex Encore Bios 2107, Intel 14900KS, Asus 5090 Astral, Phanteks Enthoo Elite, GSkill F5-8400J4052G24GX2-TR5S, Asus ROG XG349C, Heatkiller D5, Seasonic 1600W Noctua, Asus Claymore 2, Asus ROG Gladius II, Samsung 9100 Pro

Hopper64

Full Member

jeudi 18 décembre 2025, 20:09

I don’t think the bios update has anything to do with it. Everything else works fine. ??? Thanks!!
Asus Maximus Z790 Apex Encore Bios 2107, Intel 14900KS, Asus 5090 Astral, Phanteks Enthoo Elite, GSkill F5-8400J4052G24GX2-TR5S, Asus ROG XG349C, Heatkiller D5, Seasonic 1600W Noctua, Asus Claymore 2, Asus ROG Gladius II, Samsung 9100 Pro

Hopper64

Full Member

vendredi 19 décembre 2025, 04:58

I believe I figured out the issue. The red flag from the picture I linked was the lack of recognition of the high flow next, Aquaero 6 LT, and the OCTO. I looked at the only component that I have in common with those 3 devices which is a Hubby 7. The Hubby 7 takes the input from a USB 2 internal header and I have the OCTO, high flow next, and the aquaero all connected to the Hubby 7. I noticed I left the power jumper on the USB side even though I have SATA power connected as well. I have had this connected this way a couple of years at least. I simply swapped the jumper to the SATA power side and booted the computer. All devices are now recognized and functioning correctly. All the data I usually review using HWInfo64 is back up and running. Problem solved.
Asus Maximus Z790 Apex Encore Bios 2107, Intel 14900KS, Asus 5090 Astral, Phanteks Enthoo Elite, GSkill F5-8400J4052G24GX2-TR5S, Asus ROG XG349C, Heatkiller D5, Seasonic 1600W Noctua, Asus Claymore 2, Asus ROG Gladius II, Samsung 9100 Pro

Discussions similaires