activate xp

[n3m3]

Hi you all.

I have a small question.

I have a quite new system,now i replaced some parts and now it wants to validate windows.

I thought that it was a leagel copy of xp but it looks like its not.

So i got my self a licence from work,my job will pay for it.(its their multi licence code)

this will be a computer that i will use for work.

but here comes the problem.

I cant get it validated with the new key.

when i look at the system properties it says oem and dell,and i dont have a dell.

So i think that the cd i used was some kind of coperate version of a dell xp,

now i try to validate it with a key that i know works,that i use at work and have ok to use(its a multi licence key)

But i only get invalid key.

Does the XXXXXX-640-7721335-XXXXX from the system properties have anything to do with the validation?

Cause my com at home has XXXXX-Oem-XXXXXXX-XXXXX.

And if i change that will i be able to activate it?

Thanks in advance

n3m3

Edited October 4, 2006 by n3m3

[cluberti]

If you have a VLK key from your employer, but you have an OEM or retail version of XP installed on your machine, you will not be able to get Windows to activate with the VLK key. You can only get things to work properly if you use a VLK key on a VLK install, an OEM key on an OEM install (and you must differentiate between a PC-vendor OEM version and a "retail" OEM version, they're different), and a retail key on a retail install.

However, if Windows is just asking you to reactivate due to the hardware changes, change your key back to the one that came with your computer and call the clearinghouse number in the activation wizard. Microsoft will give you an activation code that you'll then type in, and it'll reactivate with the old key no problem.

[severach]

>I have a quite new system,now i replaced some parts and now it wants to validate windows

If you removed the Dell motherboard and put in a non Dell motherboard your system will not preactivate with the Dell media. If you install from an OEM Single User License media with the side-of-case key you should be able to beg an activation code from Microsoft if your story is good enough.

>XXXXXX-640-#######-XXXXX

By printing the 7 digit number you've told everyone at Microsoft which company you got the key from. I recommend editing it out. You've X'd out the unimportant numbers. The first number is the media type and the last number for a VLK key is 23+Timestamp.

>XXXXX-Oem-XXXXXXX-XXXXX

If it currently says XXXXX-OEM-0011903-XXXXX then you need to reinstall from VLK media with your legitimate corporate key. I don't think there's any keychangers that will switch from an OEM to a VLK license.

Edited October 5, 2006 by severach

[Tarun]

XXXXX-640-XXXXXXX-XXXXX

devils0wn probably.

640 through 648, 652 : Volume License (usually generated via 270 CID in setupp.ini)

As of 2005/10/22, Microsoft states that the following are invalid PIDs:

• XXXXX-640-0000356-23XXX
  
• XXXXX-640-2001765-23XXX
  

The above two product IDs are known as "Devil's Own", and usually have a product key starting with "FCKGW".

I have a list of more invalid PIDs too.

[cluberti]

Actually, the parent never pasted the last 5 digits, so we can't be sure it's a devil's own or keygen'ed key, but it is possible. What's also important to note is that it is the last 5 digits of the PID that are the important part of the PID, not really anything before, for most installed PIDs. If your key has generated a PID where the last 5 digits are 23xxx (with xxx being any numerical values), it becomes suspect at least that the key used to install XP was not a valid Windows XP product key issued by Microsoft. Not all keys that generate 23xxx PIDs are blacklisted, but all officially blacklisted keys end in 23xxx, so if your PID ends in 23xxx I'd be at least skeptical.

Edited October 5, 2006 by cluberti

[n3m3]

Thanks for the reply you all.

cluberti,cant type in the key cause its "banned" by MS.

I googled the key and i found it on like 1 billion sites,so its no wounder i cant use that one.

I was about to change the key anyway cause it will be used as an work machine,so all the software on it must be legit.

The key i would like to use is not a "stolen" key,its from my work and its payed for.

The 7 digit number i typed was not taken from my comp,i only wrote something to illustrate the difference

One says oem and the other says 640.

Has anyone uses the sysprep tool to change the installed settings?

Ill try it today and give you all some feedback.

[severach]

How does this MS employee know what company the Office key belongs to? There must be a number somewhere large enough to encompass all of the companies that own VLK copies of Office and a lot of slack space to identify the fakes.

http://forums.microsoft.com/Genuine/ShowPo...6&SiteID=25

000035, 200176

The first 6 digits of the 7 digit number are the company ID. The 7th digit is a check digit. The two famous keys that are blacklisted are blacklisted because they are formerly legit keys issued by Microsoft that would otherwise pass the legit check algorithm. All keygen'd keys are non legit keys so they don't need to be blacklisted because there's an algorithm that easily calculates that they are not legit.

>so we can't be sure it's a devil's own or keygen'ed key

We can't be sure because we don't have the algorithm. The last 5 digits are only a randomizer allowing ghosted installs to be detected if necessary. They are 23+Timestamp for all the legit and non legit VLK keys I've seen. Other key types do not use the last 5 digits in the same way.

>the last 5 digits of the PID that are the important part of the PID

>If your key has generated a PID where the last 5 digits are 23xxx (with xxx being any numerical values), it becomes suspect at least that the key used to install XP was not a valid Windows XP product key issued by Microsoft

They are completely unimportant. All legit and non legit VLK keys I've seen end with 23xxx. Microsoft matches the 6 digits in the PID against a database of valid keys to identify possibly invalid keys or runs an algorithm against the original key to be certain.

>I'd be at least skeptical

Having never seen a legit VLK key end in anything other than 23xxx, I'm not at all skeptical and I won't be even if I do run across such a key. There's just too many legit keys that end in 23xxx. All the misinformation has encouraged the OP to tell Microsoft which company he works for or has stolen a key from. Don't make it so easy for them.

Grab the 6 digits mentioned out of any legit VLK PID and put them into the 4 in 1 keygen. My example uses FCKGW:

Product Family: ... VLK ...

Product Range:

From 640-000035

To 640-000035

... and hit generate a few times. Every key shown will generate the same PID with the last 3 digits always being random but only the legit original will activate. Why does the keygen only ask for those 6 digits? Why are all the keys generated by my example blacklisted when only FCKGW was blacklisted?

http://en.wikipedia.org/wiki/FCKGW

[cluberti]

Having never seen a legit VLK key end in anything other than 23xxx, I'm not at all skeptical and I won't be even if I do run across such a key. There's just too many legit keys that end in 23xxx. All the misinformation has encouraged the OP to tell Microsoft which company he works for or has stolen a key from. Don't make it so easy for them.

I am well aware that all VLK keys end in 23xxx. However, since his machine was a Dell I made the assumption that it was possible that he would have an OEM version of XP installed. An OEM key ending in 23xxx is at the least very suspect (in fact, I know of no OEM vendor keys ending in 23xxx, but I don't have access to the database, so...), but at the time of the original post I was not completely sure from the last 5 digits that the key to his install was blacklisted. I am well aware that a lot of companies reimage or reinstall OEM hardware with OEM installations of XP with a VLK install before giving to employees, so at the time of the original post we did not know for certain who installed the OS on the Dell machine originally, and thus if it was legit or not. Since it now appears that the possibility of his company's corporate VLK being used for the installation originally is highly impossible, then an OEM machine with an XP PID ending in 23xxx is at least suspect (and of course subsequent posts have proved that this was indeed a blacklisted key used to install the OS on his machine).

It's probably the long way around, but I wanted to make no assumptions about the key used to activate Windows on this machine until told for certain the key was a leaked key, so I treated it is a possible legit VLK install on an OEM machine, but also a possible non-legit VLK install on an OEM machine (with of course the latter being correct).

Has anyone uses the sysprep tool to change the installed settings?

Ill try it today and give you all some feedback.

It may work, but generally this is not considered a "supported" way to change the key and was never a testing scenario for sysprep. It might work, but I'm guessing it will fail due to the install being a VLK install and the key being a vendor OEM key.

Edited October 6, 2006 by cluberti