How do I fix FSX menu crashes with UIAutomationCore.dll?

FSX menu crashes linked to UIAutomationCore.dll are usually fixed by placing a known-good, legacy 32-bit copy of the DLL beside fsx.exe, so FSX loads it locally. Confirm the faulting module first, never replace the Windows system DLL, and remove any old local workaround before testing FSX: Steam Edition.

How do I confirm UIAutomationCore.dll is causing the crash?

The workaround is appropriate when FSX crashes while opening, closing or repeatedly using its menu bar and Windows identifies UIAutomationCore.dll as the faulting module.

1. Reproduce the crash: note whether it happens specifically when selecting an FSX menu or right-click menu.
2. Open Event Viewer: run eventvwr.msc, then examine the recent Application Error under Windows Logs > Application.
3. Read the crash entry: check that the application is fsx.exe and the faulting module is UIAutomationCore.dll. Wording varies slightly between Windows versions.

How do I install the UIAutomationCore.dll fix safely?

For boxed FSX, the established workaround uses the Microsoft-signed 32-bit Vista SP1-era UIAutomationCore.dll, commonly identified as version 6.0.6001.18000, placed in the same directory as fsx.exe.

1. Update boxed FSX first: install Service Pack 2 or Acceleration as appropriate. Close FSX before changing any files.
2. Find the executable folder: the usual boxed location is C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X. A typical Steam location is C:\Program Files (x86)\Steam\steamapps\common\FSX, although a custom Steam library will be elsewhere.
3. Inspect existing copies: if UIAutomationCore.dll is already beside fsx.exe, rename it temporarily rather than overwriting it. Check its architecture and version under file properties.
4. Obtain the correct file: use a legitimate, trusted Microsoft-signed 32-bit copy whose origin you can verify. FSX is a 32-bit application even on 64-bit Windows. Do not use an anonymous DLL download or substitute a 64-bit file.
5. Copy it beside fsx.exe: place the file in the main FSX directory—not Modules, an aircraft folder or a Windows system directory.
6. Leave Windows untouched: do not overwrite anything in System32 or SysWOW64, and do not run regsvr32. The fix works through application-local loading and requires no registration.
7. Test and revert if necessary: start FSX and operate the menus that previously triggered the crash. If stability becomes worse or the faulting module changes, close FSX and remove the local DLL.

Our full FSX fatal-error troubleshooting sequence covers this workaround alongside compatibility settings, add-on isolation and clean-reinstall checks.

Does the fix apply to FSX: Steam Edition?

FSX: Steam Edition should normally be tested without a legacy local DLL first because its executable differs from boxed FSX and includes later stability changes.

If a copied UIAutomationCore.dll is already in the Steam FSX directory, rename it and retest. Steam file verification may leave untracked files in place, so verification alone does not prove that the local DLL has gone.

Only try the 32-bit local workaround in Steam Edition when the event log repeatedly names UIAutomationCore.dll. If the crash started after installing a legacy aircraft, gauge or menu utility, check the boxed-FSX versus Steam add-on compatibility issues before altering system components.

Why does FSX still crash after adding the DLL?

If the correct local DLL does not stop the menu crash, either FSX is loading the wrong file or UIAutomationCore.dll was not the underlying cause.

• Confirm the filename is exactly UIAutomationCore.dll; hidden extensions can produce an accidental .dll.dll filename.
• Verify that the DLL is 32-bit and located directly beside the active fsx.exe, particularly if boxed FSX and Steam Edition are both installed.
• Remove other UIAutomationCore copies from the FSX directory and test one known-good file at a time.
• Test with a default aircraft and no optional menu-integrating utilities, overlays or legacy gauges.
• Check a fresh Event Viewer entry after every test. A different faulting module requires a different repair rather than another DLL replacement.