locked
Windows XP Sp2c and product key update tool RRS feed

  • Question

  • Is the product key update tool expected to work with Windows XP Sp2c?

    I get the error 0x800402c9 ...low disk space... when I try to set the product key for Sp2c for the first time since I use this tool.
    Tuesday, January 22, 2008 12:45 PM

Answers

  • The only product key that will work with a Windows XP SP2c CD is the OEM product key it came with. If you created your own Windows XP SP2c CD image, OEM products keys released prior to SP2c will not work.

     

    Tuesday, January 22, 2008 1:36 PM
    Moderator
  • BSander,

     

    Yours is an unsupported and unwise method of deploying multiple Windows installations.

     

    The only supported method for deploying Systembuilder/OEM installations of XP is the OEM Preinstallation Kit.

     

    The only supported method for deploying VL installations is the Sysprep method plus third party disk duplication tools.

     

    If systems deployed with your method are used on a network, they may display unusual and mysterious problems operating within the network if the Key Updater Utility does not also change the Windows installation's GUID or SID.

     

    Wednesday, January 23, 2008 2:12 PM
  • I have read your post in its entirety, and what you are trying to do by loading an image then changing a key is not going to work well if at all. I and others who have responeded to your post do understand your question and what you are trying to do.

     

    The Key Change utility was not designed to be part of the imaging process.

     

    I will go thru the steps so you will understand.  I know that this is not the answer to your direct question does the key tool work with sp2c.  That answer is yes it works like it is supposed to.  The problem in your case is that you are not using the tool for what it was intended.  You don't use a hammer to put a screw in a wall.  Sure the screw will go in but you will not have a satisfactory result.

     

    Here are the steps for imaging.

     

    Do a full installation on your first PC.

    Configure this PC the way you want it.

    Make a folder called Sysprep on the root drive. (Usually C:\)

    Copy the contents of the tools\deploy.cab file from the instalation CD into the Sysprep folder you made.

    Remove the CD from the drive.

    Open the Sysprep folder on the root drive.

    Run the Sysprep.exe utility.

    Select the option to reseal.

    Answer any prompts to overwrite user and system id's with "yes"

    The utility will then run and turn itself off.

    Make an image of the drive you just created.

    Restore the image you just made to another drive.

     

    You can now use the two drives on the two machines.

    Whan you boot them up they will ask you for the new info.

    You can use your original product key on the machine you made the image from and your second key on the second machine.

    You can also use this image on any other identical hardware as long as you have the product keys to support it.

     

    This is the most basic solution that I have given to you.  It is also the fastest for low volume duplication on identical hardware.

    Wednesday, January 30, 2008 2:02 PM

All replies

  • You may wish to perform a "tune-up" that may help:


    1.    Perform a DISK CLEANUP:
           (Start > Programs > Accessories > System Tools > Disk Cleanup)

    2.    Go to Start > Run and type:  CMD  , and hit enter.  In the Command
           Prompt window type:  CHKDSK /F  , and hit enter, answer "yes" and
           reboot your computer.

    3.    Afterward, perform a DEFRAG of your hard drive.

    Tuesday, January 22, 2008 1:06 PM
    Moderator
  • It is a clean and fresh system with 100 GB free disk space. CHKDSK /F was the first thing I have already made.

    May be the problem is the non re-release Windows XP Sp2c?

    http://oem.microsoft.com/downloads/public/seo/winxp_sp2c.htm
    Tuesday, January 22, 2008 1:28 PM
  • The only product key that will work with a Windows XP SP2c CD is the OEM product key it came with. If you created your own Windows XP SP2c CD image, OEM products keys released prior to SP2c will not work.

     

    Tuesday, January 22, 2008 1:36 PM
    Moderator
  • The image was made with XP Sp2c and I assume the key is of XP Sp2c too, because the OEM CD's have been purchased at the same time from the same retailer.
    Tuesday, January 22, 2008 1:49 PM
  • Why do you want to change the product key then?

     

    Tuesday, January 22, 2008 1:52 PM
    Moderator
  • I am going to install one of two identical PC's with an image in order to save time.
    Tuesday, January 22, 2008 2:10 PM
  • Preserving OEM Pre-Activation when Re-installing Windows XP:

    http://technet.microsoft.com/en-us/library/bb457078.aspx

    Tuesday, January 22, 2008 4:17 PM
    Moderator
  • Windows had not been pre-activated by the original manufacturer.

    I give the procedure of my actions of the installation of two identical PC's with an image in order to save time.

    1. Make an image of an activated Windows of the master PC.
    2. Finish the original pre-installation of the second PC without activation.
    3. Copy the image to a local partition.
    4. Restore the image.
    5. Now there are two PC's with the same activated product key.
    6. Run the Microsoft product key update tool on the second PC in order to reassign the original product key.
    7. Restart and activate the second PC.
    I have successfully made these installations prior to Sp2c.

    My problem is, that the windows product key update tool (step 6) does not work.

    Wednesday, January 23, 2008 6:45 AM
  • BSander,

     

    Yours is an unsupported and unwise method of deploying multiple Windows installations.

     

    The only supported method for deploying Systembuilder/OEM installations of XP is the OEM Preinstallation Kit.

     

    The only supported method for deploying VL installations is the Sysprep method plus third party disk duplication tools.

     

    If systems deployed with your method are used on a network, they may display unusual and mysterious problems operating within the network if the Key Updater Utility does not also change the Windows installation's GUID or SID.

     

    Wednesday, January 23, 2008 2:12 PM
  • Hi Everybody!

    Thank you for the answers.

    But I still have not got the right answer.

    The only thing I would like to know is, wether the product key update tool can be used with Windows XP Sp2c.

    Wednesday, January 23, 2008 3:46 PM
  • Bernd,

     

    I'm having the exact same problem.  I found this thread, hoping for some answers, but none yet.  Hopefully, someone out there will know.  I've spent hours on the phone with MS and I can't get anyone on phone who even remotely understands the problem we are facing.

     

     

    Wednesday, January 23, 2008 10:52 PM
  • I have read your post in its entirety, and what you are trying to do by loading an image then changing a key is not going to work well if at all. I and others who have responeded to your post do understand your question and what you are trying to do.

     

    The Key Change utility was not designed to be part of the imaging process.

     

    I will go thru the steps so you will understand.  I know that this is not the answer to your direct question does the key tool work with sp2c.  That answer is yes it works like it is supposed to.  The problem in your case is that you are not using the tool for what it was intended.  You don't use a hammer to put a screw in a wall.  Sure the screw will go in but you will not have a satisfactory result.

     

    Here are the steps for imaging.

     

    Do a full installation on your first PC.

    Configure this PC the way you want it.

    Make a folder called Sysprep on the root drive. (Usually C:\)

    Copy the contents of the tools\deploy.cab file from the instalation CD into the Sysprep folder you made.

    Remove the CD from the drive.

    Open the Sysprep folder on the root drive.

    Run the Sysprep.exe utility.

    Select the option to reseal.

    Answer any prompts to overwrite user and system id's with "yes"

    The utility will then run and turn itself off.

    Make an image of the drive you just created.

    Restore the image you just made to another drive.

     

    You can now use the two drives on the two machines.

    Whan you boot them up they will ask you for the new info.

    You can use your original product key on the machine you made the image from and your second key on the second machine.

    You can also use this image on any other identical hardware as long as you have the product keys to support it.

     

    This is the most basic solution that I have given to you.  It is also the fastest for low volume duplication on identical hardware.

    Wednesday, January 30, 2008 2:02 PM
  • Thank You for your answer.

    I have been avoiding to use sysprep, because I thougt it would not be that easy. I think I have to give it a chance.

    Monday, February 4, 2008 6:45 AM
  • Bryan,

     

    Thanks a lot!  This worked beautifully and set me down the correct path to customize sysprep for me needs.

     

    Thanks again.

     

     

    Wednesday, February 20, 2008 7:25 PM
  • This whole problem with the Key Update Tool seems to be something that just recently happened. Before last week, the key update tool worked perfectly. However, now this error about low disk space started appearing. This error occurs before any key is entered, so it can't be due to key versions being invalid. With 127GB of free hard disk space, I doubt that's the cause for this error.

    I understand that Sysprep is the most supported and recommended way of imaging produced computers. But for right now, I have zero time to create a computer image from scratch and utilize Sysprep.

    Any ideas on what happened to the key update tool? Also, I think the tool has something to do with an activation loop I am starting to see. That's a different issue.
    Thursday, February 21, 2008 12:41 AM
  • Hey Taylor,

     

    What you are saying does not make sense.  You say you have zero time to create a computer image from scratch and use sysprep.  If you are not using an image then what you are doing now will take longer every time.  I do this very procedure from 75 to 100 time a day.  There is not a better way.

     

    Please list the current procedure you are using.  If you have not entered a key then you should not have to use the key update tool.

     

    Bryant

     

    Thursday, February 21, 2008 12:57 PM
  • Are we trying to ignore the fact that the Key Update Tool doesn't work anymore?

    I understand that my method of ghosting a system and using the Key Update tool to change the key is not a prefered or supported method, but does that mean it's ok for the Key Update tool to not work anymore?

    How long can we beat around the bush? The Key Update Tool does not work anymore. Is there going to be a fix for this?
    Thursday, February 21, 2008 9:51 PM
  • As I have already stated earlier in this post the key update tool works for what it was intended to do.

     

    Now lets address the real issue.  If you are ghosting a machine then you should be using sysprep.

    In a previous post you said you did not have time for this.

     

    let me give you a point of reference\

     

    One day a man drives his car to a station and it has a flat tire.  He airs it up.  The next day he returns and the tire is flat and he airs it up again.  This continues for few days.  On the seventh or eighth day the man with the flat goes up to the attendant and says the air pump is not working correctly.  The attendant checks the air pump and the hose and fitting and everything is fine.  The man tells him every day he comes in and puts air in his tire but today it will not air up.  Something has to be wrong with the air pump.  The attentant then askes the man if he would like for him to fix the hole in his tire.

     

    What is the real reason you do not want to do this the right way?

     

    Friday, February 22, 2008 1:31 PM
  • Will all the unhelpful repliers STOP being TOTAL TOOLS... the man is asking why the windows product key update tool will not work and is coming up with an error.  Forget how he wants to GHOST, how he should GHOST.. start another thread if you are so concerned.

     

    I have tested it also, and found that the current product key tool, on a BRAND NEW hard drive with 280 GB of space is coming up with the same error.

     

    I can tell you right now... NO ghosting, no imaging... straight install, trying to change the product key, simple as that, don't over complicate it.

     

    it doesn't work!! 

     

    Thursday, February 28, 2008 6:25 AM
  •  

    Hey Brenton,

     

    Your post is very similar to some others in the fact that some necessary information seems to be missing.

     

    In your post you stated that you performed a straight install using no imaging process.  When you did the install, why didn't you key in the correct key during the instalation?

     

    I have reviewed every possible instance of when the key change utility should be used and have not had any problems using it in situations it was designed to be used in.

     

    Please understand.  No one is saying that there could or could not be an issue.  What I and others have pointed out is that so far every post about this issue reguarding the key change utility on this post and others like it have all been from people trying to use the utility in a way that is was not designed for and now that way is no longer an option.

     

    If you would describe an instance where you are seeing a failure in detail, I and others would be glad to help.

     

    As for the comment about people being total tools and starting a new thread, I am reminding you that it is you that is posting to a sucessfully answered and marked thread.

     

    Bryant

    Thursday, February 28, 2008 5:22 PM
  • ok... the reason i am using the product key tool is...

     

    the machine i am re-installing on has an XP pro license that was an upgrade. Therefore it won't accept my product key to move forward in the install process.  So, i use the license key from the full retail version of the office machine next to me to get the install going.  Then once installed and before activation, i swap the key back out for the "upgrade" key and it always works a treat.

     

    Can anyone suggest a better way for fresh install when you only have an "upgrade" license number?

     

     

     

    Thursday, February 28, 2008 11:29 PM
  • OK!!!! found out what it was.  It's the latest microsoft updates!!  I did a windows repair reinstall taking everything back to SP2... and then the key worked fine.  Once the SP3 updates were installed, the update key tool no longer worked and came back with the error.  So it is something in SP3 (or one of the latest updates).

     

    Friday, February 29, 2008 3:13 AM
  • That is correct Brenton.  Product keys only work with the OS release they are issued for.  There are no keys for SP3.  This may be the same problem other users are having.

     

    Monday, March 3, 2008 7:18 PM
  • Tuesday, March 11, 2008 7:32 PM
  • We have been following this procedure since XP came out. The reseal process always let us reseal multiple times when we pushed Ctrl-Shift-F3 together. Now with sp2c the window to accept still comes up but it will not let us reseal again. We click the accept button and the accept window goes away. We sell 1,000s of units a year and really need this tool.

    Thanks, for any help you can provide.

    Steve

    Tuesday, March 11, 2008 7:40 PM
  •  

    Your message is not clear.  You mentioned reseal so I will make an assumption that you are using Sysprep.  You should not have to reseal an image more than 2 times.  Please post what you are doing in steps.  I will try to help.

     

    This may be an off topic post.  Are you haveing problems with the product key update tool or the sysprep utility?

    Tuesday, March 11, 2008 8:55 PM
  • Bryantwalley you are a supercilious twit (wanted to use another more appropriate word) . You are constantly ignoring the question asked to give your self importance an airing by telling everyone how it 'should be done' . In the REAL WORLD, many ways are used to achieve desired results and all people are asking is how to legitimise their installations to avoid contravening microsofts license policy. If you don't want to give a straight answer, or are unable to, then don't just spout off on how YOU think people should do it. Just help people with the answer to the question they actually asked and not what you think they should have asked, or get lost. You are not being helpful.

    Are you a politician?? You should be.

    Friday, May 9, 2008 10:31 AM