Armoury Crate installation tips

[Jimbo93]

[Jimbo93]

Mission accomplished. Very low resources being used while running aura wallpaper and other devices all synced to breathing animation.

[RogScott]

@jimbo93 - Thanks for consolidating all this info. I recently needed to uninstall/reinstall AC and your suggestions gave me some things to try. Kept getting error 504 but finally succeeded after running "windows disk cleanup" and deleting temporary files. Not sure if that is what solved the problem or if it was just ASUS' flakey servers finally downloading everything successfully, but either way -- appreciate you sharing info / suggestions to help navigate the problem.

[Bushmaster78FS]

Is that HWInfo you are using? I just uninstalled it. It is also not fully functional with virtualization turned on in windows. Not sure if it is affecting temperature readings. I might be seeing something similar.

I think you found a bug. It looks to me like Armoury Crate is reading the wrong sensor.

Hey Jimbo, sorry for the late response, yes it is HWInfo. I use it as a part of my Rainmeter desktop where I see a plethora of hardware info on the side. That screenshot of AC I shared above could be misleading as it is the temp setting to change colors on my keyboard based on CPU temp. HWinfo reads temp from a gazillion of sources, but AC must be reading from only one and I am assuming it is from the mobo. I noticed AI Suite 3 and Armoury Crate reads the same or similar temps because whenever a preset temp is exceeded and my keyboard changes colors, I used to see on AI Suite temp agreed to the threshold I set in Armoury Crate.

If you can do me a favor and if you are using a hardware monitor, since you use AI Suite, what do you suppose the temp indication in AI Suite comes from? I bet it is the same sensor where BIOS also reads from, I just don't know which.

[Jimbo93]

Hey Jimbo, sorry for the late response, yes it is HWInfo. I use it as a part of my Rainmeter desktop where I see a plethora of hardware info on the side. That screenshot of AC I shared above could be misleading as it is the temp setting to change colors on my keyboard based on CPU temp. HWinfo reads temp from a gazillion of sources, but AC must be reading from only one and I am assuming it is from the mobo. I noticed AI Suite 3 and Armoury Crate reads the same or similar temps because whenever a preset temp is exceeded and my keyboard changes colors, I used to see on AI Suite temp agreed to the threshold I set in Armoury Crate.

If you can do me a favor and if you are using a hardware monitor, since you use AI Suite, what do you suppose the temp indication in AI Suite comes from? I bet it is the same sensor where BIOS also reads from, I just don't know which.

Hi again bushmaster, so Ive been deep in the bat cave working on this whole optimization thing. I will be adding some more info I think in the next day or so as far as installing/ troubleshooting. On your sensor question I can see one value in HWINFO64 that matches with AC and AI cpu number. It is labeled cpu in HWINFO64 and is one of the motherboard nuvoton sensor values. Ill share a screenshot after Im off work. Cya.

[Jimbo93]

I made an important discovery on my system and am now getting even better reponsiveness in Armoury Crate, and better system performance. Ill give the short story here now and follow up with more later.

On my system there was a problem were the WMIADAP.EXE process, that is always launched at around 4:20 after a system start or restart, this process was running longer than normal and, I think, was failing to do its job of optimizing the performance counters. So I figured out how to get it to finish in the normal 30 second range. When I say it was running too long, it was running for 3 minutes and 40 seconds, till the 8:00 minute mark system up time. You can easily check if you are having a similar issue using task manager and/or resource monitor.

To get the process to run and finish within 30 seconds:

Set Armoury Crate to static mode and unsync all the devices, turned off aura wallpaper.
Turn off the GeForce in game overlay, this can be done in the GeForce Experience settings.
Sign out of windows.
Reboot and leave the system to idle at the sign in screen for around 6.5 to 7 minutes.
Sign in and open task manager immediately to check if WMIADAP.EXE is still running.
If it is not running then you were successful and some optimizations were performed.

I suggest you start your computer this way a few times for increased optimization.

If the WMIADAP.EXE process still runs all the way to the 8 minutes mark, it suggests that you need to uninstall Armoury Crate or GeForce Experience or other software that is using WMI a lot, then try same steps again and see if the process will finish quicker after a restart. Once you confirm it is finishing sooner, you can reinstall the software you uninstalled. I recommend doing the restart process above after each software installation.

[Jimbo93]

Did everyone get their Tuesday windows updates? I actually experienced a problem with a couple processes refusing to run afterwards. One was ArmourySwAgent. I used the recovery environment (Restart with shift key pressed) to uninstall the latest quality update and then I uninstalled both updates from the screenshot and let the system settle and was able to reinstall them both with no further issues.

Microsoft warns users: Uninstall Windows 11 KB5012643 if it crashes your apps (windowslatest.com)

May 10, 2022-KB5013628 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 11 (microsoft.com)

[Jimbo93]

Screenshot for Bushmaster! Sorry it took so long, my system had to go through some things and once I start troubleshooting its hard to stop.

[lordberti]

@ Jimbo93

Problem is already known as well as the solution.
NET Framework 3.5 make Problems because ASUS AC accesses it. Because Microsoft has disabled/updatet this in the last updates!

Solution:
In Windows 10 and 11 under Windows Features (Search), first tick .Net Framework 3.5 and press OK and continue. Restart and uncheck again.
Then everything works again

[Jimbo93]

@ Jimbo93

Problem is already known as well as the solution.
NET Framework 3.5 make Problems because ASUS AC accesses it. Because Microsoft has disabled/updatet this in the last updates!

Solution:
In Windows 10 and 11 under Windows Features (Search), first tick .Net Framework 3.5 and press OK and continue. Restart and uncheck again.
Then everything works again

Hi lordberti. Can you clarify one thing. When you say "..first tick .Net framework 3.5 and press OK.." does that mean to enable the feature or to disable the feature? For the record, I did not have that feature enabled in the first place, and second point, I do not want to enable it. Also the article I linked to seems to say something different as well. Im happy though, as everything is fine on my end.