Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
These are my current first steps when GTA5 is having launching issues.
It can solve many common issues.
It might help you.
Use WINDOWS (control panel) and uninstall both the R* Launcher and Social Club.
Manually delete the folders for both, here ...
Documents>Rock Star Games>
Go to STEAM Library and verify the local Game files (almost as good as re-install)
When you start the Game it should download / prompt you through an up to date install.
(updating from the Cloud)
*Exit Game and set both the Launcher and Social Club to run as ADMIN if the above steps have not worked.
**This is all taking for granted it is a normal un-modified install.
**You might try skipping right to setting those 2 apps to ADMIN and try before the uninstalls.
RT Click on a Game
Properties
Verify local game files
I post this often, because I have to do it about every other weekly update it seems.
Since you have no problem contacting R* you can take a chance on them VIA a live chat. The last time I had to do it, it took about 45 minutes (during working hours) for someone to jump on. But that person did know what they where doing, and hooked me up.
https://support.rockstargames.com/categories/200013306?step=ec1acf27
(link at the bottom)
P.S.
in looking at some older post where I've posted the initial procedure, on non-modified installs not using VPN's is seems a few where able to get back into the game after updating the driver for their graphics card.
Just a thought ...
GL
Installing it on any drive other than C: 'could' cause issues. (never had issue via my testing though - as long as the launcher was installed 'INTO' a folder). Changing the drive letter/path could also cause issues.
You can go look in the registry/regedit:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rockstar Service
to see where it says it is installed 'IF' it is even there. If the 'rockstar service' folder on the left IS there - you could also attempt to delete it (vs editing entries on right to be correct).
If it isn't there - you could 'try' to add it - the info in the code box below goes into a .txt, that you rename to .reg, and then run to add it to the registry ---- the R* launcher installation SHOULD be the one already handling this. This also may/may not work if it needs anything else. Could check services.msc afterwards/or pc restart, and check and see if you can force start the service there (on top of making sure it isn't disabled in msconfig/etc).
Then you have windows defender/exploit protection or mandatory ASLR on causing issues with install. You can also try adding steam/steamapps/common/gtav to whitelist/exclusions in windows defender, as well as c/program files/rockstar games (if your launcher is installed there). You have not installing the R* launcher as admin so it has permissions to do this, you have vcredists causing problems with how the launcher functions (you could grab an AIO for all vcredists and try to clean/uninstall/reinstall them - and/or also install vcredist 2022 on top and see if that fixes anything). Windows updates/missing updates etc - have also cause oddball problems with gtav/launcher/social club in the past too. Of course, after all that - you'll likely need to uninstall/remove/reinstall launcher/etc again.
If you dig hard enough - you'll also find some people that had to forcibly adjust the login/pw used to start the service to get that going as well - but again, til you can actually get the service to appear... kind of useless (but may be important once you get that portion corrected).
Since you can access the website that also 'slightly' rules out the other connectivity issues related to this - but I wouldn't completely rule that out yet until you actually get the service to appear/attempt to run, etc when you fire up the launcher. Then you can see if you get any other errors/codes related to access/permissions, firewall, etc.
And /goodluck - leaving on vacation soon so likely zero responses from me.