{Warez link removed by Taco Bell.}

simply replace the dll ins windows/system32 and windows update now works again

Here's the steps I followed to successfully bypass WGA using a non-legit VLK key:

1. Generated a key using 640-500000 - 640-600000
2. Installed Windows using generated key
3. Generated a new key using 700-0 - 700-100000
4. Followed the steps here under Use the Activation Wizard heading
5. Opened Windows Update
6. Allowed Windows Update to install the latest version of WGA
7. Entered java script:void(window.g_sDisableWGACheck="all") in the URL bar (minus the space between java & script:void)
8. Downloaded latest updates!!!!

I figure any bloody idiot should be able to follow this and get it to work....

There is one catch though... You have to do step 7 everytime you open Windows Update or Microsoft Update before clicking the Express or Custom buttons. A small price to pay I think....

Thats one hell of a mess you got there.

The windows install part is fine but you sort of loose it after that.

Whats the point of going through the headache of gening a 700 key and activating it when your going to bypass the check with the java script.
The key check software installs fine without a key change and its not tell after its installed that it checks the key.
Making the key change even more pointless is that it changes back on a restart and you have to do it all over again.

Simply doing the java script part or even better replacing the key check dll with the dumby one which perminatly fixes the problem (alest tell they change it again ).

You would have to be a bit of a idiot to do all that when the only part needed to pass the check in the whole thing is the java script...lol.

Seems the link got del although i not sure why since it wasn't warez or a illegal download site.

Still not my site and i bow to there wisdom.

which dll file ,you have to change.

@magnus33: 'cause, with the file having the same version number as before, it was seemingly a hacked Windows DLL to avoid the WGA process and therefore qualifies as a crack. Thus, breaking the board rules.

LegitCheckControl.DLL is the one changed by Microsoft.

Hmm quess it would.

I still use the patched LegitCheckControl.dll after the latest update to the WGA software. Shouldn't it have been replaced by the update? Well, it works fine so I'm happy.

Yes, there is a way to do windows update without changing any files or hacking anything after installing the newest WGA:
Try this- it works:

Now go to IE -> Add-On Manager -> Disable WGA ^^
http://www.dslreports.com/forum/remark,155...art=40#15680518

yup that works, what also works is (if you can & got a corporate xp both @ your office & at your home) you could check there pid, get a PID --> cd-key "converter" and enter that server.. (i did and it works fine)


xxxxxx-640-0343xxx-xxxxx

xxxxxx-640-0343xxx-xxxxx doesn't work for latest WGA (v1.5.526.0)

use XP x64; it doesn't use WGA

hi all, my problem is that i have selected over 25 cd keys that are valid and had pids between 640 500 and 600 but when i go to change them through any program like jelly bean keyfinder or any other like that it says they key is a fake and doesn't let me change it can any 1 help,
any help would be very apreaiated

p.s sry bout the spelling

If the keys are valid as you say, then why change it?

Yup, the worst liar. I've ever seen.

the cd key that i was using is a fake, the ones that i wanted to change it to were from that keygen used here but i know wart i did wrong now

insted of going "Windows XP Pro. VLK"
i went "Windows XP Pro."

i was not lieing b4 i did have "valid" ones to change it to

wtf is the point of installing with a 640 500-600 key then genarating another (700 0-100) and changing it to that 1, y not simply install with the new 1 (700 0-100)

yeah its pretty useless, i would make it a 5 step and install right away. the 640 PID is useless, install on 700 series then right away... safes some time and stuff

I have once again got the message that I have an invalid key, this probably because I have changed my hardware config again. Very annoying, because I have a legit key (648) that worked from the beginning! As I mentioned before, Microsoft describes how to change it in the startup script ChangeVLKeySP1.vbs at

http://support.microsoft.com/default.aspx?...kb;EN-US;328874

Unfortunately, the 700 that I tried before is only to be changed once per session, so I tried a 640 instead.
To make sure the key was OK (you can see the icon disappear in the system tray), I had to run the script manually. But first I removed the rule in my firewall (F-Secure) that always allowed for Windows checking the key over the net. So when I got the question to allow, I only did it for this time.

A strange thing is that next time XP checks the key, it could be invalid!!! So directly after the new key was OK, I changed to that key in the startup script and then restarted my computer. When up, XP tried to check the key again, but my firewall gave me a warning. I then blocked the connection to the Internet for ever for that check.

This was more than a week ago, stills works!

Those of you who have tested the 700 series have noticed that this won't work any longer.

But I have found another interesting thing, wonder if you can explain why:

I installed/changed to a corp key which validates at microsoft.com/genuine. Then tried another key in the exact same series which not validated OK before. Now, it also validates OK! Very strange!

Example: 640-012345x-xxxx (nb number not tested!)

Anyone who has a comment? Can you verify or explain this?