Unable to load MD530 or 407 [resolved]

[JonathanBleeker]

Please go to your registry, and go to HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3D v4. Take a screenshot of the AppPath key, and also of the 407's folder in the SimObjects\Rotorcraft\ folder.

[Chuck Jodry]

Hello , If I can ask you to do two things , First in the MVAMS folder ( Right click on your AMS and click on Open File location ) in the configurations open the MD530 folder and move all the .mlvz files onto your desktop , leave the md530addonpack.kmlvz.

Next in the main P3Dv4 folder , there might possibly be a folder named Milviz from the previous version , inside that are the old menu manager files , if you see one for the MD530 or B407 , delete them , these if there should be empty now having had their contents removed by uninstalling .

Then run the MVAMS , let us know if the error still occurs .

Will follow up .

Best CJ

[JonathanBleeker]

@Chuck for some reason his AMS isn't even finding his B407 and MD-530 aircraft.cfg files. Doesn't even get a chance to look at the mlvz files. Likely a registry problem.

[Jas451]

Ok here are the captures you requested.

Capture Registry for Prepar3D v4

Capture10.jpg (59.98 KiB) Viewed 3516 times

Capture SimObjects/Rotorcraft/Milviz Bell407 folder

Capture11.jpg (190.68 KiB) Viewed 3516 times

Reinstalled MD530. 530 and 407 now show in AMS, but when clicked on same error message pops up

Capture12.jpg (52.05 KiB) Viewed 3516 times

Noticed in registry there are two entries for Prepar3D. Is that correct?

[Krazycolin]

No.

[N4GIX]

Actually, I see three entries for P3D: v2, v3, and v4. This should not be the cause of your problem, but if you no longer have v2 and v3 installed, it might be a good idea to remove the registrations.

The other entry is one for v1 (LockheedMartin) and likewise should be removed if you no longer have v1 installed.

[Jas451]

Beginning to think I may have to reinstall Prepard3D to see if this will resolve this issue, but not looking forward to having to reinstall all my addons

[JonathanBleeker]

You shouldn't have to if you only uninstall/reinstall the client. But I don't think that's necessary either. I am looking further.

[Jas451]

I want thank the people of Milviz who have tried to help me with this issue. Milviz has always been great with support issues for me and others I have seen on the forum. I tried a reinstall of Prepar3d and continue to have the same issue. Since the installer is no different than any other installer for the other Milviz aircraft which I own that work without issue, then I assume that this might be an issue with Windows 10. With all the recent updates that have occurred over what seems a short period of time something may have been gotten messed up. I have no desire to attempt a reinstall of Windows. I still can't get why it's only the heilo's that are causing this error. I have decided to go ahead and just uninstall the MD530 and Bell 407. Maybe in the future if I have to reinstall Windows for some reason I will given them another go. Again Milviz thank you for all your help.

[JonathanBleeker]

I'm not quite one to give up yet. Please try this dll and send me screenshots of the popups. I have added more debug info to get to the bottom of this.

https://www.dropbox.com/s/5yz1iu1srq7qi2g/B407.zip?dl=0

[Jas451]

Downloaded and installed the new dll. Here are the Screen Captures

Capture 13.jpg (40.29 KiB) Viewed 3478 times

Capture 14.jpg (44.57 KiB) Viewed 3478 times

Capture 15.jpg (53.26 KiB) Viewed 3478 times

Now just need to get the MD530 up and running. Thank you for not giving up on this, I appreciate this more than I can convey.

[JonathanBleeker]

https://www.dropbox.com/s/5yz1iu1srq7qi2g/B407.zip?dl=0

This next dll will tell me if the registry locations are even being found.

[Jas451]

Downloaded the new dll. Here are the screen shots after running.

Capture 1A.jpg (45.45 KiB) Viewed 3464 times

Capture 2A.jpg (32.4 KiB) Viewed 3464 times

Capture 3A.jpg (25.18 KiB) Viewed 3464 times

Capture 4A.jpg (29.84 KiB) Viewed 3464 times

[JonathanBleeker]

As I thought. The registry check is failing. The following dll will tell me why it is failing.

https://www.dropbox.com/s/5yz1iu1srq7qi2g/B407.zip?dl=0

[Jas451]

That was quick, Thank you, here are the screen shots

Capture 1B.jpg (45.45 KiB) Viewed 3458 times

Capture 2B.jpg (29.84 KiB) Viewed 3458 times