Update to .161007 crashing ms FSX

[billgustaf]

I received the link that this update was available and have tried several times to install it, without success. I also grabbed another copy of the updater, which also is not taking care of the problem. I have used the removal button first to remove the previous version (.160306.) As installation is finishing, it is loading a new component called MVAMs. This runs and fails giving a fault page for each model (J, and S). The starting line of the error msg reads "Exception loading the module at C:Users\Bill\Appdata\Local\MVAMS\Modules\F4J.dll" (and the second page references same for F4S.dll). When I start FSX and first load the Cessna, then change AC to the F4, FSX crashes. Error message here states Fault mode name is MSVCR90.dll and Fault Module version is 9.0.30729.6161. When I undo everything and reinstall version .160306, I don't see that MVAMS is installed - or present. The version previous to the update will at least run, but with a few minor bugs. I have FSX original boxed with Acceleration, and am using the T-38, PMDG 737 etc, and some other complex aircraft without issue. Running WIN 7 64 bit, with an Intel I5 and Nividea 650 TI card. I rechecked everything on your "before you call" list. Is MVAMS the culprit?
Thanks!

[JonathanBleeker]

First of all, are you running the AMS and FSX as admin? As in right click, Select Properties->Compatibility->Run this program as administrator?

[billgustaf]

I always run as administrator for installs or updates of any kind. Have never launched FSX, or AS Next or Config programs as administrator. This has not caused any previous problems including the pre-updated Phantom. I did just let FSX build a new Config file after I backed it up. I have not yet reinstalled either version of your F-4, and all other aircraft are working well. Also I forgot to mention I have no anti-virus installed on this computer. It is used exclusively for FSX. Only connects to Internet for weather or software validation if required. Thks!

[JonathanBleeker]

Please try running FSX and the AMS as admin. Things have changed considerably and may now require admin permissions.

[billgustaf]

OK. Set my fsx main progs to run as administrator. Ran the install file for 161007 again. MVAMS still fails as previously described. Now the ACM is not even being installed. the J and S were installed to the simobjects folder. Selecting either will crash the sim. Was prompted to "trust the modules" before the crash happened. Should I go back to my first installer (which did install the ACM utility) then uninstall it from either that wrapper or the new one and then install the update? I am pretty sure I did that before checking in with you all. Thks,
Bill

[JonathanBleeker]

Could you post screenshots of the errors please?

[billgustaf]

I tried to attachment the MVAMS screenshot which the update installs for the first time. File size is 7,323 KB and is rejected a too big. Shall I send it to Kat's email? The first and second screen are identical except the last line which references the second F-4 type. The FSX crash to desktop has the standard "FSX has quit working" screen. The details are contained in my first posting in this thread. Looking at other posts I also tried an install after removing the Affinity mask lines in my config. The only other thing i see is that my UIAutomationCore.dll may be a different version than referenced in a memo. MVAMS appears to be mentioned by others in relation to TACPAC. Does the updater file presume I already have MVAMS or are you guys just now pushing it out to us J and S drivers? Again, If I remove the pre-update version including the config utility, that utility is not installed when I run the update. Also confused as to which removal tool to use if backing out the pre-updated F-4. Thanks!

[JonathanBleeker]

Post to a image hosting site like imgur or photobucket or dropbox and post the link.

[billgustaf]

I will give that a shot. Will have to figure out how to, since that is something I have not yet learned!

[billgustaf]

Here is an attachment for the MVAMS error. Should MVAMs have already been loaded prior to update?

[billgustaf]

Still trying to update. Downloaded a new install file. Changed out the UIAutomation.dll as mentioned in an early F86 support post. Then reinstalled the original purchase file for the F-4. Everything looked normal. Then used the update file to uninstall the original. Rebooted and then installed the update. MVAMS installed at the end, was launched automatically and failed, giving same two messages like the one attached earlier. The Milviz Menu Manager launched, but was empty. I closed the box and re-launched it as Administrator. It still is empty. I was previously able to use it for configuring the original versions. Looking at the file location, there is an exe file to run it, but it is opening up empty. The aircraft are residing the the sim objects folder and I have not tried to load them. Perhaps the crashes were due to no models showing in the Menu Manager? also MVAMS give the two error pages if I attempt to run it.

[JonathanBleeker]

It appears there is a .NET problem on your system preventing the AMS from functioning. The old Milviz Menu manager is no longer used. I am getting info from our resident .NET expert and will get back to you.

[billgustaf]

Looks like ThunderbirdChief in the thread above mine experienced almost the same kind of crash to FSX. He did not mention anything about MVAMs, but since he has the TacPack, perhaps that was no factor?

[billgustaf]

Jonathan,
I loaded vers 4.6 of Net Framework to my PC, but still no luck. When I look at the compatability tab on the menu for MV_MM.exe , should I try changing any settings?
If I can't make progress I might have to reluctantly run the previous version of the Phantom until perhaps some of these issues get sorted out in a future update. Looks like I am not the only one having problems with the update. Regards, Bill

[billgustaf]

I think I just answered my own question. I changed the settings for MVAMS to run in compatibility mode for Windows 7 Service pack 2. It worked and now shows the 2 models and the setting choices available. I think we had a communication problem in that you never said MVAMS was the new menu system. I thought it was for TACPAC and you did not answer my questions about it. Since it failed for me, this was not obvious. The Phantom now loads to FSX and does not crash on entry or exit. Anyhow, things seem OK now and I do appreciate your attempts to help!