Forum Discussion
Here is the solution that worked for me: Uninstall EA App, Wild Heart and Steam, create a new administrator account and reinstall EA App, Wild Heart and Steam. After you uninstall EA App, just to be on the safe side, remember to go to the root folder (mine is at C: Program Files/ Electronic Arts) and delete the whole empty EA folder.
To create a new administrator account on your PC (Win 11), go to Start--Right click on your avatar--Change account settings--Family & other users--Other users (you may try "your family" but I prefer "other users")--Add someone else to this PC--Enter a Microsoft email address which is different from your main account--Add the new email address as a new account and make this account as an Administrator.
After creating the new administrator account, log in to this new account and download Steam. Then download and reinstall Wild Hearts through Steam (check the box to create a desktop shortcut for the game).
After the installation, use the shortcut to run Wild Heart. Steam will ask you to download EA App, follow the instructions and install EA App, and the game will continue to run.
Wait for a few seconds and you should be able to see the loading screen of Wild Hearts now.
I don't know the mechanism behind the account trick, but it did work for me. Hope it also works for you.
- 3 years ago
@dynisa Oh my god that actually worked, thank you so much.
Also seems like you can't just switch back to your old account after installing the game, still the same issue.
- 3 years ago
Sadly this did not work for me. Same results as before. Appreciate the support in finding an answer and sharing these though!
- 3 years ago
@dynisaThis really isn't directed at you; but anyone.... anyone.... who thinks this is an acceptable solution, or even a valid work-around, is part of the problem.
- 3 years ago
So I bought the game on steam a few days ago and played it for a while. However, after trying to play it the next day, it would not launch. The EA app pops up once or twice, then closes, and nothing happens. However, the task manager says the game is still open and uses a full 300 MB of RAM while doing nothing. I've tried countless solutions, including reinstalling it multiple times, verifying the integrity of game files multiple times. I checked my firewall and it doesn't block EA or the game itself. My antivirus hasn't registered the game. I've made sure my drivers were updated and everything.
UPDATE: I fixed it... somehow. Here's what I did. I'm not really sure what part of it worked.- Cleared the EA app's cache
- Verified game files on Steam
- Cleared EA app's cache again for some reason
- Deleted the SYSTEMSAVEDATA file (/Documents/KoeiTecmo/WILD HEARTS/)
seems to have permanently fixed my game??
- 3 years ago
My wife is unable to run WH (purchased via EA app/ non-steam install) on her windows account (Admin), but WH will run on the same PC with my windows account (Admin account that installed windows). I did a ton of troubleshooting and this just seems bizzarre. Why would what account is trying to run the game have any bearing on whether it would run?
If I try to run it on her windows account, we get the odd behaviour of WH sitting in the taskmanager and using up 400mb of ram, but not actually being playable. She also has no KoeiTecmo folder in her documents. If I log out of her windows account and log in on mine, sign her into the instance of the EA app on my account and launch the game, it starts right up. All programs and services are installed as system-wide, so I have exactly the same background processes running as her account.
This is baffling. We ran thru all of the recommended steps from EA to no avail. Why does this work?
EDIT: Running the EA app as administrator seems to have rectified the issue. Once the game successfully launched, removing admin privileges from the app still resulted in the game launching. I'm not sure what changed since the last time I tried it, but progress is progress.
About EA Originals Discussion
Recent Discussions
- 3 hours ago
- 2 days ago
Wild Hearts - refund
Solved2 days ago