Entire game shows as not installed

[Branwen84]

I downloaded the game through steam, bought some packs through the EA app and some through Steam. Everything was working fine until yesterday, when I had to reboot my router. Since then, the entire game(not just some packs) shows as not installed in the EA app. In Steam it does show as installed, but it won't launch. It's certainly taking up space on my SSD, too.

I've tried clearing the cache in the EA app, but it won't restart after closing. Anyone have any other suggestions, or any ideas about why the app won't restart?

I'd prefer not having to reinstall, since I have all the packs and it would therefore take quite a while.

[puzzlezaddict]

@Branwen84  Try running an App Recovery, which you can do even when the EA App won't open:

https://help.ea.com/en-us/help/faq/clear-cache-to-fix-problems-with-your-games/

Then uninstall and reinstall the App, and see whether it picks up your Sims 4 install.  Let me know either way.

Please also make sure your Steam and EA accounts are (still) linked correctly.  Open any EA website, for example ea.com, click the Sign In button, then the Steam icon, and enter your Steam credentials.  You should land in the EA account linked to that Steam account, which is also the EA account you need to use when signing into the App.  If you get an error when trying to sign into the EA website, let me know.

[Branwen84]

App Recovery from the Start Menu worked, thanks.

Though I took some extra steps, because I still had the "EA Background Service" running and I suspected it wasn't going to work if i just left that running, but also supected that it might be related to my most recent attempt at clearing the cache and therefore didn't want to just kill the process, just like that.

For anyone else who might have the same problem, those extra steps were: I rebooted my PC, exited the EA app, then killed the "EA Background Service" process via Task Manager. Only then did I start the App Recovery.

Rebooting my PC may  or may not have been unnecessary, but I think killing the process wasn't, and like I said I didn't want to kill it while it might still be occupied with another attempt at clearing the cache.