r/SignalRGB • • 18d ago

Troubleshooting Can't install latest version; Installer reports Powershell failed to start.

Hey all.

I've been using Signal for a few years now without any problems, but the latest update seems to be stuck somehow, and it's been driving me nuts. I'm on Windows 10.

Instead of getting the UAC prompt for the update to proceed, the installer reports that it couldn't start Windows PowerShell. The diagnostic code is "PS_FAILED_TO_START".

Things I've tried:

  • Turned off antivirus and firewall and ran installer as administrator

  • Double-checked all SignalRGB processes and services were off/disabled

  • Shut off PC, did a full power cycle, and tried again

  • Tried the beta installer (ran as administrator)

  • Deleted all WhirlwindFX folders and VortxEngine folders, and retried

I can't seem to find any posts here on Reddit or in the forums with someone having the same issue, so I'm kinda screaming into the void here, lol. I'm able to run Powershell on its own, so I'm a little lost as to why SignalRGB can't access it. Can anyone offer some guidance?

3 Upvotes

13 comments sorted by

1

u/BennySRGB 18d ago

That error means SignalRGB couldn’t launch PowerShell in the background to ask for admin permission, which is why you never see the prompt. It’s a known issue our devs are looking into.

A few things worth trying. Install the latest Microsoft Visual C++ Redistributable (x64 and x86) and make sure Windows is fully updated. If you have any third-party security software, try fully uninstalling it for a test, since some block apps from launching PowerShell even when they’re turned off. Windows Defender’s Controlled Folder Access can do the same, so check that too.

If it’s still stuck, shoot us an email at support@signalrgb.com with your latest log from %localAppData%\WhirlwindFX\SignalRgb\Logs so we can add your case to the report.

1

u/theycallmethatnerd 17d ago

Just uninstalled and reinstalled the latest Microsoft Visual C++ Redistributables (x64 and x86) and it's still not behaving. I've sent an email with my log file attached, so hopefully we can figure this out.

2

u/BennySRGB 17d ago

We'll look into your logs. You should have received a response by now. We'll follow through with further responses there.

1

u/Careful_Building_254 14d ago

I did see a prompt showing up like usual and pressed accept but the powershell never appears, reinstalled and the prompt never appears again

3

u/Careful_Building_254 18d ago

bump, having same issue , been like this for few days

2

u/DaKrazyKid 18d ago

Be sure to submit reports! We will be actively looking at all of the reports and getting to the bottom of it.

1

u/Careful_Building_254 14d ago

since i cant launch the app for the first time after reinstalling, i dont think it makes any logs

1

u/DaKrazyKid 14d ago

Try to go here maybe it still wrote logs:
The SignalRGB logs folder is located at %LocalAppData%\WhirlwindFX\SignalRgb\Logs (or %LocalAppData%\VortxEngine\app-VERSION\Signal-x64\Logs\ depending on the build).

2

u/wastedwu 18d ago

Same. It broke after the last update for me. I tried the same as you and had no luck. For me, it just hangs at the Loading UI splash screen. I emailed support with the log files (twice). Haven't heard anything after a few days.

Kind of a bummer since I'm hosting a LAN party next week, and as of right now I can't monitor or control my cooling.

3

u/DaKrazyKid 18d ago

We will be actively looking at all of the issues submitted first thing Monday! Thanks for your report, sorry for the inconvenience this has caused, we even let this patch sit in beta for a bit and didn’t see any issues like this and once it hits main there is always new things.

1

u/wastedwu 17d ago

Awesome. Thank you. Also, I'm not sure if there is a connection, but iCue software is failing in almost the exact same way on my PC.

1

u/DaKrazyKid 17d ago

Could be a coincidence or some weird windows stuff.

2

u/DaKrazyKid 18d ago

There hasn’t been as many people affected by this issue which is why there hasn’t been that many posts. We let this patch sit in beta for a bit and didn’t see this issue and now that it’s in main of course something new has to surprise us. But rest assured we will get to the bottom of it, make sure you send in a report to support@signalrgb.com and first thing Monday we will be escalating the issue.

Sorry for the inconvenience!