I have two dilemmas. I'm currently on Windows 7 64-bit and have started experiencing the 'Fatal Error' nonsense. I messed with the uiautomationcore.dll and then re installed FSX to desktop because I thought the fix would be to get it out of x86. I thought it was operating smoothly, but I still got the dreaded fatal error mid-flight from clicking on the map....it's driving me crazy!!!!!! The original FSX that was in x86 was never really uninstalled because I wasn't able to (received error at uninstall)--which led me to deleting registry keys and more frustration. PLEASE! I ask...are there any other tactics to get rid of fatal error? This is so ridiculous that a user has to go through all of this to play FSX. My other dilemma isn't appropriate for this section because it deals with PMDG. I removed every trace of that because when I went to use the activation key a second time, guess what popped up.... drum-roll please......an ERROR! So I guess the next move is contact PMDG? All of this has me ready to pull my hair out. :mad: Is there anything I can do? I've given up on my end of googl-ing and reading about stuff I have no idea about, and have now turned to the experts at AVSIM. Thanks so much in advance.

What exactly does the error say? Why not switch to p3d. Fsx is very old software.

>then re installed FSX to desktop

 

Not sure what this means exactly? Did you do a total fresh clean install of FSX?

Why not switch to p3d

 

I don't know much about it...What's with academic vs. professional?

 

Not sure what this means exactly? Did you do a total fresh clean install of FSX?

 

For the most part, yes. I tried to insert disc 1 and uninstall that way, but the uninstaller was incompetent. So I reinstalled the game to my desktop. FSX loads and the game appears to work, but there's the uncertainty of the Fatal Error popping up mid-fllight or any right click.

 

What exactly does the error say?

 

Fatal Error...

So you essentially have two installations. This will be a mess. You need to completely uninstall both versions and clean out the registry. This will be easier said than done but it is possible.

 

However, *IF* you do not have too much other stuff installed, a complete reformat and reinstall of W7 and then FSX into it's own folder would be in order. There are several uninstaller programs around - REVO uninstaller is one of the better ones that you can use if you decide not to reformat.

 

Either way, you have a little work ahead.

 

Vic

However, *IF* you do not have too much other stuff installed, a complete reformat and reinstall of W7 and then FSX into it's own folder would be in order. There are several uninstaller programs around - REVO uninstaller is one of the better ones that you can use if you decide not to reformat.

 

I'm not sure how I would even find the first version because I deleted it through the recycle bin. I know it's not technically 'uninstalled', but there still would be remains that would interfere with current one? I don't think even reformatting the entire OS will fix the fatal error because I feel like I've read that in other forums.

I'm not sure how I would even find the first version because I deleted it through the recycle bin. I know it's not technically 'uninstalled', but there still would be remains that would interfere with current one? I don't think even reformatting the entire OS will fix the fatal error because I feel like I've read that in other forums.

 

 

I don't know where you got that idea! If reformatting and reinstalling the OS still gives you a fatal error - you have a serious hardware problem and need to look there first.

 

I don't often recommend a complete reformat but it sounds llike you have screwed up your FSX install by the deleting and reinstalling.

Format the drive - reinstall the OS and see what happens. Do not reinstall FSX yet. After you are positive that your system is stable, then reinstall FSX to it's own location. Do not install any add ons. See how it goes. If all is well - then complete your install.

 

There are other ways to deal with this issue but, pardon my bluntness, but I don't feel your computer expertise is at the level needed to do it. It's trick and messing it up would mean you had to reformat anyway - so save the time.

 

Good luck.

Academic and professional are the same, but professional is licensed for flight schools etc.... THe academic version has a very faint watermark in the upper right corner of the screen, that's the only difference. Honestly if you're having all of these issues, it's an excellent opportunity to erase everything, reformat and get started with P3D. Afterwards you'll wonder why you didn't switch sooner. P3D is essentially a more up to date FSX, so you won't have any major issues learning a whole new sim like if you were switching to X Plane or something. Plus almost all add ons are compatible.

I run both FSX and P3D and recommend either BUT at this point P3D is not the solution to your problem. It may also just open up a new can of worms. There are still a LOT of add-ons that do not work with P3D. I don't use PMDG but , IIRC, it does not - I may be wrong - you might want to research that if you decide to try P3D.

 

Frankly - get your FSX install working first. P3D can be tried later AFTER you resolve your issues. You don't need to throw another variable into the mix

 

Vic

One doesn't know if the fatal errors are a OS, hardware, FSX problem? Switching to P3D may be like switching from Whiskey to Vodka to resolve an alcohol abuse problem. Taste different but the symptoms are still there!

 

I believe FSX isn't inherently bad. Its just knowing how to make such a complex software integrate with hardware, OS, addons etc and can take a great deal of a lifetime to achieve.

get your FSX install working first

 

What I've been trying to accomplish.

One doesn't know if the fatal errors are a OS, hardware, FSX problem? Switching to P3D may be like switching from Whiskey to Vodka

 

Nice analogy. Forget P3D! I want error gone!

Hmm. My logic would be the opposite. If you have to format...reinstall etc he may as well take the opportunity to upgrade software. If the same problem persists then for sure it s a hardware or os problem...

Hmm. My logic would be the opposite. If you have to format...reinstall etc he may as well take the opportunity to upgrade software. If the same problem persists then for sure it s a hardware or os problem...

 

Except that, at this time, P3D is not an upgrade - at best it's a lateral transfer. My FSX runs perfectly and so does my P3D system. P3D wins on some points right out of the box but FSX is still far and away the superior product. This will probably remain true until Version 2.0.

 

The main issues still remains - the OP has NOT determined if the cause of the error is the OS, the hardware or FSX? So what good would a upgrade of ANYTHING do if you still havent identified the issue?

 

Using your logic, I guess he could go out and buy a whole new system and new software but I do think it's a bit much

Switching to P3D may be like switching from Whiskey to Vodka to resolve an alcohol abuse problem.

 

Wonderfully well put and I completely agree. Trying P3D at this point is as likely to compound your problems as it is to solve them.

 

This is so ridiculous that a user has to go through all of this to play FSX

 

Most users don't.

 

Something has happened to your system - but unfortunately stuff happens with even the most stable of applications - and at this point based on your description a clean slate is strongly advised. You can try registry cleaners (CCleaner for example) or MS installer cleanup tools, because first and foremost you need all pieces of all former FSX installs and add-ons GONE, but all of the above require some effort and can do more harm than good if you're not comfortable using them and given what has happened it's likely you'll always have some potential leftover pieces. Another possibility is reverting to a prior restore point if you've got one from before your original errors began or prior to your first FSX install.

 

Sorry, but there are no magic bullets, we don't know what happened to cause the corruption you've obviously gotten and subsequent actions have left you with a bit of a mess. I really think the best advice is a "do-over".

 

Scott

How is fsx far and away the superior product?