Aurora R16, AWCC.SCAgent causing WMI high cpu usage

Delete your alienware command center and it'll be fixed. They are aware now and we'll fix it sometime down the road. 

Hi,

If you are experiencing high CPU usage, we recommend updating your system to the latest BIOS.

Please let us know the outcome after doing so.

@DELL-Nat M​ I have the same issue with the same PC but my system is fully up to date according to that link

Hi everyone,

I’ve shared the details with the team, and they are currently investigating the issue. So far, it appears that only the Alienware Aurora R16 is affected. If you have any other systems experiencing this issue, please share the model name.

Thank you.

@DELL-Nat M​ I have the same issue listed above with AWCC.SCAgent on my Alienware M16r1. The band-aid fix that I have found is to use event viewer to navigate to "WMI Provider Host"'s operational log and use Client PID to end the task for the AWCC.SCAgent that is causing the errors. This forces the service to restart and stops the issue temporarily, but can happen multiple times in a single boot. Other than this method restarting the computer is the only other temporary fix. I have all drivers and services up to date and restart the computer daily. 

@Chrusher2004​ If it's a service you can stop and permanently disable it using the services menu.

Services Windows.

@Vanadiel​ Unfortunately it is required for AWCC to function, otherwise I would have done that to solve the issue.  

Hi everyone,

We kindly ask that you contact support by clicking on Get Help Now for personalized assistance. This will enable the team to investigate the issue more effectively using your specific case logs.

I have the same problem on a R15, I had to uninstall AWCC.

Following the engineers' recommendation, please update your AWCC to the latest version. A new update from September 23 is now available.

@DELL-Nat M

Alienware M18 R2. Same problem. I've already forwarded it to support, but they couldn't help me either. Last resort at the moment. Reinstall the entire system and take a look. WMI often has up to 20% CPU usage. If you look into it, it's a 2-3 second error from AWCC.SCSubAgent.exe. Sometimes there are no error messages for an hour, but otherwise it's almost constant. Completely reinstalling AWCC twice didn't help. Version 6.4.15.0. Support said I should install 6.2.7.0. I removed AWCC exactly as described in the video (registry etc.). Then downloaded the zip file for it. Installed it. But somehow version 6.4.15.0 came back on. No idea. It all takes a while. If you google it, it's not really a new topic. I've found posts about it over the last few years and that people have had to completely uninstall AWCC. That can't really be the solution. My laptop is only a few months old.

wir sollten melden wenn es auch Andere Laptops betrifft. Alienware M18 R2. Das selbe Problem. Habe es auch schon dem Support weitergeleitet der mir aber auch nicht helfen konnte. Momentan letzte Hilfe. Komplettes System neu aufsetzen und mal gucken. WMI hat einfach oft bis 20% CPU Auslastung. Wenn man dem nachgeht ist es ein 2-3 Sekunden Fehler vom AWCC.SCSubAgent.exe. Manchmal ist auch mal ne Stunde keine Fehlermeldung aber sonst fast durchgehend. 2 malige komplette Neuinstallation von AWCC hat keine Hilfe gebracht. Version 6.4.15.0. Support hat gemeint ich soll die 6.2.7.0 mal installieren. Ich habe AWCC genau wie im Video beschrieben (Regestry usw) entfernt. Dann die zip dazu runtergeladen. Installiert. Aber irgendwie kam wieder die Version 6.4.15.0. drauf. Keine Ahnung. Dauert ja alles auch ein Stück. Wenn man googelt ist es auch nicht wirklich ein neues Thema. Da findet man über die letzten Jahre immer wieder Beiträge dazu und das Leute AWCC komplett deinstallieren mussten. Das kann ja eigentlich nicht die Lösung sein. Mein Laptop ist gerade mal paar Monate alt. 

@DELL-Nat M​ I have the same issue with a G15.  

Same issue with my M18 R1. 

This is frustrating, and it makes my entire laptop run like a piece of junk.

@DELL-Nat M Same issue on the X17-R2, ACC says it's up to date at 6.4.15.0 and I have the latest BIOS. I did capture the WMI queries (that appear to be looking in a loop for PIDs that don't exist) if they would help you resolve.