Issue NOT resolved – AWCC installation still interrupted on Dell G15 5511 (Windows 11 25H2)

I’m opening this new thread because a related discussion is currently marked as “Solved”, but the issue is clearly not resolved for all Dell G15 5511 users.

<Dell Alienware team wants all applicable comments and replies on that thread. DELL-Admin>

To avoid confusion and help affected users find accurate information, I want to document the current state clearly.

My system is a Dell G15 5511 running Windows 11 25H2 (clean in-place upgrade from 22H2 using the official Microsoft ISO). The Microsoft Store is working correctly, there are no account or Store-related errors, and the system is fully updated via Windows Update and Dell firmware updates. I also tested the installation in a clean environment (clean boot, antivirus disabled, administrator install).

Despite all of this, Alienware Command Center (AWCC 5.x – driver RK19X) still:

• installs partially

• then shows “Installation was interrupted”

• provides no error code

• creates no functional services

• and leaves fan / performance control unavailable

I reviewed the installer log, which shows that the installer aborts during the service and thermal/performance backend registration phase, not because of Windows, Microsoft Store, or permission issues. This strongly points to a problem in the AWCC installer package or its backend compatibility, rather than a user-side configuration problem.

Some comments here suggest the issue is “fixed”, but for my Dell G15 5511 it clearly is not. Silence should not be interpreted as resolution — many users have simply stopped retrying because repeated attempts risk destabilizing an otherwise healthy system.

Dell, please acknowledge that this issue is not fully resolved, clarify whether a hotfix or updated installer is planned, and provide guidance that is specific to the Dell G15 5511.

Alienware Command Center is not a cosmetic application; it is essential for thermal and performance control on this hardware. At the moment, users are left without official fan control due to a broken installer.

I’m happy to provide logs or additional system details if needed.

I updated the 25h2 build from the 10/15/2026 version to the one I just redownloaded using Microsoft’s official USB or ISO creator app from 2/12/2026. Now, the installed AWCC is showing the CPU as overclockable again. It seems something in the old 25h2 build broke it, but after updating to the current 25h2, it’s working again, so it appears to have fixed itself for now.

 
I’m not sure if any of these Windows updates will cause issues with Alienware Command Center again.
  
For now, I’ll consider this problem fixed. Here’s the ISO size difference: both builds are based on 25h2, but the newer one, dated 2/12, appears to be the version where the Alienware Command Center is working properly again.


as for the installer I used the one labeled this.

 I’m going to mark this as the accepted answer, since updating to the current ISO build from the official Microsoft page resolved the issue.

 I used Mediacreationtool, and mounted Windows25h2_2026.iso then under the virtual iso image, I then ran setup and did windows 11, and keep files and apps, it seems again have AWCC working for me, as all the settings for now are correct, but any windows update could break it again, but I hope it works for some time before that happens, also going to run Disk Cleanup to remove the older build install which should be in windows.old directory in the C:\ drive on my Alienware R16 Desktop Pc.

I shared this info with copilot to see what it had to say about it.


       

I marked it as an answer solution on my page since upgrading to the current build with Media Creation Tool worked for me today. If the issue is due to using an older build of Windows 25H2, I’d suggest updating your ISO image to the latest 25h2 build version available on Microsoft’s official website.

‎Aurora R16, AWCC CPU Overview info on CPU Utilization, Overclockable switch from true to false on Win11 25h2 | DELL Technologies

just one last thing to write about, 

but copilot did tell me this about the update, 

I want to confirm before I download it that this update will not break AWCC?

I got this info below from copilot if the update needs to be blocked.

How to block KB5077181 cleanly and reliably

There are two stable methods that work on Windows 11 Home:

• Registry-based hide/block

• PowerShell using the Windows Update API

Since you asked specifically for a PowerShell script you can save on your USB, I’ll give you the cleanest, safest version that blocks only this one update and nothing else.

And don’t worry — this is general Windows administration, not anything harmful.

PowerShell script to hide/block KB5077181

You can save this as:

Block-KB5077181.ps1

Here’s the script:

# Blocks the Windows Update KB5077181 so it will not install
# Requires running PowerShell as Administrator

$KB = "KB5077181"

Write-Host "Searching for update $KB ..."

$Session = New-Object -ComObject Microsoft.Update.Session
$Searcher = $Session.CreateUpdateSearcher()
$SearchResult = $Searcher.Search("IsInstalled=0 and Type='Software'")

$UpdatesToHide = @()

foreach ($Update in $SearchResult.Updates) {
    if ($Update.Title -match $KB) {
        Write-Host "Found: $($Update.Title)"
        $UpdatesToHide += $Update
    }
}

if ($UpdatesToHide.Count -eq 0) {
    Write-Host "Update $KB not found or already hidden."
} else {
    foreach ($Update in $UpdatesToHide) {
        $Update.IsHidden = $true
        Write-Host "Blocked: $($Update.Title)"
    }
}

Write-Host "Done."

This script does three things:

1. Searches for all pending updates

2. Finds the one containing KB5077181

3. Sets its IsHidden flag to true, which prevents Windows Update from offering or installing it

This is the same mechanism used by the old “wushowhide” tool.

the update was safe, and did not break it KB5077181


   

Just because this solution worked for one user does not mean the issue is resolved.

Downgrading or altering Windows in order to make a Dell application function is not a real solution. Customers should not have to compromise their operating system to accommodate a broken installer.

I was on Windows 11 version 22H2, which had not updated due to a Windows Update bug — and AWCC still failed. So staying on an older build clearly does not prevent the problem.

I then upgraded via official Microsoft ISO to Windows 11 version 25H2. The installer behavior did not change. The only difference was that a Microsoft Store account warning disappeared. The AWCC installation still aborts during the service/thermal backend phase.

This makes it clear that the root cause is not a specific Windows build. It is a compatibility or installer-side issue that needs to be addressed by Dell.

A workaround that requires users to modify their OS environment should not be labeled as a resolution.

This is not a cosmetic inconvenience — it directly affects thermal control and system performance on supported hardware.

Until Dell provides a properly updated and compatible installer, this issue remains unresolved.

I have the same issue, starting today. The only solution at this moment is to uninstall the Alienware Command Center and wait for the next update patch.

im also getting same issue today : (21st jan 2026).

i think some aliens are doing this.

Same 

Heaps and heaps of users reporting it.

Tried to download the newest version 6 and said its incompatible.
Only using latest WIndows 11 25H2 updated on everything. LOLOL

@Uniacidz​ please stop and disable that service from services.msc for temporary solution.

i think its global level issue. dell mentioned it that its issue from microsoft

Estou com o mesmo problema, ja tentei instalar todos os programas sugeridos pela Dell e nada.

I'm having the same problem, I've already tried installing all the programs suggested by Dell and nothing worked.

@user_a4c436​ thank you! This has worked as a temporary measure.

Im having the same issue! It started after a windows update. I ended the task and it came back...hope this is resolved soon

@user_abd22a​ FYI

I had no windows update as it was done earlier. I just booted my computer from sleep state and started with the issues. 

I have disabled the servvice.

It's another global software stuff up.