Highlighted
12dinesh93
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

Hello all,

Even i'm experiencing this alienFX devices not detected issue, but i see that most of the people mentioned that their lights are working but were not changing. But in my case the lights went totally dark and none of the alienFX lighting system is working.

Is it only me or anyone else's had the same issue.

Reply
Highlighted
Zanovello
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

In my laptop, the keyboard lights are on as the trackpad and alien logos. But set as pale blue. Can’t change. The rainbow light effect on keyboard also occurs when booting bios.
Reply
Highlighted
AllenBronz
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

I have the same issue. No LED lights what so ever. Completely dark.

Currently working with Dell support. I don't have much faith that it will get fixed. I just want Dell to authorize me sending the unit back for repair.

Reply
Highlighted
Mighty Mark
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

mine too, dark. tried all the steps in these posts still dark, but worked fine before reinstalling windows, I noticed the Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Alienware\OC Controls is missing the system folder and .02 folder that contains the FX drivers. but I haven't found a way to get those files. 

the way I found this is I used my wife's 17 R5 bought same configuration as mine same time hers the lights work and has those files mine don't work and are missing them.

Reply
Highlighted
Mighty Mark
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

talked to dell all they say is try a older version or reinstall the newer one for the 150th time. tried both those options too.  Still dark. don't even light on boot, I'm at a loss

Reply
Highlighted
Zanovello
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

Dell programers seems to be lost too. This is an old problem (just search in other forums), that is anoying costumers for a while. In months, no definitive solution. Don’t think that they (Dell) will ever solve this problem. Looks like they are waiting for a costumer solution, lile the ones posted here in previous pages.

Reply
Zen Svelte
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

Ay, you should copy those files and send them here for us

Reply
Highlighted
Zen Svelte
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

If you can send the files from the OC Controls on the other computer I can try adding it to mine and see if that fixes it for me as well. You should also be able to do that with your own computer as well

Reply
Highlighted
Zen Svelte
1 Copper

Re: 17 R5, no supported AlienFX devices were detected

Hey, I don't quite understand this. Could you give a detailed instruction on what you did, rather than a story explanation? Sorry if the way I worded this sounds rude. I'm not trying to be at all, but I can't find a better way to ask this. I've been having a lot of issues lately with the Command Center and lights and this seems like a promising solution, but I can't get a strong understanding of what it is you are saying you did

Reply
Highlighted
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.

Reply