Preston "Keep them seperate so they dont overwrite each other" what do you mean by that and do you have a .dll that works ? I have only put one in the main folder, thanks. Ooops just saw link above to it, is that the right one?

Preston "Keep them seperate so they dont overwrite each other" what do you mean by that and do you have a .dll that works ? I have only put one in the main folder, thanks. Ooops just saw link above to it, is that the right one?

Preston is using a 64b system, which has both a SysWOW64 and Sys folder, both containing the culprit .dll file. That means two files in the same place with the same name if he moves them to a single backup folder. Preston, in your case it's fine to overwrite one and use a single backup. They're exactly alike.

Ive read that too elsewhere. However, they are different file sizes. Now, that isnt to say I did not realize they were different until I tried the fix downloading the dll. I tried the copy from system to FSX fix, and the download the dll as from the link you posted too. Neither worked until the last fix. So, at one point I may have overwritten the original trying all the fixes. One is like 543KB and the other is 719 KB. Same version number but different sizes. So, I just kept them seperate just incase. Also, when I copied the info above in my original respone, I should have removed the last part from the original thread that said to delete them. Richard, Im not sure if the same technique will work for Windows 7. If you do try it, remember that it cant be in either of the 3 locations. Just cut them and paste elsewhere, and if each is different, dont save them all into one folder. Im on probably my 20th flight right now, KSFO to KPDX, and Ive changed views and right clicked about 100 times and still rock solid. Before the fix I got a ctd EVERY SINGLE FLIGHT if I right clicked, or changed veiws several times. Well, the dreaded .dll ctd at least.

Glad you've gotten a few of the gremlins, Preston. I got my first out of memory in 3 years last night... After a 3 hour trek form Toncontin....

Preston bit confused are you using it or not using it, if you are using it which file do I use my file size is different than both of yours and how is it getting into other folders if I only place it in the main fsx folder, fyi still getting black screens, hmmm thanks.Try the light controls on the aft radio panel/pedestal. Thanks buddy

Lets give this another go lol I copy a working uiautomationcore.dll file to C:\Windows\System32 and C:\Windows\Syswow64 and C:\fsx not just the fsx folder, the file download above file size was 156kb not matcjing your file size ?

Sorry, I was tending to my flight. In Vista64 the uiautomationcore.dll file is in two system folders. The windows system 32 and syswow64 folders. I cut the dll file from both folders and saved elsewhere. I then cut and removed the one that was also in FSX. So, no uiautomationcore.dll in either system32, syswow64, or FSX. Gone from all three locations, saved elsewhere on my system.

Ok Preston, I tried that but still get black screens, crazy lol thanks for your help buddy, take care.

So as per my original response, without the deleting part LOL HERE IS THE FIX: You may have to take ownership of the files if windows stops you from deleting the file. Open CMD prompt and right click to run as administrator and then type in exactly as below substituting your windows login username where it says username: takeown /f C:\Windows\System32\uiautomationcore.dll cacls C:\Windows\System32\uiautomationcore.dll /G username:F takeown /f C:\Windows\Syswow64\uiautomationcore.dllcacls C:\Windows\Syswow64\uiautomationcore.dll /G username:F Now you can just navigate to your syswow64 and system32 folders in windows explorer and cut and paste them in a backup location. Then, remove the one thats in the FSX folder. That should be it. Just back them up somewhere else if they are different, not all in same backup location, so you dont have any in either of the 3 locations. Wow, I dont get black screens, I was just getting the dreaded uiautomationcore.dll crashes, like constantly. Havent had a single one yet since. I hope you figure it out, your system is way superior to mine. Quad Core Q9650, clocked to 4.05 stable and cool, with 8 gigs ram and gtx260.

Glad you've gotten a few of the gremlins, Preston. I got my first out of memory in 3 years last night... After a 3 hour trek form Toncontin....

OH NO! I was getting them periodically until I upgraded from 4 gigs to 8, what a world of difference. My ram was always maxed, now it sits at around 40% tops. Weird, wonder what caused the OOM error on your machine.

Howdy Guys --- Early on, like many, had the CTD problem. Ugly. When I was introduced to the UIAutomationCore.dll fix, I tried it both ways as mentioned above. The result, as far as the CTDs were concerned, was the same. CTDs completely gone. Independent of aircraft or activity in FSX. I would tend to stay with what ZackLW mentioned above because we really do not know exactly what the full scope of possible usage of this unique dll really is. We do know it is associated with the DOT NET framework within Windows. So I have left my two dlls in their places in Win7-64 unmolested and added the proper copy to the root directory of FSX. Now, my problem remains the DU panel lock up problem which just will not go away. More on this when I see how the next "fix-it" attempt goes. This one has me really frustrated. Cheers All --- Keep the Faith --- we have a great airplane here -- just needs some TLC

Howdy Guys --- Early on, like many, had the CTD problem. Ugly. When I was introduced to the UIAutomationCore.dll fix, I tried it both ways as mentioned above. The result, as far as the CTDs were concerned, was the same. CTDs completely gone. Independent of aircraft or activity in FSX. I would tend to stay with what ZackLW mentioned above because we really do not know exactly what the full scope of possible usage of this unique dll really is. We do know it is associated with the DOT NET framework within Windows. So I have left my two dlls in their places in Win7-64 unmolested and added the proper copy to the root directory of FSX. Now, my problem remains the DU panel lock up problem which just will not go away. More on this when I see how the next "fix-it" attempt goes. This one has me really frustrated. Cheers All --- Keep the Faith --- we have a great airplane here -- just needs some TLC

Thank goodness we have professionals that will follow through! Sorry to here about your freeze issues, I had a load of them before the patch. Apparently they've figured out what the issue is more or less, so not too much longer.

I have tried both ways no deal, so the new patch is going to address this ? only happens on ngx to bad have to wait I guess. Makes it really hard to follow tutorial when it crashes.

Could be tweaked ******* fsx.cfg file the new nvidia driver or directx, only things I can think of right now.

I can confirm now that I still have not had a single ctd yet since my fix. Ive also had not one single other program fail as a result of my fix.....so far. <--------key words. I luckily have not had any of the other issues others are having with the ngx, I did however for the first time last night have the red terrain "pull up" warnings on approach to RWY 28R at KPDX. Ive run that same route about 20 times without an issue and suddenly last night I got it.

Preston are you running ENB Series ?