Aurora R8, AWCC, WMI issue

---

@MiLKou wrote:

 

Went back to the last version  I knew was working 5.4.35 . It works fine with this one.

 

---

You don't mention what Alienware model/release you have, but sounds like you are now running the correct AW-CC version for your machine. Each machine tends to have a "final validated version" and you really can't go much higher than that it you want it to work properly.

Hi,

I have a Aurora R8 (BIOS 1.0.23) and AWCC 5.5.9 was proposed to install by Dell Support assist.

Indeed, I guess each machine has a final validated version, and, if the support assist works as intended, I should be able to install the last version proposed without issue.

I don't think that this is a question of "working version", but a software not stable/tested enough. Among all the installed programs, the Alienware/Dell suite is without a doubt the one that caused me the most trouble, whether it be at the level of installation, stability or slowing down the system. I have Alienware computers since 2011, and I know that softwares are not the strong side. But don't get me wrong, I'm not saying the software side is bad, but I'd like it to work without me worrying about.

I like my computer but I like having a proper installation, software running nicely, and keeping my stuff updated, but here, well, not the best experience.  That bothers me, but yeah, just my OCD.

I suppose that in the next version, the issue would be solved.

Hi,

I have an Alienware X17 R2 and I am having the same problem. Or maybe a worse problem.

1. Killing the process "AWCC.Background.Server.exe" makes the WMI Provider Host usage drop from ~8% to ~0.7%. To kill the process I ran: "taskkill /f /im AWCC.Background.Server.exe". Whenever I start "AWCC.Background.Server.exe", the WMI Provider Host CPU usage rises to ~8% again and several "errors" are shown on Windows Event Logs (run "eventvwr" and go to "Services and Applications Logs/Microsoft/WMI-Activity"). 

2. When the process "AlienwareOn-ScreenDisplay.exe" is running I get 1 Error message every 2 seconds. The message is as folows:

"Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = THEDEATHSTAR; Usuário = TheDeathStar\******; ClientProcessId = 102680; Componente = Unknown; Operação = Start IWbemServices::ExecNotificationQuery - root\wmi : select * from biosevent; ResultCode = 0x80041032; PossibleCause = Unknown"

For now, my solution is kill this processes with:

taskkill /f /im AlienwareOn-ScreenDisplay.exe
taskkill /f /im AWCC.Background.Server.exe

I am also running AWCC 5.5.9.0, I will try @MiLKou solution and go back to AWCC 5.4.35.0. I hope DELL fix this in the next version of AWCC.

Same Issue here. AWCC Service / AWCC Background Server keeps polling WMI every 2 seconds for something. It's causing noticeable lag in overall system response and issues with mouse movement - the mouse ends up reacting similar to its batteries being near dead (intermittent pauses in cursor movement while moving the mouse).

If I stop AWCCService, the WMI polling goes away and WMI CPU usage again drops to <1%.

Here's an example of the error logged in the event log. Every. Two. Seconds.

Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = xxxxxxx; User = xxxx\xxxx; ClientProcessId = 17964; Component = Unknown; Operation = Start IWbemServices::ExecNotificationQuery - root\wmi : select * from biosevent; ResultCode = 0x80041032; PossibleCause = Unknown

It's rather frustrating.

I think I have the same issue with my new Alienware m15 R7 laptop... extremely frustrating!  I see WMI CPU usage very high to the point I can barely even troubleshoot the issue.  It just locks it up completely every few hours.  Looking at the event log (which took forever), I think I have found it is due to the AWCC according to the ClientProcessId. 

I have un-installed AWCC completely now to see if this solves the issue (fingers crossed).  When is Dell/Alienware going to fix this?

Still having this problem in 2023.  Uninstalled AWCC for now and this seems to have solved the problem.  Issue can also hide behind ekrn, an eset kernel service it was triggering, as it originally showed as that, but wasn't.  Will update and apologize if it rears its head again and turns out to be something more sinister, but Dell, if you're going to add non-essential services with your products, please make sure that, first and foremost, before you implement any code whatsoever, that it in no way could burn our cpu's.  A good measure would be for a self-verification that none of your services should be doing anything at all that returns errors every two seconds, ever, and if they must, that such cycle-lock inducing errors should be flagged on the front page of your "command center' as soon as we open it, not an unkillable message box about configuring said box's grayscale (your monitors are great, but no-one cares about the colorset of your CC.  Would you in our shoes?) Again, these are deeply non-essential services.  Backgrounds to our background.  They should never even vaguely affect performance.  This really seems like a pretty minimal ask.

---

@aw_fan wrote:

Hi,

I have an Alienware X17 R2 and I am having the same problem. Or maybe a worse problem.

1. Killing the process "AWCC.Background.Server.exe" makes the WMI Provider Host usage drop from ~8% to ~0.7%. To kill the process I ran: "taskkill /f /im AWCC.Background.Server.exe". Whenever I start "AWCC.Background.Server.exe", the WMI Provider Host CPU usage rises to ~8% again and several "errors" are shown on Windows Event Logs (run "eventvwr" and go to "Services and Applications Logs/Microsoft/WMI-Activity"). 

2. When the process "AlienwareOn-ScreenDisplay.exe" is running I get 1 Error message every 2 seconds. The message is as folows:

"Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = THEDEATHSTAR; Usuário = TheDeathStar\******; ClientProcessId = 102680; Componente = Unknown; Operação = Start IWbemServices::ExecNotificationQuery - root\wmi : select * from biosevent; ResultCode = 0x80041032; PossibleCause = Unknown"

For now, my solution is kill this processes with:

taskkill /f /im AlienwareOn-ScreenDisplay.exe
taskkill /f /im AWCC.Background.Server.exe

I am also running AWCC 5.5.9.0, I will try @MiLKou solution and go back to AWCC 5.4.35.0. I hope DELL fix this in the next version of AWCC.

 

 

---

One possible solution you mentioned is downgrading to AWCC version 5.4.35.0, as suggested by @MiLKou. This may help alleviate the CPU usage and error message issues. However, it's important to note that upgrading or downgrading software versions should be done with caution and may require compatibility checks with your specific system.

I gently ask Alienware firmware developers to fix this issue. My event log viewer is full of errors from AWCC.SCSubAgent.exe under WMI activity. This issue persists from at least 2020, it's been 4 years this problem is not resolved. I just bought my brand new Alienware m18 R2, with top-gear hardware, but what's the point if third of my processor time is eaten by poorly created firmware. I am really sick of my fans become noisy each minute when laptop is idle. Sure, I can delete Alienware Command Center, but what's the point of having Alienware laptop and being unable to control its performance settings.

Error:
Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = CLASSTERR; User = NT AUTHORITY\SYSTEM; ClientProcessId = 21088; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\cimv2 : SELECT ProcessId, ExecutablePath, CommandLine FROM Win32_Process WHERE ProcessId = 58636; ResultCode = 0x80041032; PossibleCause = Throttling Idle Tasks, refer to CIMOM regkey: ArbTaskMaxIdle

By the way, I don't have process with id 58636 in my system right now.

21088 is AWCC.SCSubAgent.exe

Thank you in advance for your effort. I would appreciate this fix much more then any new feature (for project managers who always want to make features instead of fixing broken ones).

Alienware Command Center Package Manager ver. 6.3.7.0

On ACCC (AlienCommandCenter), go to global preset. Set 'Performance Preset Switch' to System.

It seems to keep WMI Provider Host to a minimum on CPU usage. I also set it to Efficiency Mode on the task manager to offset it to the E-cores.

This is not a cure to the plague ACCC has inflicted on the system. The errors on the event manager will still persist, but at the very least this will keep CPU usage from hogging valuable cputime.

@DisgruntledEarthling​ Thanks! This helped me on my M15 R7.