I spent some time this weekend breaking my account to see how many different ways I can cause the dreaded 19000 error and then fix it. Here is a list of culprits I found and what you can do: Problem: Time Sync - If your computer time does not match the time on the RSI Authentication servers, you will eventually get an error in the console. If you do not have the console open, this will take 2-3 minutes to show up, then give you a 19000 error. Fix: Log out of the RSI Launcher, In Windows go to Settings -> Time -> Synchronize from an Internet Server. Turn this on, push "Sync Now". Log back into the RSI Launcher. Alternate Fix: you can set your time manually, please make sure it remains accurate. Problem: Heuristics Anti-Virus, it seems a recent update to some AV software (I have tested with Bitdefender and Sophos) will occasionally delete log files with "suspect characters" that get generated as part of the logging CIG has turned on. Having the log file deleted while the launcher is trying to write to it also manifests a long time out and a 19000 error. Fix: Whitelist the RSI Launcher and Star Citizen executable. See vendor documentation on how to do this. Hopefully CIG will give us something nicer than a 19000 to refer to in the future. Problem: Firewall Heuristics, a recent update to some AV software (again, tested with Bitdefender and Sophos) is causing it to silently block some programs that behave "strangely" according to their definitions. This one is easier to spot as a 19000 error, because it will happen immediately when you try to log in. Fix: Whitelist the RSI Launcher and Star Citizen executable. See vendor documentation on how to do this. Problem: DNS Resolution. This one was the most interesting to troubleshoot. If you have a dual-stack computer (IPv6 and IPv4) AWS will occasionally respond to the AAAA (IPv6) request for the RSI Authentication server that the launcher sends with an A (IPv4) response for a server in an entirely different region. The time skew between your IPv6 connections to part of the RSI infrastructure and the IPv4 response in a different region will also cause a 19000 timeout, even if the time on your computer is correct. Fix: Open a command prompt, type ipconfig /flushdns, then I have found much more consistent results connecting to a VPN, preferably in the same country. Once you have AWS DNS responses that are all in the same region the error seems to be resolved. If you stuck with a VPN connection to your country, you should be able to play without the VPN as long as the DNS results are consistent. Problem: Vehicle Manager does not save changes. Fix: This also is a problem with time sync. In 3.20 - 3.22 there have been instances where time sync has been close enough that you are able to get into the game, but there is enough drift between your client and the server that the Vehicle Loadout Manager times out when committing changes. Use the Time Sync solution above. A couple other things that have worked: - See the comment from Biffbobaggins below about watching your launcher log file and see if you spot something unusual. - Make sure you don't have extra EAC copies or Roaming EAC blocking your version of Star Citizen. - Lenovo Network Optimizer and "Speedboost" programs that can buffer or modify your network stream can also cause issues. Problem: I tried all of the above and its still broke. Fix: It could be a CIG problem, check https://status.robertsspaceindustries.com or peek in the helpdesk-volunteers channel and see if others are also reporting login errors. Good luck and hopefully see you in the Verse