wa3pnt Posted September 15, 2013 Share Posted September 15, 2013 I have a system (Windows 8, ASUS Sabertooth 990FX R2.0, AMD FX-8250, AX-860i, H100i, Commander 2, Cooling Node, Lighting Node, 32GB G.Skilll Ripjaw, 500R, etc.) that is operating properly with the Link Commander and Software. Initially Corsair Link did not see the Commander, but I followed Toasted's procedure to update the Commander Firmware to 2.0.6 using Link 1.2.7 on a Windows 7 System and now all devices work with Corsair Link under Windows 8. Occasionally, when Corsair Link opens at boot there are duplicate devices (H100i, Fans, etc.) showing with no readings, but deleting the erroneous devices returns everything to "normal". The reason for the thread title is that I've just built a duplicate system in an Air 540 Case. Upon installation of Windows 8 and then Corsair Link version 2.4.4948 I again did not see the Commander. Instead of using one of my Windows 7 Systems to upgrade the Firmware on the Commander, I uninstalled Link 2.4.4948, deleted all related folders in the Programs and User (profiles) areas, did a reboot and then cleaned the Registry. I loaded Link 1.2.7 and could see the Commander to do a Firmware update. When I clicked on the START button for the update, the addresses which were being written counted up on in the window, and then stopped. Neither the START or CLOSE buttons could be selected, the Link Program was "Not Responding", and I was certain that I had bricked the Commander. I let it set for 30 minutes, and then used Task Manager to end the Link 1.2.7 processes. I uninstalled Link 1.2.7, related folders and profiles, did a reboot and cleaned the Registry. I then re-installed Link 2.4.4948 and WALA, the Commander was listed under devices with Firmware 2.0.6. Waiting for a Lighting Node (due in two days) but everything else is operating great, so a happy ending. RodeoGeorge Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.