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!

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): Do you have any idea what might have happened here? Did I hit some kind of edge case?

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.

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: 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.