The twist is that I have UIAutomationcore.dll, and have had a stable system for 12 months. Whilst trying to sort out my missing desktop after inadvertently downloading some adware, I find that FSX freezes after a few clicks on the Start Up Menu. My desktop is back, the virus is gone.

 

Strange thing is, this happened 6 months ago when I updated my Nvidia driver. I quickly rolled back the driver and my menu was normal again,

 

As part of my problem solving of the desktop issue, I update drivers, but when they didn't work, rolled back to the originals again. So I've got the freezing menu back for good this time!

 

What have I tried? Removing modules, a clean fsx.cfg, disabling UT2, launching with administrator, updating UIautomationcore.dll, removing UIautomationcore.dll. I'm sure a few other things to,

 

Any thing else I could try??! I'm not scared of a full reinstall, but would be gutted to find the problem persists!!!

Start Up Menu....is that the Free Flight Screen where you select your aircraft, flight plan, weather,

 

etc? Have you brought up the Task Manager to see if FSX is Responding or off into oblivion?

Start Up Menu....is that the Free Flight Screen where you select your aircraft, flight plan, weather,

 

etc? Have you brought up the Task Manager to see if FSX is Responding or off into oblivion?

Yes, I can choose Aircraft, Weather etc, but on the fourth click, it usually freezes. I cant see any event because their is no CTD, but I don't know about the Task Manager. It is using alot of memory, even while frozen, when I check Processes.....

If the memory use is up to 99% or higher, then FSX is looking for something and it's missing.  Is the

 

4th click always on the same thing, like season or time of day?  Some small file that FSX is looking for

 

may have been deleted.

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) 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. See our image posting rules here.

 

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.

Many thanks for your reply. Mmm, not sure if its always Date/Time, I tend to try that last ... I'll check. I'll have a look at at the process percentage too.

 

I have tried removing the logbook file, but that didn't help.

 

I wonder if it has anything to do with my screens. While trying to fix my loss of desktop, I damaged a monitor cable, so cannot use nvidia surround, I'm on a single monitor. It may or may not be related. Just one more thing to check. FSX is a fragile thing, who knows whats going on below the surface!

Thanks again Charlie, my FSX seems to have sorted itself out. I've gone fron no desktop showing, to back to normal. Not sure what I did, but I am a happy pilot again Thanks for your help!