Have you tried removing the fsx.cfg and letting it build a new one yet? Copy/Save the old one just in case.

no, nothing added to FSX, it simply stopped working, probably what broke it is some WIndows updaterenamed fsx.cfg, same error

What about a system restore, or check the updates you got from Windows?BTW a very good reason NOT to let Windows update automatically!Turn the thing off, and choose them yourself...When you´re ready to re-install (!) - get FSX out of the Games folder...

Sorry to post here, as this isn't a CTD, simply put: it won't run anymore , all was running perfect until a week ago - I was too busy with some other sim stuff and I did not notice it, could it be one of the countless Windows updates ? I am running it on Win 7 Home Premium 64 bits.and I've tried a re-install - it gave the same error.

The "side-by-side" error is not a cfg problem it is a dll problem. Either you updated something that corrupted a fsx dll or you have a virus. Either way you need to do the following.1. System restore back to the last time fsx ran without this error.2. Run a FULL system virus scan and see if anything is found.3. Completely uninstall FSX.You have get a full explanation of "DLL HELL" here: http://buffered.io/2008/05/17/resolving-side-by-side-configuration-issues/Good Luck.

going to switch off the automatic updatesI've read that article, grim reading.

going to switch off the automatic updatesI've read that article, grim reading.

I didn't see anything in the article where auto updates is not good. Before Microsoft installs any update(s), it sets a system restore point. So, if an update doesn't work right, you can simply go into the uninstall program and delete the update or go into the System Restore program and do a restore. Updates are important as new security updates are constantly issued when there are problems with coding and an evil person can load a virus or penetrate your system. I think Mike T found the problem with his excellent link. Microsoft Visual Redistributables are runtime programs to make sure programs are installed properly. There were a lot of updates to these redistributables issued recently (at least on my system) when about 18 updates were issued in one week. Perhaps one of those updates corrupted something. I know I had issues after the update and couldn't open up the 32 bit version of IE9. The 64bit version opened and ran great but FSX has programs that depend solely on the 32 bit version. FSX worked okay but some of the addons did not. I worked on it for over a week trying to figure out what happened. Google searches found several "solutions" but none worked for me. Since I have the retail version of Windows 7, I was able to "update" Windows 7 which meant reinstalling Windows 7. It did not affect any of my programs like FSX but I did have to reinstall all the updates to Windows 7 and Microsoft Office. Not a major problem since I have a high speed connection. If you have an OEM copy of Windows 7 or an Upgrade version, you cannot do the Windows 7 Upgrade. I guess it's a benefit of paying the big bucks for the full retail version. In any case, keep Windows updated or you could have more problems than you are experiencing now.Best regards,Jim

FYI, there's another individual here who has the same problem and it's posted over in the Crash to Desktop Forum here. His problem was associated with the FSUIPC.dll as indicated in his Event Viewer. Is that the dll listed in your Event Viewer? He is still looking for a solution.Best regards,Jim

"I didn't see anything in the article where auto updates is not good"I was not referring to the article, I just don´t want MS to update anything without me knowing what it is!Lots of things is just useless crap - I run my machine wiht FSX only - so don´t need all the fixes for various stuff..

FYI, there's another individual here who has the same problem and it's posted over in the Crash to Desktop Forum here. His problem was associated with the FSUIPC.dll as indicated in his Event Viewer.

No, this is a comple red herring. Those Events were normal for older versions of FSUIPC4 which used to locate and connect to the latest installed version of SimConnect by trying each in turn. Each attempt that failed generated an error in the Event log, but of no consequence, and these only applied to those folks not bang up to date.They most certainly are not indicative of any problem with FSUIPC or side-by-side DLL operation.For over a year now FSUIPC4 has used a more direct method of connecting which avoids those events occurring.Pete

I believe the reason could be Directx9 - even though Win 7/64 uses Dx11, I was getting a error message that Dx9 was not running OK, I tried to re-install Dx9 but it did not install as it pointed out that I had a later version installed.I've given up - I was planning to do it anyhow so I am going to do a re-install of Windows with a 64bit Ultimate I have, I could spend a week on trying to fix this, better spend a couple days re installing.Nothing else was affected - everything worked OK, the only casualty was FSX ... fu*k.

I believe the reason could be Directx9 - even though Win 7/64 uses Dx11, I was getting a error message that Dx9 was not running OK, I tried to re-install Dx9 but it did not install as it pointed out that I had a later version installed.I've given up - I was planning to do it anyhow so I am going to do a re-install of Windows with a 64bit Ultimate I have, I could spend a week on trying to fix this, better spend a couple days re installing.Nothing else was affected - everything worked OK, the only casualty was FSX ... fu*k.

This summer I had FSX nightmares for weeks. Nothing I tried worked. In my opinion, there is nothing wrong with FSX. The problem lies with Windows7. I run the 64-bit Pro version. Here is what I did to fix all of this nonsense.First, I formatted a drive and re-installed Windows7. When the installer ask if I wanted all the updates - I said NO!!! I reinstalled FSX. I turned on UAC and the Windows7 firewall. I installed AVG Network Security (no plug intended). This is the payware version. I installed Glary Utilities to cover the Windows Registry.Here's the key - I NOW DO NOT UPDATE WINDOWS - EVER. The original disk version was the most stable OS I've had. Ever since MS started updating Windows7, I have had problems. You may trust them but I don't. BTW - In my case, the restore point did not help the situation.Any addons that require new versions of programs such as a redistributable, I let the application load the new version. I run FSX with admin security.Thus far, FSX has been stable and is working properly. One more thing - I keep my Ethernet connection disconnected unless I really need it. When I don't need the Internet, I disconnect. While I can't prove it, my gut tells me that there is some hacking going on by people who are associated with flightsim. That's based of more than 40 years experience in the computer and network security arena. I'm probably wrong but there are a lot of folks having similar difficulties and I'm tired of reinstalling everything. Call me paranoid but I'm covering my bases.All of this is not perfect but thus far it has helped.fb

I wonder what the "Play.Lnk" file is. I don't have it on my W7 64 bit system. I think we need to see what the event viewer says. Just for the record, I know everybody has different experiences. I have never had a problem with any Windows Updates. Most of them are security updates. Why wouldn't you want those? Of course, if you never go online, that's different. Something else: an earlier post mentioned a possible virus. I know we all have our favorite AV software. We all are certain we have the best AV set up. We scan all the time. We defrag. We are very careful with our systems. We don't have any viruses. You may be surprised. I have FS9 on an old XP box that I don't use much any more. For several months now things have started to not work properly. I ran all my registry cleaners(I know some folks say you should only use one cleaner, but I've never had a problem. Multipul AV IS a problem.) I ran Malwarebytes. I ran several deep AV scans. I ran combofix. A few lightwight things showed up, but not much. My system must be clean, or so I thought. Still things were not right. I was thinking a reinstall was in order.Avast has a rootkit scanner. A few others do, too. I ran the rootkit scanner and, my word, several (ten or so)things were there! After a few passes, the system was finally clean (I hope). The computer starts, and runs faster than it has in some time. Sadly, the rootkits were in there long enough that some software and possibly windows files may have been damaged. So in the end, a reinstall may still be needed, but now I understand what happened.For fun, I clean friends computers. Dosen't matter if you have pay AV or free (I think MSSE is the worst), stuff gets through. Scans don't find everything. I think if companies want us to use their systems and internet software, they ought to provide us with free AV that works.Bob

I wonder what the "Play.Lnk" file is. I don't have it on my W7 64 bit system.

It has to do with Windows Game Explorer. It's a shortcut to FSX.exe in a file "Play" in a directory similar to "C:\ProgramData\Microsoft\Windows\GameExplorer\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\PlayTasks\0"

I've spent most of yesterday and today's evening re-installing it, first I fully completely patched Windows 7 /64 - exhausted all patches available, then I switched off automatic updates.then I've added FSX + ASE, REX2 and several A2A add ons already - and FSX is working fine,although I must admit that, after every module and game I've added ( Civ4, Shogun 2, A-10C, Cliffs of Dover and LO FC/FC2 ) I've tested FSX, each time expecting the worst, it is working fine.I've also made a backup.what an unpleasant experience this one was.