Sadly you can't run an FSX repair on this issue because M$ in its infinite wisdom developed a repair algorithm on the FSX disc that repairs everything BUT Simconnect - basically it just looks to see whether the Simconnect files are present in the WINSYS directory and if they are it says'Ok I'll skip that then ' - i.e it doesn't check to see if they are corrupt.Peter Dowson of FSUPIC fame developed a methodology to repair Simconnect files manually but it doesn't always work (I have tried it).

I have had this problem a couple of times. Corruption can happen for a variety of reasons and the results can, once again, produce an alphabet soup of. Sim Connect is widely acknowledged in the developer community as being the achiles heel of FSX. Its not a PMDG issue - it never was.The other problem that causes sporadic CTDs is a corrupt simconnect installation. it wont point the finger at uiautomationcore. I agree with Ryan, and can vouch from experience if this dll isn't there you will get CTDs after 10-20 menu clicks but the error that 'causes' the CTD could be from any one of a thousand varieties of modules that FSX was trying to call when the system bombed i.e. dlls in the windows folder is not only pointless it is positively dangersous and if you do this you deserve everything you get.

You should put the 32 bit Vista dll in the FSX root folder because windown will always look in the root folder for it first.Deleting.

Much of the problems associated with uiautomationcore.dll is that people download the wrong versions and copy them into the wrong place.FSX needs this dynamic link library but it needs the vista 32 bit version not the XP version or the 64 bit version etc etc.

Kb2538242 win 10