Microsoft has become smarter after the lastest experience?

I think even if the key in Perflib\009 is the installtion key it does not matter since somewhere Windows saves the previous key and it knows when you are trieng to put a pirate key on it. or a valid key onto a pirate.

as someone already mentioned you cant put a valid vlk onto a PC running a keygenned vlk .. u have to format.

:/

I just jumped onto this topic after running into problems.

I got all my windows updates just fine. But I went to download

MS SyncToy Beta 1, it told me my license was invalid.

my PID:

xxxxx-640-xxxxxxx-23xx


Any idea why 1 part works, another doesnt?

dkreifus - as of July 28th thats the new WGA behavior. critical updates work as before but anything from the "custom" button on windows update, or specific downlowds of MS programs/utilities one will have to pass the new WGA which checks if the key which got you to a 640 is valid.

Funky - I dont think that statement quite true, I think what has been shown is if you have a keygenned VLK key and WGA has caught it to be invalid you CAN jellybean/keychange to a valid VLK if the valid VLK ends up yielding a different PID.

However, If the valid VLK yields to the SAME pid as what has been trapped as invalid then even the valid VLK key will not work on that PC but continue to work on other PC's.

CAN SOMEONE PLEASE CONFIRM THE ABOVE?

Not entirely true. If an invalid VLK key is in your system, and you use JellyBean or any other widely known method of changing it, it will only remain changed until you reboot. At the time of reboot, the invalid key is restored.

I think if you installed XP with an invalid key (one that fails WGA), your pretty much stuck with it as it will always revert to the same key after each reboot..unless someone finds a new method (which I've heard can be done by write-protecting some file).

Some here have mentioned that the only way to get rid of the invalid key is via a format and fresh install. Can anyone confirm this. Is it a waste of time to try a repair installation or upgrade to get the original key changed as it won't work??

I installed windows with an invalid (failed WGA) key and months later switched to a valid key from a corp OEM package and it worked fine.
But when I switched to another invalid key (messing around with the keygen), the former valid key didn't work (but I only have one computer with XP so I'm sure any other system would work fine). so it's definitely NOT the 'installed' key.

Was this prior to SP2? Seems like things changed after SP2.

Everything you said is agreed. The statement which I belive to be true but wish someone to verify is this...
If you have TWO actual MS VLK keys (which of course yield out different PIDs).

If you mess around with keygen and get into a state where one of the actual MS VLK keys no longer works, you do NOT have to format and start over, I belive the other one WILL still work and get you out of the state where one key doesn't work.

I suppose we need a tool which clearles the complete registerty or where ever keys are stored nowadays.

You lot am making a mountain out of a mole hill. You can change you product key quite easly. as for that "key" in Windows NT\CurrentVersion\Perflib\009, thats a bunch of bull shit, because if you go to that key in regedit you'll find the key doesn't even show numbers!

As long as you have legit/generated key that abides by MS's pid rules, your fine.

You are 99% correct.
I was able to get my**VALID** VLK key working (finally!!) again by using the keygen (not the bluelist one; the other one which lets you select PID ranges) and generating (luckily) a PID 064 key which passed WGA on the first try. And at this time, the keyswitcher was still working to switch the key.

The problem of course, is that that key always reverted back to a 'bad' key when rebooting (the PID changed from 064 to 640, the key itself changed to the former key). And there were even MORE problems!

For some reason, after this happened, NONE Of the keyswitchers would accept ANY of the valid keys! They all said they were invalid. My own valid VLK key it would not accept at all, BUT (just to make sure there were no typos), the bluelist keygen verified the key as valid under TEST KEY.

Why did this happen? Anyone have any idea?
Did the scripts get blacklisted themselves or corrupted?

I was able to change back the product key back to the known good OEM VLK key, only by rebooting (the WPAEvents field was totally blank for some reason), which restored the WPAEvents key, changing a digit, and using the MSOOBE thingy. Even though the two keyswitchers refused to accept the key, the OOBE thing did, then I rebooted and the valid key remained, and WGA was passing validations. Thank god.

But why the hell aren't the keyswitchers accepting the keys?
To make things more confused, even though windows says its activated (if I try running that OOBE now), if I run winkeyfinder 1.66, the activation status is "BLANK". Before I started all this crap (when I originally had switched my key from the banned install key to the WGA valid key before keygenning a bunch of stuff), it said "Activation status: OK".

Now it's just blank.@_@
AND THE KEYSWITCHERS won't accept keys!

That includes both the MS4in1 and the keyfinder program.

Any ideas, people?

Oh and singh400: you are not correct. It's far more complicated than you think it is. If it isn't, answer why the keyswitchers aren't working suddenly...

And yes, you need to somehow get in a valid VLK with a different PID than the one that got the entire PID range banned (even with a good VLK), then you can switch back to the formerly good VLK.

Ok I will try and clear this up sence I have 2 licenced legit from my company VLK keys to work with.

both my legit keys are in the 640-xxxxxx range
the xxxxx of course varies along with the numbers before and after.
4in1 keygen allows u to modify the xxxxx range aswell as the 640 range using the 0-999999 settings. I was matching up the 640 and the xxxxx range as close as possible to my licenced key to see if ms simply tightned up the keyranges. It seemed to have worked I generated a few keys which seem to have been legit in the actual corporate release range it was passing the update site with no problems so I jotted them keys down. I also seemed to generate what seemed to b a bad key aswell as soon as I punched it into jellybean it came up as invalid on the MS site. I thought simple enuff switch back to my valid licenced key and keep on moving. This is where I found out that it seemed to have flagged the xxxxx range i was working in and my valid key was now showing invalid. I ran to second machine that has same validkey from my company and it was still working good. I punched in my second valid key I have from company and was still 640 range but the xxxxx section was totaly diffrent range and that key worked fine. So what I did was fire up another spare system here did a reformat I took the keys that I thought where passing in my range entered one during install of windows windows all installs fine just like normal went to check the update site and downloading the new installers and boom the 640-xxxxx key i generated in my exact key range that I thought was good was infact not good. So then what I did was enter my known working key and that was now invalid to. I then checked my other system that I dont do anyplaying on and it was still passing. So I did a format on the computer reinstalled using my good key and it worked no problem. I repeated this process several times and it was useless with the current 4-1keygen where I left before I called it a nite is. I tried another generated key in my keyrange that I jotted down that seemed to pass with old windows install and used it during install that did not work and I keyed in my working key and that was blacklisted on that computer aswell so I said enuff and went to bed. After reading a commit here later on when I got up I decided to go check the computer that when I last left my valid key that was blacklisted on that computer now worked with the update site. So what ever blacklists on the system does seem to reset itself if you enter a valid licenced key and let it sit for awhile(don't have a clue howlong though). Just to hopefully keep things clear it only blacklist the xxxxx range it seems that your working in aswell as it only blacklists on the computer you are doing the screwing around with.

As far as the jellybean keyfinder/changer I am using v1.41 which works absolutly perfect it holds the keys after reboot in sp2 and keeps the keys changed without a problem only and ONLY if u use assighned corp ranged 640 and so on. The ranges that MS assighned for the coporate version of XP. infact change to any 640 key and reboot and you will see that your corp releases will hold the key. it will not keep the 064 and so on ranges because that is not a corp range. Infact they are not even valid corp keys. If u have a spare machine go do a clean xp install using one of them 064 keys and u will see exactly what I mean. They might let u get by the update site right now providing u have a xp already installed with your previous working vlk keys that are now invalid at update site, but they are far from being legit Keys.

I am not sure about winkeyfinder 1.65 have not tried it yet simply because I was looking for valid keys that are corporate and work right from a clean install of xp all the way thru the MS update site.
I think magnus33 is absolutly right and the current keygens are useless in generating valid corp keys the way it is doing it currently that is. BUT!! by all means keep generating away u might get lucky after all there is always someone that wins the lotto just not me. GOODLUCK
P.S sorry for the long post I dont even wanna read it myself lol

XXXXX-640-0000347-XXXXX

that pid works. confirmed. but i can't gen in that range .

@canuckerfan: Yeah, and you already mentioned that last week over here. Seems a reminder was necessary though due to the recent replies.

So I understand this much....

if you have an invalid activation. Which is weird..but either way...


If I have a different installation key, can I use something like WinKeyFinder to change the key?

Step 1: change the key with WinKeyFinder
Step 2: restart
Step 3: Test it
..
.
.
Or am I way off. (sorry..theres so much discussion, I don't know what to follow)

That pid does NOT necesarily work.
I Just tried 10 keys with that range.
You may have gotten lucky or gotten a distributed valid license from that pid but it does NOT mean that all the pids of that range work.

Oh, and one of the 10 pids i generated -asked- me to download genuinecheck and give a code; the other 9 immediately failed without that being necessary. (i was on the directx page).

I switched between my known valid key and that range you gave.

U Mean this range?
Now according to canukfan there is obviously one working key in that range, if not more. Here is the problem though there are going to be bad ones aswell and MS has seemed to put something in there validation check, the minute u goto there update site and try to validate the key and if it is a non valid key according to there system it will turn around and blacklist that pid range on your computer for a period of time, so every pid key with a 0000347 will come back as invalid on there site even a good one. Probably to make it difficult for u to do this very thing. Now here is the weird thing i noticed lets say you are running the keygen on your system with a valid licensed vlk in the pid range of 0000347 they keygen will seem to spit out some keys that seem to pass the update site. The best thing to do is check that key on another system that does not have a vlk with the pid range of 0000347 to see if it actually passes there check.
Note: it does though only effect the system you change the key on and if you have a actual licensed valid key outside of the 0000347 pid range u can switch back and your system will b working and passing ms validation again. So I am guessing you have to b very lucky first shot or you better have alot of time on your hands.

d00mzday thanx for that essay a few post above

Simple answer, don't use the keyswitchers, do it yourself. (See here)

None of the keyswicthers work anyway, I remember trying a few they never work. Much better and easier to do it yourself.

HAHAHAHAHA I'll make this one shorter and with pictures to

You can get alot more accurate keys if you use all the digits available in the PID dialog

Click to view attachment

I tested my own legit corp key and it came out fine, and then I tested a keygen'ed key with a pid range as the same as my corp key. The trick is to close down the pid range.

So lets say it

From : 640 - 123456
To : 640 - 123456

yes true but in his case u should try entering 640-0000347 into your 4in1 keygen and generate the serial then test the key in bluelist and tell me what pid comes back i guarantee it wont match 0000347 the keygen dont reconzie all them 0000 infront and just see's it as 347 so it will kick back a range of 0003477 So enter 34 remove the 7 the keygen will then kick back exactly his pid range of 0000347 everytime

OK. this whole topic is crap. If you dont own XP go buy it. and your key wont be blacklisted i promiss you that. hey im not saying ive never pireated software befor. but this forum prides it self in keeping it clean of this type of stuff. thats why i use this forum. this topic should be closed. as all it realy talks about is how to get around buying windows XP.

Regards Luke

@Renames, This topic is for pure educational needs.

and nobody's ever pireated software before.

@renames
you make this call after 25 pages of posting? gOOd.

Especially after you mention yourself that you own pirated software

Don't you understand? This is one giant cover-up... We register everybodies IP who posts in this thread and send them in one giant e-mail towards Microsoft


(this message will erase itself in 5 minutes)

**thinks of lame excuse**

I was like totally out of it when I posted in this thread, I was all drunk, high, you name it I smoked it.

:roll:

Actually,
Those generated keys in that range as your valid licensed key only work -until you reboot-. I think most or all keys in that same range will pass the WGA if you came from a valid VLK, without rebooting (or maybe the first generated key entered passes (without rebooting), while the second fails)

I'm assuming this has something to do with windows still thinking you are using the old PID somehow, since not everything is updated if you haven't rebooted.

After you reboot, that pid range is blacklisted (including your good key) until you change to another key, with a -different- pid range (not the 640, etc, the 7 numbers after it) that passes WGA.
(in this case, it's that 064 key that isn't even a 'real' corp key, but somehow passes WGA And removes the blacklists from the all the other key ranges).

We already know this!
That's what I (and others) have been doing all along.

Now--try REBOOTING your computer and tell me if that key still works.
Watch your valid VLK be blacklisted too.

@Falkentyne, I was testing it on VMWare XP SP2 Machine. Have set up the net connection yet.

If you read many of us have legit keys and legit copies, so thanku kindly for pointing out we wont have blacklisted keys. I am sure the people that just found out they do not have legit version will appreciate u pointing them in the right direction. Some are simply just intrested in what MS has concoted. Now if the topic header stated"Please Post your valid working keys" then you might have a point.

P.S I thought it was a very intresting topic thats why I choose to read it. Let me ask you Luke. why did u? after all u did state yourself. you pirate software!

When 2 keys are changed back and forth, they last few digits of the PID are random numbers, (indicated by the small x)
i.e XXXXX-640-0000347-xxxxx

I have tested this without reboot and using both the WinKeyFinder_BETA_ 1.70 and Jelly Bean Keyfinder.

I'm wondering if the "invalidation" lies somewhere with the conflict of the original install key and keygened one, and perhaps a "key" asociated with the installation of SP2. while a program called viewkeyxp shows my original install key, it is nowhere to be found whne running cd key reader. The changed keygenned one shows, as well as the perflib009 one--which is not a key i have knowingly entered (perhaps associated with sp2?).

where is that original key stored, where is viewkeyxp looking that it finds my original install key. a search through the registry does not find the key or any part of it -- so where is it?

I have strong reasons to believe that using a keygen for VLK keys will NEVER pass WGA testing.
(Moderators - I have avoid putting exact URL's to any non-public URL or exact files in an effort to avoid being a problem).

First, what WGA does (if it hasn't been covered)
Three connections to microsoft servers
1) Gets a string of characters from a .../fwlink URL
2) makes an HTTPS connection to another microsoft link to confirm the VLK key, sending product key and product id
3) makes another HTTP connection to let microsoft's logging servers know what happened (purely for statistical purposes, your Somalian Proxy Server won't get unwanted attention... you didn't try this from work did you?)

Now, Microsoft doesn't like to pay too much for bandwidth, so WGA caches the response from the server. The cache is stored under \Documents and Settings\All Users\Application Data\Windows Genuine Advantage and stores validity based on Product ID *NOT PRODUCT KEY*

What will convince you that a VLK keygen works if you have a valid Corp key?
(a) You might have through the steps with your legit VLK key - this put a cached valid response in the WGA file
( You wouldn't have used the keygen that lets you specify the Product ID fields to get a new product key
© You could have changed the key with handy little VBS script off MSDN (or used someone's nasty keychanger+spyware bundle).
(d) Then you potentially ran WGA again with the keygen'd key - it hit the cache, and you think you are legit .. until it randomly decides to verify you again.

To prove this...
Get GenuineCheck.exe
Write down the "good" response
Rename/Delete the WGA cache
Change the key with the VBS script http://support.microsoft.com/default.aspx?...kb;EN-US;328874
Re-run genuinecheck.exe
Note that the response is different (invalid, probably Error code = 8)
Change the key back to your good one
Re-run and note that you again have the correct response

- Use ethereal or other tools to catch the IP addresses. Note the middle connection is SSL, so logging will involve some challenges.

VLK keygens are dead. It will just take until the next service pack to nail down the coffin.

Why are you using the Bluelist keygen to test your key? It will show "valid" on anything you generate in the 4in1 key changer.

Try it on WGA / Windows Update.

See if the number is still there after a reboot.

With Windows SP2, only keys in a given PID range will "stick" when you log out / log back in / reboot the system. If you installed Windows XP SP2 Corporate, the PID must begin with 640. The valid PID range is actually hard coded into key operating system files. This prevents the user from installing the corporate version, then changing to the home version, professional version, or media center version (or any combination of thereof). Again, each of these different versions of Windows XP have more differences than the Key / PID.

When you change the key in Windows XP, you are able to change it using a PID of anything you want, even 999-999999. Try it, use the Bluelist keygen and it will tell you that your key is valid. However, when you log out (or reboot), as soon as anyone logs back in, Windows XP performs a hash on the key. If it's in the valid PID range (again for WinXP SP2 Corp it must start with 640), Windows XP will store the hash in HKEY_LOCAL_MACHINE\SYSTEM\WPA\. It will store it under a numbered key starting at 001. The PID used to install WinXP will be 001, then the changed key will be 002, etc. It will retain every key that passes the PID check. The person saying they had 009 must have changed their key 8 times. It won't look the same for everyone.

If when you log back in, the PID check fails, Windows will revert back to the previously used key that did pass the PID check. This is why the key "changes back" after you reboot.

If you try to delete anything under HKEY_LOCAL_MACHINE\SYSTEM\WPA\, you will get an error. Out of curiosity, I tried changing the key to one with an invalid PID (999-999999), then rebooted to ERD Commander. This lets you attach to Windows before it boots and edit the registry. Here, you can delete keys under HKEY_LOCAL_MACHINE\SYSTEM\WPA\. I tried deleting them all. When I rebooted and tried to log back in, immediately the Windows activation dialog appeared. Since it didn't have any registry keys with a PID that passed the check to fall back on, it was basically asking to create another. At this point, you can't enter a key with an incorrect PID, since it will do the PID check and need to generate a registry key under HKEY_LOCAL_MACHINE\SYSTEM\WPA\ in order to log in. If you try, the activation dialog will simply pop back up again. If you don't change the key to one with the correct PID at this point (640-xx.. for WinXP SP2 Corp), Windows won't load.

I would suspect that the fact that you can change the key to one with an incorrect PID (like 999-999999) that is retained until you log out.. is a bug. It obviously messes with the WGA check because the WGA check passes if you try to run it before you log out and log back in. Try it, run the 4in1 keygen, enter a PID range of 999-999999. Change to that key and run WGA check. It will work. Log out, log back in, you will see the PID/Key is now back to what it was previously.

So far, I have not heard of any keygen'd key that passes the PID check on logoff/logon (i.e., for WinXP SP2 Corporate, 640-xxx..) that also passes WGA. If you found one that appears to work, try logging off or rebooting and see if it passes the PID test and is retained by the OS.

rigth click on genuinecheck.exe

properties

compatibilty mode

win2000

run genuinecheck.exe

cut and paste generated code

download MS antispyware

it works!

Isn't that only if you haven't already installed WGA though? Or it doesn't work on WindowsUpdate or something like that?

It doesnt work in windowsupdate, only for downloading things like MS antispyware where "solutions" for windowsupdate dont work

This may be true. But I've been curious about this and so I've been doing some experimenting and I've come across something i don't understand. I've tried installing Windows XP Pro (Corp VLK version) using various keys -- each time, I've done a clean install on a freshly formatted drive, just to make sure.. .. So far, all keygen keys give me the "This key was never issued by Microsoft" message in WGA.

However, some other keys give me a different message. I get the message "The key is invalid. This type of key is typcially used by people who want to use multiple copies of Windows. If you do not have a volume license, you may be a victim of software piracy". This is the part I don't understand. The Windows installer has the ability to detect the different types of keys. For example you can't enter a Retail key if you are installing an OEM or VLK version. The installer will tell you that the key in invalid.

So, when I install Windows with certain keys, the installer recognizes them as a valid VLK key and allows Windows to install - - but WGA says the key is invalid. Not the usual "Never issued by Microsoft" but just "invalid".

The Windows Installer and WGA are two entirely different things. WGA is much more recent; it detects keygen'd keys.

The other guy is onto something.

Something about some keys is really strange.

If you generate -certain- keys, WGA will ask you to download genuinecheck, while on other keys, it will say "this key was never issued...etc"

This assumes all the keys are valid PID's
now this could again be a cache issue; I can't be arsed into trying to 'find' a key where WGA makes you download genuinecheck.exe first, then -rebooting- and trying to see if it does the same thing or not. But one thing does stick: Keygens are 99.9% dead.
NOT 100%---99.9%.

There is still a .1% chance you can generate a VALID already issued VLK key. It -has- happened before. (and not just with windows keygens...)

That "Invalid PID passes WGA" bug is very useful, though. Lets you reenter a known good key without reinstalling windows

I've had little problem changing keys without reinstalling Windows -- what are you referring to?

I suspect that "Invalid" keys are ones that aren't assigned to any OEM's.
The ones that are "Never issued" are the ones where the product key itself hasn't been issued.

The 25 character product key is 31 bits of serial number, 28 bits for hash, and 55 bits of an ECC signature (with the ECC public key in pidgen.dll)

For a given product ID, your odds are 1 in 2^28 that you will hit the valid product key that produced it.
So with a roughly 1 in 268,435,456 chance of getting a valid product key with your server query, you might as well play the lottery and use your winnings to buy copies at retail.

Actually WGA was never intended to stay. Its only function is for demographics purposes and to help design/test the new vista anti piracy module which will never be included in any vista alfa/beta/preview version. why do you think that they are retracting it now so soon. the only flaw that was not intended was genuine.exe run as 2k. and the java script trick was intended to show that sun java is not safe to use as a security protocol.

What Microsoft wants to introduce is that software (ALL) is activated and registered on a hardware/OS level and that any companies that want their software to run has to use their verification to ensure that it can not be hacked and licenses be issued on the other companies behave via Microsoft's servers and only on genuine windows products. Genuine software key based on Genuine MS OS = Registered.

Now as to all the tries to create work around well they are logged as well all attempts to use java script work around and by disabling the Active X control because windows update knows that its disabled Duuh

Do you really think MS was this stupid ??? well if you do the joke is on you LOL

What they want is to prove that disclosure of personal identifiable information Is the only way to prevent piracy and that there is no reason why anyone would have a problem with giving this info if they purchase any product they trust because if you don't trust the company then you would not want their product would you ??

As for windows Xp well they don't care because soon it will be what nt was to windows 2K and and another option they have is a limited kernel.dll which can only be updated to the genuine kernel.dll after proven to be an Genuine legit owner and would be coded to only run on the same computer that it was installed on

you give them too much credit.

it was a screwup and nothing more.

the next step by them is going to have nothing to do with keys.

its been aparent for sometime that keys can be easly traded ,stolen or broek and they have been moving to a new system for some time now.

it was test for vista but not in the way you think.

just do a search on google and your going to see loads of articles by old ms stateing what they are planing.

What have we missed. Tried some work with VLK and VMWare. And after reading the mostly failed tests, I've got a couple of theories.

1. 4in1 is not just dependent of the PID range to generate valid keys, but the RANDOM seed seems to matter. Hence the LOTTO experience with 4in1. How does Microsoft random seeder work to generate keys?

2. The HARDWARE checksum that you normally use to register an OEM/retail version is used in VLK WGA to block out HARDWARE that tried to use multiple VLK keys, because the hardware would of course generate the same checksum and be stored in a database (worst case) or cache (better). Hence a legit VLK will not stop to work at a legit site, BUT multiple tests from hardware checksum WILL not accept any VLK, even legit ones.

Just my 2 cents.
foobar67

My experience with PIDs and the VLK version:

Install with a key in the 640 range. Updates to SP2 work, WGA fails. Activation not required. Change key to 700 PID and WGA passes everytime, with _all_ generated 700 range keys.

However, if a 700 range key is used for the install, you are forced to log in as Admin and forced to activate. Trying to change to either a 640 or 700 key is fruitless.

Any thoughts ?

strange behavior..... now I got a valid VLK key from work .. entered it in, and now my machine passes WGA...

...however, now I'm no longer able to switch to any keygened keys at all (as to where I was able to before I had a valid key) as it says they are invalid

So is there any way of generating keys that pass the Windows Update/WGA check?

I'm asking because I'm reinstalling some systems..

I can't make out if you guys are constantly referring to changing the key and it not working, or doing a fresh install and the keys not working..