I’ve had the octo in my system for 2 years nothing has changed apart from the firmware. I can see using usbdeview it’s the octo disconnecting reconnecting. My high flow next is not doing it.

Quoted from "Badgerslayer7"

I can see using usbdeview it’s the octo disconnecting reconnecting. My high flow next is not doing it.

you dont see a crashed / blocked usb connection. it looks like an valid conntion. You cant transfer any data (software sensors, rgb..) with this blocked connection.
When the service is detect an blocked connection, it forces a usb reconnect from device.

Yes it’s a valid connection. It’s has a green light next to the device. The same as the highflow next.

Quoted from "Badgerslayer7"

Yes it’s a valid connection. It’s has a green light next to the device.

Sure, but you dont see if the connection is blocked/crashed.
The reason for this faulty behavior can be a bios, driver or hardware problem. This happens in a very low level at driver / hardware side.

The connections fine I can change and save settings to the device. Is there any way to be able revert the firmware. Just to try. I have not changed anything related to bios or drivers on my system. It’s only happened fldirectly after updating to x49

Quoted from "Badgerslayer7"

Is there any way to be able revert the firmware. Just to try.

no

Well that’s pathetic.

I really do not understand what are you guys doing!!!
After today`s update to version X.49 AuquaSuite can not see HWINFO64.

What are you doing, could you stop breaking what works well?!

As a user who has been using Aquasuite for years and has not seen any of the alleged Aquasuite bugs himself in that time, I wonder why a bug is always attributed to a software without sufficient testing.

Furthermore, hardly any of these "error messages" in the forum provide any information to verify or recreate this error.

Ever thought that if the Aquasuite had a general error, the forum would be filled to the brim with messages about this error?

Consequently, the question arises whether the error is not 80 cm in front of the monitor.
Translated with www.DeepL.com/Translator (free version)

The most funny thing - on this forum I can see that X.49 is Insider (beta/test) version, but why I do not see this message in Aquasuite itself before updating?!
In Aquasuite shows just 'you have update' no information about beta/test/Insider.

What should I do if I need HWINFO64 data in Aquasuite. You guys ruin everything.

You can set whether you are offered Insider versions.
The X.49 works fine with HWInfo64.

To solve your problem, you will probably have no choice but to provide information, so that we do not have to speculate here in the dark about what it could be in your system.
A first tip could be to turn off the computer for a few minutes and disconnect the power supply from the power, helps after updates in many cases.

by default, AS gives you notifications about insider versions, just untick that box in the "Updates" tab if you want to stay with the fully released versions.

Have you maybe also updated HWinfo? If you haven't bought the current version the shared memory interface will not be available. You have to enable it manual. I will also closed after 12h.
So please check if HWinfo is running and the settings for the shared memory interface are fine. Then open the sensor tab and check again. Wait for 30 seconds, if you don't see the sensors in the aquasuite you can restart the Aqua Computer service.

There are NO known bugs right now with HWinfo.

I updated to X.49 and HWINFO data import is working fine. va3sd - Before assuming that Aquacomputer released a version that breaks the HWINFO data import capability, I suggest you make sure Shared Memory Support is enabled in HWINFO. The HWINFO settings menu layout was updated recently. I forget exactly which beta had the new layout but I remember struggling to find the check box for it at first. Its now the bottom checkbox on the left side. Assuming you have Shared Memory Support enabled in HWIFO, you can also try downloading the Shared Memory Viewer utility. https://www.hwinfo.com/beta/HWiNFOSharedMemoryViewer.exe.7z This utility will display the Shared Memory data that HWINFO is providing. If the viewer utility looks OK but it still does not work, post back here and maybe we can help you figure out what is going on.

Quoted from "Stephan"

Have you maybe also updated HWinfo? If you haven't bought the current version the shared memory interface will not be available. You have to enable it manual. I will also closed after 12h.
So please check if HWinfo is running and the settings for the shared memory interface are fine. Then open the sensor tab and check again. Wait for 30 seconds, if you don't see the sensors in the aquasuite you can restart the Aqua Computer service.

There are NO known bugs right now with HWinfo.

I have latest HWINFO 7.20 which was updated a few days before AquaSuite, everything was working before I updated Aquasuite and even after 30 seconds - no data in Aquasuite from HWINFO.

I really do not understand how you guys even write this code, because you can break everything, each update I can see something: stopped working one functionality and now it calls Outputs and no way to move settings from old to new functions, 2 pages I was asking you to make read sensor data carefully as author of HWINFO said, because your method for reading sensors creates duplicates in HWINFO, but nobody agree from developers, told me I have to stopped using HWINFO... Now HWINFO just disappeared from AQuasuite after update.

I just have some doubts that you guys even understand what are you doing with Aquasuite.

Already stopped and started service, also closed HWINFO and started again...

Quoted

I have latest HWINFO 7.20 which was updated a few days before AquaSuite,
everything was working before I updated Aquasuite and even after 30
seconds - no data in Aquasuite from HWINFO.

Aquasuite X.49 arrived on 11.02. and HWInfo 64 7.20 on 15.02.
I always use the latest Aquasuite and the latest HWInfo 64 on Windows 10 and Windows 11 and never had such problems.
How likely is the Aquasuite as a source of error then?
Especially since you still don't bother to provide any information that could help track down the problem!

Quoted

I just have some doubts that you guys even understand what are you doing with Aquasuite.

I rather suspect that the understanding problem is on your side.
Furthermore, if I were you, I would work on my expectations, you seem to think that the Aquasuite has to be tailored to you, but this is not the case, at least not in this universe.

I would understand you if you were one of many with the same problem, but that is not the case.
So, what are the possible solutions?
Very simple, since it is apparently not a general problem of the Aquasuite, and also no fundamental problem between Aquasuite and HWInfo 64, even the Windows version we can exclude, remain "only" your settings and possibly, drivers or hardware as possible problems.

Before you answer again without any useful data, keep in mind that your problem does not correspond to the experience of most users and thus is not evenly replicable ;-)

Translated with www.DeepL.com/Translator (free version)

again and again and again:
check the "Shared-Memory" configuration flag in HW-Info's settings. HW-Info ist stopping this after 12h of an uninterrupted use.
When the Shared-Memory-Support is stopped by HW-Info itself neither a reinstall, nor an update nor a restart of HW-Info or of the PC will reactivate it.
You have ALWAYS to activate it MANUALY in HW-Info settings.

Quoted from "InfoSeeker"

It would help if there were a horizontal bar between Input options in the aquasuite Inputs displayed in the system tray.

Nice - in‫puts.jpg

va3sd - Again, if this was a widespread problem with AQS X.49 there would be many many posts about it in this forum. X.49 was supposed to include improvements in monitoring imported data. I have had AQS occasionally stop displaying specific sensor data imported from HWINFO on several occasions prior to X.49. These would not start working again until I reselected the imported data item in AQS. I verified that the problem was AQS and not HWINFO. Since updating to X.49 I have not had this happen, so I think they did solve at least some of the problems with this feature. In your case, there is something going on that is specific to your system that is causing your problem. I understand that you are frustrated with AQS, and that you never really got a definitive answer about whether they use a global mutex to poll the NCT668x eSIO on your MSI Z490 Tomahawk motherboard (Sebastian said they do it "the correct way" and that "The aquasuite has a synchronized access with hwinfo" but never actually said that they use a global mutex to poll this sensor. And yes the X.45 update was major and required that some things be redone a different way, but it also added some very powerful new features.

So Aquasuite is not perfect and does sometimes have bugs. It is also a fairly complicated program that has a significant learning curve. I suspect that 95% of reported problems end up being operator error or operator misunderstanding, and this is why the AQS devs usually start out assuming that a reported problem is actually not a problem with AQS. I am not saying that is the case with your system. If you can put your frustrations aside and fully document your testing and the results you are seeing (or not seeing), I think you will have a better chance of getting meaningful support from Aquacomputer and this forum. My suggestion is to take a few deep breaths, put your emotions aside, recheck everything in your setup, then post details here, including the following.

Hardware details - mobo, RAM, GPU, PSU, fans, CPU & GPU cooling, etc.
BIOS and OS versions
List other software running, especially software that polls sensors (HWINFO, SIV, HWMonitor, GPU-Z, CPU-X, iCue, etc.)
Aquacomputer devices and setup

This is a great forum with some very experienced AQS users who will take the time to try to help you figure out what is causing your problems. Getting mad and telling Aquacomputer they don't know what they are doing is 100% NOT going to solve your problem.