FSX Install error 1628

[Norberto Rivera]

I got my new VC and SSD installed and when I plopped my FSX cd in the drive I continue to get "Error 1628: The installation failed to complete". I googled it and tried the automatic and the 3 manual fixes, but apparently I can't read too well because none of that fixed it. Any suggestions other than throwing the computer out the window????

[Norberto Rivera]

There are 6 fixes here...

http://support.microsoft.com/kb/910816/en-us

Thanks for the link, but none of those seem to be working. The installer just hangs now and one of the cores gets pegged. I looked up a fix for that and it has me editing the registry, however that didn't work either. I'll keep trying...

[Harold Henderson]

Sounds like you need a completely new computer. Start over from scratch.

[Norberto Rivera]

So I've spent all weekend fighting with FSX and it has won. I give up. I went through all the fixes on the support website, plus about a half dozen more I found throughout the web. I sank as low as actually calling microsoft tech support, only to have them tell me that my software was out of warranty so they kindly offered paid tech support for the nominal fee of $149. I'm so irate right now I can't even put it into words.

[Barry Theodore]

Sorry to hear that Bert,
I am also having problems with FSX. I have re-loaded it about 10 times and have the same problems each time. Everything appears to load ok. Sometimes I have to load the Baron 58 and then select the aircraft I want to use. I only have the generic aircraft loaded, if I try to load the 737 I sometimes get just a black screen when I load it, sometimes FSX just crashes to desktop. I can load the PMDG 738 NGX but again black screen when I try to fly it. The only conclusion I can make is that some of the Microsoft updates (to Windows 7) have affected the way FSX loads, or conflicts with something within FSX. I have used this computer for a couple of years now with no problems but all of a sudden this has happened and I don't know where to go next. The computer has an Intel I7 processor, I haven't seen any comments about Intel processors but I have about AMD and their latest software. I have managed to load FSUIPC and SquawkBox which both appear to be working ok. With a little bit of luck I will still be able to fly a good Frep and perhaps an occasional GFI.

[Norberto Rivera]

I think the only option left is to re-install the OS, which I'm not willing to do at this point. What Sergio said is correct, the problem lies with the installshield executable, but there is no redistributable for it on Windows 7.

FS9 is working for the most part so I can still fly. I might just let P3D mature a bit more and go for that. The only upgrade I have left to do on this machine is a new primary HD. It rates 7.4 and 7.9 in everything else, but a 5.4 on the HD data transfer rate. I have one of the slower i7's but it works fine for FS.

[Theodore Martin]

Sorry to hear that Bert,
..... The computer has an Intel I7 processor, I haven't seen any comments about Intel processors but I have about AMD and their latest software. ...

FYI...I just upgraded my computer and installed an i7 4770k processor that is working great and I didn't get any FSX install problems. I did have a problem with the Level-D 767 install but after reviewing their forum I found it was a .dll that needed to be replaced or deleted (can't remember which).

[Barry Theodore]

Finally fixed.
What a frustrating exercise which started with the installation of Prepar3d V2, although that was not the problem. When I installed Prepar3d I decided to down load the latest direct X11 drivers for my HD7850 video card. After this install Prepar3d worked fine but I started having problems with FSX. I removed Prepar3d and FSX and reinstalled FSX using the Gold Edition. I then had the problem that I could load the Baron 58 ok but when I tried to load the generic 737 the screen would go black but I could hear the engines in the background. I reinstalled FSX about 10 times after that but always had the same result.
I talked with a couple of FSX experts today and they suggested putting "HIGHMEMFIX=1" in the fsx.cfg file under the graphics section and installing "UIAutomaticCore.dll" in the FSX folder. These both fix known problems, but not mine.
A search of the internet found this little gem: http://www.youtube.com/watch?v=KfPYQiF6NcU which advises if you have Catalyst Version 13.9 of the AMD software loaded in your video card you will have real problems including the one I described above. I have now upgraded to the latest 13.12 version and now everything works as it should.
This just shows how you can get caught with seemingly unrelated events.

[Theodore Martin]

Wow, that was a tough one to resolve. And just think, anyone that gets automatic updates would not have any idea what caused their FSX to all of a sudden get black screens. They would be thinking "what was the last few changes I made" and try to reverse those only to get the same results.

[Michael Blakely]

This is why I don't let Microsoft update my graphics drivers.

[Barry Theodore]

The problem is Mike that I did the update. If I had let Microsoft or really Catalyst do the update then the problem would only have been there for a short time. Anyway all is ok now. Incidentally Mike have you installed the first two items mentioned in my rather long post as these may fix the problem you had when one of your long flights crashed?

[Michael Blakely]

I did the UIAutomaticCore.dll fix years ago.
I don't know about the hi-mem one.
I don't have cronic CTD issues. Only happens one a year or so.

[Wayne Pierce]

I did the UIAutomaticCore.dll fix years ago.
I don't know about the hi-mem one.

A long winded post on AVSIM.

I along with others here have discussed this issue quite a few times on this forum. Here it is again.
I have not had a CTD for a long time.

http://forums1.avsim.net/topic/281538-t ... nclusions/

[GRAPHICS]HIGHMEMFIX=1 Fixes errors with texture addressing modes in WDDM1.0 and 1.1 when using a lot of video memoryThe HIGHMEMFIX=1 you see above, fixes a bug in the FSX engine on how it handles texture addressing modes (Wrap,Clamp) and initial render states on single pass shaders, it will completely prevent textures, buildings and entire cockpits from dissapearing! this 'bug' is triggered when there is a high video memory usage situation.