The ALX Files Operation: FaceHug Area-51 R5 R6 R7 Desktop Case LED Full Resto
After Motherboard Swap Guide
OCT 31 : DISCLOSURE DAY
"... and these Area-51 R5 R6 R7 Triad 2.0 desktops were duds after a Mobo swap for reasons unknown unwanted unsolved for years now in a non-epic Swap War that'd raged 'tween Darkseid of the Moon v Lunar Light ..."
Do not go gentle into that good Night Rage, rage against the dying of the Light
The War Is Over : Let There Be Light
"... and I'd found a way that restored LEDs on three normal Mobos ...
This. Is Operation: FaceHug
Are you carbide on my Nano? Red glass on my Lightbulb? Darkseid on my Culture? Sapphire on my white Gold? Burst outta my chest & hide out in the Vents
My blood beats so alive might bite right through your Lens
"... and on several Halloween's prior I'd traditionally post a new ALX File" ... it's All Hallows' Eve & it's all happening. Right here. Right now. World-wide, send forth word to avoid connecting to all bottom row FIO Front Panel (FP) & USB pins & all Swap-Wars will all be over all the world-over ..."
(Yes. Aurora R1 dressed in partial A51 costume)
What u need to buy & know to restore Triad 2.0 case LEDs is finally here & while I don't own this desktop case I do have all its LED boards -FIO LOGO SIDE, RGB test strips, correct cables & now my sweet lil LED Suite's been face-hugged to three older Mobos (MSI X58 MSI X99 Gigabyte Z270 which pre-date the invention of the 2018 R5-7 FIO board) & when bench-tested together are equivalent to a case: all three major + all minor LED zones lit & color-changed using AlienFX 5.x software
This was basically solved way back in June on my MSI X99 (life & other delays kept the project in some doubts) just days ago I wondered about my 2009 Aurora ALX X58 as the last of three proving grounds for changeable LEDs & as they quickly worked even on that Ancient Alien? ... that's a wrap here at SkunkWorX
Legit R5 case owner Jason was recently sent the how to & when hugged-up to a newer Asus X670E Mobo, yes case LEDs were instantly resto'd there too & I'm convinced -when properly connected to- this species of FIO was like all the rest: a simple USB device, in need of the right cables & connecting scheme & now a fresh batch of owner-volunteers are needed to help reproduce our results starting right now simply by sourcing two of those exact cables then connecting up as shown & report back here or post their success on the Redditware Forum
Your help guide begins as pre-swap advice for those still using their factory Mobo who'll do a swap later, since there's still a final use for the old Alienboard before it's removed & even the old Hard Drive w/ its working pre-installed Windows & AWCC CmndCntr softwares to help trial the new swap Mobo & FIO on their initial power-up, where we can go looking for clues as to why there are no Treats & only Tricks afoot (clues help tips tricks & treats that'll apply to all swappers). Relevant I think that swappers taste how the factory "pulled it off" & dbl-check their homework on what to expect & look out for as the swap & software details unfold start to finish
-Swap Kit-
Factory R5-7 Alienboards: Pre-Mobo Swap To Do
1: Firmware Update the FIO Board Now
2: Export & Save Factory REGISTRY DATA Now
3: Cables & Connecting: The Old Factory FP & USB Are Obsolete Now
3a Buy TWO New Front Panel & USB Cables Now
3b Note: U2 Fan Loss or Issues? (see 8: U2 Fan Resto? in Part 2 next)
3c Where To Connect: Top Rows & Where To Avoid: Bottom Rows
4: Power Up: Reuse Your Old HDD SDD & Sniff Around
4a uFIOs: Device Manager Known "uNKwOnS" / UFAPs
(Check REG Editor & DVCMNGR For Device ID 187C 0550, Check Devices For AW-ELC, Launch CmndCntr: Heros vs Zeros)
5: New -or- Repair: How To Install AWCC CmndCntr 5.x Versions
R5-7 Factory Alienboards: Pre-Mobo Swap To Do
1: FIO LED Board Firmware Update
If you've NOT motherboard swapped yet & want your FIO board to have the latest firmware update (1.1.7) the factory alienboard + your working FIO board are required, just download & install the latest AWCC Command Center version 5.10.2 so the firmware can update during install
Note FIO firmware updates aren't easily done w/ out a factory R5-7 alienboard: typical gaming Mobos need an STLINK V2 programmer + STM32 CubeProgrammer software & apply it manually, but if your FIO board doesn't have or can't get the latest firmware flashed I wouldn't sweat it nor should u
2: Export & Save Your OEM Registry DATA
1: Admin > Open Registry Editor & click your way down to HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\BIOS
2: File > Export > Name your file "A51BIOS.reg", save it for use after your Mobo swap & Import it back right before your CmndCntr 5.x install (See 5: Install AWCC CmndCntr)
If You Didn't Or Can't Save Your BIOS.Reg File
I can't attach the .reg nor .txt files here so make a legit usable file yourself: copy paste the below text into Notepad > name it *.txt (ex. A51Bios.txt) > Save & later Import it into your Registry (HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\BIOS) right before u install or repair reinstall a CmndCntr 5.x version (See 5:)
Old Factory FP USB Cables Are Obsolete Now: Factory X299 & TRIP alienboards & FIOs use proprietary FP & USB pinouts-connectors that can't be reused on typical retail gaming swap Mobo header-connectors
3a Buy TWO New Front Panel & USB 2.0 Cables Now (prior Google link)
While there are several connecting options & products on the market, keep it simple for now & buy TWO inexpensive single-row 24" 60cm 5pin 5-wire USB cables like I did --> The Majik Bullets for connecting Mobo<to>FIO FP USB top row pins
3b Note: U2 Fan Loss or Issues? (see 8: U2 Fan Resto)
Jason's used R5 case didn't have nor do I have U2 fans here to test & know the outcome but soon swappers will start reporting it. Since the x4 FIO bottom row USB pins are repurposed for U2 Fans (PWM & TACH), will your non-alien Mobo & swap be penalized (?) w/ U2 fans that won't spin at all or do but at full speed &/or have no speed control at all in AWCC CmndCntr ... stay tuned (see 8: U2 Cable Resto Project when Part 2 posts next)
3c: What To Connect (Tops) & What To Avoid (Bottoms)
Factory R5-7 Mobo Diagram helps define what FIO FP USB pins are & aren't
FP & USB = a mix of Normal Tops & Proprietary "Alien" Bottoms
Your Mobo will include a paper or PDF Owner's Manual showing its specific Internal Connector Diagrams for FP & USB (printed micro-text on the board also); most Mobo brands will pin-out in the classic MSI JFP1 style (or close match) but not all do & may vary slightly: always consult your Manual or check the board to ensure your FP & USB were connected correctly
"Give me a ping Vasili, one ping only please"
Give me a top row, one top row only please. Use your Majik Bullets to connect Mobo<to>FIO FP 2 4 6 8 & USB 2 4 6 8 10
FIO FP Top Row = 2+ 4- P LED S (aka Power LED +/-) >< 6+ 8- (PWRSW +/-)
FIO USB = Top 5pins 2 (RED V+) 4 6 (WHT GRN D -/+ ) 8 10 (BLK GRD)
4: Power Up For the 1st Time
HDDs SSDs --> Old WIN or New WIN
Your Mobo is installed & connected correctly to a PSU & FIO board, what about an HDD SDD + Windows install? Some will still have their original R5-7 Windows install w/ AWCC CmndCntr pre-installed & Windows "In Working Order"
ProTip: Boot into your old Win 10 11 install as a test to see what happens
Tip: If you're still on your R5-7 Alienboard, take a short video of your case LEDs after you've pressed power on for what it does & looks like during the initial Factory Startup Routine & compare later w/ swap Mobo (or remember it well) but w/ power on & booting into old Win install observe the LEDs > Moments go by as Windows "Gets Devices Ready" for new swap Mobo > Reach the desktop > Launch your AWCC CmndCntr app & recheck if u can still color-change
If so? Terrific. Either uninstall all your old drivers & install the new ones & continue use of your old drive -or- set it aside & install Windows clean on a new drive & see what happens to your FIO & LEDs on that one --> Be it your old or new Win install, if u run into trouble follow the help tips & info directly below
Use Old Win Install To Help Fix A New Win Install
ProTip: If your case LEDs all work when using your old HDD+Win & then if a person installs Win clean on a 2nd drive - in the rare event the case LEDs "disappear" - they could use the help tips below to direct Device Manager to look for FIO drivers et al on the old drive, inspect & compare their Registry, it might help or even work
4a uFIOs: Windows Device Manager & Known "uNkNOwNs" / UFAPs
Booting the old HDD through the swap Mobo the prior-working FIO & case LEDs "have all their required software pieces in place" (lest a new chipset or driver be an issue, so install those from your Mobo Driver Suite &/or get online & check Updates > Optional Updates > & install ... it may help)
Above: My FIO Went MIA In USB On An MSI X99 & Giga Z270
Below: FIO "Comes Online" After AWCC Install Fixed the Registry
A consequential scenario would be that as CmndCntr tries to launch it may report "No AlienFX Devices Connected" + the AlienFX GUI goes missing & if that's happened to yours it may mean the Mobo-FIO-Windows didn't establish a proper USB COMM > find out by opening Windows Device Manager > check USB for an "Unknown USB Device" (the major cause of case LED loss in the past)
When FIO hugged to my X99 & Z270, both saw it as an Unknown in DVC MNGR while on the Aurora X58 it simply checked in like a VIP Rock Star
Next: Expand HID Devices & click VIEW > Show Hidden Devices > now check through any hidden Vendor Defined & USB Inputs u find by opening Properties > Events & look for your FIO ID = 187C 0550. Because your old Win install & FIO worked before, if unfunny USB junk is afoot the FIO is still listed in there but will be a hidden greyed-out 0550 device that DVCMNGR erroneously claims is "not now connected" (Windows à la 16 Candles: Auuuuuutomobile??? Lake. Big lake)
If in DVCMNGR it's down in USB as an Unknown instead of up in HID as a known u might try to be online & use the Properties box to "update the driver" through Win Updates / Optional Updates or try locally on C: drive. Otherwise & again it's because it used to be your old working Windows & CmndCntr install, all of the "correct" software & information should be there in the Registry where all the Device IDs are preinstalled & the R5-7 Desktop is listed as an AFX 2.0 Capable Device in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Alienware\System\AFXCapableDevices\2.0)
It can be of help to be online 1st & also see part 5 below & now go find the 1Gb CmndCntr.exe & do a "Repair Install" AS A POSSIBLE FIX that may work after the restart & if not then try a >Pro Tip< With desktop online, disconnect one end of the Mobo-FIO USB cable & reconnect it, see what DVCMNGR does & check if in a side-bar pop-up that "AWCC" wants to "help" install the FIO
Eventuallywhen your Mobo-FIO-Windows establishes a good USB COMM your FIO will or should also display as a Device called AW-ELC
5: New -or- Repair: How To InstallAWCC CmndCntr 5.x Versions
Whether a new clean Win or your old WIN drive, whether a new install or repair reinstall of AWCC you're going to 1st use your saved BIOS.REG or BIOS.txt file, so that the OEM REG DATA is what's being "read" by AWCC during install so open Registry Editor & click into HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\BIOS
*Click File > Import > Find Open & Import your .reg file (for .txt clik "All Files") > Factory R5-7 DATA will then overlay & disappear after the Restart
*Launch & install the 1Gb AWCC CmndCntr software & Restart
* Keep an eye on your case LEDs & when u reach the desktop > launch AWCC CmndCntr > did it open without issue?, if so, you likely have case LEDs & can modify the Default Blue Theme or create a new Theme & otherwise play w/ the settings, put the PC to sleep to check the sleep routine then eventually shutdown for a final check, power up again & enjoy etc
Or did it say No AFX Devices Connected?
I've seen CmndCntr launch into a green splash page as no device connected ... yikes, at least for a clean install of Windows you'd be back into a loop from the help guide above, to RegEditor making sure FIO device IDs registered & desktop is AFX 2.0 Capable, try to be online of course & then next you're back into a mix of rechecking DVCMNGR as shown, dis then reconnect the FIO USB & of course try a Repair Re-Install or even two repairs of AWCC or use a different version if u have one (older or newer)
Last it won't help but can't hurt to check CmndCntr Install Logs (make sure in File Explorer u can see hidden files-folders since AppDATA is a hidden folder) in C:\Users\*AccountName*\AppData\Local\Temp looking for the ELC & Firmware logs where ELC likes to see a model 5 & Firmware runs a check for outdated vs current versions & applies the update when needed & logs it ... so long as the FIO is in fact a working USB device for if not then both logs will say "no AW devices found" (yikes) which can only mean the FIO is "offline" w/ a USB error that needs corrrrected (somehow)
I've just posted about all the help I know of
However, so long as your FIO board has Molex 4pin power, the right FP & USB cables & consulted your new Mobo User Manual to connect to the right P LED S or Power LED +/- & Power On Switch +/- pins, have all your drivers installed etc I do not think you'll encounter an issue but will instead have full case LEDs (or partials like an unlit "zone" to troubleshoot later). Let someone know here or Redditware forum what happened (pics or it didn't happen)
Aurora R1 Normal MSI X58
In the end, your FIO must FaceHug corrrrrectly to your new Mobo's FP & USB headers, have your REG & DVCMNGR in order & if so then on paper it'll re-behave as the simple USB device it's always been, same as mine & Jason
(Stay Tuned For Part 2 Next)
________________________
Come On. Xperience a Meaningful After-Life w/ Your Alien
And you might be the one to take away the pain & let my mind go Quiet And nothing else is quite the same as how I feel when I'm at your Side
Come on, come on! Out from underneath who you Were Come on! Come on now you know that it's time to Emerge
6: The MSI-Alien DeepFake Conspiracy: Why Case LEDs Failed In the Past (Bottom Row Pins: A Rant)
7: P LED S (Power-Sleep) vs Power LED + -
7a: Factory RGB Startup & Sleep Routines vs P LED S
7b: What If Start & Sleep "Look Or Act Different"
8: U.2 Fan Resto Cable Project (???)
9: Total LED Parts Incompatibility Between R2-4 Triad & R5-7 Triad2.0
______________________
6: MSI-Alien DeepFake Conspiracy: Why Case LEDs Fail ???
-Bottom Row Header Pins Rant-
Narrator: The use of standard classic dual-row FP & USB cables caused LED loss time & again & USB troubles, while their disuse & use of single-row cables produced LEDs each time + no USB issues, somy gut tells me that when the new Mobo USB Controller was connecting to an FIO wrong it crashed their USB COMM or chips & the FIO also spazzed-out when connected to the Mobo FP wrong & it failed to produce LEDs & then Windows DVCMNGRsees it as a uFIO ="Unknown USB Device (Device Descriptor Request Failed) Code 43 (Try Google for help tips if your FIO is Code RED 43 in DVCMNGR) & you're trapped in an LED failure-loop until FIO connex properly ...
Factory MSI diagram shows all of the R5-7 alienboard's FP & USB top row pins are "normal" while bottom rows are abnormal, proprietary "Alien Circuitry"
FP = PostError Door CLK DAT Detect >< USB = U.2 FANS
Companion FIO boards have exclusive alien-only use over those pins which retail Mobos can not plug n' play nor replicate, nor can they have theirnormal FP & USB headers connected ... not while using industry standard dual-row FP USB cables like everyone else uses, it's been a hot mess people
Planetwide, humans were unknowingly improperly connecting their new Mobo's USB &/or Super IO chips to the FIO STM32 Micro-controller's alien circuits & U2 Fan Mosfets = USB COMMs crashed Roswell style between them & Windows 10 11 = Unknown USB Device = uFIO
Not a good idea to inject HDD LED + - & U.2 Fan "noise" into your STM32 chip & Mobo USB controller chip & expect them to work ... THEY FAIL)
Deep Faked Alienboard & FIO FP USB Headers
Theatricality & deception ... powerful agents to the uninitiated ... but we are initiated, aren't we ...
For the alien Mobo, aside from intentionally printing-on a reverse pin numbering convention then disguise-presenting Panel1 & USB1 to look "normal", there's no printed companion text or chart at all telling owner-users what the header pins are even for or do & the mix of what they intentionally did & didn't print is so very cringe if u ask me
FIO FP USB: Though MSI tried to disguise FP bottoms as HDD RESET they're anything but. That goes for "disguising" USB1 as just that: a normal dual-row USB header when it ain't & while it may've been deemed electrically "safe" to connect a normal Mobo HDD & Reset or bottom USB channel #2 it wreaks havoc on the Mobo<>FIO COMMs (AI Chatbots were in grief over how injecting HDD Activity "chatter" into the STM32's POST & Door pins meant it never knew if the door was opening-closing thousands of times a minute & worse, let alone inject U2 Fan TACH "noise" back into the Mobo USB chip etc)
For years I helped spread their deceit & misinformation that the FIO had Industry-Standard FP & USB because "just look at the labels, we know what the pins are for, it's classic MSI JFP1& to use dual-row cables like we always have" (!!!). It's this mix of purposely not labeling their Mobo pins then mislabeling their FIO pins which cost people years of head-scratching & dis-enjoyment which is just ... gross if they asked me
I know FIO boards don't have to "support" non-alien hardware but come on now ... inauthentic labeling ...
7: Mobo Brands, FIO P LED S 2 4, PWR LED + -
Factory 2009-18 alienboards were made by MSI who at times includes a 2pin Power LED design called PLED (Power) & SLED (Suspend-Sleep) where AI Bots claim MSI P LED S is a slightly different "electrical way" of doing the otherwise classic POWER LED +/- duty but the distinction & outcomes remain to be seen what effect if any on the STM32 chip & thus LEDs when connecting a new Mobo that uses classic Power LED +/- to your FIO P LED S pins 2 & 4
⦁ Pick Your Favorite Chatbot for the breakdown
⦁ Narrator: LEDs here behaved "different" when face-hugged between the factory R5 alienboard PLEDS & the Aurora R1 PLEDS (below)
7a: Factory RGB Startup & Sleep Routines
When an R5-7 Mobo & FIO power up, the three major LED zones quickly sequentially light up as Alienhead > PANEL > SIDEs followed by an RGB bulb-check that settles into a static color (or prior saved Theme) & when the PC's put to sleep the Alienhead cycles through an amber breathing animation. Those two "stunts" are made possible by the electrical states of the MSI P LED S pins 2-4 (& in some sense the FIO MCU chip which is beholden to the rules of its firmware)
7b: What If Startup & Sleep Look Or Act "Different"
My Gigaboard & Jason's Asusboard have classic Power LED +/- on pins 2-4 & while he experienced no issues the Giga made the LEDs seem "off" in a way during startup & sleep. To prove a point, when hugged w/ the Aurora R1 which has MSI's P LED S?, it acted "a bit off" on startup & when put to sleep it blinked RED twice (over & over) --> gone was the Amber breathing so just to check I sent the FIO back on the R5 alienboard & pow Startup Sleep were back > back to R1 & Start is "odd" & Sleep blinks RED again which tells me the firmware may be responsible for a "set of electrical tolerances" the MCU chip reacts to &/or doesn't
I wanted to put it out there that at BEST you'll have changeable LEDs during periods of normal use while there -may- may be a select few who experience some "feature-loss" as the cost of this Human vs Alien Swap War ... In the past, the safest advice was to swap-in another MSI Mobo w/ Asus a close 2nd &/or wait for owner confirmations on compatible brands & models to try. The more owners posting their results the better
Project cable is a "what-if", an idea I cooked up that has never been tested or used: proceed w/ caution & attempt use at your own risk
It may be possible - at least for some Mobo brands & models - to DIY fab an FIO<to>Mobo PWM TACH conversion cable ... depending: AI bots advise some brands will engineer their PWM & TACH signals differently (depending on the Super I/O or other chip designs etc) which could affect this but the simple idea is to buy a 3rd single-row USB cable:
One 5-wire end connects to FIO USB bottom row header pins while the other end has x4 pins backed-out (leave pin5 in there, insulated) & then snip-off the x4 USB pins
Next u hand-apply & jump together x2 typical new fan pin terminals (ie jump the x2 tach onto your pin1, jump x2 PWM onto pin2) & then insert them into a new 4pin PWM fan connect to help grab PWM from & send TACH back to a typical Mobo 4pin case fan header & use the BIOS or included fan software to take back control of U2 fans
⦁ AI bots suggest it's doable & could work if a "compatible" Mobo type is used -but- a side-effect of an incompatible type can be non-working fans, or a mix of (either) when it's set to 0% u get the inverse & it runs 100%, or set 100% = 0%, thus they "do work" so long as u program it to run the "opposite"
9: Total LED Parts Incompatibility Between R2-4 & R5-7
In the same way an Intel CPU can't go into an AMD Mobo & vice versa, so it is here. While R2-7 SIDE door case panels may all physically fit & can trade as panels, they're inner SIDE LED boards can't interchange
None of their LED parts -FIO LOGO SIDE- can interchange forwards nor back nor ever "mix" between Triad R2-4 vs Triad 2.0 R5-7 because their FIOs use different brand-types of MCU chips while their LED boards use different brand-types of IC controllers thus two entirely different "languages signals addresses protocols" making them 100% incompatible because they simply can not COMM
Yes u can place a newer R6 door onto an older R3 case & yes the old R3 LED board needs to come out & placed back into the R6 door
Ex: R3 FIO can not go into an R6 & make the R6 case LEDs "work" & vice versa
This uTuber claimed he couldn't get case LEDs back after a Mobo swap in an R5 & so installed an R2-4 H6HK9 FIO into an R5 case - claimed that it made all the R5 case LEDs work - claimed he didn't like the SIDE LED "look" & hot glued in some aftermarket RGB strips ...
I then noticed in vid Part1 he'd put in an R2 LOGO board as well instead of reusing the R5 LOGO then put it back in after the vid2 repaint & clearly he made that all up: the R5 FIO wouldn't work, he tried the R2 but it was incompatible w/ the R5 LED boards so he installed an R2 LOGO but had no R2 SIDEs & so got aftermarket RGB strips, yes? Yes
Can someone go point him to my Help Guide here & get that R5 FIO board there working again w/ R5 LOGO SIDEs & pull that R2 FIO-LOGO outta there & a word about spreading the mis-info R2 parts "worked" w/ R5 parts when 100% they can't (!!!)
Cass-Ole
8 Professor
•
1874 Posts
•
9716 Points
0
0
Posted November 1st, 2026 21:56
Hug Guide Part1a Post #2
3: Cables & Connecting
Old Factory FP USB Cables Are Obsolete Now: Factory X299 & TRIP alienboards & FIOs use proprietary FP & USB pinouts-connectors that can't be reused on typical retail gaming swap Mobo header-connectors
3a Buy TWO New Front Panel & USB 2.0 Cables Now (prior Google link)
While there are several connecting options & products on the market, keep it simple for now & buy TWO inexpensive single-row 24" 60cm 5pin 5-wire USB cables like I did --> The Majik Bullets for connecting Mobo<to>FIO FP USB top row pins
3b Note: U2 Fan Loss or Issues? (see 8: U2 Fan Resto)
Jason's used R5 case didn't have nor do I have U2 fans here to test & know the outcome but soon swappers will start reporting it. Since the x4 FIO bottom row USB pins are repurposed for U2 Fans (PWM & TACH), will your non-alien Mobo & swap be penalized (?) w/ U2 fans that won't spin at all or do but at full speed &/or have no speed control at all in AWCC CmndCntr ... stay tuned (see 8: U2 Cable Resto Project when Part 2 posts next)
3c: What To Connect (Tops) & What To Avoid (Bottoms)
Factory R5-7 Mobo Diagram helps define what FIO FP USB pins are & aren't
FP & USB = a mix of Normal Tops & Proprietary "Alien" Bottoms
Your Mobo will include a paper or PDF Owner's Manual showing its specific Internal Connector Diagrams for FP & USB (printed micro-text on the board also); most Mobo brands will pin-out in the classic MSI JFP1 style (or close match) but not all do & may vary slightly: always consult your Manual or check the board to ensure your FP & USB were connected correctly
"Give me a ping Vasili, one ping only please"
Give me a top row, one top row only please. Use your Majik Bullets to connect Mobo<to>FIO FP 2 4 6 8 & USB 2 4 6 8 10
4: Power Up For the 1st Time
HDDs SSDs --> Old WIN or New WIN
Your Mobo is installed & connected correctly to a PSU & FIO board, what about an HDD SDD + Windows install? Some will still have their original R5-7 Windows install w/ AWCC CmndCntr pre-installed & Windows "In Working Order"
ProTip: Boot into your old Win 10 11 install as a test to see what happens
Tip: If you're still on your R5-7 Alienboard, take a short video of your case LEDs after you've pressed power on for what it does & looks like during the initial Factory Startup Routine & compare later w/ swap Mobo (or remember it well) but w/ power on & booting into old Win install observe the LEDs > Moments go by as Windows "Gets Devices Ready" for new swap Mobo > Reach the desktop > Launch your AWCC CmndCntr app & recheck if u can still color-change
If so? Terrific. Either uninstall all your old drivers & install the new ones & continue use of your old drive -or- set it aside & install Windows clean on a new drive & see what happens to your FIO & LEDs on that one --> Be it your old or new Win install, if u run into trouble follow the help tips & info directly below
Use Old Win Install To Help Fix A New Win Install
ProTip: If your case LEDs all work when using your old HDD+Win & then if a person installs Win clean on a 2nd drive - in the rare event the case LEDs "disappear" - they could use the help tips below to direct Device Manager to look for FIO drivers et al on the old drive, inspect & compare their Registry, it might help or even work
4a uFIOs: Windows Device Manager & Known "uNkNOwNs" / UFAPs
Booting the old HDD through the swap Mobo the prior-working FIO & case LEDs "have all their required software pieces in place" (lest a new chipset or driver be an issue, so install those from your Mobo Driver Suite &/or get online & check Updates > Optional Updates > & install ... it may help)
Above: My FIO Went MIA In USB On An MSI X99 & Giga Z270
Below: FIO "Comes Online" After AWCC Install Fixed the Registry
A consequential scenario would be that as CmndCntr tries to launch it may report "No AlienFX Devices Connected" + the AlienFX GUI goes missing & if that's happened to yours it may mean the Mobo-FIO-Windows didn't establish a proper USB COMM > find out by opening Windows Device Manager > check USB for an "Unknown USB Device" (the major cause of case LED loss in the past)
Next: Expand HID Devices & click VIEW > Show Hidden Devices > now check through any hidden Vendor Defined & USB Inputs u find by opening Properties > Events & look for your FIO ID = 187C 0550. Because your old Win install & FIO worked before, if unfunny USB junk is afoot the FIO is still listed in there but will be a hidden greyed-out 0550 device that DVCMNGR erroneously claims is "not now connected" (Windows à la 16 Candles: Auuuuuutomobile??? Lake. Big lake)
If in DVCMNGR it's down in USB as an Unknown instead of up in HID as a known u might try to be online & use the Properties box to "update the driver" through Win Updates / Optional Updates or try locally on C: drive. Otherwise & again it's because it used to be your old working Windows & CmndCntr install, all of the "correct" software & information should be there in the Registry where all the Device IDs are preinstalled & the R5-7 Desktop is listed as an AFX 2.0 Capable Device in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Alienware\System\AFXCapableDevices\2.0)
It can be of help to be online 1st & also see part 5 below & now go find the 1Gb CmndCntr.exe & do a "Repair Install" AS A POSSIBLE FIX that may work after the restart & if not then try a >Pro Tip< With desktop online, disconnect one end of the Mobo-FIO USB cable & reconnect it, see what DVCMNGR does & check if in a side-bar pop-up that "AWCC" wants to "help" install the FIO
Eventually when your Mobo-FIO-Windows establishes a good USB COMM your FIO will or should also display as a Device called AW-ELC
5: New -or- Repair: How To InstallAWCC CmndCntr 5.x Versions
Whether a new clean Win or your old WIN drive, whether a new install or repair reinstall of AWCC you're going to 1st use your saved BIOS.REG or BIOS.txt file, so that the OEM REG DATA is what's being "read" by AWCC during install so open Registry Editor & click into HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\BIOS
* Click File > Import > Find Open & Import your .reg file (for .txt clik "All Files") > Factory R5-7 DATA will then overlay & disappear after the Restart
* Launch & install the 1Gb AWCC CmndCntr software & Restart
* Keep an eye on your case LEDs & when u reach the desktop > launch AWCC CmndCntr > did it open without issue?, if so, you likely have case LEDs & can modify the Default Blue Theme or create a new Theme & otherwise play w/ the settings, put the PC to sleep to check the sleep routine then eventually shutdown for a final check, power up again & enjoy etc
Or did it say No AFX Devices Connected?
I've seen CmndCntr launch into a green splash page as no device connected ... yikes, at least for a clean install of Windows you'd be back into a loop from the help guide above, to RegEditor making sure FIO device IDs registered & desktop is AFX 2.0 Capable, try to be online of course & then next you're back into a mix of rechecking DVCMNGR as shown, dis then reconnect the FIO USB & of course try a Repair Re-Install or even two repairs of AWCC or use a different version if u have one (older or newer)
Last it won't help but can't hurt to check CmndCntr Install Logs (make sure in File Explorer u can see hidden files-folders since AppDATA is a hidden folder) in C:\Users\*AccountName*\AppData\Local\Temp looking for the ELC & Firmware logs where ELC likes to see a model 5 & Firmware runs a check for outdated vs current versions & applies the update when needed & logs it ... so long as the FIO is in fact a working USB device for if not then both logs will say "no AW devices found" (yikes) which can only mean the FIO is "offline" w/ a USB error that needs corrrrected (somehow)
I've just posted about all the help I know of
However, so long as your FIO board has Molex 4pin power, the right FP & USB cables & consulted your new Mobo User Manual to connect to the right P LED S or Power LED +/- & Power On Switch +/- pins, have all your drivers installed etc I do not think you'll encounter an issue but will instead have full case LEDs (or partials like an unlit "zone" to troubleshoot later). Let someone know here or Redditware forum what happened (pics or it didn't happen)
Aurora R1 Normal MSI X58
In the end, your FIO must FaceHug corrrrrectly to your new Mobo's FP & USB headers, have your REG & DVCMNGR in order & if so then on paper it'll re-behave as the simple USB device it's always been, same as mine & Jason
(Stay Tuned For Part 2 Next)
________________________
Come On. Xperience a Meaningful After-Life w/ Your Alien
And you might be the one to take away the pain & let my mind go Quiet
And nothing else is quite the same as how I feel when I'm at your Side
Come on, come on! Out from underneath who you Were
Come on! Come on now you know that it's time to Emerge
(edited)