Trying to install PMDG 747 base package into P3D v4.51

and getting the following message

Installation cannot continue.

Your registry does not show any location information for either P3D v3 or P£D v4

Please install a simulation then run the installer again.

My simulator pat D:\Lockheed MartinPrepar3D v4\Prepar3D v4 

Not keen on playing with the registry, is there any other way please

Thanks Frank

Only two ways I know of to get the P3D path into the registry:

1.  manually edit the registry with RegEdit to replace or correct the P3D path.

2.  Uninstall and reinstall the P3D client

Flight1 had a registry path fixer for FS9 and FSX, but AFAIK there is no equivalent for P3D.

 

 all you need to do is double click on the Prepar3d.exe   When it launches it should write registry entries if there are none.

2 hours ago, ejoiner said:

 all you need to do is double click on the Prepar3d.exe   When it launches it should write registry entries if there are none.

Interesting, if this is true it's news to me...do you have a source for this?  It's normally the installer's job to make system registry entries.  And what if the registry key exists from an old install and the user then installs into a different directory?  Things that make you go "hmmmmm."

If the above doesn't work, I just stumbled across this FSX/P3D registry fixer tool on the NMG Simulations website: https://www.nmgsimulations.co.za/flight-simulator-registry-fixer/

 

Double clicking on the p3d.exe sorted it for me, thanks for the suggestion

This was the advice from the Orbx team when I had the same issue.  Worked for me.

On 5/19/2019 at 4:12 AM, w6kd said:

Interesting, if this is true it's news to me...do you have a source for this?  It's normally the installer's job to make system registry entries.  And what if the registry key exists from an old install and the user then installs into a different directory?  Things that make you go "hmmmmm."

 

One way to test if something you doubt is true or not is to try it.

Not so hard, check the P3D registry entry first:

 

Then rename the root folder and run the same exe file again:

 

All doubt now dispelled and no one's assertions questioned.

 

OK then...good thing to know. 

I don't have enough hours in my day to run experiments on every assertion that looks potentially questionable, but thanks for taking the extra step to prove this works.  I have it added to my book of tricks now.

Cheers