Newbie Alert: FSX APPCRASH | UIautomationCore.dll
FSX Appcrash with UIautomationCore.dll
I know what it is like trying to get up to speed on code that was half-baked, unfinished and now discontinued. I also know that FSX is the only viable solution that meets my particular needs at this time. And, I've quickly learned that you have to accept the limitations of FSX, which are both born of incomplete source code and operating system incompatibility in more than a few places. However, if you search far enough you can typically find answers to many frustrating problems.
When a module blows its top and pukes all over FSX (forcing it to shut down), this is what the dump typically looks like:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61472.0
Application Timestamp: 475e17d3
Fault Module Name: uiautomationcore.dll
Fault Module Version: 188.8.131.52
Fault Module Timestamp: 4a5bdb1d
Exception Code: c0000005
Exception Offset: 0000e52a
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Potential Solution for Windows 7:
There have been many suggestions offered and many more tried. Most people come back and report that the "fix" did not last for very long. Some suggest the deletion of a windows system .dll file, which I do not suggest. This problem seems to vary with internal OS configuration from Vista, to XP to Win7 - either under 32bit or 64bit modes.
Two things to note for Windows 7. There are actually two (2) uiautomationcore.dll files. One located in C:\Windows\System32, and the other located in C:\Windows\SysWOW64. The appcrash dump does not tell you what to do with the .dll file, nor does it tell you which file you need to use to provide the fix to FSX.
On my box, the fix came when I copied the 32bit version of uiautomationcore.dll from the C:\Windows\System32 path, into the root install directory of FSX, which should be C:\Program Files (x86)\Microsoft Games\Microsoft Flight (provided you accepted the default install path during initial installation of FSX).
After moving the 32bit version of this file (uiautomationcore.dll) to the FSX install root, there have been no AppCrash dumps of any kind on my box.
Though FSX does run in 64bit mode, its source code was not originally developed for the 64bit operating system and may have a conflict with the 64bit version of uiautomationcore.dll. Whether this is true or not, I don't know. Whether FSX calls the 64bit, or whether one of the 64bit capable "add-on" components ends up calling the 64bit automation file, I also do not know for sure. But, I do know that somewhere along the line, during a flight simulation using a third-party (non-native) aircraft add-on, that FSX ends up attempting to use the automation file - probably the 64bit version. Why FSX cannot locate the 32bit version on its own, or if the third-party Add-On forces the issue by using the 64bit version instead of the 32bit version, is again something that I do not fully know.
What I do know, is that supplying the FSX installation environment (its root install path) with the 32bit version, solves the UIautomationCore.dll appcrash problem on my box. Your results may vary.
Move, edit, delete, cut, paste, and/or alter any operating system level dynamic link library (.dll) file at your own risk.
Last edited by SmallJet; 02-22-2013 at 12:42 AM.
Windows 7 | 6 GB RAM | Dell Inspiron 620 | 64bit | Intel Dual Core i3 3.30GHz
Intel HD Graphics | 2.08 GB VRAM | 27" LG LCD | 1920 X 1080 | 32bit Color
Flight Sim: FSX Deluxe SP2 | Live ATC Sim: None (Currently evaluating PilotEdge & VATSIM)