I had to tell it to everybody: One of the most irritating errors of FSX has finally reached his end: http://support.microsoft.com/kb/928080/en-us?spid=11941

NOT ENTIRLY!

I gave the official MSKB928080 solution a try, but I am still receiving the error 1722 message when the installation process reaches font registration. I have done everything I can think of short of reinstalling Windows, and can say I have just about reached the point of giving up. Hopefully a solution will be found shortly!otho

I'm one of those who had this problem. Unfortunately, I had to resort to reinstalling XP which worked. But the reason I think it worked was because I did not install any of the critical windows updates. To date, I have only gotten around to installing several of the latest ones(our of about 65-66 updates). I have all my hardware/software installed back the way I had it when I first encountered the 1722 error, except for the windows updates. That is the only thing I can attribute to the difference in my system pre/post install error.My system is running very stable right now with no problems running FSX. I still feel pretty well protected from infections as I am running Windows Firewall, AVG, Spam Blockers, and I am sitting behind an unbroadcasted router. Eventually, I will try installing all the updates but I am doing so one by one so I can trace any potential system instability. It will be hard to know for sure as I don't intend to attempt to reinstall FSX each time.Perhaps you may want to help me prove my theory. I figure if you are up to date with your critical windows updates, then perhaps if you go to add/remove programs and uninstall all the updates(security fixes, etc.) to see if you are then able to install FSX. Make sure to set a system restore point prior as well.I forgot to mention, the main reason I suspect the windows updates is because, the first time I reinstalled XP, I immediately installed FSX after the XP installation was done. That's before installing nForce drivers/video/sound/etc. as well as any critical windows updates. FSX installed and worked fine. I then installed all my drivers, critical updates, software, etc. to where I had it before. FSX then crashed on me after a couple of sessions. I got some error about losing the activation. I tried doing a repair off the install disc but ended up getting the dreaded 1722 error. I tried uninstalling/reinstalling but got the 1722 error. That's when I reinstalled XP for the second time but did not install any of the windows updates(save for the few I mentioned earlier, once I felt my system was stable enough).I really don't know if uninstalling all the windows updates will fix the problem. I'm thinking that there's a possibility that one ore more of them may cause some kind of irreparable damage upon install that can only be fixed my a clean install of XP. I don't know for sure but I don't think any real harm can come from uninstalling the updates. If it doesn't fix the problem then you should be able to reinstall them or at least return to your system restore point. I'd be really interested if someone would be willing to take the risk and try it out.Sorry for the long post. I tend to go on a bit. :)

Thankfully, someone was finally able to get me past the 1722 error to successfully reinstall FSX. I had downloaded and run the Activation Reset Tool posted yesterday in Microsoft's KB928080, and was still suffering the 1722 error when the FSX installation reached font registration. I posted a message about this in MS's Simulations Forum, and received the following response:"Camden..." wrote:> Run the tool in DOS Command Prompt> Click Start, Programs, Accessories then command prompt> ONce you are in DOS, type "cd.." then hit the return key (Enter) Repeat till> you only have the c: prompt in veiw.> Then type "c:MicrosoftKB928080" hit (Return)> then type "resetsldl

:-beerchug Thanks for sharing - Doing this through the DOS window solved finally solved my problems!! I had been unable to reinstall for weeks now after getting a BSOD in FSX, so I've had to get by with just using the demo. I would highly encourage anyone who has this error to try this as nothing else solved my problem including the official MS procedure through Windows (you would think MS would add this to their site!!!) Jim

Glad to hear that you guys are getting your installs to work. I'm finding it less likely that my theory about the windows updates has any validity.I have since installed all the critical updates and so far my system seems quite stable and FSX continues to work with no problems. Guess I'll never figure out what the problem was, at least on my system. Good to know that there's at least a working fix for the problem if I should ever(doubtful) run into it again.