Hi everyone.

 

I was just testing out my system about a half hour ago and I encountered a CTD. I went over to google and looked for a fix, and I haven't heard about this method before, so I thought I'd put it on the forums. It looks like you have to completely wipe every UIAutomationcore.dll of your system. I have yet to try the results.

 

http://answers.micro...42-146414087ec5

 

EDIT: I didn't intend to post twice, this seems to be a forum bug.

Post deleted by me.

I did that once, seemed to work. However it seems that just replacing all those files with older Uiautomationcore files from Vista & placing one to your FSX folder does just the same, thats what I have done later after I encountered another problem (which after all wasn't related to Uiautomationcore at all, but other Windows problem) At least I haven't had any inflight crashes anymore.

The question that opens for me is: is UIAutomationCore.dll needed for other programs and is it vital to windows? It comes with Windows and maybe other programs are relying on it.

 

Also, it's apparently introducing another problem: when you quit FSX in flight, you get dysfunctional desktop.

I have yet to try the results.

 

I wouldn't try. As someone else stated in the link you posted, uiautomationcore.dll is part of the Microsoft.net framework packages. The latest version 4 is installed with Windows 7. Other packages are installed if required by FSX/Acceleration or an addon commercial developer. You need all versions of dotnet from version 1 to version 4 as they are not backward compatible. Check in your C:\Windows\Microsoft.netFramework folder and look to make sure you have v1.0.3705 thru v4.0.30319 installed. Also run Windows update to make sure you have the latest updates for each version installed. They are constantly updated by Microsoft.

 

Best regards,

Jim

Ok. Thanks for the reply.

Also, it's apparently introducing another problem: when you quit FSX in flight, you get dysfunctional desktop.

 

can't confirm this. Just tried it!

But I have always windowed mode. Maybe this is a difference...

Yeah no problem with desktop when running windowed mode I can remember. Only program I found not to function after it was some bad Microsoft video editing program which game with the computer.

ok found a program which is not working correctly without UIautomation:

 

the Aerosoft launcher :nea:

I think Windows Media Player also depends on uiautomationcore.dll.

Ah yes, I remember this issue. What happens is FSX CTDs after a certain number of menu bar clicks (25 or so). I don't think the UIAutomationcore.dll fix is meant to solve any other CTDs beyond the menu issue.

 

Hi everyone.

 

I was just testing out my system about a half hour ago and I encountered a CTD. I went over to google and looked for a fix, and I haven't heard about this method before, so I thought I'd put it on the forums. It looks like you have to completely wipe every UIAutomationcore.dll of your system. I have yet to try the results.

 

http://answers.micro...42-146414087ec5

 

EDIT: I didn't intend to post twice, this seems to be a forum bug.

 

The existance of the .dll is not the problem, I believe the problem is that FSX needs the Vista version of UIAutomationcore.dll instead of the Windows 7 version, and it should be placed in the FSX folder.

And supposedly FSX will communicate with the .dll in the FSX folder, not the one in the Windows32 folder, so you shouldn't even need to rename or remove the original.

 

I don't think simply renaming or removing this file will have solved anything. At least not the menu bar click CTD.