# Corsair GALLEON 100 SD - Support

**URL:** <https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883>\
**Category:** Support\
**Tags:** keyboard\
**Created:** [July 10, 2026, 12:50pm UTC](https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883 "2026-07-10T12:50:35Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![icon](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/icon/32/2012_2.png) [@icon](https://forum.signalrgb.com/u/icon)\
**Post date:** [July 10, 2026, 12:50pm UTC](https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883/1 "2026-07-10T12:50:35Z")

</div>

Hello

Just looking for some help/advice on this keyboard the device is listed as a newly supported device on the website and it does show in the device panel however when I try pulse or force a colour it does not respond. ( I do not have ICUE or any other RGP softwere installed on my PC )

Has anyone had any luck getting this keyboard to function correctly with SignalRGB or should I just assume it’s still a work in progress to get it working?

Thanks

---

<div class="post-metadata">

**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\
**Post date:** [July 10, 2026, 2:55pm UTC](https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883/2 "2026-07-10T14:55:26Z")

</div>

I’d try using USB ports, but it could be the keeb has different device IDs than the plugin expects. The [troubleshooting steps are here](https://docs.signalrgb.com/troubleshooting/common-issues/device-not-detected/), if nothing else works you can I’d report the bug using the bug icon in the app (upper-right corner) or through [this link](https://go.signalrgb.com/app/app/report-bug) so that the team can follow up with the devs.

We can get those added quickly once we know the cause and device info. 🙂

---

<div class="post-metadata">

**Author:** ![icon](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/icon/32/2012_2.png) [@icon](https://forum.signalrgb.com/u/icon)\
**Post date:** [July 15, 2026, 8:31am UTC](https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883/3 "2026-07-15T08:31:55Z")

</div>

Hi SignalBadger,

Appreciate the response, I tried these steps with no luck ill run through the bug process later tonight see how we go 🙂

---

<div class="post-metadata">

**Author:** ![Dtek](https://avatars.discourse-cdn.com/v4/letter/d/9e8a1a/32.png) [@Dtek](https://forum.signalrgb.com/u/Dtek)\
**Post date:** [July 31, 2026, 2:52pm UTC](https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883/4 "2026-07-31T14:52:26Z")

</div>

Same issue here. SignalRGB does control the stream deck knob colors but not the actual keyboard key colors:

 ![CorsairGalleon](https://us1.discourse-cdn.com/flex015/uploads/signalrgb/original/2X/d/d1cf9df86fe5da980a107eb8c8ee22886829c556.png)

---

<div class="post-metadata">

**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\
**Post date:** [August 3, 2026, 9:24pm UTC](https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883/5 "2026-08-03T21:24:28Z")

</div>

Looks like this keeb has a different device ID based on the image. I’d report the bug using the bug icon in the app (upper-right corner) or through [this link](https://go.signalrgb.com/app/app/report-bug) so that the support team can follow up with our devs to get this added. 🙂

---

<div class="post-metadata">

**Author:** ![Malnen](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@Malnen](https://forum.signalrgb.com/u/Malnen)\
**Post date:** [September 21, 2026, 1:02pm UTC](https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883/6 "2026-09-21T13:02:42Z")

</div>

It worked for me on keyboard firmware version 1.x. After updating to version 2.x, it stopped working, and I see the same error in the logs

---

<div class="post-metadata">

**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\
**Post date:** [September 21, 2026, 2:03pm UTC](https://forum.signalrgb.com/t/corsair-galleon-100-sd-support/9883/7 "2026-09-21T14:03:57Z")

</div>

Sometimes a device firmware update can cause issues, definitely good to submit a bug report for the team to development investigate and resolve.
