I reinstalled everything (planes, scenery, etc.) when Hotfix 2 came out.  I love the sim now and it's relatively problem free.  However, SODE does not work.   When I try to install the latest version, here is the message I get:

"[P3Dv5] The Registry holds an invalid path to your Prepar3D.exe.   Platform manager will be unable to register SODE for P3D - Please fix your registry"

Now, I've always been kind of scared to mess with the registry.  If you've ever had a message like this, I would appreciate your help in how to fix it.  I am willing to do a Regedit command if I know exactly what to delete or change.

I really miss not using jetways and getting the benefits of SODE.  Thanks.

Stan

Stan, check your registry under HKEY_LOCAL_MACHINE\Software\Lockheed Martin. Make sure that the "SetupPath" key under each one points to the proper location.

Open a powershell window and paste this in it to check it quickly -> gci 'HKLM:\SOFTWARE\Lockheed Martin'

When I run it, I see:

PS C:\WINDOWS\system32> gci 'HKLM:\SOFTWARE\Lockheed Martin'
 

Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin
Name                           Property                                                        
----                           --------                                                        
Prepar3D v5                    License   : Academic                                            
                               SetupPath : E:\P3D5\Prepar3D v5\                                
Prepar3D v5 Content            SetupPath : E:\P3D5\Prepar3D v5\                                
Prepar3D v5 Scenery            SetupPath : E:\P3D5\Prepar3D v5\                                
Prepar3D v5 SDK                SetupPath : E:\P3D5\Prepar3D v5\SDK\                            

 

14 minutes ago, MDFlier said:

Stan, check your registry under HKEY_LOCAL_MACHINE\Software\Lockheed Martin. Make sure that the "SetupPath" key under each one points to the proper location.

Open a powershell window and paste this in it to check it quickly -> gci 'HKLM:\SOFTWARE\Lockheed Martin'

When I run it, I see:

PS C:\WINDOWS\system32> gci 'HKLM:\SOFTWARE\Lockheed Martin'
 

Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin
Name                           Property                                                        
----                           --------                                                        
Prepar3D v5                    License   : Academic                                            
                               SetupPath : E:\P3D5\Prepar3D v5\                                
Prepar3D v5 Content            SetupPath : E:\P3D5\Prepar3D v5\                                
Prepar3D v5 Scenery            SetupPath : E:\P3D5\Prepar3D v5\                                
Prepar3D v5 SDK                SetupPath : E:\P3D5\Prepar3D v5\SDK\                            

 

Here's what I see in the Powershell:

Name                           Property
----                           --------
Prepar3D v4                    License   : Professional
                                        SetupPath : S:\P3d V4.5\
Prepar3D v4 Content      SetupPath : S:\P3d V4.5\
Prepar3D v4 Scenery     SetupPath : S:\P3d V4.5\
Prepar3D v5                    License   : Professional
                                        SetupPath : S:\P3d V5.1\
Prepar3D v5 Content      SetupPath : S:\P3d V5.1\

Prepar3D v5 Scenery      SetupPath : S:\P3d V5.1\

To the best of my knowledge, the path is correct.  On my S drive.

The Registry all seems normal to with the paths being correct.

Stan ????

Check the SODE log file to see what it thinks it found...

C:\ProgramData\12bPilot\SODE\log\PLTMGR_DETECTION.log

One other thing to check is to see if you have an older entry in the 32 bit registry. There shouldn't be one, but if there is it will confuse the SODE installer.

gci 'HKLM:\Software\WOW6432Node\Lockheed Martin'

If you see anything here, delete the keys using regedt32.

Edited December 8, 20205 yr by MDFlier

Do you have the SDK installed some programs need this ADE will.

Edited December 8, 20205 yr by G-RFRY

14 minutes ago, MDFlier said:

Check the SODE log file to see what it thinks it found...

C:\ProgramData\12bPilot\SODE\log\PLTMGR_DETECTION.log

One other thing to check is to see if you have an older entry in the 32 bit registry. There shouldn't be one, but if there is it will confuse the SODE installer.

gci 'HKLM:\Software\WOW6432Node\Lockheed Martin'

If you see anything here, delete the keys using regedt32.

Here's what I found in ProgramData.  It sure doesn't look right to me.

Trying to detect 'FSX'
Hive: HKLM
Registry Path 32: SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0
Registry Path 64: SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
Key name: SetupPath
Trying Path 32...
>>> ERROR: Unable to find 'SetupPath' key in Registry!
>>> ERROR: void QueryValue
---
Trying to detect 'FSX-SE'
Hive: HKLM
Registry Path 32: SOFTWARE\Wow6432Node\DovetailGames\FSX
Registry Path 64: SOFTWARE\DovetailGames\FSX
Key name: Install_Path
Trying Path 32...
>>> ERROR: Unable to find 'Install_Path' key in Registry!
>>> ERROR: void QueryValue
---
Trying to detect 'P3Dv2'
Hive: HKLM
Registry Path 32: SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v2
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v2
Key name: SetupPath
Trying Path 32...
>>> ERROR: Unable to find 'SetupPath' key in Registry!
>>> ERROR: void QueryValue
---
Trying to detect 'P3Dv3'
Hive: HKLM
Registry Path 32: SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v3
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v3
Key name: SetupPath
Trying Path 32...
>>> ERROR: Unable to find 'SetupPath' key in Registry!
>>> ERROR: void QueryValue
---
Trying to detect 'P3Dv4'
Hive: HKLM
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v4
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v4
Key name: SetupPath
'SetupPath' key found in 64-Bit registry -> Install Path = 'S:\P3d V4.5\'
Platform SimObjects file name: 'simobjects.cfg'
Platform Roaming path: 'C:\Users\Stan\AppData\Roaming\Lockheed Martin\Prepar3d v4'
---
Trying to detect 'P3Dv5'
Hive: HKLM
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v5
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v5
Key name: SetupPath
'SetupPath' key found in 64-Bit registry -> Install Path = 'S:\P3d V5.1\'
Platform SimObjects file name: 'simobjects.cfg'
Platform Roaming path: 'C:\Users\Stan\AppData\Roaming\Lockheed Martin\Prepar3d v5'
---
Trying to detect 'FSX'
Hive: HKLM
Registry Path 32: SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0
Registry Path 64: SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
Key name: SetupPath
Trying Path 32...
>>> ERROR: Unable to find 'SetupPath' key in Registry!
>>> ERROR: void QueryValue
---
Trying to detect 'FSX-SE'
Hive: HKLM
Registry Path 32: SOFTWARE\Wow6432Node\DovetailGames\FSX
Registry Path 64: SOFTWARE\DovetailGames\FSX
Key name: Install_Path
Trying Path 32...
>>> ERROR: Unable to find 'Install_Path' key in Registry!
>>> ERROR: void QueryValue
---
Trying to detect 'P3Dv2'
Hive: HKLM
Registry Path 32: SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v2
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v2
Key name: SetupPath
Trying Path 32...
>>> ERROR: Unable to find 'SetupPath' key in Registry!
>>> ERROR: void QueryValue
---
Trying to detect 'P3Dv3'
Hive: HKLM
Registry Path 32: SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v3
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v3
Key name: SetupPath
Trying Path 32...
>>> ERROR: Unable to find 'SetupPath' key in Registry!
>>> ERROR: void QueryValue
---
Trying to detect 'P3Dv4'
Hive: HKLM
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v4
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v4
Key name: SetupPath
'SetupPath' key found in 64-Bit registry -> Install Path = 'S:\P3d V4.5\'
Platform SimObjects file name: 'simobjects.cfg'
Platform Roaming path: 'C:\Users\Stan\AppData\Roaming\Lockheed Martin\Prepar3d v4'
---
Trying to detect 'P3Dv5'
Hive: HKLM
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v5
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v5
Key name: SetupPath
'SetupPath' key found in 64-Bit registry -> Install Path = 'S:\P3d V5.1\'
Platform SimObjects file name: 'simobjects.cfg'
Platform Roaming path: 'C:\Users\Stan\AppData\Roaming\Lockheed Martin\Prepar3d v5'
---
--- END ---
 

Edited December 8, 20205 yr by spilok

12 minutes ago, G-RFRY said:

Do you have the SDK installed some programs need this ADE will.

No I don't.  SODE used to work for me perfectly before I reinstalled P3dv5 when the last hotfix came out.

Stan

3 minutes ago, spilok said:

Here's what I found in ProgramData.  It sure doesn't look right to me.

<snip>
Trying to detect 'P3Dv4'
Hive: HKLM
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v4
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v4
Key name: SetupPath
'SetupPath' key found in 64-Bit registry -> Install Path = 'S:\P3d V4.5\'
Platform SimObjects file name: 'simobjects.cfg'
Platform Roaming path: 'C:\Users\Stan\AppData\Roaming\Lockheed Martin\Prepar3d v4'
---
Trying to detect 'P3Dv5'
Hive: HKLM
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v5
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v5
Key name: SetupPath
'SetupPath' key found in 64-Bit registry -> Install Path = 'S:\P3d V5.1\'
Platform SimObjects file name: 'simobjects.cfg'
Platform Roaming path: 'C:\Users\Stan\AppData\Roaming\Lockheed Martin\Prepar3d v5'
---
--- END ---
 

Actually, it looks okay. Mine is identical (paths adjusted to my system, of course).

19 minutes ago, MDFlier said:

Check the SODE log file to see what it thinks it found...

C:\ProgramData\12bPilot\SODE\log\PLTMGR_DETECTION.log

One other thing to check is to see if you have an older entry in the 32 bit registry. There shouldn't be one, but if there is it will confuse the SODE installer.

gci 'HKLM:\Software\WOW6432Node\Lockheed Martin'

If you see anything here, delete the keys using regedt32.

Not sure HOW to perform the 2nd part of this message.  How to I check the gci 'HKLM:\Software\WOW6432NODE\Lockheed Martin?

 

Just run powershell again and paste that whole line in it.

gci 'HKLM:\Software\WOW6432Node\Lockheed Martin'

This is looking in a different location - the WOW6432Node is where the old 32 bit registry entries go in Win 10. The other command you ran looked at the 64 bit entries.

If it shows any keys present, you can run regedt32 and delete them. You only need the 64 bit entries for P3D

Edited December 8, 20205 yr by MDFlier

16 minutes ago, MDFlier said:

Just run powershell again and paste that whole line in it.

gci 'HKLM:\Software\WOW6432Node\Lockheed Martin'

This is looking in a different location - the WOW6432Node is where the old 32 bit registry entries go in Win 10. The other command you ran looked at the 64 bit entries.

If it shows any keys present, you can run regedt32 and delete them. You only need the 64 bit entries for P3D

Here's all I see when I run that line:

    Hive: HKEY_LOCAL_MACHINE\Software\WOW6432Node\Lockheed Martin

Name                           Property
----                           --------
Prepar3D v2
Prepar3D v3

 

Have to admit...this is a little out of my level of expertise.  

Stan

Edited December 8, 20205 yr by spilok

I had that problem once and I made some notes after I resolved it. That's all I've got for that issue. Mine had the 2nd set of keys.

Thank you to all who guided me in the right direction.  I SOLVED MY SODE PROBLEM!  I found that the path in my registry listed P3d v5.1\

Well, I originally set it up that way when I installed it on my S drive.  I changed the name on the S drive to simply P3d v5 (not v5.1).  So, the registry path showed 5.1 instead of my change to 5.  I hope that makes sense...but that little .1 made all the difference in SODE recognition.  I learned  a lot from this discussion about my SODE LOG information the my Lockheed Software Registry information.

Again, thanks for pointing me towards the solution.

 

Stan

Lol. It's always the simple things. You know, it would have made it a lot easier if I had just asked you, "Is your P3D really installed in the S:\P3d V5.1\ folder?".

I'm glad it's working.

When I had that issue, it was because some sort of migration tool made a 2nd copy of the 64 bit registry keys in the 32 bit registry. I deleted them and it worked.

1 hour ago, MDFlier said:

Lol. It's always the simple things. You know, it would have made it a lot easier if I had just asked you, "Is your P3D really installed in the S:\P3d V5.1\ folder?".

I'm glad it's working.

When I had that issue, it was because some sort of migration tool made a 2nd copy of the 64 bit registry keys in the 32 bit registry. I deleted them and it worked.

Thanks again.  It's satisfying to get to the root of a problem.

Stan