← all posts site ↗

openrgb autostart needed a scheduled task

the rgb control app never started its server on boot, so every login i had to open it as admin and start it listening on all interfaces by hand. that manual step was the whole annoyance, and the cause turned out to be a windows quirk hiding in plain sight. the auto start checkbox in the app creates a shortcut in the startup folder, and windows never runs startup folder items elevated. so my rgb server started unelevated and the listening socket never came up at all.

the fix is a scheduled task, because task scheduler can launch the app as admin at logon with no uac prompt. one installer does the whole job: it finds the exe, checks the version supports a host flag, kills the existing copy, deletes the broken startup entry, opens inbound tcp on the rgb port in the firewall so another machine on the network can reach it, and creates a scheduled task that runs at logon with highest privileges and the listening flags.

the small trap is that the app's own auto start checkbox just recreates the same broken shortcut, so it has to stay off. if you re-enable it you get two instances and the same failure again. and the exe needs to be recent enough to know the host flag, because older builds only take the port flag and will listen on localhost only no matter what you pass.

once it is a scheduled task it stops showing up in the startup tab of task manager, which is normal and not a failure, and the window still pops up at logon but elevated. that one change killed the recurring manual step for good.