My Sims 3 Wont Open pls help
- 2 years ago
@KiidDior Thanks, and your dxdiag shows that you're not currently seeing the Alder Lake issue. I believe you would if you got far enough and didn't use one of the Alder Lake workarounds, but at the moment, the launcher is throwing the error, not Sims 3 itself.
To be thorough, because the error in your dxdiag references a component of Windows, please run a couple of basic checks of your Windows system files:
- Hit Windows key-X
- Choose either “PowerShell (Administrator)” or “Windows Terminal (Administrator),” whichever option is offered
- Inside the window that appears, copy and paste “DISM.exe /Online /Cleanup-image /Restorehealth” without quotes, and enter
- The system will start validating soon. If it throws an error, please list it here
- After it reaches 100%, hit Windows key-X again
- Again, choose “PowerShell (Administrator)” or “Windows Terminal (Administrator)”
- Inside the window, copy and paste “sfc /scannow” without quotes, and enter
- Post the message you receive here
Restart your computer, hit Windows key-i, select Update & Security, and click the box to check for updates. If any install, restart again afterwards.
The error specifically references .NET, so please uninstall and reinstall .NET Framework 3.5. Hit Windows key-R, enter "appwiz.cpl" without quotes, click "Turn Windows features on or off," and check the filled-in box next to .NET 3.5. Restart your computer and repeat, except this time, check the now-empty box to reinstall, and restart. If the box is already empty, you can simply install .NET 3.5 and restart.
If the above doesn't help, 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 reinstalling .NET 3.5. 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.