Here is an update, if anyone is watching. First of all, the issue of the timeout error is not resolved. Since I first reported it on August 7th, my new friend in the SWTOR customer support has opened six tickets for it, and EA has opened two. Every time I respond to a ticket and ask for a status update, they open a new ticket. I was feeling excited for my busy support friend who must be killing it in his monthly KPIs for the number of closed tickets, since he's been closing a new ticket every time I say hi, but eventually I started suspecting that he is AI. I had a couple of phone calls with the support over the phone and was offered compensation for the few months I paid for my subscription while not being able to launch the game. Spoiler: I haven't received any compensation. Feeling like maybe some folks in EA customer experience leadership would want to hear about this user case, I looked them up on LinkedIn. I found that dozens of people in customer experience roles, from frontline to VPs, have been let go this year. That's where we are, folks, that's what's up. Don't go break your game if you are not ready to fix it on your own. I am now playing via Steam, but in the light of macroeconomic events and my long-term strategic vision I made a tough decision to reduce my loyalty to the BioWare/EA brands accordingly.

Fingers crossed, so far so good, Steam version seems to be stable for me now. I'd still like to get to the bottom of the direct launcher error.

My processor is Intel i5-4440, but otherwise there are a lot of similarities indeed.

That is correct - the build is 19041.vb_release.191206-1406. Is it good or bad? I use Bitdefender. I came across discussions of whether Bitdefender blocks SWTOR, but other users with the same errors reported that uninstalling Bitdefender did not solve the issue. I am hesitant to uninstall it, but I tried disabling it, and saw no difference. Steam launcher was giving me a lot of issues for the first week I had it. Every second or third launch, there were issues: it could not connect to servers, lagged (major time out) in ops (with the graphics on minimal settings, player nametags off, and system priority real time), and crashed often. However, after I did a network reset and hardware maintenance, anything I could think of short of spraying the machine with holy water, since yesterday, Steam launcher has been stable. It is early to be sure, but fingers crossed I will be able to play on Steam. I ventured in DF/DP story 16 player yesterday and saw no lag. Also, I ran dxdiag today. The information that the support person sent me did not check out. There is no RADAR error for SWTOR. For SWTOR, I consistently see this, every time I attempt to launch the direct launcher, before and after reinstalling it: Fault bucket 2015131604088351949, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: launcher.exe_Star Wars - The Old Republic Launcher P2: 6.1.2.80 P3: 63d3414e P4: libcef.dll P5: 103.0.11.0 P6: 62bf8a9a P7: 80000003 P8: 06691afe P9: P10:

@OwenBrooks According to DxDiag, SWTOR causes a RADAR_PRE_LEAK_64 error. I saw another user mention it on the forums ten days ago: https://forums.swtor.com/topic/930750-app-crashes-after-launching/#comment-9773808 Since it was mentioned in the post, I went through the troubleshooting steps in your guide https://answers.ea.com/t5/General-Discussion-Technical/Guide-Game-failing-to-launch-on-Clicking-Play/m-p/4809830/highlight/true#M70795 still no luck.

I found one instance of this file in a system folder (not system32 or syswow64 though) and deleted it. It dated back to 2021. I still had the timeout error after that. Uninstalled and reinstalled the launcher, still having the error. I also found this file in the folders of a couple of other apps/games (OBS, Fallout 76). That shouldn't be an issue though, right? I am not using VPN. Regarding Steam, however, it might be my saving grace. I installed the Steam launcher recently. It was not working well for me (lag, frequent crashes, and unable to connect to servers every third launch or so). But today I did general maintenance on my computer (cleaned the fans, checked the battery, etc.) out of sheer despair, tried the Steam launcher again, and it seemed to be stable this time. Time will show if it will work out.

Thank you for suggesting. I followed the steps and reset the network settings, but got the timeout error again, unfortunately.

September 16 update: If anyone is watching, first of all, the issue of the timeout error is not resolved. Since I first reported it on August 7th, my new friend in the SWTOR customer support has opened six tickets for it, and EA has opened two. Every time I respond to a ticket and ask for a status update, they open a new ticket. I was feeling excited for my busy support friend who must be killing it in his monthly KPIs for the number of closed tickets, since he's been closing a new ticket every time I say hi, but eventually I started suspecting that he is AI. I had a couple of phone calls with the support over the phone and was offered compensation for the few months I paid for my subscription while not being able to launch the game. Spoiler: I haven't received any compensation. Feeling like maybe some folks in EA customer experience leadership would want to hear about this user case, I looked them up on LinkedIn. I found that dozens of people in customer experience roles, from frontline to VPs, have been let go this year. That's where we are, folks, that's what's up. Don't go break your game if you are not ready to fix it on your own. I am now playing via Steam, but in the light of macroeconomic events and my long-term strategic vision I made a tough decision to reduce my loyalty to the BioWare/EA brands accordingly. === I am one of the players affected by the launcher timeout bug. I haven't been able to launch the direct launcher since June. On August 7th I opened a support ticket for this issue. The person who replies to me creates a new ticket every time he emails me. There are five tickets open now. Every other time he replies, he sends me the same information: reinstall the launcher, work through the troubleshooting guide, ignoring all the previous communication. On August 11th, he asked me to send the team my diagnostic files (DxDiag, etc.) Having no further communication after that, I called EA on August 18th and was told that the team has my files and they are asking for my patience. Today (August 23rd), I got an email from the same person who has been communicating with me, saying that he doesn't have my diagnostic files. This is truly a shameful situation. I've been a subscriber since SWTOR launched. The quality of technical support used to be top notch. Now, I don't know what to do next. Just getting kicked around in the emails, not a sight of a solution on the horizon. Any advice?

Add me to the list. Unable to launch SWTOR on my desktop since May. Host_WindowLoadTimeout error. I have finally installed it via Steam, but the lag and disconnects make it unplayable. I am a subscriber and not happy that I have no access for three months and counting.

The bug is still there as of January 2021.

As of March 14, confirmed that it is still impossible to kill three sentinels in one go, but the strategy of stomping them one by one works. You'll die a couple times. Sentinels do respawn, but slowly: it takes a couple minutes before they reemerge. So, if you reach the timer of 1 minute plus for your revival, better release to the med center. This mission has a launch button that teleports you back to sentinels, so releasing to the med center is not a problem. They won't respawn while you are qt'ing back. Be careful that if you revive with minimal health the sentinels might attack right away (and kill you, since you just about need your full hp at level 75 to kill one sentinel). So, as soon as you revive, start spamming the button to activate rapid restoration (the last key on the quickbar).

When you get to the character screen, click alt+enter and wait for the screen to refresh, then you are good to go. It works for me. It works both ways: when the game is full-screen and alt+enter switches it into a window mode, and the other way around. I am waiting for an official fix, but for now I am able to log in with this trick.

Kudos, the solution works. Pressing alt+enter on the character screen to switch to the full-screen mode helps escape the crash bug. Thank you for sharing.

We seem to have an epidemics of people quitting flashpoint groups upon loading. Not even a few minutes into the fp, not even after wiping on the first boss, which could have possibly explained the decision. People just load in, look around and quit. Other teammates often end up stuck for extended time waiting for a replacement. I am all in for people to draw a judgment if they decide the group is not geared according to their ideas and/or the composition is not right. In this regard, I suggest that when a group match window pops up, it would be nice to be able to see the gear/achievements (or whatever else it is that people make their judgments on) at that point, before accepting the group. Basically, decide here and now, and once you accept it, stick to it. But more to the point, I want to gauge people's opinion if we should have heavier penalties for abandoning groups in the first minutes. It can be simply "eye for eye" - you wasted others' time, so you are restricted from certain activities, such as joining another group, for 15-20 minutes or more (a longer penalty than what we currently have in the game). Personally though, I think the penalty should be more material. A coin fine, an experience fine, or some such. We have command experience now. What if we see it as a "leadership skill" experience? Learn to communicate with others, learn to inspire by example, learn not to be that "A" with a hole in the team. Sorry if I digress to wax philosophical here, but the practical idea is to penalize people with a command experience fine. Maybe not automatically. Maybe other teammates should be asked to vote to confirm that the quitter should be penalized (in case s/he had a good reason to leave). Maybe the penalties should only be applied if two or more people in the group specifically ask for it (to avoid personal vendetta). Or maybe it should be cumulative: quit once, no questions asked. Quit five time in one week, get banned from the groupfinder for a week. How about that? Just my thoughts. I've been in the game for a long time and quitting fps has never been such a common issue before. If you think I'm just getting old and cranky, cut me a slack and suggest what other things can work to ease the impact quitting has on other players. All opinions welcome.

And why would you claim differently, based on what? Where is "no doubt" coming from? It is equally plausible from the roleplaying perspective or common sense that your companions are on your ship having their own "lives", and they exist and function while you are logged off. Similarly to the way crafting is accomplished by companions while you can be running an op, fp or pvp, I don't see absolutely any sensible explanation why they cannot be finishing the task while you are not doing anything, logged off. The nature of mmorpg is, events happen in the game world while you are logged off. The world doesn't stop, and the companions don't hang in the limbo while you are away - except for this one instance which, as I am saying, should be brought in accordance with how crafting works otherwise.