Sims 4 error: Failed to launch game
Sims 4 has failed to launch for some weeks now. I've uninstalled and redownloaded multiple times, repaired multiple times, as well as moved folders around and nothing seems to have worked. I've atta...
Forum Discussion
Hey everyone. I'm here to report an issue that I've been having for the past WEEK, presumably following an update.
Every single time I attempt to launch the Sims 4, I am unable to reach the main menu before the game crashes. I see the blue Sims 4 logo screen followed by the spinning plumbob screen, only for it to crash after a few rotations and give me the following error in the EA app:
I have tried everything I possibly can over the past week, from uninstalling and reinstalling the EA app / Steam / Sims 4, verifying game files through Steam, forcing the EA app to update (the updater .exe file claims that the app is up to date before closing itself), hard resetting my computer between each action I take (sometimes multiple times in a row), clearing the cache, running Steam and the EA app as administrators, running in compatibility mode, installing new graphics drivers, running without my mods/CC folder, running multiple diagnostics, taking my user file out of the Sims 4 folder, and probably more that I can't recall right now. I also updated my computer twice.
I've scoured the forums and replied to posts reporting similar issues in hopes of finding something that works but have found nothing. I've also reported the issue through the EA app and tried talking to their damned AI assistant thing but still nothing. I have encountered this issue a few times in the past, usually after updates, but usually hard resetting or something of the sort fixes it pretty quickly. Some of my friends who also play the Sims 4 aren't having any problems, even those with very heavily modified games.
I also had some issues with my UI looking weird a few weeks earlier, and I've pruned my mods folder for anything that may be causing it, but everything was working as it should. That's another issue that I've experienced in the past that fixed itself after a little while, and the UI still functions so I'm not too bothered by it. Just putting it out there.
Here's the results of a dxdiag that I ran just before writing this:
I'm starting to get more annoyed than worried now. Please let me know if there's a fix for this!
