There is no activation on VLK. You can still install retail XP on more than one machine, though, but that's not my point. M $ must know what they issue as keys, no?

Would just be a waste of time and money. Trust me. Piraters will always win.

I'll second that!

so any PID that was on the list that came with the crack is going to be blocked I checked and all those PID's are from the list

I'm using a lagit OEM copy so I don't need to worry

I can buy OEM 3 packs for 249.00 at pcclub or I can goto pcbuzz and get 1 copy for 144

all you got to do to get a OEM version is buy some pice of hardware any computer hardware it can be as small as a IDE ribbon cable that will allow you to purchase the OEM version

will there is a problem with the Data base part Microsoft would have to add the key's PID to the database as the key's are shiped out with the cd's

this would make there database huge not to mention it would most likly slow there servers down

it's better and cheaper for them to do it the way they are just adding the known PID's that are bad

Why would they need to worry about PIDs if they issue the keys in the first place?
Do the keys come from somewhere else? In fact, I don't understand the reason for a PID to be the validity check. Why not just use the key? It just adds extra garbage for them to sift through. Maybe I'm missing something, unless M $ is just too huge to keep track of itself.

the PID is some screwed up version of the key. in other words: the pid represents the key and ur hardware settings combined. Microsoft checks 2 PIDs and if the keys match but the hardware doesnt, it invalidates the keys (usually does it on a larger scale, such as if 50 ppl share 1 key using diff. hardware (and its not corp))

well.. ok.. I did it..

First I uninstalled SP2 RC2 completely, then I reinstalled and after that I was able to acces Windows Update v5 with the same key that didn't work before doing this

I don't know why, but hey.. it works

Hey folks,

Thought Id just chip in with my experience with the SP2 cock up..

I had a legit copy of OEM Windows XP pro, which came with my machine....it installed SP1 no problems, but SP2 it barfed...would install and all sorts of problems, even when I re-installed a clean copy (off recovery disks).
In the end I had to errrrr 'gain' a copy of XP pro (as e-mails to Microsoft came up with nothing) and generate a PID of what people have been suggesting.
I went for the xxxxx-640-500xxxx-xxxxx range, and can report, this works fine.
So..SP2 and even Microsoft Update works (using V5 I see!!), so seems all good

Good old Microsoft as it seems the only way to get things working is to bugger things around...
Maybe Linux isnt such a bad idea!!!

Be glad to offer help to anyone if they need it.

Cheers

xxxxx-640-0647xxx-xxxxx Werks for me

I'm (way) over due for a new comp, but had to reload the old one this weekend & figured I'd give SP2 a shot (wtf it's faster than 14,000 updates...).

I gota say I'm likeing it as I've not seen a bugg yet. DL speed is a bit erratic (firewall?) but that may be my ISP, or the fact that I live in the lightening capitol of the friggin world and it's the "stormy" season... (hehe)

Hi folks,
This new keygen sounds like the one but how does it differ from the Bluelist keygen? Does it also change the WinXP PID?

thanks

thats a very poor first post at iexbeta

and btw its PM not PIM lol

lastly: remember this. at any beta forum, you must participate before asking for things. not sure how it is here but i kno that in some others, asking for stuff on ur first post gives u an IP ban.

edit: he asked for a keygen. since he removed the line in question, u dont need to worry about it.

Well thanks,
I stated I was a noob here so don't be so harsh! Actually I was a member here a couple years ago but can't remember the account. Anyway, I don't think jumping in here and politely asking for help is such a heinous crime but I'm sure the mods will sort me out if it is.

Interesting...you've only joined recently so perhaps you should leave the castigation to the mods?!

Okay, I've already talked with bearman about it, now let's move on ...

The "new" keygen creates cdkeys based on the PID range that you specify. Which we now know must be a PID of 640 in order to install Windows XP Pro. Corp./VLk.

Thanks for your advice and help. Much appreciated!


cheers
Bearman

Thanks for the heads up. Everything worked just fine.

Just wanted to clarify, War59312, if you say the cdkeys 640-500000 thru 600000 are the actual valid keys, then in the keygen you do need to enter 500000 to 600000 to get keys that look like 640-500000X thru 640-600000X. If you do it the way you had posted, it will generate keys from 640-000500X thru 640-000600X which according to you are not true valid keys even though they will work for now.
Now a post by ml20 had already corrected you and said the same thing I just did but you later replied



This doesn't actually make sense because if you want 640-500000 to 600000 then you can't use 500 to 600 in the range in the keygen because it doesn't make the keys in the form that you specified is the correct format so your other statements about preferring 500-600 keys is wrong and is not more "specific".

Can others also please verify/clarify these points?

yes

I think the type of PID you get from 500-600 keys is something like
640-0005xx thru 640-0006xx

but, I am not at my main computer, so I don't have the keygen and cannot test it. but the one key I tested turned out like that.

but some of the keys might be vaild for SP2, i cannot verify that either, and I won't. someone else can.

It is true ml20. There is no need for you to test if the keygen with the range of 500 to 600 entered generates keys with PID's of 640-000500X to 640-000600X because I have already done that with a bunch of keys and I know it to be true. What I would like clarified from war59312 is which keys are supposed to be true valid keys, i.e. used with actual corporate licences right now, either 640-500000X to 640-600000X or 640-000500X to 640-000600X and if it is the former then his original instructions to put 500-600 in the range of the keygen is wrong.

i have found almost all 640-100000 thru 640-200000 are valid.

Valid in the sense that 640-100000 thru 640-200000 are in actual use with real corporate licences or just valid in the sense that SP2 installs and v5.windowsupdate.microsoft.com works?

Was it just B.S. that Ixus and war59312 were talking about with respect to only 640-500000X to 600000X being true keys?

SHit yea I worded it wrong. I was in a rush. And damn tired after cleaning up after a 6 week year old puppy. Yellow lab. Has to use the bathroom like every two hours. Luckly sees not mine, but my cusins who I was watching after untill yerstery night till 5:30pm when she picked her up.

Anyways, sorry, I ment 640-0005XXX to 640-0006XXX are valid corp cdkeys they are issuing right now. I just visted Comp. USA today and talked with a friend who works there. They where issused 100 640-0005000 to 640-0006000 cdkeys as well.

Edited to make sure i typied it right that time. Missed a zero.

Which like i said are created with 640-500 and 640-600 in the keygen.

Sorry was just in a rush. Did not even noticed. Was busy.

See here is my key:

XXXXX-640-0005977-XXXXX

Also:



Ment want I said. Hope its more clear now. SOrry abougt that. So both ranges work, that is 500-600 and 500000-600000. But not all 500000-600000 are cdkeys that Microsoft are issueing. But it appears to me all 500-600 that is:

XXXXX-640-0005XXX-XXXXX

In my case XXXXX-640-0005977-XXXXX.

though:

XXXXX-640-0006XXX-XXXXX

are real valid corp cdkeys that microsoft are issuing.

I have only seen only one 5000000 cdkey used by a company and that was Best Buy in Columiba SC on Two Notch Road. Then again thats with sp1 of course.

Dont recall the key. Did not think to right the podcut id down or find out the cdkey used to install windows.

So yes 500 - 600 in the keygen like in the pic i posted earler is correct. Have not had a single problem yet. Windows update works perfectly. No lock outs, etc.

Besides if they were to blacklist the key I am using right now Comp. USA would be pretty damn pissed. lol

How effective it would be to actually generate a key that was actually issued!

Very cause more than likly it will not get blacklisted. Then again Microsoft will probally keep a closer eye one it. Like recording every ip address that tries to access windows update using that cdkey/product ID.

Thanks alot war59312. That clears everything up regarding the actual keys #'s you were referring to.

I hadn't thought of that last bit. Still, I'm thinking that the odds of generating an actual issued key must be pretty small. Look at all the numbers after the 640-0005XXX-XXXXX and there is still a large pool of numbers.

Yea true, so good luck. Then again I would not advise unless your are willing to take the risk of Microsoft montering your every move.

Warning: Users with zero posts or few posts and only have recently became a iexbeta member stop pming me. They are just deleted.

I HATE LEECHERS!!!!

Thanks,
Will

updates now workin again , lol my first key generated work , Awesome
only cost 1:30 min to reapir the updates muhahahahahahaha

Because I'm confused, which are the working PIDs? XXXXX-640-500XXXX-XXXXX and XXXXX-640-600XXX-XXXXX? or XXXXX-640-5000000-XXXXX and XXXXX-640-6000000-XXXXX? or sth else?

It is:

XXXXX-640-0005XXX-XXXXX though XXXXX-640-0006XXX-XXXXX. Those are the offical keys.

Like I said. But a few XXXXX-640-5000000-XXXXX and XXXXX-640-6000000-XXXXX keys work as well. As people in this very thread have stated. I have tried a few and they work fine and with windows update working. But I tried another few and they intalled ok but windows update does nto work.

So just find a key like the following XXXXX-640-0005XXX-XXXXX. Which is create in the keygen with range 500-600 like I have said all along.

642-465544x Works!!!!, (maybe cause its a legit corp key??)

COULD BE... but I had used a "valid" corp key from a valid source, and it would not allow it. I confirmed by contacting someone who is allowed to use that corp key and they also confirmed that the "valid" corp key with a 642 PID DID NOT work. They had since contacted Microsoft, and got a new key. He confirmed that Microsoft issued them a key that generated a 640 PID.

He did not give me the key.. as I would have expected..

I have my own tho anyhow

I have a rather (maybe obious) question about this keygen. Why is this one so damn fast, when the BlueList Keygen is so slow? They both work.

EDIT: Also, what is the field labled "Random Seed" for when it automatically generates one when the generate button is presses? What would happen if I were to enter in a value in this field box prior to pressing "Generate"?

If XXXXX-640-0006XXX-XXXXX works then in the keygen the range should be 500-699. Because if I put 500-600 it will only generate XXXXX-640-0005XXX-XXXXX PIDS. Right? Also, if I have a PID like XXXXX-640-0005XXX-XXXXX will I be able to install SP2 and use Windows Update? or will I experience locks out etc? Finally, will these PIDS work for the final version of SP2 or only for the versions of SP2 now?

@Salvation: Those are two completely different scenarios. SP2 will have its specifics check, which will not change AFTER its released. However, that may change between now and then though.

Windows Update v5, on the other hand, can and probably will be regularly revised to block additional keys/PIDs since it's an active web site.

Most likely though, MS won't ever really try to block PIDs in that range since they come from official keys. However, a few of the more exploited numbers that were say skipped over by MS may at some point become blacklisted.

I think because bluelist checks to see if the key can be legitimately activated.

I tried the new keygen with Pro Retail, and while it *does* generate keys that can be used with Windows, upon activation, the wizard returns "Unauthorized Product Key". So while it does generate valid keys, it appears that Microsoft keeps a list of issued keys so it knows which ones to activate.

Oh, OK That explains quite a bit then

Hi,
I've never been on this board, but I read it for help today.

Thanks Everyone!!

I have a Corp Edition
I used XP Key Rediscover/ Recover 5.12
(1000 runs generated 49 keys and took 2 hours).
It found one code 3 times, so I tried it. I got the following:

XXXXX-640-9189XXX-XXXXX
I used the Windows Activate Deactivator for the update. (thanks God)
Windows update (v5) works like a champ.

BTW, there aren't any updates available for download

reinstalled and used a diff. non Corp key and got:

*****-640-535****-*****

You're not the only one.

well, glad to hear your happy.. welcome to the board btw..

Awesome thread. Did a google and got the keygen. Set range to 640-xxx500/600 and v5 update works flawlessly. TYVM

Don't flood me with PM's I won't answer

Ditto

Hmmm...there's a lot of potentially hostile noobs in here? I thought you need to be a member for a year or so before gain the right to get "haughty" with noobs. v strange! Anyway, people in here are in general reasonably helpful and friendly.

top forum board

great thread, all sorted roll on SP2! oh hello BTW!

Will

leeeeecherrsss

how kind

everyone is a newbie on boards at one time, i use many other boards as well!