02-15-2025 12:38 AM
After updating Armoury Crate, the AI Noise Canceling feature is missing. I cannot find it anywhere in the settings. It was working fine before the update.
I have already tried reinstalling Armoury Crate and checking my drivers, but the issue remains. Was this feature removed in the latest update? How can I restore it?
Thank you for your help.
02-18-2025 11:56 PM
also have another problem GPU mode change auto every time , ultimate to standard
02-19-2025 01:48 AM
Yes on windows restart it switches to standard mode every time
02-19-2025 03:50 AM - edited 03-05-2025 10:57 PM
Confirmed that audio section has completely disappeared.
Ok, that's enough... This "upgrade" is full of bugs and problems, no beta-testing, and my previous installation was working flawlessly. Rolling back to a Windows Restore Point before AC 6.1.13.0 bad upgrade 🤞🏻
EDIT: Restore Point roll back successful. AC 5.9.13.0 works perfectly fine on G834JY. No crashes, no big bugs, everything works as expected included bells & whistles like Audio Noise AI Cancelling and other extra features.
EDIT2: HOW TO ROLL BACK to 5.9.13.0 without a Restore Point: Rif.: ArmourySocketServer.exe crashes - Pagina 12 - Republic of Gamers Forum - 1046069
02-19-2025 09:35 AM
... Just wondering why ASUS AC doesn't automatically create a Restore Point before any major update like this anyway...
02-25-2025 03:37 PM
it's present, but it hides and unhides randomly, version 6 has many errors related to a specific process, if you get an update that fixes this, just let me know, mine doesn't even display GPU modes or system configuration.
02-26-2025 04:44 AM
I contacted ASUS service and asked for technical support. They gave me two links that gave two files, one to uninstall armoury crate and another to install it.
After installing (it installed version 5.9 point anything) and when I restarted the PC it appeared if I wanted to update to version 6.1.13.0 (I'm saying off the top of my head, I think that's the latest version). So I selected an option to not ask to update to this version. (At least for now I will only update when the next version comes out, and I hope this error has been completely fixed)