Hi.

 

Newbie and so apologies for wrong forum, question already asked/solved etc. :mellow:

 

I recently had a problem with a fairly new FSX install (few weeks old, dodgy addon) on a newly built computer that required me to remove it and start again. However, reinstalling it is proving to be more trouble than any reasonable individual has a right to expect. For "some" reason whenever I run the installer all I am offered is the Remove or Repair option. Now, I have removed it. I have scoured my registry, my hard drive for files and fragments and got rid of them. I have followed numerous Googled ideas about how to resolve this problem without success. I have used Revo Uninstaller (always do), I have tried Windows Install Cleanup (it was no help). I have manually looked though my registry using regedit and Registrar Registry Manager. I have, in short, done everything I and apparently, other people, can think of and it still will not install.

 

Please can anyone offer anything further before what is left of my hair is torn from my already weary head.

 

Two things I feel might have bearing on this. My first attempt at reinstalling was working but I realised I had selected the wrong HD and cancelled the procedure. It was literally seconds into the job and only 2 obvious files had been copied to the new (incorrect) folder. This was to my system drive and I do not install FSX on but a seperate one. Secondly, I read elsewhere and thus cannot vouch for the accuracy of the information, that it is possible that the WinSxS folder is corrupted and this will prevent FSX installing. I have no idea if this is true or has happened to me. Everything else is working fine and glance at said folder shows nothing to suggest there is a problem with it. Of course it may not be that obvious assuming this is a possibility.

 

Does anyone have any ideas, anything. I'm at a loss and although I'm no computer expert I am by no means inexperienced and without a modicum of skill.

 

Anything at all would be gratefully received. I want to fly my planes again. I do miss them so.

 

Many thanks for taking the time to read my rather pathetic plea.

 

 

Best Wishes.

 

 

Windows 7 x64 btw.

I like the following uninstall/reinstall link - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

I read elsewhere and thus cannot vouch for the accuracy of the information, that it is possible that the WinSxS folder is corrupted and this will prevent FSX installing.

 

Not sure what the WinSxS folder has to do with the install. If you started the installation and stopped it, then you'll have to manually remove any FSX folders it made in those few seconds and you will have to clean the registry again. Then restart. This is not just with FSX but with any software.

 

Best regards,

Jim

Hi there,

 

What you could try is to create another user account on your system (with admin priviledges) and then log into windows with that new user account and install FSX.

 

It may work to solve the problem... it might not... I had a similar (not the same) issue recently, and installing FSX under a different user account was the only thing that worked.

 

Worth a try at least.

For the uninstall did you remove the files under c:\Users\AppData\....\Roaming\Microsoft\FSX ?

Thanks for the replies.

 

No, I wasn't sure about the WinSxS folder either?

 

As for all other suggestions, done it, tried it, none of it worked. I had hoped the separate account might be successful but it had exactly the same result. I did forget to mention I get an Error: -1605 but searching upon this has not lead me anywhere either. I really do not want to reinstall the OS just to get the wretched thing to work, however much I enjoy it. It really is as if there is some left over data somewhere but I'm buggered if I know where. Even the MS FixIt! was useless.

 

There has to be an explanation, but I'm too tired to look further tonight

 

Greatly appreciate the suggestions and time taken to help.

 

Thanks.

I don't know if the following has any bearing on your problem, but I really recommend that you steer clear of the WinSxS folder. If you go in there and search on x86_microsoft.simconnect* you should see 3 folders (one for each version of simconnect--rtm, sp1, and sp2/acell) and a total of 6 "manifest" folders. If those are there, just leave them alone. If you try to delete them, as some "repair" tutorials tell you to do, it will firstly probably tell you that you don't have permission. If you try to force the delete, say by using a program such as Unlocker (as I stupidly did not too long ago), it will get rid of the files, but they will still be in the registry. When you try to reinstall, those first two simconnect versions won't be reinstalled. Then you will have to go in to the registry and delete all simconnect keys manually, which is scary.

How about restoring your computer to a time and date prior to your first installation? May or may not work but normally Windows will tell you ahead of time which programs will be affected by restoring to an earlier date. Just a thought.

 

JJ

registry cleaner like "Ccleaner" could help to clean things before another try to install fsx. CCleaner works great.

 

Was gona reinstall win7 before replacing fsx with p3d on my pc so that i get clean install.

 

download ccleaner and i was shocked to see just how much junk fsx + addons left behind all over the place, about 5000 + items in all

 

But FSX is now so unstable given it runs with 2012 software and it was made in 2006. My advice to anyone installing new fsx is to go P3D.

 

I am new to P3D myself, but so far it behaving more like 2012 software than FSX does.

 

Further down the line 2006 fsx code is only gona get harder to maintain.

It sounds like the new install is finding a leftover fsx.cfg somewhere. I found that this is the file that prohibits a second installation of FSX like I used to do with FS9. There is also a copy of the fsx.cfg in the "C:\Users\xxxx\AppData\Roaming\Microsoft\FSX." folder along with the one in the main FSX folder. Try searching the computer for this file as it could be the problem.

fisheye

Anything at all would be gratefully received

 

You could possibly try this,as it pertains to the "1605" error you are describing:

 

http://support.microsoft.com/kb/928080

 

 

Regards.

Strange. I've done 100 reinstalls and never had a problem...

Strange. I've done 100 reinstalls and never had a problem...

 

if you need to do a hundred re installs than there is some thing drastically wrong with your pc

Thanks for the replies.

 

No, I wasn't sure about the WinSxS folder either?

 

As for all other suggestions, done it, tried it, none of it worked. I had hoped the separate account might be successful but it had exactly the same result. I did forget to mention I get an Error: -1605 but searching upon this has not lead me anywhere either. I really do not want to reinstall the OS just to get the wretched thing to work, however much I enjoy it. It really is as if there is some left over data somewhere but I'm buggered if I know where. Even the MS FixIt! was useless.

 

There has to be an explanation, but I'm too tired to look further tonight

 

Greatly appreciate the suggestions and time taken to help.

 

Thanks.

 

Here's the fix from Microsoft - http://support.microsoft.com/kb/928080. It's basically what others have suggested but maybe this one will work.

 

Best regards,

Jim

Hi.

 

Thanks to everyone for taking the trouble to read and offer solutions. I am enormously grateful to you all.

 

With regard to the WinSxS folder, I couldn't agree more. Not being familiar with it or what it does, I researched some more about it and realised it should be left well alone. I also read the tutorials you mentioned.

 

I have tried CCleaner as it is been part of my standard suite of programs for sometime. It was unsuccessful at sorting the problem Same goes for the MS soloution provided by the links. I tried that before posting here and it didn't work.

 

I can however reveal that I have fixed the problem. The solution is something I should have hit upon already and I'm a little embarrassed I missed it. But no matter.

 

I decided to take another look through my Temp folders just to ensure I had deleted any left over installation files. As it happens I tried installing again while I was doing this. Not sure why, but there you have it. Any way, I noticed a folder was created called {9527A496-5DF9-412A-ADC7-168BA5379CA6} which contained mostly .bmp and a few ini files etc that the installer was using. As soon as the installation procedure is quit, this folder is deleted. So it doesn't hang around for you to find later. So call it inspiration or humiliated stupidity, I searched the registry for entries with this name....sure enough, there were some. I deleted them, re-booted, ran the installer again and it worked.

 

Strikes me as obvious now, but not at the time. Why nothing else found these entries I cannot explain. I'm just glad it worked.

 

So with tail firmly between legs, I once again offer my heartfelt thanks to everyone and shall now proceed to put everything back as before.

 

Lesson learned.

 

Very Best Wishes

Thanks for posting your solution. It will help others as I know many have tried the Microsoft solution and it didn't work for them either so maybe they did the same thing (only did not admit to it).

 

Best regards,

Jim