F-4J/S CTD on Start

[flyboy7798]

Before this CTD at least it crashed after getting to the cockpit. Now after the upgrade it still blows up as soon as I click the button to go from the scenario setup to load the sim and aircraft. Also I downloaded and used the latest installers:

MilViz F-4SJ Phantom II vA1.170426_JS
MilViz F-4 Phantom II SJ vA1.170323 Update

Installed like I did the F-4E, as admin, AV off etc. etc. I disabled Tacpack on start, deleted the AMS radio files. CTD seems to be similar to the F-4E CTD before the upgrade that finally fixed that problem. Here's the AppCrashView particulars:

Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.22.19868
Sig[2].Name=Application Timestamp
Sig[2].Value=588f7cbf
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_bd0b
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.479
...
LoadedModule[221]=D:\Prepar3D v3\Gauges\MV_F-4J_ACM.dll
LoadedModule[222]=C:\Windows\SYSTEM32\d3d10.dll
LoadedModule[223]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9247_none_5090cb78bcba4a35\MSVCR90.dll
LoadedModule[224]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9247_none_5090cb78bcba4a35\MSVCP90.dll
LoadedModule[225]=C:\Windows\SYSTEM32\d3dx10_43.dll
LoadedModule[226]=C:\Windows\SYSTEM32\d3d10core.dll
LoadedModule[227]=D:\Prepar3D v3\Gauges\MV_F-4J_Sys.dll
LoadedModule[228]=D:\Prepar3D v3\dsd_sound_library.dll

Let me know if there is anything I need to do different.

[JonathanBleeker]

Don't use the 170323 update. The 170426 installer is a completely full installer that voids all previous updates. That's why you are crashing.

[flyboy7798]

That did the trick...so far so good. Strange how FSPilotShop is including the update in their download.

[doodlebug]

I'll have a word with them - thanks for the heads up.

[endl3ss]

I assume the same is the case for the F-4E Phantom II vA1.170424_E installer too?
It replaces all previous versions?

[doodlebug]

Yes it replaces previous versions - the update [vA1.170323 Update] was merely a stopgap measure to get you flying while the new installers [vA1.170426_JS] and [vA1.170424_E] were being prepared. The update [vA1.170323 Update] is no longer required.