[CURRENT ISSUE] Sims 4 Failed to Launch Game
Overview Failed to launch game An error on our end caused the launch to fail. Try again a little later. Please ONLY use this thread if your game actually fails to launch. If the game does open, no matter how briefly, and then crashes, and only then do you see the "failed to launch game" error, please create your own thread. Provide a dxdiag and a lastexception with your post. How to do so is covered in this reply: [START HERE] Crashing/Back to Map/Endless loading (Patch 117.221) | EA Forums - 12512130 This is currently something of a catch-all error, caused by a variety of issues. And the game may in fact start but crash immediately after launch. Trying to relaunch the game immediately after it's crashed can cause the error as well. While troubleshooting this issue, each time the game fails to load, make sure the EA App is closed (exit out of it; don't just X out the window), and open the Task Manager and end the EABackgroundServices entry in the background processes list. Alternately, restart your computer. Workarounds jump to: Remove mods jump to: Clean user folder jump to: Set exceptions in antivirus jump to: Change OneDrive settings jump to: Update graphics driver jump to: Perform a clean boot jump to: Uncommon causes jump to: New admin Windows account These workarounds are listed in order of how frequently they cause this issue. So to avoid wasting time on steps that are unlikely to help you, it would be best to try the suggestions in order. Before proceeding, please repair the game. If you've installed through the EA App, open the App library and click Sims 4 > Manage > Repair. For a Steam install, open your Steam library, right-click the Sims 4 tile, and select Properties > Installed files > Verify integrity of the game files. Remove mods The most common cause of this error is a broken mod, and the most efficient way to find out if that's your issue is to remove the entire Mods folder, and delete localthumbcache.package, in the same Sims 4 folder. This doesn't mean playing without mods—if it helps, you can test your mods and cc until you find the broken file or files, then restore the rest. If it doesn't help, move on to the next steps. While testing, use the new Mods folder the game created when you launched it without mods. Transfer individual files or subfolders rather than the entire Mods folder, and use the fresh Resource.cfg file rather than your old one as well. ↑ Clean user folder If removing only the Mods folder doesn't help, remove or rename (these have the same effect) the entire Sims 4 folder in Documents > Electronic Arts. If it copies instead of moving, or you get an error when trying to move it, stop here and see the OneDrive section below. Otherwise, when you launch the game, if it launches, a clean folder will spawn with no content. (Your saves and other content will be intact in the folder you've moved but temporarily unread by the game.) Don't add anything to the new folder yet; just see whether you can get far enough to start a new save and play in live mode for a bit. If this works, you can start moving your content from the old Sims 4 folder to the new one. Start by testing your mods and custom content, if you have any. Use the new Mods folder and Resource.cfg file the game creates rather than your old ones. Test your mods and cc in batches, or use the 50/50 method described here if you have a lot of files to sort through: https://modthesims.info/wiki.php?title=Game_Help:Finding_Problem_Custom_Content#The_50.25_Method Once you're done with your Mods folder, you can transfer the contents of saves, Tray (saved households and builds), Screenshots and Recorded Videos if you care about those, and Options.ini if you don't want to redo all your in-game options. The rest can be discarded; the game will regenerate the files and folders as necessary. ↑ Set exceptions in your antivirus Your antivirus blocking the game from starting can cause this issue as well. Look for any recent actions involving Sims 4 or the EA App, and set exceptions/exclusions as necessary. The exceptions should be for TS4_x64, TS4_DX9_x64, and TS4_Launcher_x64, or the Bin folder they're in; set one for EADesktop.exe as well while you're there. If you use Memory Boost (still in beta and opt-in only), set an exception for TS4_x64_fpb.exe. This article has instructions for Windows Defender and a couple of common third-party programs: https://crinrict.com/blog/2020/10/add-exceptions-to-anti-virus-programs.html If your antivirus isn't covered, consult the publisher's online documentation for instructions. A search for "[antivirus name] set exception" will probably find a user manual. ↑ Change OneDrive settings If OneDrive is running on your computer, whether you use it or not, it can block Sims 4's access to Documents and cause this error. First, try pausing syncing. Right-click the cloud icon in the lower-right corner of the screen, or sometimes hidden in the Tray (^ icon), to see the option: If this helps, the underlying issue is OneDrive, and you may want or need to adjust your settings accordingly. You can choose which folders to sync, stop OneDrive from syncing your Sims 4 folder or all of Documents automatically, or get rid of OneDrive entirely. Please see this guide, specifically the "I don't want OneDrive to sync my files" and "I want to get rid of OneDrive" sections, for further help: [CURRENT ISSUE] Sims 4 saves/user content disappearing (PC) | EA Forums - 11838402 ↑ Update your graphics driver Some users have fixed this issue by updating an old graphics driver. If you know how to do this on your own, go right ahead. To find the current driver version and date, click Windows key-X, select the Device Manager, expand Display adapters, right-click the name of your GPU (the dedicated card, usually Nvidia/AMD, if your computer has two), and select Properties > Driver. If you update through the Device Manager, which has an Update button in the menu, you will probably get a slightly older driver than the most current one. This is fine for testing purposes, and this driver may still fix the issue; just understand that you won't necessarily be up-to-date, and you may be told you already have the current version when you do not. To get the most current version, go to the driver downloads page hosted by the manufacturer of your GPU. If you don't know how to do this, or you'd like help or confirmation before proceeding, or trying to install the driver you've downloaded throws an error, please reply to this thread. Include a dxdiag. Click Windows key-R, enter dxdiag in the run box, wait for the scan to finish, click "Save all information," and save the file to your desktop. From there, you can attach it to a reply using the paper clip (Attachment) icon included with the other formatting buttons. ↑ Clean Boot A clean boot is the process of temporarily disabling all nonessential services on your computer, including some that may start with Windows and perpetually run silently in the background. (It is NOT a clean install of Windows; I am not suggesting you erase your data.) The idea is to see whether any background process is interfering with Sims 4. Here's how to perform a clean boot: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd The one service to leave enabled is the EABackgroundService, which the EA App needs in order to run. Disable the rest as described. When you reboot your computer, go through the Task Manager's background processes list shutting down any service that doesn't absolutely need to be running, for example anything from MSI Afterburner to RGB software might still be enabled. If you accidentally kill a critical process and it doesn't restart on its own, just reboot your computer again. Don't open anything other than Sims 4 and the EA App while testing, not even a browser window. If this helps, you can selectively reenable services until you find the culprit, then either leave that disabled or (if it belongs to an app you want to keep using) let me know what it is so we can try to fix the underlying issue. If the game freezes or crashes in a clean boot, please try again, except with your computer offline. You can sign into the EA App and put it in offline mode, then disable wifi and/or disconnect the ethernet cable before pressing Play. Uncommon causes These have been the underlying cause for a few uses but don't appear to be major contributors. Still, if any apply to you, try the suggestions. Disable Game Mode and Game Bar: Both of these settings are under Windows Settings > Gaming. DirectX 9 mode: Sims 4 now defaults to DirectX 11 mode on most computers. To force DX9 mode in the EA App, open the App game library, click Sims 4 > Manage > View properties, add -dx9 to the box, and save. If you play through Steam, open your library, right-click Sims 4, select Properties > General, and add -dx9 to the Launch Options box. Windows insider build: For certain other EA games, a couple of updates to the Windows beta build can trigger this error. I haven't seen this apply to Sims 4 yet, but if you're running the insider build, please see the accepted solution of this thread. Conflicting software: For other games (not Sims 4 as far as I've seen), MSI Afterburner or RivaTuner Statistics Server can trigger the error. You can close all unnecessary apps in the Task Manager; be sure to check the background processes list as well. ↑ New admin Windows account It's possible that the problem is caused by a setting or broken permissions in your main Windows account, and the fastest way to test this theory is to create a new account. It must have admin rights (not a standard user account), and it must be local, as in, not connected to your Microsoft account. The account name can only contain letters from the Roman alphabet and numbers, no special characters, accents, or anything else that isn't standard. To create a new account, open Windows Settings > Accounts > Family & other users, click "Add someone else to this PC" (under Other users, not Your family), click "I don't have this person's sign-in information," then "Add a user without a Microsoft account." Choose the username and password, answer some security questions, and you'll see the new account. Click it and select "Change account type" to make it an Administrator account if it's not already. It should say "Administrator - Local account" when you're done: Click ctrl-alt-delete, select Switch user, and sign into the new account. Then open the EA App (and Steam or the Epic launcher if applicable) and try to launch Sims 4. You shouldn't need to reinstall anything. Your saves and other user data won't be available, but that's fine for the purpose of this test. If Sims 4 works in the new account, it means the problem is contained to your old account. You can simply continue playing in the new account if you want. For any saves or other user data you'd like to transfer to the new account, sign into the old account again and copy the relevant files to C:\Users\Public. This folder is accessible from all user accounts; you can grab the files from there once you're in the new account. If you'd like help fixing your old account, please see below. ↑ If nothing else in this guide helps or applies to you, OR if Sims 4 only works the new admin Windows account but you'd like to play in your old account, try the other steps listed in this thread, which is for a distinct but sometimes related issue: [CURRENT ISSUE] Sims 4 Unable to Start, Already Running | EA Forums - 11818313 If those don't help either, please reply to this thread. Let me know whether the new Windows account worked. If it did not, please provide a dxdiag. Click Windows key-R, enter dxdiag in the run box, wait for the scan to finish, click "Save all information," and save the file to your desktop. From there, you can attach it to a reply using the paper clip (Attachment) icon included with the other formatting buttons. ↑
Problem with Renewal quest
Every player has same issue with Renewal Quest. Everyone can't claim reward for Collect Monthly reward once . Can we know what should we do or someone manually will just proceed our quests? This bug/problem is from 2 weeks and everyone in support is saying that case is under investigation and noone helped us since it. Its irritating when u have rewards to claim and u can't do that because of quest is bugged for such a long time ... Especially noone wants to guaranteed us that we will have those rewards after time will end and bug wont be fixed
High Usage CPU/GPU After S4
Hello Everyone, after this update and season 4 , im having some issues on my game. Cpu and Gpu usage randomly increased. Sometimes after returning to the class and flag selection screen and spawning again , performs returns to normal usage ( CPU ~35% ) ( GPU ~60%) . And some moments later after anothers death/spawn performs jumps to CPU ~70% and GPU ~98% without any graphics settings changes. Same PC same MAP same match. Tested on Tsuru Reef and others maps having the same issue after this patch.The FPS dropped a bit, and the latency in ms shoots up significantly—not to mention the temperature of the entire PC. Tried to uninstall graphics driver with DDU, Rollback nvidia drivers , rollback windows updates and some anothers things and not solved yet. It just goes to show that the problem really stems from the game itself following the last update. SPECS : R7 9800x3d / RTX 5070 Ti / 32GB RAM I have attached the images.EA BUG OF TODAY
EA ,we are tired of seeing so many glitches in the game nowadays. Today, there was Nyland having only 1.4k shards,when we saw them,we f2ps became so happy and I thought that it will be there forever,but when I opened fc mobile for one more time it was gone. What is this,is this money mobile?. Do you only want P2Ws ?. Nowadays,fc mobile is getting worse. You used to consider the f2ps before. You were used to listen to the community.Why don't you considering us now? We are losing the hope in you. Today,so many players got the Nyland but a large number of players didn't get it. So we hope that you will compensate us because it is compulsory because we are heart broken by losing that low priced Nyland . Please give us compensation 😔
Sims 4 Will Not Launch
After updating my game today (7/21) through the EA app, the app will minimize and appear as if it was launching the Sims before giving me the attached Error message. The EA app does log the launch as if I've had a minute of game time. I have been attempting to find the problem all evening and so far have: - Removed my Mods - Cleared the cache - Restarted my computer multiple times - Logged out of the EA app - Uninstalled & reinstalled the EA app - Repaired the game via the EA app - Made sure my Windows security & other virus detection software was not blocking the game - Run the EA app as an Administrator - Read every blog post or Reddit thread or forum or video I could find from within the last 5 years that might be helpful - Called a far more tech capable sibling to assist who could only conclude it was the update & hopes my save files aren't corrupted It's Tuesday night, it worked fine on Sunday night, so my guess is also that it's the new update. If anyone has ideas, they're welcome. In the mean time, I hope a patch update might resolve my issue soon and allow me to actually play the game.
@EA_Alijo Requested report: PC hard freezes since Season 3, returned in Season 4
Hello @EA_Alijo As requested, I am opening a new thread and attaching my current DxDiag report together with the only crash dump (.dmp) that I was able to obtain during the original investigation. Because this issue has now persisted across multiple seasonal updates despite extensive troubleshooting, I wanted to provide a complete chronological history instead of reporting only the latest symptoms. I believe the timeline itself may contain important clues that could help identify the underlying cause. I have been playing Battlefield 6 since December. Throughout Season 1 and Season 2, the game ran flawlessly. I never experienced a single freeze, crash, or system instability, and my PC has remained completely stable in every other game and application. Everything changed with the release of Season 3. Shortly after the Season 3 update, Battlefield 6 began randomly freezing my entire computer after several minutes of gameplay. Sometimes it happened before joining a battle, or in the menu, or maybe after five minutes, sometimes after fifteen or twenty, but eventually the result was always the same: the image froze completely, Windows became entirely unresponsive, and the only way to recover the system was by performing a hard reset. Since this behavior was exclusive to Battlefield 6, I began an extensive troubleshooting process over the following weeks. Among many other tests, I performed multiple clean AMD driver installations using DDU in Safe Mode, tested several different Radeon driver versions, updated my motherboard BIOS, installed the latest AMD chipset drivers, verified the integrity of the game files, completely reinstalled Battlefield 6, reinstalled EA Anti-Cheat, repaired Windows using both SFC and DISM, reviewed Windows Event Viewer, analyzed the generated crash dump using WinDbg, restored all Radeon settings to their defaults, and tested different graphics configurations and frame rate limits. The attached crash dump corresponds to the only BSOD generated during the entire investigation. WinDbg identified it as a DPC_WATCHDOG_VIOLATION (0x133). The analysis consistently pointed to ntkrnlmp.exe (KeAccumulateTicks), but it never identified any specific third-party driver, hardware device, or software component as the direct cause of the failure. Apart from that single watchdog crash, the vast majority of failures resulted in complete system freezes that produced no usable crash dump at all, making the issue particularly difficult to diagnose. One of the most significant improvements came after rolling back to AMD Adrenalin 25.9.1 WHQL, which proved noticeably more stable than the newer driver versions I had tested. Another important observation came after completely reinstalling Battlefield 6 and later clearing the EA App cache using App Recovery. After those steps, the behavior of the game changed dramatically. Battlefield became completely stable again, allowing me to play for several weeks, including many long gaming sessions, without a single freeze or crash. At that point I genuinely believed the issue had finally been resolved. Unfortunately, everything changed again with the release of Season 4. Immediately after updating to Season 4, Battlefield began freezing my entire computer again with symptoms that are virtually identical to those experienced during the beginning of Season 3. Another detail that caught my attention is that Battlefield once again started recompiling shaders every time the game launches. This is exactly the same behavior I observed when the issue originally appeared during Season 3. During the weeks when the game remained completely stable, shader compilation behaved normally, but after the Season 4 update it returned to recompiling shaders at every launch. Naturally, I repeated the exact same troubleshooting steps that had previously restored stability. I cleared the EA App cache again because that had coincided with a major improvement during Season 3. Unfortunately, this time it made absolutely no difference. I also continued testing different AMD driver versions, including Adrenalin 25.9.1 WHQL, which had previously provided the best results. Under Season 4, however, even that driver is no longer sufficient to restore stability. One detail that I believe may be relevant is that between the period when the game was completely stable and the moment the issue returned with Season 4, there were no hardware changes, BIOS changes, Windows reinstallation, CPU changes, GPU changes, RAM changes, storage changes, or significant software changes on my system. The only meaningful change before the freezes returned was the Season 4 update itself. This repeatable sequence—stable throughout Season 1 and Season 2, unstable after Season 3, stable again for several weeks after troubleshooting, and unstable again immediately after the Season 4 update—appears to form a consistent pattern rather than isolated random failures. During the original investigation, I was directed by a Community Manager to the main technical megathread dedicated to these freezing issues, where many affected players were gathering information and comparing troubleshooting results. For reference, my original report and follow-up posts can be found here: That discussion documents the complete troubleshooting process, every major test that was performed, the temporary recovery achieved during Season 3, and all the observations collected while trying to isolate the problem. At this point, my impression is that Season 4 has brought the issue back to almost exactly the same state in which it originally appeared during Season 3. The symptoms are practically identical, while the workaround that previously restored stability is no longer effective. The fact that the game remained completely stable for several weeks before the Season 4 update strongly suggests that the underlying trigger may be influenced by changes introduced between seasonal updates rather than by a permanent hardware or operating system issue. For completeness, I am attaching both my current DxDiag report and the original WinDbg crash dump in the hope that they may provide additional information for the investigation. If there are any additional logs, ETW traces, memory dumps, experimental builds, or diagnostic tools that could help narrow down the root cause, I would be more than happy to provide them and continue testing. If this report can help correlate similar cases reported by other players or assist the development team in identifying a common pattern, I will gladly continue providing any additional information or performing any further diagnostic tests that may be useful. Thank you again for your time, @EA_Alijo, and for continuing to investigate this issue. I genuinely appreciate your efforts
