RedM can't connect to Rockstar Games Launcher

What is the issue you’re having?

For about three consecutive days, when I try to install RedM, it get stuck on “Checking for Rockstar Games Update Services”, which becomes “127. Could not locate the Rockstar Games Launcher Process!”.

Additionally, after failing to connect to Rockstar the first time, RedM continued to try to update the Rockstar Launcher files every subsequent time I tried to run the RedM installer.

And I also started getting error messages that would say “Error updating RedM. Unable to open C:\Users[PC name]\AppData\Local\RedM\RedM.app\data\game-storage\launcher/Launcher.exe for writing.” Of note, there’s a slash going the other way at the end.

What have you tried already to fix the issue?

I have tried the following:

  1. reinstalling RedM, Rockstar Games Launcher, RDO, verifying RDR2 files in Steam
  2. clean uninstall and reinstall of the above
  3. resetting my router (unplugged for 7 minutes, replugged)
  4. flushing DNS
  5. turning off antivirus and firewall (and also adding the programs as exceptions)
  6. putting RedM.exe into Program Files\Rockstar Games\Launcher (as suggested by this forum post: Error 127 - #4)
  7. running both as administrator and as a regular user
  8. restarting my PC (it may work the first time, but not subsequent times, and then stopped working entirely)

Error screenshot(s)





Windows version

Windows 11 Home Version 25H2 OS build 26200.6899

System specifications

MSI Codex R2 Gaming Desktop – Intel Core Ultra 7 265 - NVIDIA RTX 5060 8GB – Windows 11 Home - 32GB RAM - 2TB SSD

Antivirus software

Sophos Home

CitizenFX crash zip file (‘Save information’ on a crash)

CfxCrashDump_2025_11_10_04_19_17.zip (136 KB)

Log files

CitizenFX_log_2025-11-10T041734.log (5.61 KB)

Hello, this is a friendly reminder because this is your first time creating a topic (or it has been a while since your last topic) in this category.

Please note that most of the support is provided by the Cfx.re community on a voluntary basis. We ask you to be patient; there is no guarantee we have a solution to your problem(s). To avoid unnecessary/duplicate topics, please browse the forums before creating a topic.

To improve your chances of your issue(s) being solved, please provide as much information as possible about the issue(s) you are having. Also —whenever possible— please use the template given to you when creating a topic.

Thanks for keeping these forums tidy!
:mascot:

Try and roll back your windows update. I had this issue since about mid October. It was weird because I could connect sometimes after trying 3-30 times. Tried every troubleshooting step, including reinstalling windows. Don’t do that. unistall the last update not sure what it was but googled what update was released around halloween. There was one on october 14th. I ended up getting a older release of windows sept 29th installed it with no internet and disable update after install. Been working fine for 3 days now. Hope this helps

1 Like

Update:

Yesterday, a friend helped me with the following:
So, we uninstalled and reinstalled Rockstar
Then we went to Program Files\Rockstar Games\Launcher
We made sure that none of them were running as administrator (because RedM doesn’t like that)
We also went to Launcher.exe Properties, then Security tab, then edit “Permissions for Authenticated Users”, and then clicked on each group and checked “Allow” next to “Full control”.
Then I think we uninstalled RedM and reinstalled a fresh version of RedM (installer downloaded from website), and that worked.
So we were able to have Rockstar and RedM running. However, it would only work the one time. If you closed either of them and tried to reopen them, you would get those same errors again.
So the only workaround we found is restarting my PC and immediately opening Rockstar and then immediately opening RedM.
If you crash or quit either one, it will not open again unless you restart your PC.

Today, we tried uninstalling the 3 most recent Windows updates on my PC and everything started working fine!

Thanks! A friend having the same issue made the same discovery as you and he helped me fix it yesterday.