Aha!
Wow, talk about obscure. It seems one cause of the activation problems some people have had is a seemingly innocuous registry value placed there by another program prior to installing FSX. So far we've determined that Iomega backup software is one culprit but there may be others. Apparently the software is "supposed" to set a valid value that the activation component looks at but instead it just writes a '0'. Essentially what happens is the activation component says. "What the %$!?", and bails out. Some people have had success by un-installing the backup software and then trying to activate. I'm looking into whether we can post a manual fix for those of you who feel comfortable editing your registry. Stay tuned.
Comments
Anonymous
October 23, 2006
Maybe someday people will realize that any problems they might have probably relate to something on their machine and not the Sim. I've been meaning to post this in the forums, but it would be pointless. I can hear the groans of "not my machine" already. Keep up the good work, Mike.Anonymous
October 23, 2006
The comment has been removedAnonymous
October 23, 2006
Forums all over the internet appear to be littered with stories about activation problems from legitimate users who paid out their money to buy the product legally. At the time of writing I don't believe I have seen as much as one word of complaint from the vast numbers of individuals who appear to have illegally obtained the product and of course subsequently installed it without a hitch. Ironic that so many legitimate users have understandably felt compelled to download a fix that was most probably the work of the very type of people that are the root of the activation problem in the first place. I'm all for revenue protection on the part of software producers but when it inconveniences innocent buyers - as it most surely has - then there simply has to be more work put into finding a better way. Incidentally, a user on the flightsim forums suggested that Microsoft Activation also include an option for deactivation as well - for those instances where the user upgrades their hardware, they can "deactivate" the product (back to 30 minute mode) and then re-activate once they have upgraded the hardware. Sounds like an excellent idea to me.Anonymous
October 24, 2006
The comment has been removedAnonymous
October 24, 2006
The comment has been removedAnonymous
October 24, 2006
The comment has been removedAnonymous
October 24, 2006
The comment has been removedAnonymous
October 24, 2006
The comment has been removedAnonymous
October 24, 2006
I'm patient. I'll wait until I see an "Official" fix for this activation issue. Looks like there are thousands of folks with this same issue. I thought it might be a problem to have 2004 ACOF and FSX installed together. I couldn't get FSX to activate, so I went back to 2004. Bingo...I had to accept the EULA again and I have been running 2004 since it came out. Don't know if that will help you folks or not.Anonymous
October 24, 2006
I have the exact same installation problem.. I was wondering if it has anything to do with the fact that I use Win XP Pro x64? I know this is a bad idea, but if you hit the reset button on your computer after the 1722 error pops up, the installation won't be rolled back, and you can fly for another 30 minutes until the activation stops working agian. >.> -JesseAnonymous
October 24, 2006
The comment has been removedAnonymous
October 24, 2006
Tyr the steps below after making a backup of your registry, create a restore point in Windows... (see here if help needed: http://windowsxp.mvps.org/registry.htm)
- Click on Start, point to Run and type regedit. Click OK.
- Expand: HKEY_LOCAL_MACHINESYSTEMCURRENTCONTROLSETCONTROLCLASS{4D36E967-E325-11CE-BFC1-08002BE10318}
- Once you found the folder, on the right-side, double-click Upperfilters. Change the value from 0 to PartMgr and then click OK.
- Close Registry Editor.
- Reboot the computer and try the activation wizard again.
Anonymous
October 24, 2006
I am also getting error 1722 after flight sim x about a week after running it without problems.Anonymous
October 25, 2006
Oh please! One of the FS programmers didn't validate their input. That's a basic programming error. Don't try and make it sound like it's some gigantic plot to make MS look bad. This was a small programming mistake that didn't get picked up in testing and had serious consequences. The programmers and testers should be apologetic and learn from the mistake.Anonymous
March 03, 2007
I am getting cab errror on my ps while installing any software ihave done formatting reinstallation changed harddisk bught new cd rome un installed antivirusbut still error is coming can anybody sugget what to do with this problem, plz i am on urgent project and my pc is not working feelfreel to mail any solution on manish_kolmbkar@yahoo.comAnonymous
June 26, 2007
I really dont know what you are talking about here but, uhm... Can anyone help me with fsx.. When i install it everything goes as i should but when im done installing i have to activate my cd key and such things but when my installing progress comes to 100% it pop ups a window where it stand: error 1722. There is a problem with this windows installer package. A porgram run as part of the setup did not finish as expected could anyone give me a answer fast i really miss playing this game :( Im sorry if this dont have anything to do with what you where talking about here but i realy need help with this!:D thank you!Anonymous
June 29, 2007
I've bought this game recently and due to several unwanted software issues and other probs i've had to reinstall everything a few times now on my new computer i keep being told that i have used the serial key too many times and microsofts almight database of uslessnaes isnt letting play the game if apple make a flight sim im buyingAnonymous
September 06, 2007
I tried to install fkight sim X and i get to the very end and it states an error 1603 during intstallation. I also have flight sim 2004 installed prior to sim X Would that (sim 2004 registry file) cause an installation error in sim X ?