Unsolved
This post is more than 5 years old
4 Posts
0
1457
November 24th, 2016 23:00
Alien Command Centre
I have a 51 R2
running Windows 10
the Command Centre FX does not work. the side panel light remain an off white color and the alien head is pale yellow.
I have:
disabled fast startup
checked all the boxes for .NET 3.5 and 4.6
uninstalled and reinstalled ACC and set it to run as Admin..
nothing works??
help please
0 events found
No Events found!
Eimy_B
6 Operator
•
4.4K Posts
0
November 25th, 2016 10:00
Hi,
Have you tried the Alien FxTester? If not, you can check how to do it on the article below. You can also follow ALL the steps on how to uninstall and reinstall the Command Center in a proper way (deleting registry, etc):
SLN303405 - How to Remove and Reinstall the Alienware Command Center
Let me know!
amsuae
4 Posts
0
November 26th, 2016 08:00
Ok, yet to try FX tester but have carried out the full uninstall as listed on your link. Before and After your message. Still no joy .... side panels are pale white and Alien face is pale yellow...
amsuae
4 Posts
0
November 28th, 2016 03:00
HI,
tester does not work. what it is not doing is a firmware check? should it do one. anyway still have no lights?
Eimy_B
6 Operator
•
4.4K Posts
0
November 30th, 2016 14:00
Can we have a screenshot of what you're seeing on the FXtester?
amsuae
4 Posts
0
December 1st, 2016 23:00
chipster666
1 Message
0
December 4th, 2016 14:00
Having the exact same issue with my new R4 laptop. I am guessing it started after an update about the same time frame as when this message was started. I know its not the hardware, as when I change themes, it will show for a brief moment with the new theme, then resort to blank with only the special keys and power button showing any light at all. Also tried the same diagnostics as listed above with same results.
Eimy_B
6 Operator
•
4.4K Posts
0
December 6th, 2016 12:00
Amsuae,
Send me a private message with the service tag, so I can assist you further!
SimplyJ3sse
8 Posts
0
December 6th, 2016 15:00
I will say that I have the same issue periodically on my Alienware 15R3. I have found that going back to bios revision 1.0.2 fixes the issue, but it reappears after a few days of running the "latest" 1.0.8.