AH3 Initialization error

[SWkiljoy]

Since the recent update I am no longer able to launch AH3.
I had DX11 installed and updated then it crashed upon launch. Removed and re-installed, same problem.
I tried installing DX9 with updates and ran into the same problem with this error code.
Error message pops up saying "Initialization failed with -9 mainWLD_FAILED-1"  or "-11" with DX11
After trying to change settings folder name after reading into similar user problems I am asking for further assistance.

Any help would be appreciated, thanks.

  SWkiljoy

[Skuzzy]

That means stdshape.res is corrupt.  You will have to download and install the full game over the top of your current installation to correct it.

What anti-xxx software are you running on your computer?

[SWkiljoy]

-Malwarebytes anti-malware
-Windows Defender

Neither were running during installation, i made sure of it.

Should I run off DX11 or 9 if i was already having no problems with 11?
Pros vs Cons? Not too invested in the details of both.

So if i run DX11 just download it again and patch over it is what you're saying Skuzzy?

[Skuzzy]

Just install the full version over the top of the existing version.  It will preserve all your settings that way.

[mittsy]

Having the same issue. Reinstalled and downloaded the patch 3 times, same error. Downloading full version now and going to reinstall overtop.
Downloaded full version... now I am back to the NSIS error, and can't install the game at all.
Why would the patch fail?
I have a previous version (patch 2) but it will install without the NSIS error.
Load all patches fine, except the latest version, it fails, then I get the corrupt shapes message.

[boxboy28]

Oh I got it to install, then came the map update and that crashed it back 5 times to cant install even thought it was 90% through,   same thing all anitV off Malwarebytes off  nothing else running..... theres a bad bug here.

[Skuzzy]

There is no bug in the executable causing this.  It is strictly a localized issue.

It is corruption of the files causing these problems.  We have no control over it.  How many of you are trying to run the installer/patch from an SSD, or installing to an SSD?

By the way, disabling most anti-xxxx programs only disables the reporting of issues, it does not stop them from actually running.  Kaspersky, AVG, Norton, McAfee are all known to interfere with the executables.  The problem stems from all these anti-xxx programs assuming compressed data in an executable is a virus.

There is also an SSD firmware bug, which the patcher will hit, which can cause problems with the patch.  We ran into this during Beta.

We may have to do what other game companies have been forced to do and that is to ship a small installer which will copy the files from our server (over the Internet) and install them one at a time.  It might work around these issues.

[SWkiljoy]

Tried to launch the Installer and found the NSIS error message. Hands seem to be tied at the moment.   

[Skuzzy]

Would you mind posting a DXDIAG output?

By the way, running both Defender and Malwarebytes is not a good thing to do as they are both trying to do the same thing.  Sort of like running Norton and McAfee at the same time.

There are three possibilities, I can think of.  There may be more.

1)  The file is getting corrupted during the download.
2)  There is not enough free memory to run the installer.
3)  Trying to run the installer from an SSD, which would reduce the amount of system memory due to the system RAM drive needed to hold the temp files, or the bug in the SSD firmware causing corruption.