July 2016 - last edited July 2016
so today i decided to restart my system and then loaded origin it attempted to update then i received the above message it happened twice after a quick goggle searching i find this exact issue is over a year old and has no official fix what the * is wrong with origin? are they trying to drive people away with their client?
its slow
its dated
it cant even update itself properly
are they going to fix the * t thing or just leave it and call it a "feature"?
perhaps they should scrap their client and just release everything on steam/GoG since they actually * work and update without issues
Solved! Go to Solution.
July 2016
What worked for me (as I had this issue at least 3 or 4 times) was quite simple... I logged out of Origin, made sure that Origin.exe is not running and deleted Origin folder (not Origin Games though). Then I rebooted my laptop, downloaded Origin installation file from the official Origin site and installed it from the scratch. That's more or less it.
July 2016
What worked for me (as I had this issue at least 3 or 4 times) was quite simple... I logged out of Origin, made sure that Origin.exe is not running and deleted Origin folder (not Origin Games though). Then I rebooted my laptop, downloaded Origin installation file from the official Origin site and installed it from the scratch. That's more or less it.
July 2016
Hello.
If nothing helped, try use my script for clean of Origin data and reinstall it. Download it, delete .txt in name and run it as Admin.
July 2016
Have you been able to try the suggestions posted? Let us know how you are getting on.
Cheers,
Nils
July 2016
spitfiresiemion solution seems to have worked for now and i have granted XP for it but i do not want to do this every time i restart my computer nor should i or anyone. it proves there is something seriously wrong with the origin client for this issue to still exist after 18+months. You would think that a company that can produce some incredible story's could at least create a simple distribution client that is not a bad joke
July 2016
To be fair, it should not happen after every reset... I had this problem only a couple of times since the year started, and I think that the only common point was that in both cases it happened after Windows updated itself.
July 2016
The problem shouldn't occur again. If it does, then please reply to this thread with a dxdiag.