Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

Application Halted When Starting GIT

I purchased GIT today because I want to use my GoFlight MCP Pro and EFIS with my PMDG aircraft. After downloading and installing the software, I go to run it and it give me a big error saying the application was halted and it quits. I have the latest drivers from GoFlight (2.28.0) and the lastest version of GIT. I have reinstalled many times to no avail. Also, I was looking through the forums and saw the suggestions of renaming the My Documents/GoFlight Interface Tool, but that did nothing. I also followed all the instructions in the installation guide and still no luck. I have been working on this for hours and have no idea what else to try. Any help is appreciated, as I have seen what this software can do and I really need to use it. Thanks so much.

-Addison Grose

Comments

  • My first thought is this from the FAQ:

    The Interface Software Crashes After PMDG SDK License Acceptance

    This occurs when a system has had its uiautomationcore.dll file replaced in the Windows\System32 directory. Although this fix is valid to resolve FSX crashes, the advice to replace the file in the Windows sub-directory is wrong because it then affects all the software on the system and causes problems.

    If you wish to apply the uiautomationcore.dll fix, simply copy the corrected file into the FSX directory and leave the existing file in the Windows\System32 intact if you didn't replace it; otherwise replace the changed file with the original version to get GIT working.
  • Thanks for the quick reply! The original file is in System32 and I tried doing a copy instead of replacing, like you said, but still no luck. Any other suggestions?
  • The only other thing I can think it could be if you are absolutely certain you have not replaced uiautomationcord.dll in c:\windows\system32 is the .NET Framework is not up to date. See the system requirements in the user guide for the .NET versions needed.

    Best wishes
    Steve
  • I'm not completely certain if I have not replaced it. In Windows/System32, it shows the UIAutomationCore.dll from 7/13/2009, which makes me feel like it is the original. Is there any way to check? Thanks.
  • Well according to the link below, the Windows 7 version should have a date of 2015 at least. I suspect 2009 version is for Vista and used for the FSX crash:

    https://support.microsoft.com/en-us/help/3005770/applications-crash-when-automated-by-a-ui-automation-client-app-in-win
  • Hmm... Ok I will try to install that one and see if that does anything. It is possible I replaced it with the Vista one and I thought it was something else. Also, I noticed .NET Framework 3.5 was not installed, so I went to install that and it’s not installing for me. Do you have a link I could use to download that? Thanks.
  • Running Windows Update should make sure you have the latest .NET Framework installed.
  • edited July 2017
    I ran Windows Update and it said everything was up to date. Hopefully just putting the uiautomationcore.dll will fix it.
  • Still no luck. I have the most recent uiautomationcore.dll and I only used a copy like you said, but it is still crashing. I have met all of the system requirements too. I don't know what to do next! Hope you can help.
  • I'm sure its an issue with uiautomationcore.dll. Someone using a game had a very similar error and the following thread offers some useful steps to resolve: https://steamcommunity.com/app/107410/discussions/1/492378806378110829/

    Best wishes
    Steve
  • I don't know if it was running the system file checker, or reinstalling .NET Frame as suggested in that article, but it is fixed! Thanks so much!
  • Great news!
Sign In or Register to comment.