all of the above works fine with one exception.

its unlikely your going to find any vlk key that works.

the check is doing something more then checking keys against a database.

you can get keys that should be valid by showup as not belonging to your system.

somehow the check can tell if your system is supose to have a vlk key.

how is up in the air at the moment since i have had no time to check.

why?
i got 1 try to find a legal key...theres no problem generating pids lower than 640
an *lol* its not even need to use the key,u only need the checksum,*GGGGG*
triple *lol* trixie even works fine till ow

i really dont understand whats the problem of this thread,all is fine,when u r able to use google,or not?

I got something last week about not passing WGA and now it's working... Maybe last week there was just a flaw in the system? And my key is from the 4in1keygen...

Well, I used the VLK Keygen. Changed the first field from the default 640, to 64 (used a range of 500000 - 600000 for the second field as always) and guess what? Key passes the WGA check in both Windows Update and when downloading programs such as Microsoft Antispyware. I don't know why it works, I just know that it does, and that's good enough for me.

Dirtie, I tried to PM you, any chance you'd share that working key?

your PM folder appears to be full... but mine isn't

As of 12:14 PM Pacific time on August 5, 2005 the following PID passes WGA:

XXXXX-640-0000347-XXXXX

that's well weird. I thought to install sp2 it had to be in the 640-500000 to 640-600000 range but i can confirm that your method does work.

Problem is it's just a temporary fix...the original key is restored upon logoff/reboot. We still need a more "permanent" solution

now if some guys had read the whole thread instead of being smart asses they would know this...lol

already been said that this has more to do with then just the key this time.

doing a temp change or even permint change of the ky wont work tell we figure out what going on.

I didn't realise the original key was restored on restart O_O
The Magical Jellybean keyfinder has always worked fine for changing my key until now.

So how exactly do you change your key permanently now?
I don't wanna have to checge my key temporarily every time I access Windows Update.

DevilotX: For some reason I don't have a PM function, perhaps I need more posts first. Just use the 4in1 keygen and the instructions I posted.

I was able to get permission from work to use their key and changed mine to theirs using Jellybean and have experienced no problems with the key changing back.

@Dirtie: You need to have ten posts before you can access the PM system.

You are of course correct that the original key is restored at start up. However, after some research i have determined that rather than changing the whole key you simply need to modify the digital productid in the registry to 064 not 640 and then close regedit and both updates and the download centre work. Then again the original key will be restored on reboot but how difficult is it to make a startup script that makes this registry modification. My concern is that microsoft will fix this little hiccup rather quickly.

Where abouts in the registry is this value?

magnus33 There is nothing magical going on here. U simply need a key that passes there database if u do not want to use workarounds or they have changed something that is rejecting the keys from the keygen(generating bad keys now?). I have been allowed 2 legit VLK from work and have used the jellybean to change my key on a corporate copy(sp2) and it works perfectly fine. I have rebooted several times the key stays and no reverting back to old key and it passes all there checks fine. As far as whats going on with the switching the 640 range to other ranges like 64 I dont know whats going on but the key diffently doesnt belong with the corporate release. Probably is why the key is not sticking. Another thing is I have tried to do reinstall on another box using that 64 key range that bypass's the wga checks in window and first boot after install it kicks you to the login screen With only a adminitrator account no other choices. The assighned admin password does not work and it tries to force you to reg. otherwise u can not continue so the key diffently doesnt belong.

This is really no diffrent than what they have been doing in the past for example when devilsown rolled out they blacklisted the key. windows thought it was a legit key enuff to get u intalled but u couldnt hit the update site. Along came the bluelist keygen which got around that then soon as sp2 was in beta one of there RC releases demostrated that they could refuse the certain ranges from the bluelist keygen. Then here we are with the 4and1 keygen nothing diffrent windows up to this point thinks its a legit key until u goto the update site once again. So did they narrow the ranges on the keys? or are they comparing it to a actual database where u would need a valid vlk within the ranges or actually assighned? All I know is legit valid keys are working perfectly fine on what ever machine installed on and whatever corporate release used

Everything else is left up to the keygen experts if there is a way they will release something out there, but only time will tell. Until then there is exploits(workarounds) or having to open your pocket book and having to finaly purchase your windows.

magical no.

and the work arounds do work for the moment but lets get off this find a keygen that works foolishness shall we.

its takes no brains to see that more then a simple key check is going on here and i suspect its none too complacated.

whatever coders did this weren't anything more then rookies since this is a joke in the protection area.

do store bought keys work yes and there cheap enough to buy (i did).

and if you had read the whole thread you would know that i already said older key changers don't work but newer ones are around and you can change them to anything you want not just a range.

admin acount is not needed fro changeing the key and this sillness with the 64 instead of 640 works fine to a restart since the check can't add up the numbers tell a restart .

the only reason this weak codeing has lasted this long is because theres so much code to go through, but by next week i think this should be fixed more permintaly.

ps..no keygen at present offers a solution.

pps.. this database check is more then alittle unlikly.
for one person a check would be easy and quick
for millions of computers 24/7 for different programs its insane
there does seem to be a check but its much simpler then you think.

well take it 4 what it is worth but the windows 4in1 keygen pumps out perfectly working keys if u know a exact working pid range to work with, so hitting it randomly for example a 640 and range of 0-999999 and having to manualy enter the keys and check with there valadation system each time(manually) goodluck u will need it. I tested several generated keys in my valid vlk working range and it worked fine even after reboot the keys stuck and hit the update site with no problems. Odd thing I did notice is I'm not sure what triggers it mayb to many bad keys or to many key changes but after awhile windows update fails on this machine that I have been playing with it on. even with a legit key, while my other windows box works fine with the exact same key.

Hi , just wondering if you can give me a valid PID range for windows xp vlk keygen , have tried many but all i get ís that it is not issued by microsoft .

I'm sorry I wish i could and I dont wish to appear to b a d*ck. My company has trusted keys to me on computers that they have supplied me and I dont want to jeprodize that sence I dont fully understand this myself. I like magnus33 and the rest of u folks are just really curious in what MS has done and how it works. I actually just stumbled on this cool board one nite and this topic kinda caught my attention and was intresting non the less. I am sorry hope u understand.

ok i found out why my legit key became invalid. but first some not so cool news ok first i had my legit key in. i then generated some keys that where in the product range and seemed to b fine and stayed after reboot with the jellybean and even passed validation. Not all keys in the range seemed to b good though. Once I hit a bad one and entered it into system with jellybean it seems to put up some sort of flag on the system causing all keys in that product range to report back as invalid including the legit one. I dont know how to reset it so i just did a reformat on my spare box. I used one of the keys that looked to b fine that was generated and everything seemed to go well but it failed the validation. Now i tried to change back to legit key and that key failed validation aswell. So I did another format used my good key and it worked perfectly fine again. Does MS do this on purpose to mayb fool what could b future generators that might try to bruteforce and check against validation or to screw with the current one or or cold it b some sort of glitch lol? I think its to screw with the current one to keep u from trying to generate a key or install key based off a legit pid. Whats your thoughts? If someone knows please b kind to explain

ps..no keygen at present offers a solution.
So magnus33 it so far seems u might b right atleast not a quick and easy way with currrent keygens. u could b generating to pigs fly?

Well if Microsoft charged a reasonable amount and let you put a legit copy on at least two computers that you own, we really wouldn't have a problem. But I don't think that is slated to happen any time soon, so I say good luck to the key crackers.

Didn't work this way for me.

I'm a little confused. I don't understand how some people are not having their original PIDs restored upon reboot. Has this problem been resolved?

How are you changing the PID? By entering a new key in the activation screen or by modifying the registry?

d00mzday - I have question for you. You said ... "Once I hit a bad one and entered it into system with jellybean it seems to put up some sort of flag on the system causing all keys in that product range to report back as invalid including the legit one..."

I am rather hoping you are correct and the legit key simply doesn't work on that system. However based on situation at work I'm concerned that it might be the entire pid/key is flagged as invalid for x-hours. I raise this question because my legit key failed WGA a few days ago - I got fed up and left work to tackle the problem the next day - But the next day the problem was gone and the same system passed WGA! I never bothered to follow up because all was well.

Now you got me wondering if a legit key can be knocked as invalid for x-hours as an MS attempt to thwart an outside agent trying to keygen up a valid key.

Can you (or anyone else who reads this), Do us a favor, and try a test where two systems have the same valid vlk key and both pass WGA. Then do your magic to try various keygen keys that make the same PID but fail WGA. Once this happens, put the original key back and prove that this valid key now fails WGA on this system.

Now he's the $64 question - try a WGA on the machine that was working fine and left alone during this entire process. If it too fails WGA then hackers can hinder a legit site simply by trying to hack their key YIKES!

However it the 2nd pc still passes WGA then the problem must be a registry/DLL setting local to the PC being messed with, which if thats the case comparing before/afters should yield what is causing this local problem.

Let us know the results.
Thanks in Advance.

Excellent question. One I had (or still have) as well. My take is that this seems to be a private hell enjoyed by some. My tests, and that of prior posters such as busman401 show that this does NOT happen when key being changed to is a valid key. (not sure if valid means keygen valid or WGA valid).

I know that when key is WGA valid, there is NOT an issue. As for what we used, Both I and busman401 used the utility "magical jellybean" to change our keys.

actually during this time the system that would not pass the validation check with my valid key i did turn around and run to my other system that had same key and checked the update site with it. It was running no problem and passed validation so the protection seems to only takin place on the system your screwing with and not ms side which of course does make sence and also as noted fixed quickly with a quick reformat and reinstall of the os with a licenced valid key. I just checked my machine that I was doing all the playin on and u seem correct. Whatever it is doing with banning the range or what have u, it does seem to b time related because all is well now on the machine. Validation with the legit key is passing once again on that machine. Come to think of it now I wouldnt be a bit surprised if they where using method with every key that fails the validation check to make it more difficult if not impossible for users to try to test and find keys with current keygen and keychangers unless u get lucky on the first shot.

I am just using the magical jelly bean keyfinder 1.41 to view and change my key for sp2. The reason it didn't resort back to original key or pid during reboot was because I was trying to see if it would generate valid keys in my 640-xxxxx range where I do have a legit key already and using the 4and1 leaving the the 640 range but adjust the 0-999999 range to match my xxxxx range to see if mayb ms just tightned up ranges more. But ya if you are using the 64 or the 1 or i think there is a couple other ones, then no it won't stay far as I know and resorts back to your old what use to be valid key because they are outside of the corp range and infact are not even working keys for the corp releases. Like magnus33 said some hiccups in ms stuff and I imagine they might start slowly closing these loop holes over time.

I've read elsewhere to try using a PID with 700. So I created a key with keygen in the 700 range. This will pass WGA as well as allow you to download updates.

However, it does revert back to the old key after reboot.

I've read that there is a file that you can write-protect and the key would not revert to the original. Does anyone know which file this is?

As someone has already mentioned they tried installing XP with a real corp key .. which works .. and then chaing the key to a keygened one .. and then it obviously doesnt. But when you change the key back to the real corp key it also classifies it as invalid .. until u reformat and install with that key again.

this is because xp always saves the original key in the system which can not be changed by current keychangers.

I have found a tool (keyviewer) which displays the originanl key and the current one.

hxxp://www.skaro.net/cd-keyreader/cd-keyreader.exe

If the "original" key which xp was installed with can be changed it will make it possible to acctualy change the key back to the "real" one and have WGA qualify it as valid.

If someone could write a program that changes this "first" key we could make alot more progress. I tried changing .. deleting it through regedit but it wouldnt let me.

Anyways thought I should post this shit.

I've changed my corp keys loads of times, and it always remember which one I've put in. However I only do that for education purposes only and I always go back to my legit corp key after I have tested the keygen'd one.

Thats not what I m saying .. it does remember the key you change .. as long as its not as 470 or 46 PID .. but they key isnt only stored in 1 place.

There is a reg entry for the key that you install windows with and then and entry for the key that you changed to. Check out that software I posted. It shows all the keys which XP knows.

It's possible to change the "first" key. Microsoft tell you how on this site: http://support.microsoft.com/default.aspx?...b;en-us;Q328874

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. In the left pane, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Current Version\WPAEvents
4. In the right pane, right-click OOBETimer, and then click Modify.
5. Change at least one digit of this value to deactivate Windows.
6. Click Start, and then click Run.
7. In the Open box, type the following command, and then click OK.
%systemroot%\system32\oobe\msoobe.exe /a
8. Click Yes, I want to telephone a customer service representative to activate Windows, and then click Next.
9. Click Change Product key.
10. Type the new product key in the New key boxes, and then click Update.

If you are returned to the previous window, click Remind me later, and then restart the computer.
11. Repeat steps 6 and 7 to verify that Windows is activated. You receive the following message:
Windows is already activated. Click OK to exit.
12. Click OK.

Well I tried that piece of software and it showed the key that XP was using now, along with IE's Key and a few CD-Key for some games. No different from that Magical Jelly Bean Keyfinder.

This method no longer keeps the new key. I think something was changed with SP2. After changing this key and rebooting, the original key is restored in XP.

@slim26, nope that method works - used it loads of times on a sp2 machine.

So your saying if you use keyfinder to look at the key that you just changed, reboot the pc, then use keyfinder again, you see the new key (after the reboot)?

This is the problem that so many people are having. The key change does not hold after a reboot. Are changing the key to a VLK?

when using the keyreader tool, does anyone know which key the following is?
Windows NT\CurrentVersion\Perflib\009\

I think the copy you are changing the key on has to be a Corp Copy?

Thats exactly the problem .. the "original" key is stored here .. the one you install with. You can still change your key .. but it wont be stored in perflib\009.

If you change your key it changes in "Windows NT\CurrentVersion\"

Thats why after u put a keygened key on a real VLK copy and than change it back it still somehow knows that u fucked with it .. until a reboot.

Uhh double post .. sorry ..

Are you sure thats what it is? When I reboot my machine and run keyreader I get a different key than what this tool is showing as under perflib/009.

The key that my machine reverts to after a reboot is not shown anywhere on that tool (until I do the reboot).

hmm I m not sure what the problem is. You see .. my key gen keys never revert back to the old key unless its a 64 or 470 PID ... but thats not the issue. Like the guy with the real VLK key said that once you install a Keygenned key onto a maschine with a real key you cant revert back properly (WGA will tell u ur invalid) until you format.

Really odd that you aren't running into the problem.

My copy is a corp version with a VLK key.

Did I miss something? ...

We already know that having a 64 or 670 PID range just doesnt work. because it resets when you restart.
People shouldnt even bother with this because thats not the problem.

The problem is within XP
---d00mzday

Scenario:
You used a Legit VLK key during XP install = WGA valid
You changed legit VLK with a keygen one = WGA invalid
You try to change your key back to the Legit VLK = WGA still inavlid
whilst ur other PC has still the Legit VLK and = WGA valid
(u have to format the PC and install with the legit Key to get WGA valid)
.. I just wrote this cause peops dont seem to read the whole post and dont realise the problem.

During windows installation the key u enter does NEVER changes afterwards and is stored here:"Windows NT\CurrentVersion\Perflib\009\"
Then you can use a key changer but that stores the key in this place:
"Windows NT\CurrentVersion\"

although it may seem like you changed it (because when you use any reqular key viewer it views the "Windows NT\CurrentVersion\" ) XP still remembers the key it installed with.

I reckon thats the problem why d00mzday couldnt get his real Legit VLK to work afterwards cause once you change it to a bad key and try to revert it wont let you do it properly.

BTW this keyviewer shows you everywhere the XP key is stored
hxxp://www.skaro.net/cd-keyreader/cd-keyreader.exe

I have just installed a copy of XP Pro Sp2(Corp), on Vmware and and have run cd-keyreader.exe and it shows me 2 keys, one is the key that I used in the XP setup, another one is shown, but I didnt enter that - so I have no idea where it is gettin that key from.

I then proceeded to change the Product Key as described here. I then rebooted and ran cd-keyreader.exe. It showed that Windows had remembered the new key that I had input. But remember that other key (1st paragraph) that hasn't changed at all.

Btw the pid i used was 64,

Also, if you open HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009 in regiedt, you'll see that it has nothing to do with the PID or Product Key

Yeah exactly no point doing that .. its a waste of time.

The trouble is that even "IF" we get a real VLK key and type it in it wont work because it remembers the installation key .. or that you somehow used a keygened key. So it will call u INVALID although you might be VALID.

Seems like we need new keychangers or something

Funny , we need a new keychanger that can change the first install key aswell , smart check ms .. I get valid on my newly installed system with my key but on my old i get invalid with same key(not install key)

winkeyfinder 1.65 can change they key .

and it now doesn't matter if the key is 649 ,670,690 they all work and you wont need to activate.

trouble is the check looks at the computer pid and the key you install to check to see if the key is valid.

a new keygen could fix this but its doubtfull we shall see one since xp is old news and the work arounds are much simpler.

the coders at ms for this must be new since this is less then affective.

it could be just a test for vista though.

I can confirm that the key in Windows NT\CurrentVersion\Perflib\009\
is definitely not the original key, as I installed Windows with a totally different key. I'm not sure where this one came from :/

Don't know if anyone caught this article? not always the most reliable source of technews but non the less u might get a giggle, but looks like ms is far from done.
http://www.theinquirer.net/?article=25245

this seems to have more to do with a test run for vista then xp.

which sort of makes sense but seems rather futile.