thx, appreciated

with this pid 55274-647-2797271-23060 I'll find problem with the SP2 update?

thanks a lot from Pino Italy

As Taco Bell said, "... if it worked in SP1, then it will continue to work in SP2."

opps i m not in INN

Your being told that Microsoft has chosen (for now) ignore possibly pirated xp. Bear in mind, beta testing has shown that Microsoft CAN detect the common pirated XP. This forum has shown how to appear/become virginal again. Do nothing and you'll stand out and will be easy pickings for future action - follow the advice of this forum and your just one more zebra in the vast herd.

Hello all, long time lurker, first time poster.

Being the cautious type, I went ahead and used the standard keygen (you know the one), changed the key, obtained a PID in the 640-528xxxx range (on the first try!), and everything worked great. Also, I don't feel quite so nervous now about having my OS disabled in the future (or updates being cut off). Now I just have to do the same for my mom's computer.

I just wanted to thank you all for the awesome information posted on these forums.

@Jorian: You're welcome man and glad to have you on board.

ok well im going to have to say i had a pid that was 645 and it was rejected on MS website... for valid keys..... the Corp edition TOOK the key just fine but according to MS it was invalid!
http://www.microsoft.com/resources/howtote...ws/default.mspx

check here if.. ya want... what i want to know is.. why.. the CORP edition takes pids other then 640.....anyone know? cause it seems MS
doesnt say those are valid on there website!

@generalnewbie: Because the code for the Corporate Edition CD has gone unchanged since it was released whereas the web site takes into account all of the known pirated PIDs.

Also, MS reversed its position on blocking such additional PIDs during SP2's installation and, for now, using Windows Update v5, but that may change. 'cause they still know which are valid & which are invalid. They're just not enforcing it (at the moment).

Out of curiosity, what happens if a blacklisted key is used? Would the installation be prevented entirely? Or would it install just fine and then force a key change after the installation?

you get a prompt saying you have an invalid product key

so what 4in1 PID ranges for xp vlk can get updates? still 640-500 .. 640-599 ?

my corporate PID is *****-652-8284616-***** (win xp x64 btw)

seeing as this has been posted in kind of recently, I'll ask. I've got a PID of *****-649-6478953-***** and I'm running SP1. Am I cool to move up to SP2 when I clean install? Sorry for the bother

There are some keys that have weird PIDs, you might have one of them. But usually they begin with -640-

Yeah, my PID is weird, but WU works, and I'm already on SP1

I supose the best way to find out is to try it. But make sure you have a bare xp cd standing by just incase

I'll prolly be making an unattended install so I'll try it in VMWare first

Mine is xxxxx-640-0005952-xxxxx ( Corp. version w/SP2 )

Works fine on Windows Update and Windows Genuine Advantage says that it is legit.

xxxxx-640-376389x-xxxxx (SP2) doesn't work in Windows Update now, though it was OK in the WGA test program 1 week ago :/
Does anyone have the same issue?

I belive there will be a lot of, "it worked last week" posts.

Did something change ? because iam also having problems now, i did a fresh install last night, and i cant pass geninue check for the life in me.

My current ProductID: XXXXX-640-0005727-23XXX

I would assume this was in the good range.

@JamesHong: Generally 640 is okay, but as we discovered during the XP SP2 beta, not necessarily every number in that range.

I would recommend just getting another 640 PID value though and try, try again.

It looks like Microsoft has finally lowered the axe on all the VLK PIDs out there that were generated by a Keygen, but never issued by Microsoft. The latest Windows Update (released today - 7/26/05) loads a validation tool into your PC and checks for exactly that issue. If it finds that your PID was never issued by Microsoft, it blocks you out of further updates - YOU ARE THEN SCREWED!!

Does someone have a valid fix for this situation?

Thanks for the reply Taco, but i shoulda mentioned that was about my 7th try, i should give up for today before they blacklist my ass or something lol, anyways they did do a update today i read it in some news, i wonder if more people will have the same problem.

Ah, well that explains why they're pushing this legalization program then.

YUP!

This works so far. Credit to A.B. at FST.

This seems rather too simple to work...but it seems to bypass the check

In Internet Explorer
Tools > Manage Add-ons
Disable "Windows Genuine Advantage" thingy

Close Internet Explorer, then go back to the update site


Works here.

Well known "hacker" and Extended64.com blogger, Rafael, has posted instructions on how to circumvent Microsoft's Windows Genuine Advantage protections in Microsoft's Internet Explorer and Mozilla's Firefox web browsers.

Rafael has posted two javascript files, one for "Trixie" - an IE plugin, and one for "Greasemonkey" - a Firefox extension. At this time, Rafael admits that the IE script still shows some problems, but the Firefox script is working fine. Rafael adds that the problem might be related to Trixie and not his script, but he is working on an update that will fix the problems.


http://www.extended64.com/blogs/rafael/arc...07/27/1026.aspx

OMG I wonder how long that will last? freaking amazing working here too for now. Unbelieveable.

like a Sharpie Disabling millions of dollars of anti copying technology.

Yep Works here too.

Something will work out. As long as Microsoft doesn't get real evil. Don't even want to type what I'm thinking. Don't want to give Microsoft ideas.

Same here. WGA reported that my key was legit until yesterday.. Now it says invalid -- "was never issued by Microsoft". Tried 4 different ones in the xxxxx-640-0005xxx-xxxx range and got the same thing.

can't see this being all that effective.

people who used a keygen would still likely get ones that were made by ms.

and whats to stop people doing what they just did turning off the addon?

Damnit! And I thought I was so damn clever for working it out just now myself ;) Damn you all for being so quick!

I only discovered the problem 45 minutes ago and wanted to tell the world!

You're welcome.

Thanks to all for the "fix." I just wonder how long it will take Microsoft to do something else to mess this up? Anyway, I knew that someone on the ieXbeta board would come up with an answer - I just didn't think it would happen so damn quick - Way to go!! TheBeagle

Ha! I can't belive it was that easy to get rid of it! Interesting note though, I found this windows update site that works with firefox and the like (and no validator!): http://windowsupdate.62nds.com/, don't know how effective it is though, made by some 3rd party, so use at your own will

@zapjb: This does not work for Microsoft Downloads and will be fixed on Microsoft Update soon.

I wonder ....... what is Micrsoft's new validation program really doing? Is it checking your key aginst a database of known keys? Or is it just checking the PID against a much tighter range?

actually if you really look at the keygen keys i will bet that every single one of them is:
xxxxx-640-xxxxxxx-23xxx

lol, the person who wrote the keygen only allowed determining the 640-xxxxxx0 it doesnt even let you create one based on all of the 3rd set of digits...

@zapjb: I don't see that setting in there?

tools > manage addons

Then at the top of that windpows where is says " addons currently used by IE" select " addons that have been used"

And you should see it there

It would be nice to have some valid VLK PID's to try the keygen out on a specific range that is known to be "valid." Does anyone have a VLK copy of XP on their machine at work? If so try it and report what happens!

Maybe someone needs to make a new keygen??




I'm sure it will.

I have discovered another workaround (posted by someone on the somethingawful forums), this will also probably be "fixed" by ms as well, but it works for now anyways...

Using the keygen, enter both a starting and ending PID range of 999 999999. Generate a key. It will be valid. Then change your WinXP product key to this key you just generated. Check "My Computer" "General" tab to verify that your PID has the string of 9's in it.

WGA will now validate!

IMPORTANT NOTE!!! This key change is NOT permanent. While it is "valid," Windows XP will not generate the required registry key under HKEY_LOCAL_MACHINE\SYSTEM\WPA\ in order to make this key "permanent." So, when you log off or reboot, the key will switch back to the last known "proper" corporate VLK key in HKEY_LOCAL_MACHINE\SYSTEM\WPA\. You will therefore need to change the key again if you want WGA to validate after a logoff or reboot.

(I did play around with this a bit... HKEY_LOCAL_MACHINE\SYSTEM\WPA\Key-XXXXXXXXXXXXXXXXXXXX keys are all locked at all times when WinXP is running, even in safe mode. You can delete or modify them with ERD Commander however. I tried changing my key to the one with a PID of 999 999999, rebooting into ERD Commander, and deleting all of the HKEY_LOCAL_MACHINE\SYSTEM\WPA\Key-XXXXXXXXXXXXXXXXXXXX keys. On rebooting, Windows prompts for activation. When I tried re-entering the key with a PID of 999 999999, the activation prompt simply came up again. So, I'm unable to get back in with this key. I have to use a key with a correct VLK starting with 640 xxx. So the bottom line is there's no way to make the key with 999 999999 "permanent.")

I am willing to bet in the coming weeks there will be some more cleaner slicker "workarounds" appear around the net.

Someone has already cracked the windows key validation within 24 hours of it's launch. And its not as hard as one might think. Read the full story for how to get past this key check.


full story here
http://www.boingboing.net/2005/07/28/micro...genuine_ad.html

holly crap! ms really dont know what security means!

LOL, I think iexbeta is my new fav board.

Microsoft needs to just give XP Away with Vista comming out around the corner who is going to rush out and buy XP now.

MS already has enough money to almost buy the planet, they can afford to loose a few sales of XP.

YaYa, I know they are kinda giving it away with the trade in program, but I would rather not send a letter with my and address on it to MS handing over a un-licensed copy a cd.

I'm sure they're using XP to test out their security for Vista...either way, its win-win for them.


Doesn't this do the same thing as disabling WGA in the Add-Ons Maanger in IE?

good question... i would assume no... i think if u disable that it wont let u get the updates, but when u enter that javascript into the address bar it tells the browser it has already checked your key and its all good...

i think thats how it is anyway

They're accepting warezed copies in turn for legal copies? Link?