It seems that the long awaiting Gatchaman is going to be delayed. The original script writers was changed and also it seems Imagi is involved in Astroboy 2009... I guess its ok to be delayed as long as it is not ruined.
Wednesday, September 30, 2009
ガッチャマンGatchaman 2009 is being delayed to 2011
It seems that the long awaiting Gatchaman is going to be delayed. The original script writers was changed and also it seems Imagi is involved in Astroboy 2009... I guess its ok to be delayed as long as it is not ruined.
Micosoft Security Essentials Download
The download is finally available from:
http://www.microsoft.com/Security_essentials/default.aspx?mkt=en-us#dlbutton
The RTM version was 1.66 and it has been upgrade to 1.67.188 now.
http://www.microsoft.com/Security_essentials/default.aspx?mkt=en-us#dlbutton
The RTM version was 1.66 and it has been upgrade to 1.67.188 now.
Tuesday, September 29, 2009
Microsoft Security Essentials Launches!
On Sep 29, finally Microsoft launches the release final version of codename "Morro" or Microsoft Security Essentials. As mentioned before, this "black horse" had gotten first in VB100 and detects 97.8% of the viruses from AV-Test.org. And its FREE. Do you still want to buy another product. Well, maybe. Because MS Security Essentials does not have a firewall. However, Windows does have a reasonable one.
MS Security Essentials supports Windows XP, Vista and Windows 7.
There is no full download links yet, but it will appear in a few hours.
Dell launches Latitude Z with wireless charging
Wireless charging of battery is finally possible with the world's first laptop of such capability from Dell.
Read more at:
Saturday, September 26, 2009
Yoriden Samurai Troopers
This is one of those I really miss a lot. Well, actually I kinda never manage to wake up early enough in the morning to watch it at 5:30... Still, I managed to ctahc almost all of the 2nd season.
Thursday, September 24, 2009
Tuesday, September 22, 2009
Microsoft Morro aka Microsoft Security Essential is going final soon!
We all know from the results of VB100 that Microsoft gotten first this month (Aug 09) for antivirus solution. Sad thing was Symantec failed. In any case, the Microsoft product was actually ForeFront, which is not targeted for consumer desktop. However, it is noted that Microsoft Security Essential and probably OneCare is using the same technology.
This is what I got from a email from Microsoft:
Dear Beta User,
Thank you for participating in the Microsoft® Security Essentials Beta. Your participation has been instrumental to ensuring the best possible product release quality.
The final version of Microsoft Security Essentials will be released to the public in the coming weeks. If you are running the older version of the beta (1.0.1407.0), we encourage you to upgrade to a newer version of the beta (1.0.1500.0). To ensure a smoothest possible experience, please follow one of these options:
· Click on the ‘Upgrade Now’ button on the Microsoft Security Essentials Home tab. OR
· Select ‘Upgrade Microsoft Security Essentials’ under the Help drop-down menu
Thank you again for your participation in the Microsoft Security Essentials Beta!
Best regards,
Microsoft Security Essentials Team
After the update, I think I have the RTM version now.
This is what I got from a email from Microsoft:
Dear Beta User,
Thank you for participating in the Microsoft® Security Essentials Beta. Your participation has been instrumental to ensuring the best possible product release quality.
The final version of Microsoft Security Essentials will be released to the public in the coming weeks. If you are running the older version of the beta (1.0.1407.0), we encourage you to upgrade to a newer version of the beta (1.0.1500.0). To ensure a smoothest possible experience, please follow one of these options:
· Click on the ‘Upgrade Now’ button on the Microsoft Security Essentials Home tab. OR
· Select ‘Upgrade Microsoft Security Essentials’ under the Help drop-down menu
Thank you again for your participation in the Microsoft Security Essentials Beta!
Best regards,
Microsoft Security Essentials Team
After the update, I think I have the RTM version now.
Monday, September 21, 2009
ClustrMaps is back
It took me so long to realized that something was missing from my blog after hte upgrade. Yes, ClustrMap is gone. It is finally back now on the top left sidebar.
Anyway, since I mentioned about ClustrMap, it is a visitor tracker to keep track where people come from. As of Map 2009, here are the top 10 of this site:
United States (US)
United Kingdom (GB)
Australia (AU)
Canada (CA)
Germany (DE)
Singapore (SG)
India (IN)
Italy (IT)
Netherlands (NL)
France (FR)
Anyway, since I mentioned about ClustrMap, it is a visitor tracker to keep track where people come from. As of Map 2009, here are the top 10 of this site:
United States (US)
United Kingdom (GB)
Australia (AU)
Canada (CA)
Germany (DE)
Singapore (SG)
India (IN)
Italy (IT)
Netherlands (NL)
France (FR)
Tuesday, September 08, 2009
Fortinet Offers Free FortiClient Endpoint Security Firewall + Anti Malware
Fortinet now is giving away they FortiClient (which works for 2000, XP, 2003, 2008, W7) for FREE. FortiClient basically includes:
Antivirus/Antispyware engine
SSL and IPSec VPN clients
Personal Firewall protection
Intrusion Prevention
Web Filtering
Endpoint Application Detection
Endpoint Monitoring and Control*
WAN Optimization*
Anti-Rootkit Protection
Pre- and Post-Execution Behavioral Analysis
(Heuristics and Antispyware engine)
Real-Time Poisoned Webpage Protection
FortiGuard update services -
Antivirus/Antispyware, Web Filter,
Application Detection, Antispam
Online Forum (self-help)
The only thing which you will be missing out are (which is available in the Premuium Edition):
Antispam Protection
Central Management**
Logging (and centralized reporting)
Download it via (both 64 and 32 bits available):
http://www.forticlient.com/download.html
To be honest, I had only played around for a while, but enough to make me feel its ok. I should need to conduct a more through test before I can conclude on this product. But then again, the only other free Anti Malware which works in Windows Server is Rising Antivirus.
Antivirus/Antispyware engine
SSL and IPSec VPN clients
Personal Firewall protection
Intrusion Prevention
Web Filtering
Endpoint Application Detection
Endpoint Monitoring and Control*
WAN Optimization*
Anti-Rootkit Protection
Pre- and Post-Execution Behavioral Analysis
(Heuristics and Antispyware engine)
Real-Time Poisoned Webpage Protection
FortiGuard update services -
Antivirus/Antispyware, Web Filter,
Application Detection, Antispam
Online Forum (self-help)
The only thing which you will be missing out are (which is available in the Premuium Edition):
Antispam Protection
Central Management**
Logging (and centralized reporting)
Download it via (both 64 and 32 bits available):
http://www.forticlient.com/download.html
To be honest, I had only played around for a while, but enough to make me feel its ok. I should need to conduct a more through test before I can conclude on this product. But then again, the only other free Anti Malware which works in Windows Server is Rising Antivirus.
Saturday, September 05, 2009
Assassin Creed 2 is in Venice!
Yes, finally its going to come out in Nov 2009. Assassin Creed is not dead!
Friday, September 04, 2009
OpenDNS Multiple Network Configuration - You cannot add more networks until you complete all fields in the My Info section.
OpenDNS is a Secure DNS solution which is not affected by DNS Poisoning sometimes back. Do check it out at:
http://www.opendns.com
After signing up, I really like it and wish to have all my connections goes through it. However, when I try to set up my second network, it get this error that say:
"You cannot add more networks until you complete all fields in the My Info section."
Basically, I tried to fill it up several times, but it just doesn't update or allow me to do so. Finally, I found out the reason. It is because I had set my account to "Home User". In short, home user is only suppose to have 1 network interface.
Just change your profile to "Work / Business" and update the info. You should be able to update now and add the second network.
http://www.opendns.com
After signing up, I really like it and wish to have all my connections goes through it. However, when I try to set up my second network, it get this error that say:
"You cannot add more networks until you complete all fields in the My Info section."
Basically, I tried to fill it up several times, but it just doesn't update or allow me to do so. Finally, I found out the reason. It is because I had set my account to "Home User". In short, home user is only suppose to have 1 network interface.
Just change your profile to "Work / Business" and update the info. You should be able to update now and add the second network.
Thursday, September 03, 2009
Fake Antivirus Goes Green!
http://securitylabs.websense.com/content/Blogs/3469.aspx
If you take a close look at this, you will notice that the box is a rip off of Microsoft's packaging! In any case, be very careful when you start to think about doing your part for the planet.
If you take a close look at this, you will notice that the box is a rip off of Microsoft's packaging! In any case, be very careful when you start to think about doing your part for the planet.
Tuesday, September 01, 2009
XP Media and OEM Keys
The secret is all inside a file \i386\setupp.ini.
WinXP's setupp.ini controls how the CD acts. First, find your setupp.ini file in the i386 directory on your WinXP CD. Open it up, it'll look something like this:
ExtraData=707A667567736F696F697911AE7E05
Pid=55034000
The Pid value is what we're interested in. What's there now looks like a standard default. There are special numbers that determine if it's a retail, oem, or volume license edition. First, we break down that number into two parts. The first five digits determines how the CD will behave, ie is it a retail cd that lets you clean install or upgrade, or an oem cd that only lets you perform a clean install? The last three digits determines what CD key it will accept. You are able to mix and match these values. For example you could make a WinXP cd that acted like a retail cd, yet accepted OEM keys.
Now, for the actual values. Remember the first and last values are interchangable, but usually you'd keep them as a pair:
Retail = 51882 335
Volume License = 51883 270
OEM = 82503 OEM
So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read:
Pid=51882335
And if you wanted a retail CD that took OEM keys, you'd use:
Pid=51882OEM
Note that this does NOT get rid of WinXP's activation. Changing the Pid to a Volume License will not bypass activation. You must have a volume license (corporate) key to do so.
What is the pid?
Microsoft uses various Product IDs to identify variants of the Windows platform. A Windows product ID (currently, as of XP/2003/Vista) has the following format: xxxxx-yyy-zzzzzzz-zzzzz
'xxxxx' -- the Microsoft Product Code
The xxxxx section is the Microsoft Product Code, which in this case describes the platform, build, and version of Windows. Other product IDs with the same format, such as those found in Microsoft Office (and many other Microsoft products), serve the same purpose.
'yyy' -- the Channel ID
This section of the PID describes the channel (OEM, Volume License, Retail, bundle/Not For Resale) a given XP CD/system has come from.
000 : Other (includes some retail, upgrade and evaluation versions)
006 : MS or Partner promotions
007 : FIXME : Retail
009 : Not for resale - bundle
011 : Upgrade (XP Home?)
083 : Windows Genuine Advantage
OEM : OEM (This does not specify royalty or normal OEM)
270 : Volume License
296 : MSDN
308/347 : Microsoft Action Pack subscription
335 : Retail
640 through 652 : Volume License (usually generated via 270 CID in setupp.ini)
699 : Volume Windows XP Tablet Edition
071 : FIXME : Unknown.
NOTE: According to DjLizard.net visitor Catalyst, newer discs now check to see if the CD's volume label matches the type of CD you have. So if you make a CD with the wrong volume label, then it still won't work. I haven't been able to confirm this because most of my CDs have a custom label and all of them work fine thus far. Visit TACKtech to see a list of volume labels.
MPC list - English locale
55274 : XP Pro generic OEM
55276 : XP Pro (upgrade)
55276 : XP Home (?) †
55277 : XP Home generic OEM
55285 : XP Pro †
55661 : XP Pro (retail)
76475 : XP Home (upgrade) (?)
76477 : XP Home Royalty OEM ‡
76481 : XP Pro Dell OEM
76487 : XP Media Center Edition 2005
76487 : XP Pro Royalty OEM ‡
76487 : XP Pro SP2 (retail)
76487 : XP Pro SP3 (OEM)
76487 : XP Pro volume license (with '640' channel ID)
76500 : XP MCE 2005 (which is XP Pro with no domain capability)
76588 : XP Pro x64 OEM
MPC list - other languages
55372 : XP Home - German (OEM)
55375 : XP Pro - German (VLK)
55677 : XP Home - Dutch
55679 : XP Pro - Dutch
76381 : XP Home - Danish
76392 : XP Pro - Danish
76396 : XP Pro (also Home?) - Dutch
76412 : XP Home - French (OEM)
76413 : XP Pro - French (OEM)
76440 : XP Pro - Norwegian (retail)
76447 : XP Pro - Polish
76460 : XP Home - Spanish (Royalty OEM) ‡
76470 : XP Home - Traditional Chinese (Royalty OEM) ‡
Notes:
‡ : Royalty OEM (Original Equipment Manufacturer) means manufacturers that are special to Microsoft's endearing heart. They get their own private key and generated product keys that typically don't require activation (or are different than the product key on the COA sticker affixed to the computer). Certain big OEMs [Dell, Gateway, HP, Compaq, and more] are Royalty OEMs, and the little guys (your local mom + pop store) are obviously not. The mom and pop stores get 55277 for Home and 55285 for Pro. Typically, generic OEM discs (such as 55277 and 55274) will work on these systems, but activation will often fail -- you will have to call Microsoft's activation hotline and speak to a representative in order to activate Windows. This usually only takes a few minutes.
Windows XP complete list - English locale
Edition Volume Label File Date (DD-MM-YY) MPC CID
Windows XP Combo Home/Pro WXPHFPP_EN 23-08-01 1:00
Windows XP Home Retail WXHFPP_EN 23-08-01 8:00 55277 000
Windows XP Home Retail SP1 XRMHFPP_EN 29-08-02 8:00 55277 000
Windows XP Home Retail SP1a X1AHFPP_EN 31-03-03 8:00 55277 000
Windows XP Home Retail SP2 VRMHFPP_EN 4-08-04 8:00 55277 000
Windows XP Home Upgrade WXHCCP_EN 23-08-01 8:00 55285 000
Windows XP Home Upgrade SP1 XRMHCCP_EN 29-08-02 8:00 55285 000
Windows XP Home Upgrade SP1a X1AHCCP_EN 31-03-03 8:00 55285 000
Windows XP Home Upgrade SP2 VRMHCCP_EN 4-08-04 8:00 55285 000
Windows XP Home OEM WXHOEM_EN 23-08-01 8:00 55277 OEM
Windows XP Home OEM SP1 XRMHOEM_EN 29-08-02 8:00 55277 OEM
Windows XP Home OEM SP1a X1AHOEM_EN 31-03-03 8:00 55277 OEM
Windows XP Home OEM SP2 VRMHOEM_EN 4-08-04 8:00 55277 OEM
Windows XP Home OEM SP2 VRMHOEM_EN 4-08-04 12:00 76477 OEM
Windows XP Home Volume WXHVOL_EN 23-08-01 8:00 55274 270
Windows XP Home Volume SP1 XRMHVOL_EN 29-08-02 8:00 55274 270
Windows XP Home Volume SP1a X1AHVOL_EN 31-03-03 8:00 55274 270
Windows XP Home Volume SP2 VRMHVOL_EN 4-08-04 8:00 55274 270
Windows XP Home (SP2) DELL System Install XP2_PER_ENG
Windows XP Pro (SP2) DELL System Install XP2_PRO_ENG
Windows XP Pro Retail WXPFPP_EN 23-08-01 8:00 55274 000
Windows XP Pro Retail SP1 XRMPFPP_EN 29-08-02 8:00 55274 000
Windows XP Pro Retail SP1a X1APFPP_EN 31-03-03 8:00 55274 000
Windows XP Pro Retail SP2 VRMPFPP_EN 4-08-04 8:00 55274 000
Windows XP Pro Retail SP2 VX2PFPP_EN 28-02-2006 5:00AM 76487 000
Windows XP Pro Upgrade WXPCCP_EN 23-08-01 8:00 55276 000
Windows XP Pro Upgrade SP1 XRMPCCP_EN 29-08-02 8:00 55276 000
Windows XP Pro Upgrade SP1a X1APCCP_EN 31-03-03 8:00 55276 000
Windows XP Pro Academic Upgrade SP1 X1APCCP_EN 31-03-03 23:00 55276 000
Windows XP Pro Upgrade SP2 VRMPCCP_EN 4-08-04 8:00 55276 000
Windows XP Pro Academic Upgrade SP2 VRMPCCP_EN 4-08-04 23:00 76488 000
Windows XP Pro OEM WXPOEM_EN 23-08-01 8:00 55274 OEM
Windows XP Pro OEM SP1 XRMPOEM_EN 29-08-02 8:00 55274 OEM
Windows XP Pro OEM SP1a X1APOEM_EN 31-03-03 8:00 55274 OEM
Windows XP Pro OEM SP2 VRMPOEM_EN 4-08-04 8:00 55274 OEM
Windows XP Pro OEM SP3 GRTMPOEM_EN 4-14-08 5:00 76487 OEM
Windows XP Pro Volume WXPVOL_EN 23-08-01 8:00 55274 270
Windows XP Pro Volume SP1 XRMPVOL_EN 29-08-02 8:00 55274 270
Windows XP Pro Volume SP1a X1APVOL_EN 31-03-03 8:00 55274 270
Windows XP Pro Volume SP2 VRMPVOL_EN 4-08-04 8:00 55274 270
Windows XP Pro Tablet PC SP1 Disc 1 XRMPFPP_EN 29-08-02 8:00 55274 000
Windows XP Pro Tablet PC SP1a Disc 1 X1APFPP_EN 31-03-03 8:00 55274 000
Windows XP Pro Tablet PC SP2 Disc 1 VRMPFPP_EN 4-08-04 8:00 55274 000
Windows XP Pro MSDN WXPFPP_EN 23-08-01 8:00 55274 000
Windows XP Pro MSDN SP1 XRMPFPP_EN 29-08-02 8:00 55274 000
Windows XP Pro MSDN SP1a X1APFPP_EN 31-03-03 8:00 55274 000
Windows XP Pro MSDN SP2 VRMPFPP_EN 4-08-04 8:00 55274 000
Windows XP Pro Evaluation WXPEVL_EN
Note: these Channel IDs (CIDs) were taken from i386\SETUPP.INI. Windows Setup may generate a completely different Product ID than you see here; this is soley based on your product key.
Server 2003 MPC list - English locale
69712 : Standard Edition 32-bit retail
69712 : Standard Edition 32-bit volume licensing
69712 : Standard Edition 32-bit OEM
69763 : Standard Edition 32-bit evaluation
69753 : Web Edition 32-bit retail
69753 : Web Edition 32-bit volume licensing
69753 : Web Edition 32-bit OEM
69763 : Web Edition 32-bit evaluation
69713 : Enterprise Edition 32-bit retail
69713 : Enterprise Edition 32-bit volume licensing
69713 : Enterprise Edition 32-bit OEM
69763 : Enterprise Edition 32-bit evaluation
69713 : Enterprise Edition 32-bit checked build
69754 : Datacenter Edition 32-bit retail
69754 : Datacenter Edition 32-bit OEM
69770 : Enterprise Edition 64-bit retail
69770 : Enterprise Edition 64-bit volume licensing
69770 : Enterprise Edition 64-bit OEM
69763 : Enterprise Edition 64-bit evaluation
69770 : Enterprise Edition 64-bit checked build
69769 : Datacenter Edition 64-bit retail
69769 : Datacenter Edition 64-bit OEM
74995 : Small business server
76868 : Unknown Enterprise Edition 64-bit (FIXME)
Notes
If you have to perform a "repair install" (Microsoft calls this an "in-place upgrade", and DjLizard interchangeably calls it an "overlay" or "repair install") then you MUST know these two things:
1.The MPC of your destination computer, and
2.the MPC of all of your Windows OEM CDs.
If you don't, then you will not be able to activate Windows properly, or in some cases, get the installation to accept your product key.
The MPC of your CDs can be determined by editing the SETUPP.INI in the i386 directory on your disc. You can (in some cases) simply edit this file, change the PID, and recompile the CD to be able to use whatever key you happen to need.
Retrieving your product ID or MPC
The current MPC for a system can be retrieved by various methods:
If the destination computer's operating system works well enough [even in safe mode], you can get it by right-clicking My Computer, clicking Properties, and reading the long ID number that appears under 'Registered to'.
You can use the command reg query "hklm\software\microsoft\windows nt\currentversion" /v ProductID at a command prompt (Start > Run > cmd.exe).
If the destination computer does not work very well, you can get the ID by attaching the hard drive to a working machine and mounting the appropriate registry hive. Highlight HKEY_LOCAL_MACHINE in your local regedit and choose File > Load Hive. Then browse to X:\Windows\System32\config\SOFTWARE (where X:\Windows is the drive letter and path to the Windows installation in question). It will ask you what key to mount; you then give it any name you like, and it will appear under your own HKEY_LOCAL_MACHINE. Drill-down through Microsoft\Windows NT\CurrentVersion in this new key. You will see ProductID on the right.
Do not forget to highlight the top key of the mounted hive, and choose File > Unload Hive when you are done.
Finally, you can sometimes find the ID you need if you check for the presence of either X:\i386\setupp.ini (where X: is the system's drive letter) or X:\Windows\i386\setupp.ini (where X:\Windows is the drive letter and path to the Windows installation folder in question).
Once you have the destination ID, it's as simple as inserting your CD that uses the same ID.
Bad Product IDs
As of 2005/10/22, Microsoft states that the following are invalid PIDs:
XXXXX-640-0000356-23XXX
XXXXX-640-2001765-23XXX
The above two product IDs are known as "Devil's Own", and usually have a product key starting with "FCKGW".
XXXXX-640-643718X-23XXX
XXXXX-641-309376X-23XXX
XXXXX-642-064580X-23XXX
XXXXX-642-464364X-23XXX
XXXXX-643-334701X-23XXX
XXXXX-644-081772X-23XXX
XXXXX-644-451265X-23XXX
XXXXX-644-874896X-23XXX
XXXXX-644-933704X-23XXX
XXXXX-644-962396X-23XXX
XXXXX-645-833254X-23XXX
XXXXX-645-994962X-23XXX
XXXXX-646-031843X-23XXX
XXXXX-646-104081X-23XXX
XXXXX-646-105103X-23XXX
XXXXX-647-318838X-23XXX
XXXXX-647-592029X-23XXX
XXXXX-647-677834X-23XXX
XXXXX-648-301691X-23XXX
XXXXX-648-819992X-23XXX
XXXXX-649-106765X-23XXX
XXXXX-649-941392X-23XXX
XXXXX-650-292312X-23XXX
These PIDs are detected when you attempt to install SP1, 2 or 3.
And here are for the other OSs:
CCP = Compliance Checking Program (Upgrades)
FPP = Fully Packaged Product
OEM = Original Equipment Manufacturer
SEL = Select (No Key Required)
VOL = Volume License Key Required
EVL = Evaluation Software
MS-DOS 6.22/Windows 3.11 OEM Combo = 05/31/94 2:22 AM / 11/03/93 4:11 AM
Windows 95 Retail = 07/11/95 9:50 AM (09:50:00)
Windows 95 Retail Upgrade = 07/11/95 9:50 AM (09:50:00)
Windows 95 OEM = WINDOWS95 07/11/95 5:50 AM (05:50:00) or 07/11/95 9:50 AM (09:50:00)
Windows 95 OEM OSR1 "A" = WINDOWS95 12/31/95 5:50 AM (05:50:00) or 02/02/96 9:51 AM (09:51:00)
Windows 95 OEM OSR2 "B" = W95_FULL_AR 08/24/96 8:11 AM (08:11:00) or 08/24/96 11:11 AM (11:11:11)
Windows 95 OEM OSR2.1 "B" = W95_FULL_AR 05/01/97 8:14 AM (08:14:00) or 06/25/97 9:07 AM (09:07:10)
Windows 95 OEM OSR2.5 "C" = WIN95_C 11/25/97 10:16 PM (22:16:00) or 11/26/97 12:14 PM (12:14:00)
Windows 98 Retail = Windows 98 05/11/98 8:01 PM (20:01:00)
Windows 98 Retail Upgrade = Windows 98 05/11/98 8:01 PM (20:01:00)
Windows 98 OEM = Windows 98 05/11/98 8:01 PM (20:01:00) or 11/24/98 4:02 AM (04:02:00)
Windows 98 SE Retail = Win98 SE 04/23/99 6:22 PM (18:22:00) or 04/23/99 10:22 PM (22:22:00)
Windows 98 SE Retail Upgrade = Win98 SE 04/23/99 6:22 PM (18:22:00) or 04/23/99 10:22 PM (22:22:00)
Windows 98 SE OEM = Win98 SE 04/23/99 6:22 PM (18:22:00) or 04/23/99 10:22 PM (22:22:00)
Windows ME Retail = Windows Me 06/08/00 1:00 PM (13:00:00) or 06/08/00 3:00 PM (17:00:00)
Windows ME Retail Upgrade = Windows Me 06/08/00 1:00 PM (13:00:00) or 06/08/00 3:00 PM (17:00:00)
Windows ME Retail Step Up = Windows Me 06/08/00 1:00 PM (13:00:00) or 06/08/00 3:00 PM (17:00:00)
Windows ME OEM = Windows Me 06/08/00 1:00 PM (13:00:00) or 06/08/00 3:00 PM (17:00:00)
Windows ME MSDN = Windows Me 06/08/00 1:00 PM (13:00:00)
Windows NT 3.1 Workstation Retail =
Windows NT 3.1 Advanced Server Retail =
Windows NT 3.5 Workstation Retail = WORKSTATION xx/xx/xx
Windows NT 3.5 Server Retail = SERVER xx/xx/xx
Windows NT 3.51 Workstation Retail = NTWKS xx/xx/xx
Windows NT 3.51 Server Retail = NTSRV xx/xx/xx
Windows NT 4.0 Workstation = NTWKS40A 10/13/96 9:38 PM (21:38:00) 50036
Windows NT 4.0 Server = NTSRV40A 10/13/96 9:38 PM (21:38:00) 50370
Windows NT 4.0 Enterprise Server Disc 1 = NTSE_BASE_D 09/12/97 8:00 AM (08:00:00) 70234
Windows NT 4.0 Enterprise Server Disc 2 = NTSE_COMP 09/15/97 8:00 AM (08:00:00) -----
Windows NT 4.0 Terminal Server = WINNT-TSE40 07/22/98 2:09 PM (14:09:00) 88090270
Windows 2000 Combo Pro/Svr/Asvr = WIN2000_EN
Windows 2000 Pro OEM = W2POEM_EN 12/07/99 8:00 AM (08:00:00) 51873OEM
Windows 2000 Pro OEM SP1 = SP1POEM_EN 07/26/00 8:00 AM (08:00:00) 51873OEM
Windows 2000 Pro OEM SP2 = SP2POEM_EN 05/08/01 3:00 PM (15:00:00) 51873OEM
Windows 2000 Pro OEM SP3 = YRMPOEM_EN 07/24/02 8:00 AM (08:00:00) 51873OEM
Windows 2000 Pro OEM SP4 = ZRMPOEM_EN 06/20/03 8:00 AM (08:00:00) 51873OEM
Windows 2000 Pro Retail = W2PFPP_EN 12/07/99 8:00 AM (08:00:00) 51873000
Windows 2000 Pro Retail SP1 = SP1PFPP_EN 07/26/00 8:00 AM (08:00:00) 51873000
Windows 2000 Pro Retail SP2 = SP2PFPP_EN 05/08/01 3:00 PM (15:00:00) 51873000
Windows 2000 Pro Retail SP3 = YRMPFPP_EN 07/24/02 8:00 AM (08:00:00) 51873000
Windows 2000 Pro Retail SP4 = ZRMPFPP_EN 06/20/03 8:00 AM (08:00:00) 51873000
Windows 2000 Pro Select = W2PSEL_EN 12/07/99 8:00 AM (08:00:00) 51873270
Windows 2000 Pro Select SP1 = SP1PSEL_EN 07/26/00 8:00 AM (08:00:00) 51873270
Windows 2000 Pro Select SP2 = SP2PSEL_EN 05/08/01 3:00 PM (15:00:00) 51873270
Windows 2000 Pro Select SP3 = YRMPSEL_EN 07/24/02 8:00 AM (08:00:00) 51873270
Windows 2000 Pro Select SP4 = ZRMPSEL_EN 06/20/03 8:00 AM (08:00:00) 51873270
Windows 2000 Pro MSDN = W2PFPP_EN 12/07/99 8:00 AM (08:00:00) 51873000
Windows 2000 Pro MSDN SP1 = SP1PFPP_EN 07/26/00 8:00 AM (08:00:00) 51873000
Windows 2000 Pro MSDN SP2 = SP2PFPP_EN 05/08/01 3:00 PM (15:00:00) 51873000
Windows 2000 Pro MSDN SP3 = YRMPFPP_EN 07/24/02 8:00 AM (08:00:00) 51873000
Windows 2000 Pro MSDN SP4 = ZRMPFPP_EN 06/20/03 8:00 AM (08:00:00) 51873000
Windows 2000 Server OEM = W2SOEM_EN 12/07/99 8:00 AM (08:00:00) 51876OEM
Windows 2000 Server OEM SP1 = SP1SOEM_EN 07/26/00 8:00 AM (08:00:00) 51876OEM
Windows 2000 Server OEM SP2 = SP2SOEM_EN 05/08/01 3:00 PM (15:00:00) 51876OEM
Windows 2000 Server OEM SP3 = YRMSOEM_EN 07/24/02 8:00 AM (08:00:00) 51876OEM
Windows 2000 Server OEM SP4 = ZRMSOEM_EN 06/20/03 8:00 AM (08:00:00) 51876OEM
Windows 2000 Server Retail = W2SFPP_EN 12/07/99 8:00 AM (08:00:00) 51876000
Windows 2000 Server Retail SP1 = SP1SFPP_EN 07/26/00 8:00 AM (08:00:00) 51876000
Windows 2000 Server Retail SP2 = SP2SFPP_EN 05/08/01 3:00 PM (15:00:00) 51876000
Windows 2000 Server Retail SP3 = YRMSFPP_EN 07/24/02 8:00 AM (08:00:00) 51876000
Windows 2000 Server Retail SP4 = ZRMSFPP_EN 06/20/03 8:00 AM (08:00:00) 51876000
Windows 2000 Server Select = W2SSEL_EN 12/07/99 8:00 AM (08:00:00) 51876270
Windows 2000 Server Select SP1 = SP1SSEL_EN 07/26/00 8:00 AM (08:00:00) 51876270
Windows 2000 Server Select SP2 = SP2SSEL_EN 05/08/01 3:00 PM (15:00:00) 51876270
Windows 2000 Server Select SP3 = YRMSSEL_EN 07/24/02 8:00 AM (08:00:00) 51876270
Windows 2000 Server Select SP4 = ZRMSSEL_EN 06/20/03 8:00 AM (08:00:00) 51876270
Windows 2000 Server MSDN = W2SFPP_EN 12/07/99 8:00 AM (08:00:00) 51876000
Windows 2000 Server MSDN SP1 = SP1SFPP_EN 07/26/00 8:00 AM (08:00:00) 51876000
Windows 2000 Server MSDN SP2 = SP2SFPP_EN 05/08/01 3:00 PM (15:00:00) 51876000
Windows 2000 Server MSDN SP3 = YRMSFPP_EN 07/24/02 8:00 AM (08:00:00) 51876000
Windows 2000 Server MSDN SP4 = ZRMSFPP_EN 06/20/03 8:00 AM (08:00:00) 51876000
Windows 2000 Advanced Server OEM = W2AOEM_EN 12/07/99 8:00 AM (08:00:00) 51879OEM
Windows 2000 Advanced Server OEM SP1 = SP1AOEM_EN 07/26/00 8:00 AM (08:00:00) 51879OEM
Windows 2000 Advanced Server OEM SP2 = SP2AOEM_EN 05/08/01 3:00 PM (15:00:00) 51879OEM
Windows 2000 Advanced Server OEM SP3 = YRMAOEM_EN 07/24/02 8:00 AM (08:00:00) 51879OEM
Windows 2000 Advanced Server OEM SP4 = ZRMAOEM_EN 06/20/03 8:00 AM (08:00:00) 51879OEM
Windows 2000 Advanced Server Retail = W2AFPP_EN 12/07/99 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server Retail SP1 = SP1AFPP_EN 07/26/00 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server Retail SP2 = SP2AFPP_EN 05/08/01 3:00 PM (15:00:00) 51879000
Windows 2000 Advanced Server Retail SP3 = YRMAFPP_EN 07/24/02 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server Retail SP4 = ZRMAFPP_EN 06/20/03 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server Select = W2ASEL_EN 12/07/99 8:00 AM (08:00:00) 51879270
Windows 2000 Advanced Server Select SP1 = SP1ASEL_EN 07/26/00 8:00 AM (08:00:00) 51879270
Windows 2000 Advanced Server Select SP2 = SP2ASEL_EN 05/08/01 3:00 PM (15:00:00) 51879270
Windows 2000 Advanced Server Select SP3 = YRMASEL_EN 07/24/02 8:00 AM (08:00:00) 51879270
Windows 2000 Advanced Server Select SP4 = ZRMASEL_EN 06/20/03 8:00 AM (08:00:00) 51879270
Windows 2000 Advanced Server MSDN = W2AFPP_EN 12/07/99 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server MSDN SP1 = SP1AFPP_EN 07/26/00 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server MSDN SP2 = SP2AFPP_EN 05/08/01 3:00 PM (15:00:00) 51879000
Windows 2000 Advanced Server MSDN SP3 = YRMAFPP_EN 07/24/02 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server MSDN SP4 = ZRMAFPP_EN 06/20/03 8:00 AM (08:00:00) 51879000
Windows 2000 Datacenter inc. SP1 = W2DFPP_EN
Windows XP Combo Home/Pro = WXPHFPP_EN 08/23/01 1:00 AM (01:00:00)
Windows XP Home Retail = WXHFPP_EN 08/23/01 8:00 AM (08:00:00) 55277000
Windows XP Home Retail w/ SP1 = XRMHFPP_EN 08/29/02 8:00 AM (08:00:00) 55277000
Windows XP Home Retail w/ SP1a = X1AHFPP_EN 03/31/03 8:00 AM (08:00:00) 55277000
Windows XP Home Retail w/ SP2 = VRMHFPP_EN 08/04/04 8:00 AM (08:00:00) 55277000
Windows XP Home Upgrade = WXHCCP_EN 08/23/01 8:00 AM (08:00:00) 55285000
Windows XP Home Upgrade W/SP1 = XRMHCCP_EN 08/29/02 8:00 AM (08:00:00) 55285000
Windows XP Home Upgrade W/SP1a = X1AHCCP_EN 03/31/03 8:00 AM (08:00:00) 55285000
Windows XP Home Upgrade W/SP2 = VRMHCCP_EN 08/04/04 8:00 AM (08:00:00) 55285000
Windows XP Home OEM = WXHOEM_EN 08/23/01 8:00 AM (08:00:00) 55277OEM
Windows XP Home OEM w/ SP1 = XRMHOEM_EN 08/29/02 8:00 AM (08:00:00) 55277OEM
Windows XP Home OEM w/ SP1a = X1AHOEM_EN 03/31/03 8:00 AM (08:00:00) 55277OEM
Windows XP Home OEM w/ SP2 = VRMHOEM_EN 08/04/04 8:00 AM (08:00:00) 55277OEM
Windows XP Home Volume = WXHVOL_EN 08/23/01 8:00 AM (08:00:00) 55274270
Windows XP Home Volume W/ SP1 = XRMHVOL_EN 08/29/02 8:00 AM (08:00:00) 55274270
Windows XP Home Volume W/ SP1a = X1AHVOL_EN 03/31/03 8:00 AM (08:00:00) 55274270
Windows XP Home Volume W/ SP2 = VRMHVOL_EN 08/04/04 8:00 AM (08:00:00) 55274270
Windows XP Pro Retail = WXPFPP_EN 08/23/01 8:00 AM (08:00:00) 55274000
Windows XP Pro Retail w/ SP1 = XRMPFPP_EN 08/29/02 8:00 AM (08:00:00) 55274000
Windows XP Pro Retail w/ SP1a = X1APFPP_EN 03/31/03 8:00 AM (08:00:00) 55274000
Windows XP Pro Retail w/ SP2 = VRMPFPP_EN 08/04/04 8:00 AM (08:00:00) 55274000
Windows XP Pro Upgrade = WXPCCP_EN 08/23/01 8:00 AM (08:00:00) 55276000
Windows XP Pro Upgrade w/ SP1 = XRMPCCP_EN 08/29/02 8:00 AM (08:00:00) 55276000
Windows XP Pro Upgrade w/ SP1a = X1APCCP_EN 03/31/03 8:00 AM (08:00:00) 55276000
Windows XP Pro Upgrade w/ SP2 = VRMPCCP_EN 08/04/04 8:00 AM (08:00:00) 55276000
Windows XP Pro OEM = WXPOEM_EN 08/23/01 8:00 AM (08:00:00) 55274OEM
Windows XP Pro OEM w/ SP1 = XRMPOEM_EN 08/29/02 8:00 AM (08:00:00) 55274OEM
Windows XP Pro OEM w/ SP1a = X1APOEM_EN 03/31/03 8:00 AM (08:00:00) 55274OEM
Windows XP Pro OEM w/ SP2 = VRMPOEM_EN 08/04/04 8:00 AM (08:00:00) 55274OEM
Windows XP Pro Volume = WXPVOL_EN 08/23/01 8:00 AM (08:00:00) 55274270
Windows XP Pro Volume w/ SP1 = XRMPVOL_EN 08/29/02 8:00 AM (08:00:00) 55274270
Windows XP Pro Volume w/ SP1a = X1APVOL_EN 03/31/03 8:00 AM (08:00:00) 55274270
Windows XP Pro Volume w/ SP2 = VRMPVOL_EN 08/04/04 8:00 AM (08:00:00) 55274270
Windows XP Pro Tablet PC w/SP1 Disc1 = XRMPFPP_EN 08/29/02 8:00 AM (08:00:00) 55274000
Windows XP Pro Tablet PC w/SP1a Disc1 = X1APFPP_EN 03/31/03 8:00 AM (08:00:00) 55274000
Windows XP Pro Tablet PC w/SP2 Disc1 = VRMPFPP_EN 08/04/04 8:00 AM (08:00:00) 55274000
Windows XP Pro MSDN = WXPFPP_EN 08/23/01 8:00 AM (08:00:00) 55274000
Windows XP Pro MSDN w/ SP1 = XRMPFPP_EN 08/29/02 8:00 AM (08:00:00) 55274000
Windows XP Pro MSDN w/ SP1a = X1APFPP_EN 03/31/03 8:00 AM (08:00:00) 55274000
Windows XP Pro MSDN w/ SP2 = VRMPFPP_EN 08/04/04 8:00 AM (08:00:00) 55274000
Windows XP Pro Evaluation = WXPEVL_EN
Windows Server 2003 Combo Std/Ent = EN_WS03 03/25/03 8:00 AM (08:00:00)
Windows Server 2003 Standard Retail = NRMSFPP_EN 03/25/03 8:00 AM (08:00:00) 69712000
Windows Server 2003 Standard OEM = NRMSOEM_EN 03/25/03 8:00 AM (08:00:00) 69712OEM
Windows Server 2003 Standard Volume = NRMSVOL_EN 03/25/03 8:00 AM (08:00:00) 69712270
Windows Server 2003 Web Retail = NRMWFPP_EN 03/25/03 8:00 AM (08:00:00) 69753000
Windows Server 2003 Web OEM = NRMWOEM_EN 03/25/03 8:00 AM (08:00:00) 69753OEM
Windows Server 2003 Web Volume = NRMWVOL_EN 03/25/03 8:00 AM (08:00:00) 69753270
Windows Server 2003 Enterprise Retail = NRMEFPP_EN 03/25/03 8:00 AM (08:00:00) 69713000
Windows Server 2003 Enterprise OEM = NRMEOEM_EN 03/25/03 8:00 AM (08:00:00) 69713OEM
Windows Server 2003 Enterprise Volume = NRMEVOL_EN 03/25/03 8:00 AM (08:00:00) 69713270
Windows Server 2003 Datacenter = NRMDFPP_EN
Windows Server 2003 Enterprise Eval = NRMEEVL_EN 69763000
WinXP's setupp.ini controls how the CD acts. First, find your setupp.ini file in the i386 directory on your WinXP CD. Open it up, it'll look something like this:
ExtraData=707A667567736F696F697911AE7E05
Pid=55034000
The Pid value is what we're interested in. What's there now looks like a standard default. There are special numbers that determine if it's a retail, oem, or volume license edition. First, we break down that number into two parts. The first five digits determines how the CD will behave, ie is it a retail cd that lets you clean install or upgrade, or an oem cd that only lets you perform a clean install? The last three digits determines what CD key it will accept. You are able to mix and match these values. For example you could make a WinXP cd that acted like a retail cd, yet accepted OEM keys.
Now, for the actual values. Remember the first and last values are interchangable, but usually you'd keep them as a pair:
Retail = 51882 335
Volume License = 51883 270
OEM = 82503 OEM
So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read:
Pid=51882335
And if you wanted a retail CD that took OEM keys, you'd use:
Pid=51882OEM
Note that this does NOT get rid of WinXP's activation. Changing the Pid to a Volume License will not bypass activation. You must have a volume license (corporate) key to do so.
What is the pid?
Microsoft uses various Product IDs to identify variants of the Windows platform. A Windows product ID (currently, as of XP/2003/Vista) has the following format: xxxxx-yyy-zzzzzzz-zzzzz
'xxxxx' -- the Microsoft Product Code
The xxxxx section is the Microsoft Product Code, which in this case describes the platform, build, and version of Windows. Other product IDs with the same format, such as those found in Microsoft Office (and many other Microsoft products), serve the same purpose.
'yyy' -- the Channel ID
This section of the PID describes the channel (OEM, Volume License, Retail, bundle/Not For Resale) a given XP CD/system has come from.
000 : Other (includes some retail, upgrade and evaluation versions)
006 : MS or Partner promotions
007 : FIXME : Retail
009 : Not for resale - bundle
011 : Upgrade (XP Home?)
083 : Windows Genuine Advantage
OEM : OEM (This does not specify royalty or normal OEM)
270 : Volume License
296 : MSDN
308/347 : Microsoft Action Pack subscription
335 : Retail
640 through 652 : Volume License (usually generated via 270 CID in setupp.ini)
699 : Volume Windows XP Tablet Edition
071 : FIXME : Unknown.
NOTE: According to DjLizard.net visitor Catalyst, newer discs now check to see if the CD's volume label matches the type of CD you have. So if you make a CD with the wrong volume label, then it still won't work. I haven't been able to confirm this because most of my CDs have a custom label and all of them work fine thus far. Visit TACKtech to see a list of volume labels.
MPC list - English locale
55274 : XP Pro generic OEM
55276 : XP Pro (upgrade)
55276 : XP Home (?) †
55277 : XP Home generic OEM
55285 : XP Pro †
55661 : XP Pro (retail)
76475 : XP Home (upgrade) (?)
76477 : XP Home Royalty OEM ‡
76481 : XP Pro Dell OEM
76487 : XP Media Center Edition 2005
76487 : XP Pro Royalty OEM ‡
76487 : XP Pro SP2 (retail)
76487 : XP Pro SP3 (OEM)
76487 : XP Pro volume license (with '640' channel ID)
76500 : XP MCE 2005 (which is XP Pro with no domain capability)
76588 : XP Pro x64 OEM
MPC list - other languages
55372 : XP Home - German (OEM)
55375 : XP Pro - German (VLK)
55677 : XP Home - Dutch
55679 : XP Pro - Dutch
76381 : XP Home - Danish
76392 : XP Pro - Danish
76396 : XP Pro (also Home?) - Dutch
76412 : XP Home - French (OEM)
76413 : XP Pro - French (OEM)
76440 : XP Pro - Norwegian (retail)
76447 : XP Pro - Polish
76460 : XP Home - Spanish (Royalty OEM) ‡
76470 : XP Home - Traditional Chinese (Royalty OEM) ‡
Notes:
‡ : Royalty OEM (Original Equipment Manufacturer) means manufacturers that are special to Microsoft's endearing heart. They get their own private key and generated product keys that typically don't require activation (or are different than the product key on the COA sticker affixed to the computer). Certain big OEMs [Dell, Gateway, HP, Compaq, and more] are Royalty OEMs, and the little guys (your local mom + pop store) are obviously not. The mom and pop stores get 55277 for Home and 55285 for Pro. Typically, generic OEM discs (such as 55277 and 55274) will work on these systems, but activation will often fail -- you will have to call Microsoft's activation hotline and speak to a representative in order to activate Windows. This usually only takes a few minutes.
Windows XP complete list - English locale
Edition Volume Label File Date (DD-MM-YY) MPC CID
Windows XP Combo Home/Pro WXPHFPP_EN 23-08-01 1:00
Windows XP Home Retail WXHFPP_EN 23-08-01 8:00 55277 000
Windows XP Home Retail SP1 XRMHFPP_EN 29-08-02 8:00 55277 000
Windows XP Home Retail SP1a X1AHFPP_EN 31-03-03 8:00 55277 000
Windows XP Home Retail SP2 VRMHFPP_EN 4-08-04 8:00 55277 000
Windows XP Home Upgrade WXHCCP_EN 23-08-01 8:00 55285 000
Windows XP Home Upgrade SP1 XRMHCCP_EN 29-08-02 8:00 55285 000
Windows XP Home Upgrade SP1a X1AHCCP_EN 31-03-03 8:00 55285 000
Windows XP Home Upgrade SP2 VRMHCCP_EN 4-08-04 8:00 55285 000
Windows XP Home OEM WXHOEM_EN 23-08-01 8:00 55277 OEM
Windows XP Home OEM SP1 XRMHOEM_EN 29-08-02 8:00 55277 OEM
Windows XP Home OEM SP1a X1AHOEM_EN 31-03-03 8:00 55277 OEM
Windows XP Home OEM SP2 VRMHOEM_EN 4-08-04 8:00 55277 OEM
Windows XP Home OEM SP2 VRMHOEM_EN 4-08-04 12:00 76477 OEM
Windows XP Home Volume WXHVOL_EN 23-08-01 8:00 55274 270
Windows XP Home Volume SP1 XRMHVOL_EN 29-08-02 8:00 55274 270
Windows XP Home Volume SP1a X1AHVOL_EN 31-03-03 8:00 55274 270
Windows XP Home Volume SP2 VRMHVOL_EN 4-08-04 8:00 55274 270
Windows XP Home (SP2) DELL System Install XP2_PER_ENG
Windows XP Pro (SP2) DELL System Install XP2_PRO_ENG
Windows XP Pro Retail WXPFPP_EN 23-08-01 8:00 55274 000
Windows XP Pro Retail SP1 XRMPFPP_EN 29-08-02 8:00 55274 000
Windows XP Pro Retail SP1a X1APFPP_EN 31-03-03 8:00 55274 000
Windows XP Pro Retail SP2 VRMPFPP_EN 4-08-04 8:00 55274 000
Windows XP Pro Retail SP2 VX2PFPP_EN 28-02-2006 5:00AM 76487 000
Windows XP Pro Upgrade WXPCCP_EN 23-08-01 8:00 55276 000
Windows XP Pro Upgrade SP1 XRMPCCP_EN 29-08-02 8:00 55276 000
Windows XP Pro Upgrade SP1a X1APCCP_EN 31-03-03 8:00 55276 000
Windows XP Pro Academic Upgrade SP1 X1APCCP_EN 31-03-03 23:00 55276 000
Windows XP Pro Upgrade SP2 VRMPCCP_EN 4-08-04 8:00 55276 000
Windows XP Pro Academic Upgrade SP2 VRMPCCP_EN 4-08-04 23:00 76488 000
Windows XP Pro OEM WXPOEM_EN 23-08-01 8:00 55274 OEM
Windows XP Pro OEM SP1 XRMPOEM_EN 29-08-02 8:00 55274 OEM
Windows XP Pro OEM SP1a X1APOEM_EN 31-03-03 8:00 55274 OEM
Windows XP Pro OEM SP2 VRMPOEM_EN 4-08-04 8:00 55274 OEM
Windows XP Pro OEM SP3 GRTMPOEM_EN 4-14-08 5:00 76487 OEM
Windows XP Pro Volume WXPVOL_EN 23-08-01 8:00 55274 270
Windows XP Pro Volume SP1 XRMPVOL_EN 29-08-02 8:00 55274 270
Windows XP Pro Volume SP1a X1APVOL_EN 31-03-03 8:00 55274 270
Windows XP Pro Volume SP2 VRMPVOL_EN 4-08-04 8:00 55274 270
Windows XP Pro Tablet PC SP1 Disc 1 XRMPFPP_EN 29-08-02 8:00 55274 000
Windows XP Pro Tablet PC SP1a Disc 1 X1APFPP_EN 31-03-03 8:00 55274 000
Windows XP Pro Tablet PC SP2 Disc 1 VRMPFPP_EN 4-08-04 8:00 55274 000
Windows XP Pro MSDN WXPFPP_EN 23-08-01 8:00 55274 000
Windows XP Pro MSDN SP1 XRMPFPP_EN 29-08-02 8:00 55274 000
Windows XP Pro MSDN SP1a X1APFPP_EN 31-03-03 8:00 55274 000
Windows XP Pro MSDN SP2 VRMPFPP_EN 4-08-04 8:00 55274 000
Windows XP Pro Evaluation WXPEVL_EN
Note: these Channel IDs (CIDs) were taken from i386\SETUPP.INI. Windows Setup may generate a completely different Product ID than you see here; this is soley based on your product key.
Server 2003 MPC list - English locale
69712 : Standard Edition 32-bit retail
69712 : Standard Edition 32-bit volume licensing
69712 : Standard Edition 32-bit OEM
69763 : Standard Edition 32-bit evaluation
69753 : Web Edition 32-bit retail
69753 : Web Edition 32-bit volume licensing
69753 : Web Edition 32-bit OEM
69763 : Web Edition 32-bit evaluation
69713 : Enterprise Edition 32-bit retail
69713 : Enterprise Edition 32-bit volume licensing
69713 : Enterprise Edition 32-bit OEM
69763 : Enterprise Edition 32-bit evaluation
69713 : Enterprise Edition 32-bit checked build
69754 : Datacenter Edition 32-bit retail
69754 : Datacenter Edition 32-bit OEM
69770 : Enterprise Edition 64-bit retail
69770 : Enterprise Edition 64-bit volume licensing
69770 : Enterprise Edition 64-bit OEM
69763 : Enterprise Edition 64-bit evaluation
69770 : Enterprise Edition 64-bit checked build
69769 : Datacenter Edition 64-bit retail
69769 : Datacenter Edition 64-bit OEM
74995 : Small business server
76868 : Unknown Enterprise Edition 64-bit (FIXME)
Notes
If you have to perform a "repair install" (Microsoft calls this an "in-place upgrade", and DjLizard interchangeably calls it an "overlay" or "repair install") then you MUST know these two things:
1.The MPC of your destination computer, and
2.the MPC of all of your Windows OEM CDs.
If you don't, then you will not be able to activate Windows properly, or in some cases, get the installation to accept your product key.
The MPC of your CDs can be determined by editing the SETUPP.INI in the i386 directory on your disc. You can (in some cases) simply edit this file, change the PID, and recompile the CD to be able to use whatever key you happen to need.
Retrieving your product ID or MPC
The current MPC for a system can be retrieved by various methods:
If the destination computer's operating system works well enough [even in safe mode], you can get it by right-clicking My Computer, clicking Properties, and reading the long ID number that appears under 'Registered to'.
You can use the command reg query "hklm\software\microsoft\windows nt\currentversion" /v ProductID at a command prompt (Start > Run > cmd.exe).
If the destination computer does not work very well, you can get the ID by attaching the hard drive to a working machine and mounting the appropriate registry hive. Highlight HKEY_LOCAL_MACHINE in your local regedit and choose File > Load Hive. Then browse to X:\Windows\System32\config\SOFTWARE (where X:\Windows is the drive letter and path to the Windows installation in question). It will ask you what key to mount; you then give it any name you like, and it will appear under your own HKEY_LOCAL_MACHINE. Drill-down through Microsoft\Windows NT\CurrentVersion in this new key. You will see ProductID on the right.
Do not forget to highlight the top key of the mounted hive, and choose File > Unload Hive when you are done.
Finally, you can sometimes find the ID you need if you check for the presence of either X:\i386\setupp.ini (where X: is the system's drive letter) or X:\Windows\i386\setupp.ini (where X:\Windows is the drive letter and path to the Windows installation folder in question).
Once you have the destination ID, it's as simple as inserting your CD that uses the same ID.
Bad Product IDs
As of 2005/10/22, Microsoft states that the following are invalid PIDs:
XXXXX-640-0000356-23XXX
XXXXX-640-2001765-23XXX
The above two product IDs are known as "Devil's Own", and usually have a product key starting with "FCKGW".
XXXXX-640-643718X-23XXX
XXXXX-641-309376X-23XXX
XXXXX-642-064580X-23XXX
XXXXX-642-464364X-23XXX
XXXXX-643-334701X-23XXX
XXXXX-644-081772X-23XXX
XXXXX-644-451265X-23XXX
XXXXX-644-874896X-23XXX
XXXXX-644-933704X-23XXX
XXXXX-644-962396X-23XXX
XXXXX-645-833254X-23XXX
XXXXX-645-994962X-23XXX
XXXXX-646-031843X-23XXX
XXXXX-646-104081X-23XXX
XXXXX-646-105103X-23XXX
XXXXX-647-318838X-23XXX
XXXXX-647-592029X-23XXX
XXXXX-647-677834X-23XXX
XXXXX-648-301691X-23XXX
XXXXX-648-819992X-23XXX
XXXXX-649-106765X-23XXX
XXXXX-649-941392X-23XXX
XXXXX-650-292312X-23XXX
These PIDs are detected when you attempt to install SP1, 2 or 3.
And here are for the other OSs:
CCP = Compliance Checking Program (Upgrades)
FPP = Fully Packaged Product
OEM = Original Equipment Manufacturer
SEL = Select (No Key Required)
VOL = Volume License Key Required
EVL = Evaluation Software
MS-DOS 6.22/Windows 3.11 OEM Combo = 05/31/94 2:22 AM / 11/03/93 4:11 AM
Windows 95 Retail = 07/11/95 9:50 AM (09:50:00)
Windows 95 Retail Upgrade = 07/11/95 9:50 AM (09:50:00)
Windows 95 OEM = WINDOWS95 07/11/95 5:50 AM (05:50:00) or 07/11/95 9:50 AM (09:50:00)
Windows 95 OEM OSR1 "A" = WINDOWS95 12/31/95 5:50 AM (05:50:00) or 02/02/96 9:51 AM (09:51:00)
Windows 95 OEM OSR2 "B" = W95_FULL_AR 08/24/96 8:11 AM (08:11:00) or 08/24/96 11:11 AM (11:11:11)
Windows 95 OEM OSR2.1 "B" = W95_FULL_AR 05/01/97 8:14 AM (08:14:00) or 06/25/97 9:07 AM (09:07:10)
Windows 95 OEM OSR2.5 "C" = WIN95_C 11/25/97 10:16 PM (22:16:00) or 11/26/97 12:14 PM (12:14:00)
Windows 98 Retail = Windows 98 05/11/98 8:01 PM (20:01:00)
Windows 98 Retail Upgrade = Windows 98 05/11/98 8:01 PM (20:01:00)
Windows 98 OEM = Windows 98 05/11/98 8:01 PM (20:01:00) or 11/24/98 4:02 AM (04:02:00)
Windows 98 SE Retail = Win98 SE 04/23/99 6:22 PM (18:22:00) or 04/23/99 10:22 PM (22:22:00)
Windows 98 SE Retail Upgrade = Win98 SE 04/23/99 6:22 PM (18:22:00) or 04/23/99 10:22 PM (22:22:00)
Windows 98 SE OEM = Win98 SE 04/23/99 6:22 PM (18:22:00) or 04/23/99 10:22 PM (22:22:00)
Windows ME Retail = Windows Me 06/08/00 1:00 PM (13:00:00) or 06/08/00 3:00 PM (17:00:00)
Windows ME Retail Upgrade = Windows Me 06/08/00 1:00 PM (13:00:00) or 06/08/00 3:00 PM (17:00:00)
Windows ME Retail Step Up = Windows Me 06/08/00 1:00 PM (13:00:00) or 06/08/00 3:00 PM (17:00:00)
Windows ME OEM = Windows Me 06/08/00 1:00 PM (13:00:00) or 06/08/00 3:00 PM (17:00:00)
Windows ME MSDN = Windows Me 06/08/00 1:00 PM (13:00:00)
Windows NT 3.1 Workstation Retail =
Windows NT 3.1 Advanced Server Retail =
Windows NT 3.5 Workstation Retail = WORKSTATION xx/xx/xx
Windows NT 3.5 Server Retail = SERVER xx/xx/xx
Windows NT 3.51 Workstation Retail = NTWKS xx/xx/xx
Windows NT 3.51 Server Retail = NTSRV xx/xx/xx
Windows NT 4.0 Workstation = NTWKS40A 10/13/96 9:38 PM (21:38:00) 50036
Windows NT 4.0 Server = NTSRV40A 10/13/96 9:38 PM (21:38:00) 50370
Windows NT 4.0 Enterprise Server Disc 1 = NTSE_BASE_D 09/12/97 8:00 AM (08:00:00) 70234
Windows NT 4.0 Enterprise Server Disc 2 = NTSE_COMP 09/15/97 8:00 AM (08:00:00) -----
Windows NT 4.0 Terminal Server = WINNT-TSE40 07/22/98 2:09 PM (14:09:00) 88090270
Windows 2000 Combo Pro/Svr/Asvr = WIN2000_EN
Windows 2000 Pro OEM = W2POEM_EN 12/07/99 8:00 AM (08:00:00) 51873OEM
Windows 2000 Pro OEM SP1 = SP1POEM_EN 07/26/00 8:00 AM (08:00:00) 51873OEM
Windows 2000 Pro OEM SP2 = SP2POEM_EN 05/08/01 3:00 PM (15:00:00) 51873OEM
Windows 2000 Pro OEM SP3 = YRMPOEM_EN 07/24/02 8:00 AM (08:00:00) 51873OEM
Windows 2000 Pro OEM SP4 = ZRMPOEM_EN 06/20/03 8:00 AM (08:00:00) 51873OEM
Windows 2000 Pro Retail = W2PFPP_EN 12/07/99 8:00 AM (08:00:00) 51873000
Windows 2000 Pro Retail SP1 = SP1PFPP_EN 07/26/00 8:00 AM (08:00:00) 51873000
Windows 2000 Pro Retail SP2 = SP2PFPP_EN 05/08/01 3:00 PM (15:00:00) 51873000
Windows 2000 Pro Retail SP3 = YRMPFPP_EN 07/24/02 8:00 AM (08:00:00) 51873000
Windows 2000 Pro Retail SP4 = ZRMPFPP_EN 06/20/03 8:00 AM (08:00:00) 51873000
Windows 2000 Pro Select = W2PSEL_EN 12/07/99 8:00 AM (08:00:00) 51873270
Windows 2000 Pro Select SP1 = SP1PSEL_EN 07/26/00 8:00 AM (08:00:00) 51873270
Windows 2000 Pro Select SP2 = SP2PSEL_EN 05/08/01 3:00 PM (15:00:00) 51873270
Windows 2000 Pro Select SP3 = YRMPSEL_EN 07/24/02 8:00 AM (08:00:00) 51873270
Windows 2000 Pro Select SP4 = ZRMPSEL_EN 06/20/03 8:00 AM (08:00:00) 51873270
Windows 2000 Pro MSDN = W2PFPP_EN 12/07/99 8:00 AM (08:00:00) 51873000
Windows 2000 Pro MSDN SP1 = SP1PFPP_EN 07/26/00 8:00 AM (08:00:00) 51873000
Windows 2000 Pro MSDN SP2 = SP2PFPP_EN 05/08/01 3:00 PM (15:00:00) 51873000
Windows 2000 Pro MSDN SP3 = YRMPFPP_EN 07/24/02 8:00 AM (08:00:00) 51873000
Windows 2000 Pro MSDN SP4 = ZRMPFPP_EN 06/20/03 8:00 AM (08:00:00) 51873000
Windows 2000 Server OEM = W2SOEM_EN 12/07/99 8:00 AM (08:00:00) 51876OEM
Windows 2000 Server OEM SP1 = SP1SOEM_EN 07/26/00 8:00 AM (08:00:00) 51876OEM
Windows 2000 Server OEM SP2 = SP2SOEM_EN 05/08/01 3:00 PM (15:00:00) 51876OEM
Windows 2000 Server OEM SP3 = YRMSOEM_EN 07/24/02 8:00 AM (08:00:00) 51876OEM
Windows 2000 Server OEM SP4 = ZRMSOEM_EN 06/20/03 8:00 AM (08:00:00) 51876OEM
Windows 2000 Server Retail = W2SFPP_EN 12/07/99 8:00 AM (08:00:00) 51876000
Windows 2000 Server Retail SP1 = SP1SFPP_EN 07/26/00 8:00 AM (08:00:00) 51876000
Windows 2000 Server Retail SP2 = SP2SFPP_EN 05/08/01 3:00 PM (15:00:00) 51876000
Windows 2000 Server Retail SP3 = YRMSFPP_EN 07/24/02 8:00 AM (08:00:00) 51876000
Windows 2000 Server Retail SP4 = ZRMSFPP_EN 06/20/03 8:00 AM (08:00:00) 51876000
Windows 2000 Server Select = W2SSEL_EN 12/07/99 8:00 AM (08:00:00) 51876270
Windows 2000 Server Select SP1 = SP1SSEL_EN 07/26/00 8:00 AM (08:00:00) 51876270
Windows 2000 Server Select SP2 = SP2SSEL_EN 05/08/01 3:00 PM (15:00:00) 51876270
Windows 2000 Server Select SP3 = YRMSSEL_EN 07/24/02 8:00 AM (08:00:00) 51876270
Windows 2000 Server Select SP4 = ZRMSSEL_EN 06/20/03 8:00 AM (08:00:00) 51876270
Windows 2000 Server MSDN = W2SFPP_EN 12/07/99 8:00 AM (08:00:00) 51876000
Windows 2000 Server MSDN SP1 = SP1SFPP_EN 07/26/00 8:00 AM (08:00:00) 51876000
Windows 2000 Server MSDN SP2 = SP2SFPP_EN 05/08/01 3:00 PM (15:00:00) 51876000
Windows 2000 Server MSDN SP3 = YRMSFPP_EN 07/24/02 8:00 AM (08:00:00) 51876000
Windows 2000 Server MSDN SP4 = ZRMSFPP_EN 06/20/03 8:00 AM (08:00:00) 51876000
Windows 2000 Advanced Server OEM = W2AOEM_EN 12/07/99 8:00 AM (08:00:00) 51879OEM
Windows 2000 Advanced Server OEM SP1 = SP1AOEM_EN 07/26/00 8:00 AM (08:00:00) 51879OEM
Windows 2000 Advanced Server OEM SP2 = SP2AOEM_EN 05/08/01 3:00 PM (15:00:00) 51879OEM
Windows 2000 Advanced Server OEM SP3 = YRMAOEM_EN 07/24/02 8:00 AM (08:00:00) 51879OEM
Windows 2000 Advanced Server OEM SP4 = ZRMAOEM_EN 06/20/03 8:00 AM (08:00:00) 51879OEM
Windows 2000 Advanced Server Retail = W2AFPP_EN 12/07/99 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server Retail SP1 = SP1AFPP_EN 07/26/00 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server Retail SP2 = SP2AFPP_EN 05/08/01 3:00 PM (15:00:00) 51879000
Windows 2000 Advanced Server Retail SP3 = YRMAFPP_EN 07/24/02 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server Retail SP4 = ZRMAFPP_EN 06/20/03 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server Select = W2ASEL_EN 12/07/99 8:00 AM (08:00:00) 51879270
Windows 2000 Advanced Server Select SP1 = SP1ASEL_EN 07/26/00 8:00 AM (08:00:00) 51879270
Windows 2000 Advanced Server Select SP2 = SP2ASEL_EN 05/08/01 3:00 PM (15:00:00) 51879270
Windows 2000 Advanced Server Select SP3 = YRMASEL_EN 07/24/02 8:00 AM (08:00:00) 51879270
Windows 2000 Advanced Server Select SP4 = ZRMASEL_EN 06/20/03 8:00 AM (08:00:00) 51879270
Windows 2000 Advanced Server MSDN = W2AFPP_EN 12/07/99 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server MSDN SP1 = SP1AFPP_EN 07/26/00 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server MSDN SP2 = SP2AFPP_EN 05/08/01 3:00 PM (15:00:00) 51879000
Windows 2000 Advanced Server MSDN SP3 = YRMAFPP_EN 07/24/02 8:00 AM (08:00:00) 51879000
Windows 2000 Advanced Server MSDN SP4 = ZRMAFPP_EN 06/20/03 8:00 AM (08:00:00) 51879000
Windows 2000 Datacenter inc. SP1 = W2DFPP_EN
Windows XP Combo Home/Pro = WXPHFPP_EN 08/23/01 1:00 AM (01:00:00)
Windows XP Home Retail = WXHFPP_EN 08/23/01 8:00 AM (08:00:00) 55277000
Windows XP Home Retail w/ SP1 = XRMHFPP_EN 08/29/02 8:00 AM (08:00:00) 55277000
Windows XP Home Retail w/ SP1a = X1AHFPP_EN 03/31/03 8:00 AM (08:00:00) 55277000
Windows XP Home Retail w/ SP2 = VRMHFPP_EN 08/04/04 8:00 AM (08:00:00) 55277000
Windows XP Home Upgrade = WXHCCP_EN 08/23/01 8:00 AM (08:00:00) 55285000
Windows XP Home Upgrade W/SP1 = XRMHCCP_EN 08/29/02 8:00 AM (08:00:00) 55285000
Windows XP Home Upgrade W/SP1a = X1AHCCP_EN 03/31/03 8:00 AM (08:00:00) 55285000
Windows XP Home Upgrade W/SP2 = VRMHCCP_EN 08/04/04 8:00 AM (08:00:00) 55285000
Windows XP Home OEM = WXHOEM_EN 08/23/01 8:00 AM (08:00:00) 55277OEM
Windows XP Home OEM w/ SP1 = XRMHOEM_EN 08/29/02 8:00 AM (08:00:00) 55277OEM
Windows XP Home OEM w/ SP1a = X1AHOEM_EN 03/31/03 8:00 AM (08:00:00) 55277OEM
Windows XP Home OEM w/ SP2 = VRMHOEM_EN 08/04/04 8:00 AM (08:00:00) 55277OEM
Windows XP Home Volume = WXHVOL_EN 08/23/01 8:00 AM (08:00:00) 55274270
Windows XP Home Volume W/ SP1 = XRMHVOL_EN 08/29/02 8:00 AM (08:00:00) 55274270
Windows XP Home Volume W/ SP1a = X1AHVOL_EN 03/31/03 8:00 AM (08:00:00) 55274270
Windows XP Home Volume W/ SP2 = VRMHVOL_EN 08/04/04 8:00 AM (08:00:00) 55274270
Windows XP Pro Retail = WXPFPP_EN 08/23/01 8:00 AM (08:00:00) 55274000
Windows XP Pro Retail w/ SP1 = XRMPFPP_EN 08/29/02 8:00 AM (08:00:00) 55274000
Windows XP Pro Retail w/ SP1a = X1APFPP_EN 03/31/03 8:00 AM (08:00:00) 55274000
Windows XP Pro Retail w/ SP2 = VRMPFPP_EN 08/04/04 8:00 AM (08:00:00) 55274000
Windows XP Pro Upgrade = WXPCCP_EN 08/23/01 8:00 AM (08:00:00) 55276000
Windows XP Pro Upgrade w/ SP1 = XRMPCCP_EN 08/29/02 8:00 AM (08:00:00) 55276000
Windows XP Pro Upgrade w/ SP1a = X1APCCP_EN 03/31/03 8:00 AM (08:00:00) 55276000
Windows XP Pro Upgrade w/ SP2 = VRMPCCP_EN 08/04/04 8:00 AM (08:00:00) 55276000
Windows XP Pro OEM = WXPOEM_EN 08/23/01 8:00 AM (08:00:00) 55274OEM
Windows XP Pro OEM w/ SP1 = XRMPOEM_EN 08/29/02 8:00 AM (08:00:00) 55274OEM
Windows XP Pro OEM w/ SP1a = X1APOEM_EN 03/31/03 8:00 AM (08:00:00) 55274OEM
Windows XP Pro OEM w/ SP2 = VRMPOEM_EN 08/04/04 8:00 AM (08:00:00) 55274OEM
Windows XP Pro Volume = WXPVOL_EN 08/23/01 8:00 AM (08:00:00) 55274270
Windows XP Pro Volume w/ SP1 = XRMPVOL_EN 08/29/02 8:00 AM (08:00:00) 55274270
Windows XP Pro Volume w/ SP1a = X1APVOL_EN 03/31/03 8:00 AM (08:00:00) 55274270
Windows XP Pro Volume w/ SP2 = VRMPVOL_EN 08/04/04 8:00 AM (08:00:00) 55274270
Windows XP Pro Tablet PC w/SP1 Disc1 = XRMPFPP_EN 08/29/02 8:00 AM (08:00:00) 55274000
Windows XP Pro Tablet PC w/SP1a Disc1 = X1APFPP_EN 03/31/03 8:00 AM (08:00:00) 55274000
Windows XP Pro Tablet PC w/SP2 Disc1 = VRMPFPP_EN 08/04/04 8:00 AM (08:00:00) 55274000
Windows XP Pro MSDN = WXPFPP_EN 08/23/01 8:00 AM (08:00:00) 55274000
Windows XP Pro MSDN w/ SP1 = XRMPFPP_EN 08/29/02 8:00 AM (08:00:00) 55274000
Windows XP Pro MSDN w/ SP1a = X1APFPP_EN 03/31/03 8:00 AM (08:00:00) 55274000
Windows XP Pro MSDN w/ SP2 = VRMPFPP_EN 08/04/04 8:00 AM (08:00:00) 55274000
Windows XP Pro Evaluation = WXPEVL_EN
Windows Server 2003 Combo Std/Ent = EN_WS03 03/25/03 8:00 AM (08:00:00)
Windows Server 2003 Standard Retail = NRMSFPP_EN 03/25/03 8:00 AM (08:00:00) 69712000
Windows Server 2003 Standard OEM = NRMSOEM_EN 03/25/03 8:00 AM (08:00:00) 69712OEM
Windows Server 2003 Standard Volume = NRMSVOL_EN 03/25/03 8:00 AM (08:00:00) 69712270
Windows Server 2003 Web Retail = NRMWFPP_EN 03/25/03 8:00 AM (08:00:00) 69753000
Windows Server 2003 Web OEM = NRMWOEM_EN 03/25/03 8:00 AM (08:00:00) 69753OEM
Windows Server 2003 Web Volume = NRMWVOL_EN 03/25/03 8:00 AM (08:00:00) 69753270
Windows Server 2003 Enterprise Retail = NRMEFPP_EN 03/25/03 8:00 AM (08:00:00) 69713000
Windows Server 2003 Enterprise OEM = NRMEOEM_EN 03/25/03 8:00 AM (08:00:00) 69713OEM
Windows Server 2003 Enterprise Volume = NRMEVOL_EN 03/25/03 8:00 AM (08:00:00) 69713270
Windows Server 2003 Datacenter = NRMDFPP_EN
Windows Server 2003 Enterprise Eval = NRMEEVL_EN 69763000
Vista OEM Product Keys
Definition of OEM:
The term, OEM (original equipment manufacturer) refers to companies that make products for others to repackage and sell. Resellers buy OEM products in bulk, minus the costly retail packaging that comes with individually sold units. The product itself is essentially the same as its more expensive, retail-packaged sibling. OEM products are used in many industries, but are perhaps most prevalent in electronics.
Generally, dealers of OEM products add something of value before reselling the merchandise. An OEM vendor that does this is known as a \"value added reseller\" (VAR). A VAR might build components, sub-systems, or systems from quality OEM parts. OEM goods allow VARs a wide range of creative marketing choices, which permits smaller dealers to be competitive in the marketplace.
OEM software will have different product numbers than retail packages, and support may be provided by the VAR, rather than the maker of the software. Functionally, OEM and retail versions of software should be essentially the same.
Two kinds of OEM Product Keys:
OEM SLP Keys:
* OEM SLP (System-Locked Pre-installation) keys are only issued to the big manufacturers such as Dell, Asus, Sony, etc.
* These are the only keys that are able to bypass activation that is, perform offline activation without contacting Microsoft.
* They will work with any OEM SLP system, regardless of the OEM system's brand i.e. Product Keys are not brand specific.
OEM NONSLP Keys:
* Similar to Retail, but distributed and supported by an OEM. Needs activation by phone or online and they are not brand specific. .
OEM COA Keys:
* OEM COA keys (Certificate of Authentication) are regular OEM keys that require activation, either by phone or online and they are not brand specific.
(you will find the sticker with the key underneath you Laptop or on the side of you PC)
* These keys will work in general same as Retail or Upgrade keys and can be used only once.
OEM SLP Product Keys activation:
* You need is an OEM SLP Product Key that matches the version of Windows Vista you have installed or are going to install.
(Home Basic, Home Premium, Business or Ultimate), plus the OEM certificate matching the SLIC table
* The OEM SLP Product Key does not have to match the OEM-brand certificate nor the OEM-brand BIOS ACPI_SLIC information.
(The only ones that need to match are the OEM-brand certificate and the OEM-brand BIOS ACPI_SLIC information.)
* SLP activation doesn't work with Vista Release Candidates or Vista Beta versions. Only the final version (RTM, Retail or OEM).
i.e.: A+B+C = Vista Activated Offline
OEM SLP Key + OEM Certificate + Full SLIC Table = Vista Activated Offline
If one (A,B or C) is missing, activation will fail!
Note: (the SLIC table can be emulated)
FAQ
Why so many different keys for the same edition of Windows Vista?
I believe it's mainly because different keys are issued to the same brand in different countries.
Also, like Volume Licensing, I believe Microsoft imposes a limit to the number of systems that can be shipped with the same license or OEM SLP key.
When the limit is reached, the Royalty OEM will buy a new license and a new key is then issued .
What is SLP 2.0?
This mechanism referred as 'SLP 2.0' ('system-locked pre-installation 2.0') consists in THREE (3) elements:
1. The OEM's hardware-embedded BIOS ACPI_SLIC information signed by Microsoft
Toshiba = “TOSQCITOSQCI00?
HEX: 54 4F 53 51 43 49 54 4F 53 51 43 49 30 30
2. A certificate issued by Microsoft that corresponds to the specific ACPI_SLIC information.
Something like 'oemname.xrm-ms'.
3. A special type of product key that corresponds to the installed edition of Windows Vista.
Is the OEM SLP license mechanism a crack?
There is no cracking here; the OEM SLP license mechanism was created by MS and is completely legitimate.
Where do these keys come from?
These keys were retrieved from OEM SLP systems that are being sold by the big OEM vendors.
Do I need to activate my Vista online when I use a OEM Product Key?
Yes, if you use an OEM COA Product Key or any other Retail or Upgrade Product Key
No, if you use an OEM SLP Product Key
Is MS going to black list the OEM SLP Product Keys?
No, these keys have been used by the big brands for thousand of computer with legally preinstalled Vista. If they black list those keys all these legal costumers would be affected too.
Why big manufactures can use OEM SLP Product Keys?
Large OEMs tend to ship large numbers of PCs with Windows preinstalled. The keep the process of installing the OS cost effective Microsoft has decided that these companies will be allowed to use the some key to preinstall Vista on their units.
Also, because of the direct relationship Microsoft has with those OEMS, the company has a higher degree of confidence that a genuine COA will be attached to each PC and that there will be accurate reporting of the number of units shipped preinstalled with Microsoft Windows.
I tried those Vista Ultimate keys here but getting an error saying something like to call Microsoft for activation?
Well, OEM SLP Key and/or OEM Certificate and/or Full SLIC Table is missing. Or the installed key is not matching your Vista Edition.
How to change the product key?
Launch command prompt window with elevated privileges (Admin mode)
type:
slmgr -ipk
The term, OEM (original equipment manufacturer) refers to companies that make products for others to repackage and sell. Resellers buy OEM products in bulk, minus the costly retail packaging that comes with individually sold units. The product itself is essentially the same as its more expensive, retail-packaged sibling. OEM products are used in many industries, but are perhaps most prevalent in electronics.
Generally, dealers of OEM products add something of value before reselling the merchandise. An OEM vendor that does this is known as a \"value added reseller\" (VAR). A VAR might build components, sub-systems, or systems from quality OEM parts. OEM goods allow VARs a wide range of creative marketing choices, which permits smaller dealers to be competitive in the marketplace.
OEM software will have different product numbers than retail packages, and support may be provided by the VAR, rather than the maker of the software. Functionally, OEM and retail versions of software should be essentially the same.
Two kinds of OEM Product Keys:
OEM SLP Keys:
* OEM SLP (System-Locked Pre-installation) keys are only issued to the big manufacturers such as Dell, Asus, Sony, etc.
* These are the only keys that are able to bypass activation that is, perform offline activation without contacting Microsoft.
* They will work with any OEM SLP system, regardless of the OEM system's brand i.e. Product Keys are not brand specific.
OEM NONSLP Keys:
* Similar to Retail, but distributed and supported by an OEM. Needs activation by phone or online and they are not brand specific. .
OEM COA Keys:
* OEM COA keys (Certificate of Authentication) are regular OEM keys that require activation, either by phone or online and they are not brand specific.
(you will find the sticker with the key underneath you Laptop or on the side of you PC)
* These keys will work in general same as Retail or Upgrade keys and can be used only once.
OEM SLP Product Keys activation:
* You need is an OEM SLP Product Key that matches the version of Windows Vista you have installed or are going to install.
(Home Basic, Home Premium, Business or Ultimate), plus the OEM certificate matching the SLIC table
* The OEM SLP Product Key does not have to match the OEM-brand certificate nor the OEM-brand BIOS ACPI_SLIC information.
(The only ones that need to match are the OEM-brand certificate and the OEM-brand BIOS ACPI_SLIC information.)
* SLP activation doesn't work with Vista Release Candidates or Vista Beta versions. Only the final version (RTM, Retail or OEM).
i.e.: A+B+C = Vista Activated Offline
OEM SLP Key + OEM Certificate + Full SLIC Table = Vista Activated Offline
If one (A,B or C) is missing, activation will fail!
Note: (the SLIC table can be emulated)
FAQ
Why so many different keys for the same edition of Windows Vista?
I believe it's mainly because different keys are issued to the same brand in different countries.
Also, like Volume Licensing, I believe Microsoft imposes a limit to the number of systems that can be shipped with the same license or OEM SLP key.
When the limit is reached, the Royalty OEM will buy a new license and a new key is then issued .
What is SLP 2.0?
This mechanism referred as 'SLP 2.0' ('system-locked pre-installation 2.0') consists in THREE (3) elements:
1. The OEM's hardware-embedded BIOS ACPI_SLIC information signed by Microsoft
Toshiba = “TOSQCITOSQCI00?
HEX: 54 4F 53 51 43 49 54 4F 53 51 43 49 30 30
2. A certificate issued by Microsoft that corresponds to the specific ACPI_SLIC information.
Something like 'oemname.xrm-ms'.
3. A special type of product key that corresponds to the installed edition of Windows Vista.
Is the OEM SLP license mechanism a crack?
There is no cracking here; the OEM SLP license mechanism was created by MS and is completely legitimate.
Where do these keys come from?
These keys were retrieved from OEM SLP systems that are being sold by the big OEM vendors.
Do I need to activate my Vista online when I use a OEM Product Key?
Yes, if you use an OEM COA Product Key or any other Retail or Upgrade Product Key
No, if you use an OEM SLP Product Key
Is MS going to black list the OEM SLP Product Keys?
No, these keys have been used by the big brands for thousand of computer with legally preinstalled Vista. If they black list those keys all these legal costumers would be affected too.
Why big manufactures can use OEM SLP Product Keys?
Large OEMs tend to ship large numbers of PCs with Windows preinstalled. The keep the process of installing the OS cost effective Microsoft has decided that these companies will be allowed to use the some key to preinstall Vista on their units.
Also, because of the direct relationship Microsoft has with those OEMS, the company has a higher degree of confidence that a genuine COA will be attached to each PC and that there will be accurate reporting of the number of units shipped preinstalled with Microsoft Windows.
I tried those Vista Ultimate keys here but getting an error saying something like to call Microsoft for activation?
Well, OEM SLP Key and/or OEM Certificate and/or Full SLIC Table is missing. Or the installed key is not matching your Vista Edition.
How to change the product key?
Launch command prompt window with elevated privileges (Admin mode)
type:
slmgr -ipk
Subscribe to:
Posts (Atom)