Origin Sims 4 "download failed"
- 5 years ago
@heyburak Is the InstallLog you uploaded from The Sims 4\__Installer\ on your C or D drive? I ask because if you look at the InstallLog you uploaded, you can see all the failed attempts have been to C:\Program Files (x86)\Origin Games\The Sims 4\.
I do see an error in the InstallLog, but I want to make certain this is the current InstallLog from your most recent installation attempt on whichever drive you are currently trying to install the game on. Origin is failing when setting up the uninstall data; unfortunately it doesn't indicate why it failed to copy a particular file.
First, in Verkenner, on the Beeld tab, enable Verborgen items. To test this, go to C:\ and look for a directory named ProgramData once "Verborgen items" has been selected. If you can see the ProgramData directory, then go to C:\Program Files (x86)\Common Files\ and see if there is a directory named "EAInstaller". If so, within the EAInstaller directory is there a subdirectory named "The Sims 4"? If so, inside The Sims 4 subdirectory are there two files named Cleanup.exe and Cleanup.dat? Try removing any files (e.g. Cleanup.exe and Cleanup.dat) and folders inside C:\Program Files (x86)\Common Files\EAInstaller\The Sims 4, then try installing the game again. If there were no files in C:\Program Files (x86)\Common Files\EAInstaller\The Sims 4 or if there were files which you removed, please let me know. If the installation process fails again after you've emptied C:\Program Files (x86)\Common Files\EAInstaller\The Sims 4, please post the current InstallLog.txt.
Sorry to beat a dead horse, but when you searched through Register-editor for C:\Program Files (x86)\Origin Games\The Sims 4\, once you encountered the first match, you pressed the F3 key on your keyboard to search for the next match, and repeated the process (using the F3 key) until the entire registry had been searched? If you search for just The Sims 4 (pressing the F3 key to continue the search), do you return any matches in the locations I mentioned?
Also, once again run the commands in PowerShell (as an administrator) I mentioned in post #9.