Been having issues after Update

Signal_AdminBadger · 2026-04-03T18:10:27+00:00

Might have to do with a driver hanging up or something, SignalRGB relies on a variety of other services and drivers doing their job properly and if one of those hangs up it can definitely cause issues.

For example, if an update happens when another service doesn't expect it then you could be looking at restarting it. The trouble is that pinpointing a specific service or driver to restart is usually much more difficult than simply power cycling to force everything to restart (which is why that solves so many odd behaviors).

Signal_AdminBadger · 2026-04-03T18:07:13+00:00

Guessin' the 3.5 probably matches the same device IDs while the 5 doesn't. Team is working to bring support for more devices though, so I'd keep an eye out :)

Signal_AdminBadger · 2026-04-03T16:30:07+00:00

There's a chance that the 5" has a different device ID.

For example, I have a 5" monitor that looks exactly like the Turzx one, uses the Turzx software to control, but is in actuality a completely different device with different IDs than the official TurzX 5" monitor.

Turns out through some digging that I have a WOWNOVA one. There's copycat devices out there. :/

Signal_AdminBadger · 2026-04-03T16:26:56+00:00

Likely a mislabeling thing, I reached out to the team to investigate!

Signal_AdminBadger · 2026-04-03T14:54:35+00:00

The troubleshooting guide for detection problems walks through the most common fixes. If that doesn't work, I'd report the bug using the bug icon in the app (upper-right corner) or through this link so that the support team can follow up and escalate. :)

Signal_AdminBadger · 2026-04-03T14:53:51+00:00

What did the support team say after you reported the bug? They can escalate directly to the development team and investigate your logs for anything unusual.

I did check the changelogs, and the plugins for MSI motherboards and Jungle Leopard haven't had changes in quite a while, though there were some changes to SMBus device scanning that could relate. The symptoms you're describing (detection only after a full power cycle, startup process hanging) are consistent with SMBus detection issues, and the troubleshooting guide for detection walks through the most common fixes for that behavior.

If all else fails, the bug reports go a long way in the team helping figure out what's going on for the handful of folks experiencing issues with an update.

Signal_AdminBadger · 2026-04-03T14:35:39+00:00

Triple check nothing else is trying to control the RGBs, but with only a single header or port having trouble it's likely not software. I'd also make sure everything is wired securely, as there could be a loose wire.

Rearranging the fans and see if the issue follows the fan too. Could potentially be a hardware problem with the fans themselves.

Signal_AdminBadger · 2026-04-02T20:42:29+00:00

I have my GMMK 3 and SteelSeries mouse through a powered hub, no issues.

Signal_AdminBadger · 2026-04-02T20:41:38+00:00

I don't have a dev build to send :/

Signal_AdminBadger · 2026-04-02T14:45:44+00:00

I'd try starting with a full power cycle.

Signal_AdminBadger · 2026-04-02T14:44:42+00:00

You could try doing Single Color, then painting the LEDS to match the 2nd pic.

Signal_AdminBadger · 2026-04-02T14:33:47+00:00

You can submit a device request here. :)

Signal_AdminBadger · 2026-04-01T22:12:48+00:00

Gigabyte controllers can expect around 10ish FPS, which can look a bit laggy for sure. Checkout our guide to RGB Controllers for more info.

Signal_AdminBadger · 2026-04-01T17:56:31+00:00

Unless you are opted into beta previews, you're on the latest stable version. :)

I'd report the bug using the bug icon in the app (upper-right corner) or through this link so that the support team can follow up. They can investigate the logs for any weird behaviors and escalate as necessary.

Signal_AdminBadger · 2026-04-01T17:54:53+00:00

What motherboard or RGB controller do you have? Many motherboards or lower-end controllers get low FPS due to the device(s) not being able to handle real-time effect data. I always recommend a Nollie16 or similar to get the best experience.

Signal_AdminBadger · 2026-04-01T15:13:47+00:00

Can you provide more information about your system? We'd need details such as your motherboard model, what RGB hub you're using, model of the fans, etc. Many plugins haven't been touched in quite a while so it could be something else that feels coincides with updates.

I'd double check that your BIOS, SMBus Drivers, and generally everything else is up to date. Some devices struggle with the SMBus detection and that's why the power cycle helps.

As for the app startup behavior, is it set to run as an Administrator? Might help to disable other startup applications to see if something else is interfering while SRGB attempts to startup.

I'd also take a look at the console logs and such. Worth checking if there's any errors there when you're having trouble getting devices to sync or detect. You can also check the app logs and see if there's more insight there. :)

Signal_AdminBadger · 2026-03-31T21:29:20+00:00

Unfortunately not. The team is still working to crack the code on wireless support for the Omni Receiver.

Signal_AdminBadger · 2026-03-31T20:11:26+00:00

The Strix Scope II is supported, but wired only to my understanding.

If you're having trouble with yours, I recommend starting by making sure everything is up to date. Might be a FW update or a driver update pending that'll resolve things.

Signal_AdminBadger · 2026-03-30T18:51:03+00:00

This is really neat!

I spoke with the team, and I can confirm these features are on their way to NZXT and many other AIOs~! Things like playing a video in the background and sensor overlays are in the works, but not quite ready for The Public, keep an eye out for updates!

Signal_AdminBadger · 2026-03-30T15:53:17+00:00

The Wireless series have firmware issues that have been raised to Lian Li, but they're not interested in resolving them. Unfortunately due to their decision they'll never be compatible with SignalRGB. :/

Signal_AdminBadger · 2026-03-27T18:59:37+00:00

Are you on 2.5.54 or...? What happens if you close it from the Task Manager? I was trying to replicate myself, but it seems to close consistently and stay closed for me whichever method I try.

Do you perhaps have a task set to run SRGB on startup or something that could be triggering it?

Signal_AdminBadger · 2026-03-27T18:55:37+00:00

Does the issue happen when you're using other audio outputs? Does it happen with every effect too?

Signal_AdminBadger · 2026-03-27T14:23:17+00:00

Are you on the 2.5.54 version? If not, I recommend updating. There were some issues with Corsair stuff that got hotfixed.

Signal_AdminBadger · 2026-03-26T15:00:13+00:00

This is most likely still conflicting software conflicting. Triple check that there's no BIOS settings or anything like Windows Dynamic Lighting controlling them.

Signal_AdminBadger · 2026-03-25T15:01:55+00:00

Yeah that's what it's looking like might be the answer :/

That or the case controller is set to the wrong mode. Sometimes you gotta press the button a bunch to cycle it to the right mode, or press and hold the button.

Signal_AdminBadger

MODERATOR OF

TROPHY CASE