Registry Path 32: SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0 If you see anything here, delete the keys using regedt32. Gci 'HKLM:\Software\ WOW6432Node\Lockheed Martin' There shouldn't be one, but if there is it will confuse the SODE installer. One other thing to check is to see if you have an older entry in the 32 bit registry. The Registry all seems normal to with the paths being correct.Ĭheck the SODE log file to see what it thinks it found.Ĭ:\ProgramData\12bPilot\SODE\log\PLTMGR_DETECTION.log To the best of my knowledge, the path is correct. Prepar3D v5 Scenery SetupPath : S:\P3d V5.1\ Prepar3D v5 Content SetupPath : S:\P3d V5.1\ Prepar3D v4 Scenery SetupPath : S:\P3d V4.5\ Prepar3D v4 Content SetupPath : S:\P3d V4.5\ Prepar3D v5 SDK SetupPath : E:\P3D5\Prepar3D v5\SDK\ Prepar3D v5 Scenery SetupPath : E:\P3D5\Prepar3D v5\ Prepar3D v5 Content SetupPath : E:\P3D5\Prepar3D v5\ Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin PS C:\WINDOWS\system32> gci 'HKLM:\SOFTWARE\Lockheed Martin' Open a powershell window and paste this in it to check it quickly -> gci 'HKLM:\SOFTWARE\Lockheed Martin' Make sure that the "SetupPath" key under each one points to the proper location. Stan, check your registry under HKEY_LOCAL_MACHINE\Software\Lockheed Martin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |