Been trying for a week with tool unable to get it to work Am going to ask for my money back. I've had enough

Hey guys. I had problems installing FSX after the tool...i kept getting Error 1722The problem was that the installation was having problems with sending a license file to the temp directory (because it was using long filenames instead of the old format filenames).You can try:1. creating a folder called "temp" within the C:2. Enter system properties > Advanced > Environment Variables3. Edit TEMP so that the variable value reads "C:temp"4. Do the same for TMP5. click OK6. restartI hope that works for you. Many thanks to Dave Templin for this resolution also.If you have any other problems after that I suggest you email Dave Templin with a log of the installation.Original emailAfter setting NtfsDisable8dot3NameCreation=0 and rebooting, I still got a shortpath for SET TEMP.Try creating c:temp, set TEMP environment variable to "c:temp" from MyComputer, and then reinstall (with log). See if that works.________________________________________From: Kent MelendezSent: Friday, November 10, 2006 8:16 PMTo: Dave TemplinSubject: RE: Unsuccessful Error 1722 fix(w/ Files requested)These are my settings as they are now(didn't edit the anything yet).>From: Dave Templin>To: Kent Melendez >Subject: RE: Unsuccessful Error 1722 fix(w/ Files requested)>Date: Fri, 10 Nov 2006 20:02:15 -0800>>I think the problem might be with the long path in your TEMP.>>My suggestion is to try changing your environment such that when you type>SET PATH from a command prompt it says something like the following...>>TEMP=c:docume~1kentlocals~1temp>>Please try the following...>>1. Right click on My Computer and choose Properties>2. Click on the Advanced tab>3. Click on Environment Variables>4. Select "TEMP" under "User variables for Kent">5. Click on Edit and report back what it says for "Variable value">6. Then change it to "%USERPROFILE%Local SettingsTemp">7. Go back to your command prompt and type "SET PATH", verify it is now>"TEMP=c:docume~1kentlocals~1temp">8. Reinstall FlightSim (with a log)>>I really hope that does it for you. Let me know how it goes.>>Thanks!>Dave>>________________________________________>From: Kent Melendez>Sent: Friday, November 10, 2006 7:42 PM>To: Dave Templin>Subject: RE: Unsuccessful Error 1722 fix(w/ Files requested)>>I've had problems Installing another game because of "issues with my temp>directory">>With the set temp command i got:>TEMP=C:Documents and SettingsKentLocal SettingsTemp>>could it be because of a tweak I applied which modified these values in my>registry to:>>[HKEY_LOCAL_MACHINESystemCurrentControlSetControlFileSystem]>"NtfsDisable8dot3NameCreation"=1>"Win31FileSystem"=0>"Win95TruncatedExtensions"=1>> >From: Dave Templin > >To: Kent Melendez > >Subject: RE: Unsuccessful Error 1722 fix(w/ Files requested)> >Date: Fri, 10 Nov 2006 16:36:00 -0800> >> >Yes, this is a really nasty problem.> >As you mentioned, the problem is around the following entry in the log...> >> > >C:WINDOWSInstallerMSI28.tmp, command: /I @C:Documents and> > >SettingsKentLocal SettingsTemp~SL1F.tmp> >> >Other successful logs I have reviewed pass a short path instead of a long> >path...> >> > >C:WINDOWSInstallerMSI28.tmp, command: /I> >@C:Docume~1KentLocal~1Temp~SL1F.tmp> >> >My theory right now is it's the long path that's causing the failure.> >> >Can you check your TEMP environment variable?> >Do this by opening a command prompt and typing "SET TEMP".> >> >> >

Tried all the above. i must be doing something wrong. However as I do not have a degree in computing I'm up the creek without a paddle. perhaps someone can release a dumbos guide to getting the b----- thing to work and I might just about do it. By the way I have sent E-Mail to MSN and my software vendor asking for money back or a proper remedy.

Maybe I missed it, but what exactly is the problem that this executable is attempting to fix?Since I've been trying to troubleshoot this on my own and have a theory that it may be one or more of the windows updates(see my previous post a few pages back), I'm interested in knowing what they think the source of the problem is.

I think the tool resets the dll. that monitors any changes to your system. The only trouble with the tool is that you have to have a FSX that was completely installed, with out any missing files, or folders. The tool is useless to those who could not repair, or un-install the product. We are still waiting for some sort of "un-install tool" to get the rest of the sim's up and running. So we wait. Ken

Gents,I had exactly the same problem after using the new KB928080 tool to reset the activation. I ran the reset tool, tried to reinstall FSX several times, and still received the same 1722 error as before. In response to my query, the following advice was posted in the MS Simulations forum:"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

>>Hi,>>Did you try doing it the windows resource kit way? Making>sure>>to reboot after applying the security change? >>Also when adding your name you need to make sure your pc is>>included, when I did it through Admin Tools had to use the>>Name Lookup function to get it quite right, PC/Name....>>Hope this method works for you...>>Cheers>>Mike>>>I did this too. And it didn't help.... I will try the>uninstall of the Installer and see if that helps.... but I>don't hold my breath any more... :-(>>Cheers>MarkHello Mark,After you did the complete uninstall, did you try manually deleting all the registry keys for FSX and then do a fresh install? Just wondering if that works better. Uninstall doesn't necessarily remove all the registry entries from the uninstalled program.Cheers,Mark.

The problem is now in MS Knowledge Base:http://support.microsoft.com/kb/928080/en-us?spid=11941I have not said it,but the tool worked for me at the second atempt.At the firts i was not runing it in command line but simply by clicking in it which has no effect!

>Gents,>>I had exactly the same problem after using the new KB928080>tool to reset the activation. I ran the reset tool, tried to>reinstall FSX several times, and still received the same 1722>error as before. In response to my query, the following>advice was posted in the MS Simulations forum:>>"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

Me too, any suggestions as to how get rid of ">" Ive been trying to fix this for over a week now. (sobs)

>Me too, any suggestions as to how get rid of ">" Ive been>trying to fix this for over a week now. (sobs)Glad I'm not the only one. I was beginning to get a complex.

Simon, I am currently posting on various forums in search of answer. I must have wasted about 24 hrs of my life trying to reinstall this game. Not impressed! By the way did you install demo prior to installing fsx?

>>Me too, any suggestions as to how get rid of ">" Ive been>>trying to fix this for over a week now. (sobs)>Glad I'm not the only one. I was beginning to get a complex.You never used DOS, did you?The > is just a symbol. It's marking the prompt and calls you to enter something. You can even change that in the config-files to your like.If you have c:>, then everything is as needed. Everything left of the > is the directory you're at.PS: You should check if the file exists on c: ... I don't know if it's a directory or a file, but if there is no c:MicrosoftKB928080, then it's no wonder it can't be found. Also, did you type it without the ""?

Jedi, firstly thanks alot for reply and no, ive never used dos before, the general equation runs thus:Me + Computers = Confusion.So, I know ive got "MicrosoftKB928080" cos I downloaded it. Its in my documents. So just to re-iterate, in the command prompt do i typec:MicrosoftKB928080 or MicrosoftKB928080?, I know its without the "Thanks again.

Try "cd MicrosoftKB928080" instead. I think someone mixed it up.From what I've read now, it's a directory. So going from c: to c:MicrosoftKB928080 via the cd command should be best. Also, instead of typing "cd.." again and again, you can use "cd"They treated it as if it was an executable, but as I understood, the fix is already extracted to the directory at that point.I would translate the post to:1. Once you are in DOS, type "cd" then hit the return key.2. When at c: type "cd MicrosoftKB928080", hit return.3. Type "resetsldl