I am done. I have tried 3 seprate uiautomationcore.dlls, removing fsx se one. Verifing cashe, uninstalling completely and then reinstalling, uninstalling steam, run as administrator but still! Fatal error while clicking menus. So I think the only option is to completely take out the uiautomation core from system32 and the other place. It seems to be my only option at the moment. Has anyone else done this and had any negative results?
I myself have done it with no ill results. I removed uiautomationcore.dll from system 32 and wow 64. Created a backup of the folders and store them elswere. You will however need them if you run Orbx ftx central 2 or Rex4 but I just reinstall them, do what I need them remove them.
I think I should do it. It does not seem to be a vital system componet and a majority of people have done it. Also the description on microsoft page says it is for developers so it seems to not effect the default windows. -us/library/ms747327%28v=vs.110%29.aspx It also says that it is for Windows Vista, Microsoft Windows XP, and Windows Server 2003. Not windows 10.
I myself have done it with no ill results. I removed uiautomationcore.dll from system 32 and wow 64. Created a backup of the folders and store them elswere. You will however need them if you run Orbx ftx central 2 or Rex4 but I just reinstall them, do what I need them
JSkorna is correct. The uiautomationcore.dll is a component of Microsoft.net. It is used to make sure an application runs as required by a developer, including memory management. The one in the main FSX-SE folder was put there by DTG. In FSX, the dll was used by some to fix menu crashes. It was called something like "the holy grail of fixing FSX crashes". Removing the one from the FSX-SE folder should be simple but removing the one in the Windows System folders is dangerous as those are used for all of your applications not just fsx-se. It's also very difficult to remove a Windows System file. For Windows 10, I suspect those files will be reinstalled immediately if anyone is successful in deleting them as Microsoft does not like anyone messing with their system files even in previous versions of Windows. You should search your main Windows folder for uiautomationcore.dll. It should show you several versions are installed as, according to Google, they are not backward compatible. This is why you should have at least 2.0 which was installed around the time FSX Acceleration/SP2 were released. Microsoft.net 1.1 was installed with the installation of FSX.
I have never willingly used the uiautomationcore.dll fix in the main FSX folder and never had a menu CTD. In fact, I found out an addon developer was placing a copy of the uiautomationcore.dll in my main fsx folder as I was getting unexplained crashes. I removed the dll from the main fsx folder and the crashes stopped. Many members do not use the uiautomationcore.dll "fix". I suspect DTG placed the proper version of the old uiautomationcore.dll in the main FSX-SE installation as they believe it fixes crashes so I would not remove that one too. My two-cents worth....
That's correct - -wrong-version-of-uiautomationcoredll/ . But my point was that I never ever wanted it in my main FSX directory as I did not believe in this "holy grail" fix and I have tried several times to replicate the crash w/o it in my main fsx folder and I simply cannot cause fsx to crash. It's frustrating. I turn all of my settings up and right click on the vc and open and close menu's and no joy. FSX continues to run. But, I have had crashes and many of them in the past. But they were not caused because I did not have the uiautomationcore.dll in my main fsx folder. I know exactly what caused everyone of my crashes. But, if anybody is not having crashes when they place the correct version of the uiautomationcore.dll in their main fsx directory, that makes me happy. But that's not the case as you can go into the AVSIM CTD Forum here and when I ask the person having crashes, I ask them to submit an AppCrashView report. It shows everything that loaded and I see the uiautomationcore.dll was loaded in the main fsx folder. I ask them to remove it and their crashes stop. Get out of here! How can that be!! I have proof beyond all doubts that the uiautomationcore.dll does not work as intended. It's a placebo. Look at all the crash reports in the AVSIM CTD Forum and you will see that individuals continue to get crashes/freezes no matter what version is in their main fsx folder.
I contend that maybe, just maybe, several years ago when fsx was first released, the uiautomationcore.dll in the main fsx directory probably was good and may have stopped crashes from occurring but not today with our modern and updated computer systems. We have better memory management and greatly enhanced CPU's.
Uh, what does that have to do with it? I do not have the problem. Others have the problem because they turn their settings up to the max and then blame it on the uiautomationcore.dll. I had no crashes when I had a 32 bit OS and have had no crashes with a 64 bit OS w/o the uiautomationcore.dll in my main fsx directory. Many, many other members here at AVSIM do not have the uiautomationcore.dll in their main fsx directory and have no problems.
I've been experiencing CTDs for the last 10-12 days due to this UIAutomationCore.dll with FSX-SE which is really weird because its built-in UIAutomationCore.dll should prevent these type of crashes from occurring. I've not installed any new addons or removed any addons but randomly, for the last 10-12 days, it's crashing. When I right click frequently or use the menus frequently during flight, fsx-se randomly crashes. I've:
-I've completely uninstalled FSX along with all the addons using RevoUninstaller Pro to ensure that all the shortcuts, registry entries etc. are all deleted for FSX along with ALL THE ADDONS and also double checked using PMDG's uninstall guide to uninstall FSX completely from here: -to-uninstall-and-reinstall-fsx.aspx
Yesterday, I did a fresh install IN C drive's ROOT FOLDER and NOT Program Files (x86) folder after redownloading FSX-SE and installed the following addons so far which I've been using since 2015 and had no issues..... PMDG 737 NGX, FTX Global Base & Vector, MyTraffic 6, FSUIPC 4.9 Registered. Then, during flight today with the ngx, I right clicked to change views and BOOM FSX-SE Crashed.
The uiautomationcore.dll is part of the Microsoft.net package. When it is the faulting module, it indicates you have a serious problem with one of your add-ons that needs a specific Microsoft.net to be installed. The AVSIM CTD Guide provides information on how to check for Microsoft.net errors and to make sure all of your Microsoft.net's are up to date. See page 29 of the guide. Best thing to do (and fastest) is to uninstall every add-on, run FSX-SE to make sure it is working, and then slowly start adding your add-ons again.
You might also check you anti-virus program and make sure there was no files quarantined. A lot of add-ons erroneously are identified by the anti-virus program as being trojans and viruses so they quarantine the file and it is impossible for you to run FSX-SE or the add-on until you tell your anti-virus program it was not a virus and allow the file to be installed.
Even if your issue has been resolved I had a similar problem with my FSX\Accl when I changed views or used the menus often. Charlie helped me find the culprit and since I fallowed his advice I haven't suffered any CTD Here's alnk to my topic:
There are several copies of the ntdll.dll on your computer. The one that should be in your SysWow64 folder has a version of 6.1.7601.17725. Look for the same version and copy it over to the SysWow64 folder. Do not understand how you could be missing the ntdll.dll in that folder though.
The Uiautomationcore.dll is only suppose to be placed in your main fsx folder. You should never try to replace the Windows 7 version. If used, only the Vista version should be placed in your FSX folder.
Uiautomationcore.dll - The uiautomationcore.dll only fixes one problem and that's a crash if you repeatedly hit the FSX menu bar. I personally cannot replicate this crash and have tried several times to crash my FSX by repeatedly clicking on the fsx menu bar. No joy... I really think the menu bar crash is caused by high settings where fsx is running short of memory by the constant hitting on the menu bar. I do not have the uiautomationcore.dll in my main fsx folder and never have (except for testing). The uiautomationcore.dll belongs with the Microsoft.net framework packages and, developers of FSX and FSX addons require dotnet versions 1.1 thru 4.5 installed to make their products work properly. I believe the Vista version of dotnet is 1.1 as it is installed with FSX/Acceleration. Installing the Uiautomationcore.dll in your main fsx folder could create more problems so, if it doesn't work, take it out. I have seen several reports here already (including me) where CTD's have stopped after removing the Vista version from the Main FSX folder.
I had deleted one time also the Uiautomationcore.dll from FSX folder but the problem did still occured. I try this time to delete all Uiautomationcore.dlls from System32 + Syswo64 + fsx , and see what happens.
7fc3f7cf58