“A bizarre rumor about Microsoft making sweeping changing to its Product Activation technology in Windows XP Service Pack 1 (SP1) is completely untrue, the company told me today. The rumor, which was started by a small technology enthusiast Web site, had Microsoft changing the product keys for all of its customers using volume licensing.” Read the report at WinInformant.
Rumors About XP SP1 Product Activation Changes Not True
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
From what I heard, the only key that will not work with the service pack is the well known “FCKGW” one, and the company that owned it was asked to change it.
Yeah, right. What better than, after your plan to squash all the pirates leaks, than to say, “Wait…no….that’s not true!?”
No one cares about changes to WPA, they only care if their copy is about to become toast, which it apparently is.
oops, that’s my key
who doesn’t know some windows key by heart, just because he had to install a thousand times the OS ?
i have legal keys for 1 98, 1 95, and maybe a few others too….
Linux rules sometimes
While you wouldn’t find me running Windows XP, I have heard of a file named “All_Microsoft_XP_Programs_Keygen.zip” and one called “XPKey.exe” which allow one to easily deal with such an “oops” type of situation. Otherwise, I think changing a few files and registry keys will be required. Perhaps http://home.att.net/~nogoodpig/ has additional information? Now who can give me an “I”, give me an “N”, give me another “N”, give me an “O”, give me a “V”, give me an “A”, give me a “T”, give me an “I”, give me an “O”, give me an “N”. What does that spell? What does that spell?
Gee, the workaround for WPA came out hours after the XP official release. The workaround for the SP-1 WPA change is out BEFORE the official SP-1 release. Hmmm?
01000-XXX-0123456-01000 has always been my favorite
if i recall correctly, valid 95 oem keys used the following pattern:
NNNII-oem-00JJJJJ-XXXXX
where:
NNN is the day of the year it was packaged
II is the last 2 digits of the year it was packaged
JJJJJ the digits of this had to add up to a multiple of 7
XXXXX could be any number, didnt matter what
on my own box (i did own a legit copy of 95 at the time) i used 00195-oem-0000007-00000 alot (i was a frequent formatter)
That must be the OEM key format which I have always been too lazy to remember. Anyway if you put;
[SETUP]
ProductType=1
in msbatch.inf you didn’t even have to remember anything.
I reckon “that” key got stolen cos you can make a memorable phrase outta the first letter group…
Down wiv the president 🙂
As well as the Microsoft wishful thinking phrase about some other company quitting business.
They did something similar with Office 2k.
If you were using a certain (pirated) key and installed the service pack, all of the Office apps would ‘commit suicide’ and shut down as soon as you started them up.
If you use that particular FCK,,,RH.. key – dont go to Windowsupdate, they’ll send you a file that closes you down with a complete screenfreeze every 50 minutes. This is a fairly recent change.. when I installed @ xmas ’01 it was fine, at Easter ’02 it was fine.. June ’02..not fine.
I think downloading the fixes from the Windows catalog site from another PC, backing them up and transferring across should work though.
NOONE, including the owners of “toasted” ids care… Where are you living? This stuff is even cracked before MS will/would officially release the SP, so what?