ST100 Headphone Stand F/W Update

Looks like the ST100 headphone stand just received a firmware update, ver. 0.04.106, and it looks like the issue it had with RGB turning off when locking Windows or closing iCUE is gone, defaults to rainbow like it used to. Somewhere along the way with one of the updates, it stopped defaulting to rainbow in "hardware mode" and would just turn off. Sometimes it would randomly light back up for a few seconds then go off again, sometimes repeating several times before finally shutting off completely. Now it seems to stay on rainbow.

 

Any release notes for the f/w update? I was also having USB disconnect issues where the ST100 would drop out entire USB hubs on my motherboard causing devices to drop out and come back. Since plugging it into an external powered hub, those issues have gone away. Curious if it is just the lighting issue that was addressed or were the USB disconnect issues also addressed?

Well, figured I'd go ahead and plug the ST100 back into the back of the mobo instead of the hub to see if it's still causing resets. I prefer to have the HS70 adapter plugged into the headphone stand, as I don't get drop outs. With the HS70 adapter plugged into the back of the computer, I get drop outs if I so much as turn my head wrong. Unfortunately, I also get a looped static noise with the adapter plugged into the headphone stand when it's plugged into the hub, which is why it's plugged in the back to a mobo port.

 

Well, it hasn't even been 5 minutes, and all my USB devices just reset twice, as I type this post. So no, USB disconnects haven't been addressed. Back to the hub it goes. *SIGH*

UPDATE 2: So the ST100 is plugged back into the powered hub, no more USB resets/disconnects. I then plugged the HS70 adapter back into the ST100 to see if the looped static was still there (probably noise from the hub's power adapter) - yup still getting the noise, though the headset doesn't drop out. Plugged the HS70 adapter into the same port on the back, static noise gone but the drop outs returned. Plugged the HS70 adapter into a USB Type C to Type A adapter and then plugged that into my mobo's type C port. Drop outs disappeared, no looped static, everything chugging along. Hopefully it's fixed now.

For you I try to do the upgrade and it gives me an error, it throws the device away and in order to find it again I have to remove the usb and put it back

what to do??

For you I try to do the upgrade and it gives me an error, it throws the device away and in order to find it again I have to remove the usb and put it back

what to do??

 

Me too! I tried every USB port on my PC, and nothing works. Works fine for every other device in iCUE, except this.

For you I try to do the upgrade and it gives me an error, it throws the device away and in order to find it again I have to remove the usb and put it back

what to do??

 

Me too! I tried every USB port on my PC, and nothing works. Works fine for every other device in iCUE, except this.

 

Not sure what's going on there. Mine updated first try, no issues. Make sure you have a good USB cable. Also try to plug into a native USB type A port on the back of your motherboard. I did the update on mine with it still plugged into the powered hub, though, and the hub plugged into a USB 3.0 port on the back of my motherboard.

Not sure what's going on there. Mine updated first try, no issues. Make sure you have a good USB cable. Also try to plug into a native USB type A port on the back of your motherboard. I did the update on mine with it still plugged into the powered hub, though, and the hub plugged into a USB 3.0 port on the back of my motherboard.

 

I'm using the USB cord that came with the ST100 (which is the only one I have b/c it has the funky end on it) and I've tried all USB ports (2.0, 3.0, 3.1) that are on my MB, and Front IO.

Same problem here, tried every port.

Same problem here ST100 update failed

Can all of you confirm which version of iCUE and Windows you are on? Just to confirm, the primary issue you all are having is that ST100 is not showing in iCUE after performing the firmware update?

 

Windows 18363.778

iCue 3.27.70

iCue 3.28.70

I'm also on iCue 3.28.70 and I'm getting the same update fireware error

Can all of you confirm which version of iCUE and Windows you are on? Just to confirm, the primary issue you all are having is that ST100 is not showing in iCUE after performing the firmware update?

 

iCUE 3.28.70

 

Stand newly placed on my table with current version 0.02.91

Does not want to update to newest version/crashed and stays disconnected from iCUE until I re enter its USB Cable to my PC. Hower the newest patch seems to be not applied so it is still 0.02.91 and crashes again when trying to update via iCUE. :sigh!:

 

Windows 10 with current version 1909

Same problem... is there any solution?

Same problem here as well, it's an odd one.

 

iCUE 3.28.70

Windows 10 Home 1909 64 Bit

Or is there another way around this to update the stand via workaround to its current version?

Same here.

iCUE 3.28.70 (Spanish from Spain language) with:

1) K55 RGB v30.05

2) ST100 RGB v0.02.91 -> v0.4.106 Fail

Windows 10 Pro 1909 64 bits (10.0.18363)

 

In iCUE Setup, Export info and register appears under Chipset:

Corsair composite virtual input device

Auriculares (CORSAIR ST100 Headset Output)

CORSAIR ST100 Headset Output

Micrófono (CORSAIR ST100 Headset Output)

Corsair Bus

And under Corsair Devices:

Corsair Corsair Gaming K55 RGB Keyboard

 

All Corsair device features works perfectly (USB hub of ST100, sound, ...)

 

Excerpt from CUELogs after trying the update:

2020-05-17T10:08:40 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image"

2020-05-17T10:08:40 I cue.firmware.index: "ST100RGB" firmware update, expected version: 0.4.106 update available, on device: bootloader: 0.1 firmware: 0.2.91

2020-05-17T10:08:41 I cue.lightings.direct_player: Stopped lighting worker in 0x1f5c

2020-05-17T10:08:41 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_0a34#7&1d49b690&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2020-05-17T10:08:41 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0a34#7&1d49b690&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.

2020-05-17T10:08:41 I cue.hid_device_detector: Mark all tasks as finished.

2020-05-17T10:08:41 I cue.devices.audio.comp: Audio control device was cleared

2020-05-17T10:08:41 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_0a32&mi_03#8&28fe0412&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2020-05-17T10:08:41 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0a32&mi_03#8&28fe0412&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.

2020-05-17T10:08:41 I cue.hid_device_detector: Mark all tasks as finished.

2020-05-17T10:08:41 C cue.server.device: Unknown device type: 0

2020-05-17T10:08:41 C cue.server.device: Unknown device type: 10

2020-05-17T10:08:41 C cue.server.device: Unknown device type: 11

2020-05-17T10:08:41 C cue.server.device: Unknown device type: 12

2020-05-17T10:08:41 C cue.server.device: Unknown device type: 13

2020-05-17T10:08:41 I cue.firmware.update.controller: "ST100RGB" FW update has been started. From "Primary FW: 0.02.91; Secondary FW: 0.02.91; Bootloader FW: 0.01" to "Secondary: Application: 0.4.106"

2020-05-17T10:08:42 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpen: Failed to open \\?\hid#vid_1b1c&pid_0a34#7&1d49b690&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}: 32

2020-05-17T10:08:42 I cue.firmware.update.process.proto_n: "0" exit code: 4 exit status: 0 Reported: false false

2020-05-17T10:08:42 I cue.firmware.update.process.proto_n: All FW update tools finished: false

2020-05-17T10:08:42 I cue.firmware.update.controller: "ST100RGB" FW update has been failed. From "Primary FW: 0.02.91; Secondary FW: 0.02.91; Bootloader FW: 0.01" to "Secondary: Application: 0.4.106"

2020-05-17T10:08:42 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "ST100 RGB"

2020-05-17T10:08:42 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "ST100 RGB"

2020-05-17T10:08:42 W cue.firmware.update: Failure during abort.

Edited May 17, 2020 by CptOx

Win10 64bit

ICue 3.28.73

Dongle 1.5.54

VIRTUOSO SE, K57, Dark Core Pro (Multi Point Enabled with Audio Dongle)

ST100 Direct to USB on Motherboard

 

When I try to Update the ST100 Firmware it Fails and Removes the ST100 from the Software (as if it's Unplugged).. It Only Shows Back up in ICue if you Unplug and Plug back in or Reboot...

 

It's the ONLY Issue I've had So far...

ST100 fails firmware update and disconnects. Only solution is to unplug USB and reconnect.

 

There is an issue with the stand connecting and disconnecting continuously.

 

 

iCue - 3.28.70

Windows - 18363.836

I'm getting the same issue as everyone else where when trying to update the ST100 firmware it disconnects and fails.

 

iCue Version: 3.28.75

Windows Edition: Windows 10 Home

Version: 1909

OS Build 18363.836

Restart windows 10 in safe mode, open up icue and install the firmware. It took like 20 minutes on mine to finish but it worked.

 

I remembered that last time my scimitar mouse would not update its firmware, support had me do it in safe mode.

Restart windows 10 in safe mode, open up icue and install the firmware. It took like 20 minutes on mine to finish but it worked.

 

I remembered that last time my scimitar mouse would not update its firmware, support had me do it in safe mode.

 

I will try this, thanks for sharing although we shouldn't have to do this, there is some issue with the iCue software, it needs fixing in this area.

Can all of you confirm which version of iCUE and Windows you are on? Just to confirm, the primary issue you all are having is that ST100 is not showing in iCUE after performing the firmware update?

 

Windows 10 Pro

iCUE V3.28.75.

 

Firmware update fails and after the firmware fail the ST100 is no longer visible in iCUE. USB cable has to be unplugged and then plugged back in again for iCUE to recognise the ST100 again

Restart windows 10 in safe mode, open up icue and install the firmware. It took like 20 minutes on mine to finish but it worked.

 

I remembered that last time my scimitar mouse would not update its firmware, support had me do it in safe mode.

 

Thank you very much! Restart Windows 10 in safe mode with networking and update ST100 firmware, works for me in seconds.