In the past I had crashes while running the program but haven't had them since moving UIAutomation.dll to the root FSX directory.  Now, the program runs flawlessly to the completion of flight but when I hit escape to exit the flight I end up on the desktop with a blank FSX home screen stuck offscreen in the lower right.  Clicking on it does nothing.  Trying to grab the title bar and drag it does nothing.  If I click in the blue menu bar area on the right side of the home screen I can get one of the tabs to appear (Learning Center, Settings, Missions, etc.).  After that, clicking has no effect.

 

Anyone see this with their crashes?  I've thought about simply reinstalling the program to see if that fixes it but I'd like to see if anyone has any ideas before I do that.  I've attached a screen grab showing the symptoms.

 

Thanks,

Mike

 

 

Did this start after placing the Uiautomationcore.dll in the main fsx folder?  The Uiautomationcore.dll is part of the dotnet framework package used by developers to make sure their product runs properly, including managing the memory.  The old Vista version that should be placed in the main fsx folder only fixes crashes related to repeated hits on the FSX menu.  It does not fix any other type of crash.  So you received a placebo when you placed the Vista dll in your main fsx folder in regards to completing a flight.  If you look at the various posts in this CTD Forum you will see that many people have the Vista version of the Uiautomationcore.dll in their main FSX folder and still get crashes and cannot complete a flight.  You have other major issues with your system which need to be corrected. 

 

I like the Bing background program.  I have it too and get a different desktop every day.  However, you should click on the Bing icon in the task bar and exit from it after Windows starts up.  I have found all kinds of problems with the icon bar running in the background on the desktop with FSX running.  Either minimize the Bing bar or exit the program completely by right clicking on the icon (it will not affect your background).  This could be the issue you are having.  I don't know as this is the first time I have seen the FSX anomaly when you exit this a flight.  There may be a bug with using the Esc key to exit a flight.  It might be better to just use Ctrl+C and completely exit the program then restart.  You are using an extremely large amount of Virtual Memory by doing what you are doing especially after a long flight.  Check your fsuipc.log and see if you see any warnings about running out of memory (the log has to be opened right after a crash or anomaly as the log is rebuilt every time you restart FSX).

 

Best regards,

Jim