My first attempt to get FSXrunning again, was using the repair tool in XP. And I can confirm that it DIDN'T help. So next up is a full format and install.CheersMark

Hi Guys,Trying to think of other things to try but in the mean time if you are having to reload windows and fs9 with all your addons many times can I recommend a drive backup imager like Norton Ghost (or whatever it is called these days) so that once you get to a stable position backup your drives (if you have room to store the drive image - which is a compressed file), then you can load whatever you need and if it goes wrong you just restore the drive image. Its saved me hours in the past and you can probably pick it up reasonably cheaply these days.RegardsMike

Well, I reinstalled Vista RC2, and FSX installed without problem.Still no clue as to why it actually failed, but at least it's working.

>Well, I reinstalled Vista RC2, and FSX installed without>problem.>>Still no clue as to why it actually failed, but at least it's>working.If you're feeling adventurous, now try uninstalling & reinstalling it... though I don't blame you for not doing that :)

Just an update for others who have this error:Microsoft support called me back today to see if their fix from last night was successful. I gave them the bad news and restated the problem again 2 or 3 times before the guy understood me. He said that they are getting a lot of reports in about the "registering fonts" step killing the installation and they are working on it. He said he needed another day to investigate the issue and will call me back tomorrow (friday) night. I guess I'll hold onto my copy of FSX until then. Not expecting much, but at least they called... He was about to make me go through the whole safe-mode install before I reminded him that we already did that.

At least they do know, that makes me feel better. Just a matter of waiting now.

See if the information here helps at all.http://julianyap.blogspot.com/2005/05/inst...error-1722.html[hr color=#000000][table border=0" width="98%" id="table1" height="2" cellspacing="1" cellpadding="1][td width=500]Jason[br /]General Aviation Fan[br][/b]

>See if the information here helps at all.>>http://julianyap.blogspot.com/2005/05/inst...error-1722.html>>[hr color=#000000][table border=0" width="98%" id="table1">height="2" cellspacing="1" cellpadding="1][td>width=500][font>color=#000080]Jason[br /][/font]General Aviation Fan[br][/b]I hadn't seen that before in my 1722 searches. I looked for the file in my C: directory, but didn't have the one in question. Thanks for the info, regardless.

Sadly that file does not exist.

Thanks for the responses. Last night I called the registration number and keyed in the 45 digit code they gave me........ FSX crashed. Closed down, restarted the PC, tried again. FSX wouldn't load at all. Task manager shows FSX "not responding". I have uninstalled and reinstalled the program and it now seems to work fine. However it has not now asked me to register the product. Will the PC have retained the registration details despite my uninstalling of FSX? Sorry to ask what may seem a silly question but when it comes to hardware / software issues I'm a complete novice.In fact, if I was a first timer to FS and was not aware of sites such as AVSIM where support and encouragement can be found in abundance, I would have thrown the game back at the retailer by now. I wonder how many first timers will be doing that?????BTW, the frame rates I am getting since reinstallation are significantly lower than previous despite the same settings and the tweeks being reintroduced. Getting frustrated!!RobEngland (FSX ####):-fume

I would say yes.So I get FSX running, installed XP on the old HD and installed FSX and success! Buy copying the files over did not work, I can now launch the game but it still says there was an error with the activation. So now what I am going to do is install FS9 on my old hard drive and see if I can "kill" FSX, then we will know that they cannot be run together!

Same problem here.I had an activated FSX Deluxe version that was working well until it crashed for none reason.Not a simple program crash,but a complete system crash with automatic reboot and no message or blue screen.Something i did not see for months.Then firts problems occurs with FSX telling me that there was a problem with my activation and that i should try to re-install the program.That's what i did for many times but it is always blocking at the same point (registering fonts...).I don't know what is the cause of the problem.I also have FS9 installed and it works perfectly well.My pc:Core2Duo E6600MSI Nvidia7900 GTO2 Go DDR2 Hitachi 160Go SataSblaster live valueWin xp home sp2.

Sorry to hear you're experiencing our dreaded font problem. I'm currently on hold with Microsoft to follow-up on my case. I know, I'm a glutton for punishment... at least I have speakerphone.Only the 21st person in line today. :)Edit: Just got off hold and spoke briefly with a MS support guy - only 1h 6min today! The current status is "we're still working on it" with no ETA. Actually considering reinstalling XP, but maybe they'll resolve it soon...

I will wait a couple of weeks and see if they can find a solution, I am hopeing they will, but after that I might just format and reinstall. So it appears that you cannot run FS9 and FSX together, while doing some experimenting on my old HD, I had FSX running and activated fine, installed FS9 and launched, it ran fine, then I went to lanuch FSX and the errors began and now I am at the same situation, says there was a problem with activation so I uninstalled and then attempted to reinstall and now I can't install the game.

I bit the bullet and reinstalled XP on Sunday. Can't believe I did it... for a GAME!!! I'm going to stay far away from any potential FS2004 conflicts (still not sure what the actual problem is) and enjoy FSX by itself while it's working again. Every time I start it up, I hold my breath waiting for the "please reinstall" activation message, but so far so good (even after a CTD using the tower view).I was about to defrag my C: anyway, so I guess this is just going a step further. :) My last conversation with MS tech support left me with little hope of a fix in the near future, so this is what it came down to.See you in the skies.