McScruffy
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

Not sure if this is related to my post but installed the update to Alienware Command Center (AWCC) and it broke it again.  I was able to fix it within about 20 minutes, so here's what I did to try to streamline my previous steps which worked pretty well:

First off, right now I'm running Windows 10 Pro build 1903, fully up to date according to Windows Update.

Opened AWCC for the first time in a few weeks to change a light setting and got the update notice, went through with the update, after a reboot it was back to broken like most the year.

1) Rebooted into the built-in Administrator account (you have to enable it in local users and groups as it's disabled by default and has absolute permissions across entire system as opposed to standard administrator accounts)

2) Ran Revo Uninstaller to uninstall AWCC, when prompted to check for leftover files I chose "Advanced".  Selected all files that were showing as under any directory path with Alienware Control Center in it as well as that directory itself. **Make sure you click the delete button toward the bottom left of the scan window before hitting next.**

3) Refreshed application list in Revo and Uninstalled Alienware OC controls and did the same "Advanced" check as above but it said nothing leftover was found.

4) Refreshed again and went to the Windows Apps tab in the top ribbon of Revo. AWCC was listed there as well so ran uninstall and did "Advanced" scan/check as in steps 2&3. Selected anything referencing Alienware Command Center/AWCC for the registry keys as well as all files/directories referencing the same.

5) Moved log files from Installed AWCC and OC Controls (C:\ProgramData\Dell\UpdatePackage\Log) into a new subfolder there I created labeled "Old."

6) Rebooted and logged back in directly to built-in Administrator account.

7) Went to registry and completely disabled UAC (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -> set EnableLUA to "0").  Reboot back to built-in Administrator.

8 ) Downloaded latest AWCC and OC Controls installers directly from Dell Support.  Installed AWCC and OC Controls.

9) Rebooted back to built-in Administrator account.

10) Ran AWCC and got error when it opened saying no FX devices found, clicked okay, saw notice at bottom right services were starting up, 10 or so seconds later app was accessible and regained control of FX lighting and Fusion tab.

11) Rebooted and logged in to regular user account.

12) No AWCC application (not surprised), ran installer downloaded in step 8 and selected "Repair" option.

13) No AWCC application listed to run in start menu after completing step 12, but files and folders are in the right place and the Command Center Suite is in Apps and Features.

14) Install AWCC from Microsoft Store. Launch when installed.

15) If it tries installing other components (AW Sound Center, FX Systems, etc) go with it following prompts and verifying identity if necessary (for me facial recognition would say something went wrong, try again, though using PIN instead worked). You may or may not get a prompt that says you already own it. If so, just click the close button on bottom left of prompt and continue.

16) After all in the previous steps finish it will ask to download the content now. Click "Okay." It will run the install of these components in the background over a minute or two and you should see messages pop up to say when each is installed. AWCC app should still be up and running and you should be able to verify full access to FX and Fusion tabs again.

17) Once verified you can access FX and Fusion, reenable UAC by going to the registry (refer to step 7) and setting EnableLUA to "1" and reboot.

18) Logging back in to your regular account, launch AWCC app again and it may pop up the no FX devices found message again, click okay and you should see the message about AWCC services starting at the bottom right. After 10-20 seconds there was a UAC prompt to let AWCC make changes. Click "Yes" and you should be able to access FX and Fusion from your regular account with security in place again. (It may have a pop up for a component install again and go ahead and do it if it does.)

The above I've been able to recreate successfully so I really hope it fixes others' issues. I've rebooted after finishing the steps a number of times and it always pops up with the no FX devices found message but hitting OK on that and letting the service startup for it run (followed by the UAC approval window) has given me full access every time. Closing out the app and running it later doesn't give me any no FX devices errors as well, it just loads straight to the app (the service is already running in the background at that point, so duh).

This is pretty much confirmed to me to be a combined issue of permissions as well as the application calling files from two separate locations that you only are getting by running the installer from Dell Support as well as running the install from the Microsoft Store. With Windows 10, the folders the Microsoft Store utilizes seem to be off limits to anything 3rd party.

Alan Slemani
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

My alienware command center not working after update my windows to 1903. my alienware command center not work properly i uninstall the software and re download the newest version. i did all steps deleting alienware folder in appdata and program data and rigedt and re install the soft ware but dot work it shows a private message said that not supported alienFX were detected.

 

0 Kudos
Zanovello
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

Hey McScruffy, i’m trying to follow your steps... but a need a little help. When you say adm account and user account. How do I change that. A have only one account in my windows, and this one is already and admin account. Is there another admin way to use windows? If there is, how i change between them? Thank you for trying to do what Dell desn’t.

0 Kudos
McScruffy
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

If you have Windows 10 Pro, right click on the Start Menu button at the bottom left of your task bar and select Computer Management.  In the window that opens up navigate to Local Users and Groups-->Users.  In the Users folder there is an account called Administrator that is disabled by default in all versions of Windows.  Double click Administrator, uncheck the box for "Account is disabled," and click OK.  I'd suggest right clicking it after and selecting "Set Password" and setting a secure password because that account has control over everything.

If you don't have Pro or just want the command line version, from your account with admin rights click on the Start Menu and type "cmd" and right click on the Command Prompt app to select Run as Administrator.  Enter the following in the elevated privilege instance you just ran:

net user administrator /active:yes 

Hit enter, then type net user administrator <Password>  (instead of <Password>  put in the actual password you want assigned to the account.

Either way you do it I'd reboot before logging in as the administrator and doing any of the other steps.  Once you've finished (hopefully with success!), I'd also highly recommend disabling the administrator account.  From command line you open the elevated instance as outlined above and instead of typing /active:yes you change to: /active:no

From the first method mentioned you'd go into the properties (double clicking the administrator user in Computer Management) and check the box for "Account is disabled."

Hopefully that helps you and you are able to get it working for you like I was for me!

0 Kudos
Zanovello
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

I’m at work right now, but as soon as i get home, i’ll do as you said. Thank you so much for the quick answer.

0 Kudos

Re: 17 R5, no supported AlienFX devices were detected

Hey Mc scruffy I followed all the steps you mentioned above... i am getting the same message... not working for me... help me... is there any other method i can try?

0 Kudos
Quadfarmer
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

My command center just did an update and I lost control.  I had it previously without doing any of these steps.  I only have an Aurora R8 so I dont even know that these steps are worth getting the light control back but man oh man how broken can this be.

0 Kudos
AllenBronz
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

Hi,

I tried everything posted here and all the troubleshooting steps supplied by Dell Support. Nothing worked to get my LED lights to come back on my m17.

Ended up that Dell sent a technician to the house and replaced the motherboard, Now everything works as intended but I am super worried about doing any updates in the fear that it will break again.

0 Kudos
Quadfarmer
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

On top of my other issues I do not believe the fan speeds are changing on my Aurora R8

Command center always reports 25% on top fan and 9% on front.  Don't know why.

0 Kudos
Highlighted
ZephyrNelo
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

Was able to fix this by logging into the Administrator account, unlocked it like McScruffy said, with the command line. 
Then, in Add/remove programs, select Alienware Command Center Suite entry, click Modify and then choose Repair.

After this you can check the command center, AlienFX was working without messages immediately.

Logged back into my own account, started AWCC and AlienFx worked immediately without messages or further action required.