Shaith

Microsoft has determined through investigations that most pirated installations are made with either of two VLKs. VLKs are used by corporate or other volume license customers to install Windows XP on their computers. These two particular VLKs, however, were never in use by a customer in a production deployment. Product keys are 25-character alphanumeric codes arranged in five groups of five characters each and used during setup to install the product. The product key produces the product ID number that, after setup is completed, is displayed on the General tab in the System Properties dialog box.

Windows XP SP1 ships with a list of the two product IDs that are created by the pirated VLKs. To determine eligibility for the update, Windows XP SP1 compares the Windows XP product ID on the system to this list. The comparison and the list reside locally on the user's computer; no information is sent to Microsoft as part of this process. The Windows XP SP1 installation will fail on computers with the following product IDs:

XXXXX-640-0000356-23XXX
XXXXX-640-2001765-23XXX
If installation fails for this reason, this message will be displayed:

Service Pack 1 Setup Error
The product key used to install Windows is invalid. Please contact your system administrator or retailer immediately to obtain a valid product key. You may also contact Microsoft Corporation's Anti-Piracy Team by e-mailing piracy@microsoft.com if you think you have purchased pirated Microsoft software. Please be assured that any personal information you send to the Microsoft Anti-Piracy team will be kept in strict confidence.

To view your ProductID, hold down the Windows key and press the PAUSE/BREAK key (upper right on your keyboard). It's the number that appears under "Registered To:"

Access to Windows Update
Access to Windows Update is likewise reserved for licensed users. Windows Update determines eligibility for access to its service by checking that the product key used to install Windows XP is valid and was manufactured by Microsoft. When a user visits the Windows Update Web site, two pieces of information are transmitted to Windows Update: the product ID, and a hash value of the product key used to install Windows XP. (A hash value is a one-way mathematical transformation. This value is transmitted in lieu of the entire product key to safeguard privacy and security.) Windows Update compares the product key hash value and the product ID to a list of valid, Microsoft-manufactured product keys. Because this list is very large—about 1 billion values—the information must be validated on the Microsoft side. Once Windows Update validates the transmitted product key hash value and product ID, it discards the information. Neither the product key hash value nor the product ID are stored by Windows Update, and no personally identifiable information is required to access Windows Update.

Volume License Key Encryption
Service Pack 1 adds an encryption feature to unattended setups of Windows XP. This feature is applicable to customers with volume licensing agreements with Microsoft such as Microsoft Select, Microsoft Enterprise Agreement, and Microsoft Open License. Customers who place a VLK in an unattended setup file (unattend.txt) will be able to encrypt the VLK such that it will be time-limited (in increments of 5–60 days) and not visible as plain text. This feature provides customers deploying Windows XP with an additional layer of protection by obscuring the VLKs in unattended installations.



For more details on changes to activation, VLK encryption, etc, visit
<a target="_blank" href="http://www.microsoft.com/licensing/resources/vol/volkeys_winxpsp1.asp">http://www.microsoft.com/licensing/resources/vol/volkeys_winxpsp1.asp</a>

uf4

Yup.
i know spider man will help me if i need one

;

Furious

Glad I don't have either one of the product ID's.

__________________

One of the Twelve

__________________

Shawn319

FYI, Those banned Product ID's are produced by using the "FCKGW" key that is very popular with the "Devils Own" version of Windows XP Corp (Pirated).. so if you have ever used this "FCKGW" cd-key, your going to be screwed when SP1 comes out


/me is glad his PID is nowhere near the two that are banned

AUDIT45

To all that have replied before me, I do not think you understand about the product keys
that were listed by Shaith. Here is it explained a little further:

SP1 will not install on installations with the following product IDs containing the following serial numbers (note that X takes the place of any other value):
XXXXX-640-0000356-23XXX, & XXXXX-640-2001765-23XXX

X's take the place of any other value so if you have:

12345-647-1234567 and then 23xxx that product ID will be no good

As with most of you read before you reply and say my product ID is
not one of the above. There are 1000's of different variations of the
product keys above not just the 2 that are listed. So if your last set
of numbers begins with 23xxx, your product key is not valid and SP 1
will not install!!!



Audit45

AlanT

Will changing the value in the registry do anything?

Furious

Trust me. I believe most here are smart enough to figure that out. Also your example is wrong. The x's are the only variables. If your example were correct then they would've stated that any serial number ending with 23xxx would be invalid. That's not the case.

__________________

Furious

Also the problem I see when reading this information is access to Windows Update. It appears that they may be changing the requirements for accessing the site. Although I'm sure that if it's a problem then someone will be hosting a mirror.

__________________

AUDIT45

If product keys XXXXX-640-0000356-23XXX, & XXXXX-640-2001765-23XXX
are the only ones that are not valid.
X is for any other value-why did they not just list(last group of product ID)
23000 or 23100 or 23200 or whatever the invalid number is instead of
23XXX
With X standing for any other value any product
key with last group starting with 23XXX means that X can mean any other
number/value and that makes it invalid according to:

http://www.microsoft.com/licensing/r...s_winxpsp1.asp

Pete

"Windows Update determines eligibility for access to its service by checking that the product key used to install Windows XP is valid and was manufactured by Microsoft. When a user visits the Windows Update Web site, two pieces of information are transmitted to Windows Update: the product ID, and a hash value of the product key used to install Windows XP. (A hash value is a one-way mathematical transformation. This value is transmitted in lieu of the entire product key to safeguard privacy and security.) Windows Update compares the product key hash value and the product ID to a list of valid, Microsoft-manufactured product keys."
We all got first part with xxxx correct, what is with second part? Did I miss something?

Louie6666

ie6 sp1

not sure where this came from must have been wrecked at time

sorry for most irrelivant post ever

__________________

jbartone

XXXXX-640-0000356-23XXX, & XXXXX-640-2001765-23XXX


Doesnt that mean 12345-640-0000356 -23456

So it means that it needs to have the numbers in the middle for it to be invalid?

dreken

OK so where does one find the Serial Key in the registry exactly, just installed xp and no not with the fckgw cd key!

The_Sire

Ok here you can download a utility that will show you what vlk you are using

http://www.webtree.ca/windowsxp/tools/ViewKeyXP.exe

__________________
MSI KT400 Ultra (msi-6390)
Amd Athlon Xp 2600+ barton
1024meg ddr pc2700
Nvidia G4 TI 4200 4x
onboard 5.1
2 - 80 gig maxtor hard drives
3com NIC (3c905c-tx)
TDK 440n DVD burner
Buslink 16x dvd

Furious

That's how it reads to me also.

__________________

Furious

No, it means that any Id with the middle being 640-0000356-23 or 640-2001765-23 are invalid. Period. It doesn't matter what the other numbers are and it's not just the 23xxx part that makes it invalid, it's the rest of the non-variable part of the ID also.

Listen, here is your original example.

Notice the 647 part? That's not a variable according to the release.

If your assumption were correct they would've said any ID with xxxxx-xxx-xxxxxxx-23xxx was invalid.

__________________

AUDIT45

Everytime you replied you contradicted what you said in you previous post-first it was only 2 product ID's that were invalid(XXXXX-640-0000356-23XXX, & XXXXX-640-2001765-23XXX ).
Now you say what I was saying from the beginning that:
640-0000356-23 or 640-2001765-23 are the same as:
640-0000356-23XXX or 640-2001765-23XXX

I was using (12345-647-1234567 )-the first three gropus of product ID(no matter what numbers I used as a example). I was not saying that the last group(fourth group of product ID) was the only part that mattered. But if this last group starts with 23 and has the other:
640-0000356 or 640-2001765 and the 23 or 23XXX is the same but that is not what you said the first time you replied. But if you figure in the (X-value's or variable's)there are more then 2 product ID's that are (not good) invaild. In the article below from BetaOne, Microsoft tried
75 different corporate keys they found or tried and none of them worked with the new algorithm feature switched on. They have switched off the new algorithm feature for the Beta SP 1 Release's that most of us cannot get enough of. Read below for more info on the NEW Algorithm Feature.

Here is article from BETAONE:

Microsoft is planning what could end up being quite a shock for the Windows XP warez world, and what currently looks to be one of the most amazing moves made by Microsoft since Windows Product Activation was introduced.

Currently, Microsoft is in the works of completely rewriting the algorithm for the way Windows XP Corporate keys are generated, and is rewriting the code for Windows XP to recognize this new algorithm. This new code will be an added 'feature' of Service Pack 1 due out later this year.

At the present moment, an upgrade to Windows XP SP1 from Windows XP with no SP installation will not give any problems or errors about an invalid CD-Key on a corporate version of Windows XP. This is because the new algorithm feature has been switched off in SP1 upgrades. To get to see this new feature, you would have to slipstream SP1 into the Windows XP installation media and setup Windows. Once you've reached the CD-key, no current Corporate Windows XP key (none of the 75 that we've tried) will work, as they are all invalid. Even if a corporate key is managed to be found, the chances of it working when SP1 final comes out are slim to none, as Microsoft is rumored to 'still be working on the algorithm for SP1 for Corporate customers'.

So why is Microsoft keeping this a secret? To put it mildly, they are a bit perturbed that warezers have been able to exploit the corporate edition of Windows XP to completely bypass WPA. They are planning to keep it a complete surprise until SP1 final has been released and shut down as many warez users from using Windows XP as possible. They know if it's made widely known what they are planning, nobody will upgrade to SP1 until an appropriate patch has been made.

And as far as patches go, as far as we can guess right now the only patch that is going to work will be the ever popular "Reset" patch. If you slipstream a corporate version of Windows XP as you're supposed to do, it will upgrade the algorithm. Note that the slipstream patches the DLL files which generate the CD keys, it doesn't replace them. This is why you cannot slipstream a non corporate version of Windows XP and drop the corporate files in and expect the installation to work properly. Windows also checks for the DLL files version numbers and if they don't match, errors will be created during install. It could be possible to find these DLL's, replace the version numbers with those of SP1, and put them back into the installation media, but you'd also have to find a way to replicate the Microsoft signature on the DLL's as well as the CAB files for setup to actually copy the files to the hard drive.

The first thing that comes to mind when thinking about this is that the current Corporate users of Windows XP are going to have to get a new CD-key reissued for their versions of Windows with SP1. Microsoft has decided that the cost of current corporate customers having to get a new CD-key is less that what they are losing in the market of Windows XP being distributed as a corporate installation amongst warez users. Microsoft is also planning to warn those with corporate editions of Windows XP to not let the CD-keys slip into the mainstream. The EULA is going to be rewritten to fit a new type of 'Corporate release' and it's been rumored that if a customers key is to get into the market, Microsoft may take legal action against those consumers.

Another rumor that is running rounds at Redmond is that Microsoft may actually include a type of "Phone home" feature in the corporate versions of Windows XP only. This feature would connect to a Microsoft server upon connection and deliver the IP address of the connected computer and what the Installation ID is. Before privacy advocates begin screaming, realize that if Microsoft was to want to do this, they could very easily make provisions in the EULA that they (Microsoft) have included a feature that makes sure the Corporate edition of Windows XP is not installed on more computers than it's contract is made out for, and the computers IP address and the Installation ID may be transmitted to a local Microsoft server thought 128-bit encryption. No more information would be transmitted to the servers, and for more information, see the Microsoft Privacy Statement. It's a possibility, as corporate versions of Windows aren't exactly tailored for use by home and everyday users, so the EULA could very well be expanded to include such a feature.

As far as activation goes on a legal copy of Windows XP, we slipstreamed our copy and it installed and activated without any problems. The algorithm for normal customers will stay the same apparently. So far, only the corporate version of XP gets the new revamped algorithm feature. It's one less feature I can do without personally.



Source: BetaONE

sawkdanny

Man I am confused! Right now I am using WIN ME. I am planning to install XP. But All this I am gettting on confused!! Which one should I install Xp Pro / Xp crop . I really need help from you guys!!

And I heard that any cdkey starting "F" or "D" its been added to Windows Blacklist. Is it true?

Pls help me out!

uf4

Hi,
well you picked a hard question to start off with let say that i can only answer part of it..
re:"Which one should I install Xp Pro / Xp crop".. i think XP Pro is the right choice. well XP HE(home edition) is good too and its made for winME upgrading.
for the rest i'm not sure about it may be others will help you with that. hth.

rgds,

;

Yemble

Sorry, but I thought that M$ had ONLY blacklisted to specific keys. TWO keys, NOT two ranges of keys!

I'm buying a new 80Gb disk today, so I will take the opportunity to prove whether or not a generated 640/23XXX corporate key works fine by doing a fresh install. I am confident that it will!

I'll keep you posted.

__________________
See all, hear all, say nowt.
Eat all, sup all, pay nowt.
And if tha does owt for nowt, alus do it for thisen.

Zardon

please dont post any keys in this thread (I know no-one has yet), as its illegal and there are microsoft staff on the board.

Thank you.

dai

i id'nt have the time bomb in the euala but then i saw a post that said run winver and see what it comes up mine came up with the time bomb in it totally different to the eula that came up during install of sp1.i changed the key and ran winver again the time bomb had gone from the eula my product id does not start 640.but it does have the 23 starting the last set of numers.i have also tried changing the product id in the registry to see what happend.this reulted in a message coming up,that the prouct id and the key did not match.i connect to windows update with no problems.so i am just waiting to see if one day soon i have a blank screen or not.if it was not for thing like this life would be so dull. regards dai

Yemble

Right, my 80Gb disk is in. I've installed XP from scratch using a Corp. edition CD slipstreamed with SP-1 v1106.

Guess what... it was perfectly happy to accept my generated corporate (NOT pro) key.

Oh yes, and there is NO 180day time-bomb and Windows Update DOES work.

So no more M$ bullshit please, these are the REAL facts!!!

Still don't believe me? Well why not try it for yourselves instead of just guessing?

__________________
See all, hear all, say nowt.
Eat all, sup all, pay nowt.
And if tha does owt for nowt, alus do it for thisen.

uf4

who says anything about anythings like that

Louie6666

arrrrrhhh what thread are you reading, perhaps a different one from the rest of us


The issue is will you be able to use V5 of windows update with generated corp key (when the site goes live) ignoring the bit above about ppl who want to argue over what number goes where is pretty meaningless (does it really matter?) Key gen dosen't generate keys with that number range anyway...lol plonker eg XXXXX-649-6478953-23XXX

__________________

kbleft

Furious is right. Just listen to furious

thisisnuts

With all these assumptions, why don't people who have done the deed with keygens say weather or not XP1 loaded properly. For the record, a key with xxxxx-640-xxxxxxx-23xxx works. No ifs or buts about it. Otherwise you wouldn't be seeing this post.

Next topic.

thisisnuts

Again, my understanding is that for the following:
XXXXX-640-0000356-23XXX
XXXXX-640-2001765-23XXX

The numbers as you see them are constants IN THOSE POSITION. Therefore if you were to have a key : abcde-640-0000356-23fgh , you're screwed. Similarly, abcde-640-2001765-23fgh, again you're screwed.

Now if on the otherhand you were to have: abcde-640-0000xyz-23fgh then your OK.
It seems to me that if you have these: 0000356 & 2001765 , then you're screwed. So you could have 640 and 23 in the position depicted above, but make sure that the middle numbers are NOT what is shown above.

My thoughts. Again, IT HAS BEEN PROVEN.

Yemble

That's exactly what I've done. I got a load of abuse, but what the f**k I know that you ARE correct because I've proved it for myself.

__________________
See all, hear all, say nowt.
Eat all, sup all, pay nowt.
And if tha does owt for nowt, alus do it for thisen.