Windows XP PRO doesn't accept original OEM key
 

Hi !

Last days i manage to put my hand on 2 original OEM key for Win XP PRO. I went very happy home and wanted to install win using those keys. Guess what ... INVALID KEY. I couldn't belive my eyes as i was sure i copied them well from original licenses. So now comes a question ... posible only some builds of xp to accept those keys ? Or ...

Br;)

the dvl cracked version of xp needs a winxp corp edition cd-key i think.

That's right :eek:

Little hint to find a good serial:
Use your favorite search engine to find a keymaker for WinXP home/pro/corp

Tried that ... i really need it to work with those licensed keys.

Br;)

I assume you can install with the key that came with your version of xp pro.
The original OEM keys are tied to the disk they came with, so you won't be able to make it work with those specific keys.
Or you need to install your version :D with the dvls key.

What you need is to remove this key after you install xp and generate a new one for yourself. Hopefully this is what you want to do.

That gets you a clean licensed key.

Dr Pete

Thx ... Seems those keys are useless without the cd they came with. Damn ...

Br;)

try to use this key:
HH8PQ-P3KM8-VW2P4-QPQJG-KCBW9

it should work with windows update and stuff, atleast for a while. but i can always generate a couple of new ones.

hmm.. seems to be hard to get the KG over the net ...

because this i´ll attach the KG package to this post.

I´m using this a long time witout any problem (Windowsupdate incl. SP2rc) !

Maybe it works when you copy these two files(PIDGEN.DLL;SETUPP.INI) from OEM ver. into your XP pro setup directory.

...
 

Possible ... but problem is that i don't have from where to get them. Maybe some one could pm me with some dl link from corp version or attach here those files.

Br;)

There's a document available which describes how to modify the setupp.ini so that a retail windows xp pro version accepts (for example) VLK keys.

Google a bit and you will find it...

...
 

@ArC

Thx for guiding me man !!! Now i solved my problem !

For all interested how i managed that here is a short tut:


Unlocking WinXP's setupp.ini

(Original from wxw.thetechguide.com)

WinXP's setupp.ini controls how the CD acts. IE is it an OEM version or retail? First, find your setupp.ini file in the i386 directory on your WinXP CD. Open it up, it'll look something like this:

ExtraData=707A667567736F696F697911AE7E05
Pid=55034000

The Pid value is what we're interested in. What's there now looks like a standard default. There are special numbers that determine if it's a retail, oem, or volume license edition. First, we break down that number into two parts. The first five digits determines how the CD will behave, ie is it a retail cd that lets you clean install or upgrade, or an oem cd that only lets you perform a clean install? The last three digits determines what CD key it will accept. You are able to mix and match these values. For example you could make a WinXP cd that acted like a retail cd, yet accepted OEM keys.

Now, for the actual values. Remember the first and last values are interchangable, but usually you'd keep them as a pair:

Retail = 51882 335
Volume License = 51883 270
OEM = 82503 OEM

So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read:

Pid=51882335

And if you wanted a retail CD that took OEM keys, you'd use:

Pid=51882OEM

Note that this does NOT get rid of WinXP's activation. Changing the Pid to a Volume License will not bypass activation. You must have a volume license (corporate) key to do so.

best regards,
.:hack3r2k:.

Some rumor is said that m$ will relieve the restriction of using pirated VLK in sp2. But now I have known it is not true.

I usually get a VLK key from a public PC with WinXP-Key Viewer.

Maybe this file will be useful. A lot of M$'s serials.

The differences :
 

From my experience :
This is the all files different from a PRO and a CORP version :
\I386\DPCDLL.DL_ DPCDLL.DLL
\I386\NT5INF.CA_ NT5INF.CAT
\I386\OEMBIOS.BI_ OEMBIOS.BIN
\I386\OEMBIOS.CA_ OEMBIOS.CAT
\I386\OEMBIOS.DA_ OEMBIOS.DAT
\I386\OEMBIOS.SI_ OEMBIOS.SIG
\I386\PIDGEN.DLL
\I386\SETUPP.INI

The keys uses this array "BCDFGHJKMPQRTVWXY2346789" (ie PidGen.DLL:SetupPIDGenA)

setupp.ini :
Pid=?????OEM => unique OEM key

ProductId :
MMMMM-NNN-PPPPPPP-QQQQQ
MMMMM= (cf. PID=MMMMM...)
NNN (640 if PID=?????270)
PPPPPPP depends on S/N
QQQQQ fonction of the hour

ExtraData
Ex: 617466716E636E6A756D9A251AC0D0
617466716E636E6A756D 9A251AC0 D0
"atfqncnjum" 9A251AC0 D0
SUM = 5D0 (so 0xD0 is a sumcheck)