tech007

@kewlmunky - thanks for that info, I will reach out to them. In other news, I ended up making a fix today that works without really any coding (other than copy/paste) using Task Scheduler. In Task Scheduler, create a new Task - call it whatever you want, I called mine "Thermaltake" Under the Triggers tab, create a new trigger and select "On an event" Select Custom and then Edit Event Filter... Under the XML tab, click the checkbox to Edit query manually then enter <QueryList> <Query Id="0" Path="System"> <Select Path="System">*[System[Provider[@Name='Microsoft-Windows-Power-Troubleshooter'] and (Level=4 or Level=0) and (EventID=1)]]</Select> </Query> </QueryList> The only option I have selected under Advanced is "Enabled" Under Actions you will create two. For the first one, create an action to "Start a program" and under Program/script enter taskkill - this closes the running instance In the Add arguments field enter /f /im "TT RGB Plus.exe" - this targets the app itself, if it doesn't work make sure you have the right process here Click OK and add another action For the program/script, browse to where your TT software is installed, mine is "C:\Program Files (x86)\Tt\TT RGB Plus\TT RGB Plus.exe" - this should be the same as step 7 A few other nits: Not sure if needed, but under Settings I have "Allow task to be run on demand" checked, this way I could run it to test before doing a sleep test I have "If the running task does not end when requested, force it to stop" checked And finally, I have set "If the task is already running, then the following rule applies:" set to Stop the existing instance Probably sounds more complicated than it is. Only takes a minute to set this up. It will be saved under Task Scheduler Library in case you need to tweak it. I have tested it and it seems to work well. Once you log back in or otherwise wake from sleep you should see the TT program quit then reopen. The only issue I see is the ghost tray icons which show in the bottom right of my task bar till I mouse over them. TT if you read this, this is why I am frustrated with you guys. You could have easily done this yourselves in many different ways. If there is indeed an updated cable I will got that route as it would seem like a better solve.

Thank you for this. I am not sure why this isn't getting more attention. I am very disappointed in the product because of the ridiculously poor software/hardware (controller) design. The posts on this forum (ThermalMike) that users should shut down their computer, change bios/EFI settings, buy different hardware (implied), or develop their own fix is inexcusable. Where is the fix for this? As mindPreBlown suggests, we can fix this ourselves as the consumer. But that is absolutely ridiculous. I am still weighing whether I should write a script for this (I would prefer PowerShell) or just return it. To quote ThermalMike: "Hi, Unfortunately a limitation of the MB USB 2.0 header. Check to see if you can do a different sleep mode that does not disable the 5V. Basically when the system goes to sleep it drops connection to the controller, therefore you have to reboot the software for it to reconnect." Mike, I would disagree from a consumer point of view. You are blaming what was something that should have easily been uncovered through testing before you shipped the product. I perceive this as 1) a limitation of your own software and/or 2) a limitation of your controller. I have a View 32 case and the cheaper controller saves state fine with no software whatsoever. Regardless, in this era at this price point, I expect your gear to work as advertised with standard computer features like sleep. Quite frankly, I am surprised I just dropped $300 on hardware from you guys to only be met with comments like I should shut down my computer instead of using sleep. Honest questions: Why do you a) not save state on the controller itself? or b) develop software to reconnect to your own controller after sleep? While you cannot roll back time and fix the hardware, fixing this in software seems to be a few lines of code. You have spent more time on the forums than it would take to write the fix. Does.not.compute.