Changing the KeyCode on XP

  • Thread starter Thread starter JCO
  • Start date Start date
J

JCO

I re-did a computer for a friend. He did not have a CD, therefore, I used
my CD for the installation. Before starting, I managed to extract his CDKey
from the system using a free tool. Wrote the His key down so that I can
install the system using my CD. My plan was to do the installation, then
change the CDKey back to his number. Now for some reason, I always get an
error trying to make the change.

What other ways are there for me to get his computer to reflect the his old
CDKey?
I really don't want his computer using my Key, but the work is done now. I
just need to change it back to his original Key.

Thanks
 
Keys are not attached to specific CD's so much as to specific versions.. is
the version that you installed exactly the same as the version that it
replaced?
 
How would I know that. My version is a CD purchased at the store, intended
to be installed on a desktop computer (not OEM).

The Laptop that I installed on must have a different algorithm because it
won't take the original key.
Any way to resolve this? This is a Presario 2100 Compact Laptop that I did
the installation on. The thing is, I extracted the original key before
wiping it clean. It is not an OEM type.
 
The KeyChanger displays a Windows Script Host Error. It says:

"An error has occurred. This was probably caused by the keying of an
invalid number. Please check it and try again."

This is when I try to put the original keycode back on the computer.
 
Did this laptop come with XP? If it did then it IS OEM, and that is your
problem, your trying to use an OEM key on a retail install. If it did not,
does it's install match your CD? If it was upgraded using a retail upgrade
version and you did an install with anything other than a retail upgrade CD
the key will not work.
 
This laptop came with Windows Home Edition installed, however, when I
extracted the key, it did not have OEM in it. I understand what your
saying. My install is from a Retail CD.

I guess there is no way to change it?
 
As I said If the laptop shipped from Compaq with XP, it IS OEM. The product
key will not have OEM in it no matter what version it is. There is no way to
use an OEM key on a retail install.
In order to fix the problem, you need to do a repair install with an XP
Home Edition OEM CD. All this assumes you are concerned with the EULA and
your license agreements.
 
I am concerned.. that is why I thought I could change it.
I will have to get on the Compaq (Presario 2100) website and get the
recovery CD's to correct the issue. That should not be to expensive... I
think it costs about 10.00.
 
That would probably be the best/easiest solution if you can't get your hands
on an OEM Home Edition CD.
 
My friend is working on that issue now.
I'm not sure of the consequences of him keeping my CD Key or not. Maybe
nothing. I know MS is constantly checking the Genuine Key Validations.
 
Well, the police aren't going to show up at your door. If it activated with
no problems you will likely encounter no issues at all. I can't say 100%
that one or the both of you would encounter a problem as far as validation
goes.
 
Yeah I know.
I started out just trying to do something nice for a friend... and it comes
back to byte me.
 
JCO said:
Yeah I know.
I started out just trying to do something nice for a friend... and it
comes back to byte me.
Click to expand...

That's the way it happens, sometimes. :)

You don't want to leave your key on his system. This will cause problems if both systems go through a validation. The validation server will detect 2 different systems with the same key which will disable both system from using features that require validation.
 
Noted!

JCO said:
Yeah I know.
I started out just trying to do something nice for a friend... and it
comes back to byte me.
Click to expand...

That's the way it happens, sometimes. :)

You don't want to leave your key on his system. This will cause problems if
both systems go through a validation. The validation server will detect 2
different systems with the same key which will disable both system from
using features that require validation.
 
Back
Top