Another bad one.....

[Thu Jul 14 10:59:12 2022]
--- End of Vendor Software Log ---

[Thu Jul 14 10:59:12 2022] Vendor Software Return Code: 1602
[Thu Jul 14 10:59:12 2022] logo.png
[Thu Jul 14 10:59:12 2022] (MUPXMLParser::GetResultName): *** Vendor Return Code is not found in Mup.xml
[Thu Jul 14 10:59:12 2022] Name of Exit Code:
[Thu Jul 14 10:59:12 2022] (DupAPI::GetReturnCode): *** Unable to find DUP value for:
[Thu Jul 14 10:59:12 2022] Exit Code set to: 1 (0x1)
[Thu Jul 14 10:59:12 2022] Result: FAILURE
[Thu Jul 14 10:59:13 2022] (MUPXMLParser::GetResultName): *** Vendor Return Code is not found in Mup.xml
[Thu Jul 14 10:59:13 2022] Name of Exit Code:
[Thu Jul 14 10:59:13 2022] (DupAPI::GetReturnCode): *** Unable to find DUP value for:
[Thu Jul 14 10:59:13 2022] Execution terminated at date-time Thu Jul 14 10:59:13 2022
[Thu Jul 14 10:59:13 2022] ######

I have it installed. Seems plug and play.

Not exactly plug&play,  depending on your model , installation etc. it may behave differently.

The problem with this installer ( seems to be a patch) is, it stalled at the awcc_core install and finished saying it had been interrupted ( does not say by what) as a result, it left a little mess.Had some of the old version and new version install, it disabled the dell/alienware client management service and the overclocking in the bios. All that resulted , when I started awcc with the famous and never ending extra component download, and the alienware update program died...etc,  I finally got it (5.5.8) working but took some time.. and alternate methods

Version 5.5.0  v2 was running ok  but v1 installer was another bad one.

reasons to update:

Alienware Command Center Application

This package contains Alienware Command Center Package Manager. It is a new installer package that provides a simpler installation experience. The package size is significantly smaller, which results in faster downloads.
After you begin the installation, Package Manager installs all the software packages components that are part of Alienware Command Center. It also detects your system configuration and accordingly downloads the following components to install:
- Overclocking and Thermal Module
- Alienware Sound Management Solution
- AlienFX Peripherals components such as AlienFX Displays, AlienFX Mouse, and AlienFX Keyboard.
Alienware Command Center offers the following capabilities:
- Lighting control and management in the FX Module for Alienware gaming systems and peripherals
- Thermal control and overclocking
- This update addresses Common Vulnerabilities and Exposures (CVE). Common Vulnerabilities and Exposures (CVE) is a list of security vulnerabilities and exposures that are publicly disclosed.
Fixes & Enhancements
Alienware Command Center
Fixes:
- Fixed the issue where the Alienware Package Installation Manager updates are downloaded and installed in loops in some non-English languages.
- Fixed the issue where the Alienware Command Center installation progress that is displayed as a toast message does not appear for certain languages.
- Fixed the issue where the Thermal profile that is assigned to a game is not shown when Alienware Command Center is relaunched.
- Fixed the issue where the System 3D image is not displayed on the Home and FX page. This issue occurs when you upgrade the Alienware Command Center from the earlier versions.

Enhancements:
- Supports the Dell G16 7620 system.
- Supports the Alienware AW2723DF gaming monitor with AlienFX, new AlienVision features, and first-time usage guideline.
- Supports the Alienware AW2523HF gaming monitor with new AlienVision features, and first-time usage guideline.
- Updated the End User License Agreement (EULA).
- Removed the icon that indicates the number of devices that are connected on the home screen when only one device is connected.
- Changed the name for the Games section to Library on the home screen.
- Changed the name for the Default section to Default profiles on the home screen.
- Changed button name from Auto to Scan on the library screen.
- Changed the text from Add games to your library to scan your PC to add apps on the library screen.

Alienware OC Controls
Fixes:
- Driver updates to address security vulnerabilities including (Common vulnerabilities and Exposures - CVE) such as CVE-2022-22139.
- Fixed the issue where a Windows error message is displayed on Alienware Aurora R13 systems when applying the overclock profile.

Enhancements:
- Added a warning message to notify users about the functionality issues with runtime overclocking on Intel platforms when Microsoft Windows Hypervisor is enabled.
- Added the ratings of CPU, GPU, Thermal Comfort, and Acoustic Comfort per thermal mode in Thermal Control on Alienware x15 R2 and Alienware x17 R2 systems.
- Supports GeForce RTX 3080 Mobile/Max-Q overclock on Alienware m17 R5 AMD and Alienware m15 R7 AMD systems.

Alienware Command Center extra info

- Overclocking controls are installed only on Alienware and G Series systems.
- Peripheral Installer Package for Alienware keyboards, mouse, headsets, and displays are installed only if the corresponding hardware is connected and installed on the system.
- Alienware Sound Management Solution package is installed only on Alienware or G Series systems, or if an Alienware headset is connected.
- Depending on your system configuration, and the Alienware peripherals that are connected to your system, Alienware Command Center provides different options for customization in Default Mode and during gaming.

Hello Chris M,

I saw 3 companies updates, Microsoft,Intel and Dell

Amazing good job and special thanks to your whole team and specially Simran, Tarik, Magendra and Dell - Cares.

Those 4 are top of the build support, respect for that!

Updated perfectly, just needed 2 reboots.  Its still odd with the R13 being the flagship, has been out about 9  months now, and the fan labels still do not match their locations.  

@steadler and the others ...

Good posts here about how this version installs and works.

However, might help developers if you also additionally mention your exact Alienware model in your reports.

Area 51 R5; updated AWCC 5.5.8.0 with 2 reboots . . . no unusual problems

R13. Installed with no issues. Thanks. Luckily saw that this was a prerequisite to installing BIOS 1.4.0. BIOS also installed without issues.

I made a thread for this issue, not seeing this one for this kind of complaint. If anyone has any suggestions, I’m all ears.

It seems if I kill the AWCC Background Service using Task Manager, it loads, but then it tells me no FX Devices found, and I can't control anything. 

Seems to be an issue with the AWCC Background Service.

No matter what I do I cannot get 5.5.8 to work on my R13. I have Win11 installed, does this not work on it? I cannot get 5.5.0 to work either. The only release I can get to work is the one previous to these.

Every time I install it, it asks me after I open it to allow it to do something, I allow this, and after I just get a white screen with an Alienware symbol. I've completely removed it multiple times, reinstalled my computer, I'm forcing it to run as admin in case its a permissions issue. 

Anyone have this problem and know a fix? 

Try this:  reboot, then manually launch AWCC immediately, it will give a popup for permission to update, hit yea then let the white window sit for like 10-15 minutes. Its slow but it is doing something.  Make sure you are connected to internet as it downloads the new oc modules.  Once it comes back, click to open the fx and oc windows to test.  Next, do another re-boot and manual re-launch so it can complete the install and download.  When done, go back into the fx tab and re-save your led color schemes, my R13 kept booting dark until I did this.

Behemyth - I had this happen when the factory installed version had already corrupted (Overclock and Themal tabs broken).

Since the problems with AWCC (and they go waaaaaay back to previous machines, so I've learnt to run regular Macrium Reflect system images I can restore when AWCC corrupts) I restored a Macrium back up to a working AWCC state (I've had to do this three times in about 4 weeks) and ran the 5.5.8.0 installer from a working state. It ran fine with no white window.

That doesn't really help, but in my experience once AWCC is corrupt there's no getting it back without restoring a system image or reinstalling Windows.