Sims 3 Not working windows 11
Hi, i had this issue for a long time, since i updated my pc to windows 11, i can't play trough the EA app. If i press play in the EA app it goes to the launcher of sims 3, but when i press the play...
Forum Discussion
@SHADYN-72 You'll still need to find a way to limit Sims 3 to one CPU core as it's loading. That's the only way around this issue. Since PowerShell isn't working, try updating it manually, as described here:
You can try the Task Manager method if you prefer.
@Bhue Your dxdiag also shows the error associated with the Alder Lake problem. Interestingly, the two most recent errors list TS3W.exe, which is strange unless you happened to uninstall the EA App version and install from disc or Steam.
The blank launcher is a separate issue that can usually be cleared up by clearing Edge's Internet Explorer data, as described at the end of this article:
For the already running error, does it still happen with Bitdefender disabled? Is OneDrive running, whether you use it or not, and how full is it?
I used the Alderlake Patch. The game shows up on both EA App (with all of the DLC) and on Steam (without the DLC). I can uninstall the Steam version. Not sure why it is showing TS3W, I ran TS3 as administrator. I will repair the files through EA App, uninstall the Steam version, kill the EA App/EABackground (my EA App was force updated to the latest version btw). I have tried it with both the exceptions and with BitDefender completely off. As to Microsoft Edge, I do not use it. I do not have any cookies, cache, or history there and it force clears it if the app is accidentally opened. I do the same with Chrome, but again I do not use it. I use Firefox with DuckDuckGo/NordPass/BitDefender. I have not had Edge open even accidentally since the side went blank. But I will check that Microsoft did not reset my settings with the last patches.
@Bhue The Sims 3 launcher uses Edge in IE mode whether you use Edge or not. So please clear that data and try to open the launcher again.
A Steam install uses TS3W.exe, so if you tried to launch the game through Steam, that's why that .exe crashed. It's a good idea to uninstall the Steam version and also remove the associated registry entries. They're here:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Electronic Arts\Sims(Steam)
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sims(Steam)Hit Windows key-R, enter "regedit" without quotes, and before doing anything else, export a copy of the registry (File > Export) in case you accidentally delete the wrong entry. You can restore this version of the registry by double-clicking the saved file. Then navigate to each location in turn and delete all entries inside the Sims(Steam) sections. Restart your computer when you're done, then try to run Sims 3.
If you still can't play, please please look for new errors in the Reliability Monitor. Hit Windows key-R and enter "perfmon /rel" without quotes, and you'll see a chart of errors and updates with a column for each day. Today is on the right.
Look for an error that happened at exactly the time of your most recent attempt to launch Sims 3, specifically after you've done the steps I listed. If you find one, double-click it to see more details, then copy that info and paste it into a reply here. If you don't see a new error, check back in an hour or so—the Reliability Monitor doesn't always update right away.
I do not save cookies, histories, etc in Edge - plus sync is off.
I had uninstalled Steam version - but had not removed the registry keys - done.
It still did not work, but the right hand side of the launcher was no longer blank.
But I did find the problem later, it was none of the things that were suggested. I was looking at the properties of the executable and saw that it was set to run as administrator. When I started it, I also ran it as administrator. I believe it was trying to run it twice and shut down because it was already perceived to be running. I removed the administrator tag off of the executable and it now works correctly.
Thank you for all of your assistance.
Bhue
**edit I had already run the Reliability Monitor and there were not any critical events for this evening - again thank you.
