FSUIPC installer is unable to edit the DLL.XML file - it tries to locate FSX-SE exclusively, only FSX exists

[Thomas.]

Hi Pete,

I recently uninstalled FSX:SE and removed all left over data in the AppData and ProgramData folders in order to start over with a fresh new installation of FSX:SE (I did not clean the registry, which I now regret). Unfortunately I have run into an issue with the FSUIPC installer I've never experienced before. Here's a full copy of the install log:

Quote

Installer for FSUIPC4.DLL version 4.975a

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"AppPath"
... NOT found! ...

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=F:\Steam\steamapps\common\FSX

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX-SE:
SetupPath="F:\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.60905.0*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.62615.0*"
    Found the path, now trying "C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_1ed9da73c880e429_10.0.62615.0_none_69960aa860d87067\SimConnect.dll"
Found SimConnect build 10.0.62615.0
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.61242.0*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.61259.0*"
    Found the path, now trying "C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll"
Found SimConnect build 10.0.61259.0
Checking if there's already a version of FSUIPC4 installed in:
       F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... Version 4.975a found.
FSX-SE Modules folder already exists.
Okay -- installed FSUIPC4 into "F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Thomas\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\RDV GRAPHICS SERVICE\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Thomas\AppData\Roaming"
 ... No FSX_SE.CFG there
Cannot edit the DLL.XML file to activate FSUIPC.
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "The 2016 List of FSX and P3D Controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC CHECK
Checking FSUIPC registration ...
Registration check for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************
 

I have searched for a solution on the internet, but none of the cases I found matched my situation (most of them involved having FSX and FSX:SE coexist, or at least having been installed once on the same system, which is not the case here). Hence I am reaching out to you.

Is there anything I could do to resolve this without tinkering with file paths and names?

On another interesting side note, the installer somehow found a reference to Prepar3D v3 in the registry even though I've never used Prepar3D before (I don't even have a license for it). I've let FSUIPC fix that though.

[Pete Dowson]

4 minutes ago, Thomas. said:

I have searched for a solution on the internet, but none of the cases I found matched my situation

The only problem I see in the Installer logging is that the DLL.XML file couldn't be edited. You need to check why. Have you actually run FSX-SE since reinstalling? Is not, that will be the reason there's no FSX_SE.CFG file.

If you have run it beforehand, where is your FSX-SE.CFG file? It should certainly be in one of the folders searched according to the Log!

Also, don't forget to run the Installer "as administrator".

Pete

 

 

[Thomas.]

Yes, I have run FSX:SE several times since the reinstallation (the first time being right after Steam finished installing it). The actual fsx.CFG is located in "C:\Users\Thomas\AppData\Roaming\Microsoft\FSX", although there's no trace of a "DLL.XML" in there. I vaguely remember it being there in my previous installation, not sure if that's unusual, is FSX:SE supposed to generate that file in its absence by default?

The FSUIPC installer is running as administrator.

Edited August 22, 2020 by Thomas.

[Pete Dowson]

41 minutes ago, Thomas. said:

Yes, I have run FSX:SE several times since the reinstallation (the first time being right after Steam finished installing it). The actual fsx.CFG is located in "C:\Users\Thomas\AppData\Roaming\Microsoft\FSX",

Aha! So you have an FSX.CFG rather than an FSX_SE.CFG, which is what the installer is looking for.  With my last install for FSX-SE I got this is the log:

Looking in "C:\Users\JohnG\AppData\Roaming"
Found FSX.CFG in "C:\Users\JohnG\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now in my case it was actually looking for an FSX.CFG rather than an FSX_SE.CFG.  I think this is because of your EXE being found as:

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=F:\Steam\steamapps\common\FSX

whilst mine is:

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\

So, somehow you have a sort of cross-over FSX/FSX_SE install. In my FSX-SE installation I have no FSX-SE.exe file. mine installed as FSX.exe. Did you nename the EXE? If so it is that which is confusing my Installer.

Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)

Anyway, please see if making a copy of your FSX.CFG and renaming the copy as FSX_SE.cfg will work with an installer re-run.

Pete

 

 

[Thomas.]

Something quite strange just happened - I followed your instruction, merely creating a copy of FSX.CFG and renaming it to FSX_SE.CFG. Re-ran the installer, and it worked! But for a very different reason.

Here's the install log, notice how this time it did find the "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0" registry key, causing it to also look for FSX rather than FSX_SE only (I did nothing else than what I mentioned above):

Quote

Installer for FSUIPC4.DLL version 4.975a

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"AppPath"
... >>>  OK! FOUND FSX!  <<< ...
     AppPath=F:\Steam\steamapps\common\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=F:\Steam\steamapps\common\FSX

************ BUT this is the same path as for FSX! Will only install for FSX-SE ************

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX-SE:
SetupPath="F:\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.60905.0*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.62615.0*"
    Found the path, now trying "C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_1ed9da73c880e429_10.0.62615.0_none_69960aa860d87067\SimConnect.dll"
Found SimConnect build 10.0.62615.0
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.61242.0*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.61259.0*"
    Found the path, now trying "C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll"
Found SimConnect build 10.0.61259.0
Checking if there's already a version of FSUIPC4 installed in:
       F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... Version 4.975a found.
FSX-SE Modules folder already exists.
Okay -- installed FSUIPC4 into "F:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Thomas\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\RDV GRAPHICS SERVICE\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Thomas\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking for the current user's Application Data path: 
... found as "C:\Users\Thomas\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\RDV GRAPHICS SERVICE\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Thomas\AppData\Roaming"
 ... No FSX.CFG there
Looking for the current user's Application Data path: 
... found as "C:\Users\Thomas\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\RDV GRAPHICS SERVICE\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Thomas\AppData\Roaming"
Found FSX.CFG in "C:\Users\Thomas\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... No previous DLL.XML found, creating new one (for FSUIPC4 only).
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "The 2016 List of FSX and P3D Controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC CHECK
Checking FSUIPC registration ...
Registration check for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************
 

Do you have any idea what might have happened here? Did I hit some kind of edge case?

[Pete Dowson]

8 minutes ago, Thomas. said:

Do you have any idea what might have happened here? Did I hit some kind of edge case?

Sorry, I don't know. I don't think it is time-related. Could something (not necessarily related) have changed the order of things in the Registry? The installer will believe the first valid link it gets for the Install folder.

Pete

 

[Thomas.]

Not that I'm aware of at least. However, I've given it some thought, during the first run of the FSUIPC installer I gave permission to fix the leftover registry entry of the previous FSX:SE installation (which was installed on a different drive, so it recognized that the path was not correct). Then of course I ran into this issue. During the initial troubleshooting I did fire up FSX:SE for a brief moment. Perhaps the combination of the removal of the old registry entry and then starting FSX:SE somehow fixed the registry? That's really all I can think of, although I ran the FSUIPC installer several times in the mean time as well, so if this is indeed what caused it to work then I would imagine it should have worked sooner than it did... oh well

Thanks for the prompt support Pete!

Edited August 22, 2020 by Thomas.

[mjl1966]

I did fresh install of FSX SE about a month ago.  Let me be clear: This is a fresh SE install on a new OS hard drive.  FSX boxed has never been here.

FSUIPC 4.977:

Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one

 

And this:

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=C:\STEAM\steamapps\common\FSX

************ BUT this is the same path as for FSX! Will only install for FSX-SE ************

 

and lots of this:

... No FSX_SE.CFG there

My reality:

AppData\Roaming\Microsoft\FSX\fsxse.CFG


Indeed, there is nothing with "fsx_se" in my entire appdata folder structure. 

If I rename fsxse.cfg to fsx_se.cfg, then FSUIPC is happy. 

HOWEVER

If I change anything in my actual FSX SE configuration (I reset unlimited fuel for example), those changes are saved to fsx.cfg. So, for whatever reason, my FSX SE install has never heard of FSX_SE.CFG nor does it use it.

ymmv, but this is what I see.

Either way, FSUIPC still can't edit xml file, which is alive and well in appdata\roaming\microsoft\fsx.  I hacked it with this:

<Launch.Addon>
    <Name>FSUIPC</Name>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>   

And all seems to be well so far.

So, in summary, I had to rename fsx.cfg to fsx_se.cfg to make FSUIPC happy although fsx_se.cfg isn't actually used by fsx.  And I had to manually add FSUIPC entry to dll.xml.

[John Dowson]

So the issue is that the installer is not determining the correct path for your DLL.xml file? If so, please attach your FSUIPC4 Install.log file.

Don't worry about those other message discrepancies - they are normal and are for historic reasons. Don't read anything into them, they are for me for analytic purposes.

I can look into why the correct location of your DLL.xml file was not located, but FSUIPC4 and its installer has been closed for development/updates for many years now, and so I will not be making any changes.

John