DO NOT USE UIAtomationCore.dll IN WINDOWS 8!!!

 

Although this is the only trick in the book that worked for win8

Furthermore after applying this trick everything started to work as it should;

Including additional tweak in fsx.cfg that didn’t seem to take affect prior to applying this.

 

WARNING!!! APPLYING UIAtomationCore.dll IN WINDOWS 8 WILL BREAK METRO INTERFACE!!!

THIS WILL STRIP OPERATING SYSTEM AND USER INTERFACES ELEMENTS,

WITHOUT ABILITY TO REPAIR OTHER THEN SYSTEM RESTORE!!!

I heard otherwise...Where are you putting the file?

Why are you even using FSX on Win 8? What is wrong with Win 7? Why create problems for yourself when Win 7 runs FSX perfectly ok?

Come on Graham....if everyone had that attitude (as much as i agree, dont fix what aint broken) We would still have mobile fones in briefcases.

 

We have to try things to see if its better...its human nature.

i been tinkering aroud with win8, i have to say i like it alot! (once i go t the hang of the new flow in it, it flys!)

fsx was the next thing to load, it run bad no matter what i did

removing the dll made fsx come to life, better then my win7 fsx expriance

but i was left with stripped down version of metro and UI

 

on a side note, win8 comes alomost tweaked to the bone out the box

as apose to earlier concept MS used, leave it all on!

it runs sweet fully loaded @600mb cashd 90% of the time

win7 runs sluggish and with twice the resurces comaperd to win8!

 

try it!

 

ps: lets not get distracted here; this isnt win8 fsx review

just a warning to fwloew pilots out there; trying to get fsx runing right on win8

I heard otherwise...Where are you putting the file?

 

i tried every which way possible

Dropped it in fsx root, used the vista version, used in7 version both 64&32

 

The only think that worked was to actually delete them all UIAtomationCore.dll

From fsx root dir, system32 & syswow64, that broke metro and related UI

 

But that made fsx like I’ve never seen it run before on my box, all fsx.cfg tweaks started working in harmony

(and I don’t have a killer system, a generic board with quad core proc; 4GB & NVidia 8400GS (256mb))

 

i believe the built-in explorer 10 (not browser) is using the dll in conjunction with the new ribbon interface and other enhancements

i tried every which way possible

Dropped it in fsx root, used the vista version, used in7 version both 64&32

 

The only think that worked was to actually delete them all UIAtomationCore.dll

From fsx root dir, system32 & syswow64, that broke metro and related UI

 

But that made fsx like I’ve never seen it run before on my box, all fsx.cfg tweaks started working in harmony

(and I don’t have a killer system, a generic board with quad core proc; 4GB & NVidia 8400GS (256mb))

 

i believe the built-in explorer 10 (not browser) is using the dll in conjunction with the new ribbon interface and other enhancements

 

If you put it in the FSX root, nothing else will even see it unless your FSX root is in the system path, which is unlikely. Never touch the file in the system directories; your're asking for trouble if you do that. Ever since the DOS operating system its always been like this; an executable will look in the folder that it was run out of (working directory) for all resources that it needs. If it doesn't find a file, it searches directories in the system path, if it still doesn't find a file, it throws an error. By putting the file in the FSX root, FSX will find that one first and not use the one in the system directory. But every other program will use the one in the system directory. If you're still having problems, you might have the wrong version of the dll.

 

My understanding from others, is that its works fine in Win8; same as Win7.

 

And just to be clear, this is not a trick or a tweak. The sole purpose is to prevent FSX from crashing to desktop when using the FSX menus more than a few times.

this fix had made a huge difference on my win 8 like nothing else did

it goes beyond just the crashing issue, it solved the crashing issue

and for some reason started accepting all sfc.cfg tweaks

 

applying this fix in Win8 will brake metro (Win8 x64 ENT)

anyone telling you otherwise; didn't apply UIAtomationCore.dll fix on win8 final release!

 

still trying to figure out how to reverse this on Win8 before i restore from image

This is an automatic message.

 

This topic has been moved from "Flight Simulator Tips and Tricks" to "MS FSX Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
  
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  
• The images might not have been "illustrative" or "explanatory" in nature.
  
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
  

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

If you put it in the FSX root, nothing else will even see it unless your FSX root is in the system path, which is unlikely. Never touch the file in the system directories; your're asking for trouble if you do that.

That pretty much sums it up so far.

 

Maybe the OP's 'warning' should point out that, if one replaces the system file (which wasn't a good idea with Win7 too), it's more justified. One can also find some posts from Avsim members using that fix (properly), being happy as the menu crashes went away. Just like in Win7.

 

The thing which can't be repeated often enough is to backup your files before changing them. If those few kilobytes of the uiautomationcore.dll really caused the trouble, they were in need for a backup. Sorry to say.

 

Besides, CAPS LOCK thread titles always come in.. well, you know, overly dramatic. :unsure: Maybe it's just me though.

Yeah OP apparently removed all those UIAutomationcore.dll files from his Windows folder, which is harmful in Windows 8 (Did it once with Windows 7, there it caused no problem).

 

But to most people simply adding uiautomationcore.dll to FSX folder without removing anything seems to fix crashing, and that causes no problems to Windows 8 UI.

 

Anyway upgrading to Win 8 is waste of money if you aren't using touch screen.

To help the OP, somebody may hand him the native Win8 file. Should fix his Metro UI problems, not? I'm not near my Win8 thingy right now. :( But I can look it up later.

To help the OP, somebody may hand him the native Win8 file. Should fix his Metro UI problems, not? I'm not near my Win8 thingy right now. :(

 

im good mate, i had them backedup prior!

 

Yeah OP apparently removed all those UIAutomationcore.dll files from his Windows folder, which is harmful in Windows 8 (Did it once with Windows 7, there it caused no problem).

 

But to most people simply adding uiautomationcore.dll to FSX folder without removing anything seems to fix crashing, and that causes no problems to Windows 8 UI.

 

that's 100% on the money!

Ok, good news that is on the backup. :smile:

I just placed the UI in the FSX directory and all has be well... I am still in the early stages of testing. Will report back if I have a UI related crash...