# Latest Signal RGB Version Causing Turing Screen to Disconnect

**URL:** <https://forum.signalrgb.com/t/latest-signal-rgb-version-causing-turing-screen-to-disconnect/10147>\
**Category:** Support\
**Tags:** issues\
**Created:** [September 21, 2026, 1:02pm UTC](https://forum.signalrgb.com/t/latest-signal-rgb-version-causing-turing-screen-to-disconnect/10147 "2026-09-21T13:02:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![NapalmBobby](https://avatars.discourse-cdn.com/v4/letter/n/b77776/32.png) [@NapalmBobby](https://forum.signalrgb.com/u/NapalmBobby)\
**Post date:** [September 21, 2026, 1:02pm UTC](https://forum.signalrgb.com/t/latest-signal-rgb-version-causing-turing-screen-to-disconnect/10147/1 "2026-09-21T13:02:29Z")

</div>

So the latest version of Signal RGB seems to want to take over my computer and it caused several conflicts. First of all there was a severe conflict with Fan Control which I eventually solved by disabling fans in the Signal app but one thing I haven’t been able to fix is the conflict with TURZX / Turing Screen which disconnects randomly when Signal RGB is running. I’ve made sure the Turing Screen is disables in Signal RGB but the conflict doesn’t resolve.

---

<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:00pm UTC](https://forum.signalrgb.com/t/latest-signal-rgb-version-causing-turing-screen-to-disconnect/10147/2 "2026-09-21T14:00:11Z")

</div>

While disabling a device in SRGB does stop it from controlling the device, the underlying services are still running. If those are conflicting with the TURZX software, it could cause it to close. I would reach out to their support to see what information they have about their software closing.

That’s likely similar to what was causing issues in that other software while Fan Control and System Monitoring were enabled in the SRGB app.

---

<div class="post-metadata">

**Author:** ![NapalmBobby](https://avatars.discourse-cdn.com/v4/letter/n/b77776/32.png) [@NapalmBobby](https://forum.signalrgb.com/u/NapalmBobby)\
**Post date:** [September 21, 2026, 2:21pm UTC](https://forum.signalrgb.com/t/latest-signal-rgb-version-causing-turing-screen-to-disconnect/10147/3 "2026-09-21T14:21:30Z")

</div>

I’ve uninstalled Signal RGB and gone to Open RGB for now which has solved the conflicts. The current behaviour of Signal RGB is similar to malware IMO so I have removed it. Signal RBG should ask for permission to take over control of devices rather than do it silently on install and where a device has been disabled in Signal RGB because the preference is to use other software it should disconnect cleanly without locking COM ports etc.
