February 2019
February 2019
February 2019
This didn't work, nor did any of the other solutions like deleting the cab files etc, or uninstalling all the directx versions. I even copied the full install from another pc. Still didn't work. I used process monitor to find out what was hung while the error message was up and analyzed the properties of the executable. The application touchup.exe was trying to run and wouldn't run on install. I ran a cmd prompt as admin and manually forced the statement to run in flashed in the background several windows and then I tried to run the game 2 more times to get past the initial error and the game launched. In my instance the game is installed to H, but yours could be C: so just copy that instead.
If your drive is H like mine:
"H:\PROGRA~2\ORIGIN~1\Apex\__INST~1\touchup.exe" install -locale en_US -installPath "H:\Program Files (x86)\Origin Games\Apex\" -autologging -startmenuIcon=0 -desktopIcon=0
IF your drive is C:
"C:\PROGRA~2\ORIGIN~1\Apex\__INST~1\touchup.exe" install -locale en_US -installPath "C:\Program Files (x86)\Origin Games\Apex\" -autologging -startmenuIcon=0 -desktopIcon=0
Peace God bless! Many hours finally over lol.
February 2019
Please help me my Discord is Technicc_#7296 i have tried everything and i don't understand how to do what you explained.
February 2019
March 2019
thx mate worked with anthem , after you swap thos files , DALETE game and restart origin and instal new copy of game and its working
March 2019
BIG THX Stoogiemeister WORKS THX
March 2019
Absolutely worked for me. You are a baller man! Thanks for the fix AND the walkthrough for regedit for those of us who are old and slow. Someone at EA hire this dude.
March 2019
Thank you for providing a workaround fix for this, @Stoogiemeister
For those experiencing Apex getting stuck at 38% our team is aware of this and investigating. We'll provide an update surrounding this as soon as we find out more details.
March 2019 - last edited March 2019
Thanks for noticing and replying @EA_Blueberry , changing the version number doesnt seem to affect anything either as far as i can tell, only what the application reads for when it checks.
Also im not talented, im just an aspie with schizoids with nothing to do in life at age 31 except a lot of googling and reading(so im mediocore at language and actually dislike programming as its a language).
I am guessing the problem is a small programming mismatch with directx checksum that could be fixed by adding the higher version by 1 digit as a pass when it checks, so easy 5 second fix?
edit: well technically its microsofts problem when they created it in june 2010, basically u need to unpack it edit the exe for the checksum check of the version number to fix that issue then repack it, then update your origin servers with modified version of june 2010 for each game/application so when you verify or install the game it verify's with the modified version and then it will work fine and this issue will never exist. Or you can ask microsoft to edit a fix, which they wont since they havent edited it since 2010 hence its name
A lot of community programmers or modders could easily do this fix as well(not me though), but EA needs to update the origin servers with the modified version.