Re: [PC] PvZ Error Writing User File

@claraathiessen So you are able to log in and play but then after playing a match you get that error?

Do you get that error when you first launch the game?

@EA_Shepard Yes, since I've had the game for years I am already logged in, but yes I get to play one match (the same match every time I launch) but when the match is over it just instantly pops up with that error.

@claraathiessen See if these steps help.

Please clear your temp files:

• Press the Windows key and "R" at the same time
• Into the new window, type or copy & paste: "%temp%" (Without the quotes.) > hit "ENTER"
• Now your Windows Explorer should have brought you to the "C:\Users\>your user name<\AppData\Local\Temp" folder. > Delete all files and folders in it.
• (If some files or folders can't be deleted, reboot and try again.)

Then:

• Make sure the EA app is closed.
• Press the Windows key and "R" at the same time.
• Type or copy and paste "%ProgramData%\Electronic Arts\EA Services" (without the quotes) into the new Window > ENTER
• Delete all files.

@EA_Shepard This shows up everytime i try to delete (attached file): it says "the file is open in EA" however EA isn't open, and it also says some of the other times "open in chrome browser" or "microsoft edge" or "the file dosn't exist" - I can't delete these files, even though the only thing i have open is my files holder because i close everything down and I*''ve tried like 10 times now, and restartet my pc. what should I do?

@claraathiessen So what you have to do is close every open program you can down by where the clock is on your PC. Open tasks manager and make sure the EA app is not running at all either.

Any files it doesn't allow you to delete just skip. Some need admin permissions, some are using background programs so it is okay if you cannot delete them.

Hello. I am having the same exact issue as this other person, I followed your advice and deleted all my temporary files and the folder that you mentioned. It still doesn't work for me. Could you help me?

@senhor_prickles We sent this over to the team to have looked at. Not entirely sure what is causing that error. We are doing more digging into this but at the moment, there isn't a workaround to get around that error.

Can you attach a DxDiag?

Thank you! I think I did the DxDiag correctly. If you need anything else please let me know.