Like Romain, I too only have Username/AppData/Roaming/Microsoft/FSX, but I reckon Kyle is bang on the money. I too completely wiped off any traces of the FSX Gold boxed version, then just re-installed FSX-SE from a fresh Steam account installer. Then all the PMDG aircraft slotted in seamlessly.

12 hours ago, Mejjo said:

Hi Bud,

Just tried a default aircraft and believe it or not.... Same thing happens! Freezes then crashes, So NOT just a PMDG issue, Sorry to bring it to this forum. I have no idea what else i can do. When i uninstalled FSX Boxed i did a registry clean, However i had a look through the registry and there was still a entry there for FSX boxed. Don't know if that would cause any conflict? 

Before doing a full uninstall reinstall, I suggest you try the "Verify Integrity of Game Files" function on Steam.  Won't hurt and only takes a few minutes. Go to Steam, make sure you are logged on.  Go to Library.  On the panel to the left you should see a line for FSX.  Right click on it, select "Properties," then select "Local Files," then click on "Verify Integrity of Game Files."  It should do a scan of all the FSX files on your computer.  In the past it has replaced some files, including the Simconnect current version, which may or may not have actually fixed something.

All of the folder names in a single install of FSX Steam should not have "SE" in them.  Only in a dual install of Box and Steam should they have SE.  They are as follows:

C:\Users\[NAME]\Documents\Flight Simulator X Files

C:\Users\[NAME]\AppData\Roaming\Microsoft\FSX

C:\ProgramData\Microsoft\FSX

You probably already know this, but if you do reinstall FSX Steam don't put it in a programs folder.

Mike

 

My FSX-SE is in the default location and it runs fine.

For what it's worth:

• If you have FSX alone, our aircraft will work fine.
• If you have FSX:SE alone, our aircraft will work fine.
• If you have both FSX and FSX:SE side by side, our aircraft will work fine.

...where things get weird, though, is when you have one, install the other, and then remove one. As an example, a lot of people will have FSX installed, and then install FSX:SE. Once they verify everything is okay, they'll remove FSX. This can cause issues with the registry among other things. Sometimes, people will also attempt to just drag parts of their old FSX install into the FSX:SE install. For some products, this will work. For others, this will cause issues. This is why I suggested the slash and burn method. It basically resets your installation to a base install where the registry and paths should all match up without issues.