August 2020 - last edited August 2020
My Origin Client continuously writes to an xml file in C:\Users\[username]\AppData\roaming\Origin every second. This has happened to me on a previous install of Windows on my machine, and after installing Windows from scratch, it is still happening. In my case the file is called local_72e10e604ec451c9e31d8905ce8f8e36.xml, even though there is a local.xml file there already.The contents of the XML file seems to contain settings for the Origin Client such as AllowNonSecureDownloads, AllowNonSecureDownloads, AllowNonSecureDownloads, and AllowNonSecureDownloads among others. It is a relatively small file: 1.5KB. In Windows Explorer, I can actually see the file being updated by a temporary file which is then renamed to the above filename with the current date/time as the timestamp.
The frustrating thing is that whenever the Origin Client is running (which is whenever I play any EA games I own), I can hear my drive being written to every second. For a gaming client, I believe this is quite unacceptable. Having being a developer for a few years and currently an IT specialist/architect, I find this to be rather sloppy of the Origin Client developers.
I have already tried to contact EA support using the online chat, however the AI/individual that assisted me did not quite grasp what I was trying to explain since they are only a support person with limited knowledge into how the Origin Client works. Since the only other form of support on this site is through the Answer HQ, I thought I would post this in the hopes of other people experiencing a similar problem and hopefully EA can actually do something about this.
August 2020
October 2020 - last edited October 2020
I have this issue too on all of my 3 machines, whats happening here?
I reinstalled origin today, iam currently testing if this solves the issue...
i noted that this issues happens directly after a game update. If i close and restart origin issue is gone until the next game update.
October 2020
Re-Install does not fix this issue. Whats wrong here?
December 2020
any update as to whats happening here, got it too
December 2020
Still no change. There are client updates, but this little bug still exists. Not sure how to attract the attention of the EA support team. It really is a small coding bug, I'm sure, that can be easily fixed but if only they would pass on the details to the client dev team...
January 2021