windows xp service pack edition
Service packs
Microsoft occasionally releases service packs for its Windows operating systems to fix problems and add features. Each service pack is a superset of all previous service packs and patches so that only the latest service pack needs to be installed, and also includes new revisions.[23] Older patches need not be removed before application of the most recent one.
[edit] Service Pack 1
Set Program Access and Defaults was added in Service Pack 1.
Service Pack 1 (SP1) for Windows XP was released on September 9, 2002. It contains post-RTM security fixes and hot-fixes, compatibility updates, optional .NET Framework support, enabling technologies for new devices such as Tablet PCs, and a new Windows Messenger 4.7 version. The most notable new features were USB 2.0 support, and a Set Program Access and Defaults utility that aimed at hiding various middleware products. Users can control the default application for activities such as web browsing and instant messaging, as well as hide access to some of Microsoft's bundled programs. This utility was first brought into the older Windows 2000 operating system with its Service Pack 3. The Microsoft Java Virtual Machine, which was not in the RTM version, appeared in this service pack.[24]
On February 3, 2003, Microsoft released Service Pack 1a (SP1a). This release removed Microsoft's Java virtual machine as a result of a lawsuit with Sun Microsystems. [25]
[edit] Service Pack 2
Windows Security Center was added in Service Pack 2.
Service Pack 2 (SP2) (codenamed "Springboard") was released on August 6, 2004 after several delays, with a special emphasis on security.[26] Unlike the previous service packs, SP2 adds new functionality to Windows XP, including an enhanced firewall, improved Wi-Fi support, such as WPA encryption compatibility, with a wizard utility, a pop-up ad blocker for Internet Explorer 6, and Bluetooth support. Service Pack 2 also introduced a significantly faster kernel boot when the operating system loads. The new welcome screen during the kernel boot removes the subtitles "Professional", and "Home Edition" since Microsoft introduced new Windows XP editions prior to the release of SP2. The green loading bar in Home Edition was replaced with the standard blue bar, seen in Professional and in different version of Windows XP, making the line of operating systems resemble each other.
Service Pack 2 added new security enhancements include a major revision to the included firewall which was renamed to Windows Firewall and is enabled by default, advanced memory protection that takes advantage of the NX bit that is incorporated into newer processors to stop some forms of buffer overflow attacks, and removal of raw socket support (which supposedly limits the damage done by zombie machines). Additionally, security-related improvements were made to e-mail and web browsing. Windows XP Service Pack 2 includes the Windows Security Center, which provides a general overview of security on the system, including the state of anti-virus software, Windows Update, and the new Windows Firewall. Third-party anti-virus and firewall applications can interface with the new Security Center.[27]
On August 10, 2007, Microsoft announced a minor update to Service Pack 2, called Service Pack 2c (SP2c).[28] The update fixes the issue of the lowering number of available product keys for Windows XP. This update will be only available to system builders from their distributors in Windows XP Professional and Windows XP Professional N operating systems. SP2c was released in September 2007.[29]
[edit] Service Pack 3
This article or section contains information about computer software currently in development.The content may change as the software development progresses.
Microsoft has announced that it plans to release Windows XP Service Pack 3 (SP3) in the second half of April 2008.[30] A feature set overview has been posted by Microsoft[31] and details new features available separately as standalone updates to Windows XP, as well as features backported from Windows Vista, such as black hole router detection, Network Access Protection and Windows Imaging Component.
According to a file released with the early beta version and relayed onto the Internet there are a total of 1,073 fixes in SP3.[32]
This update to Windows allows it to be installed without a product key, and be run until the end of the 30-day activation period without a product key.
On December 4, 2007, Microsoft released build 3264 of a release candidate of SP3 to both TechNet and MSDN Subscribers. On December 18, 2007, this version was made publicly available via Microsoft Download Center.[33] The following release of SP3 was Release Candidate 2, which was released to the private beta-testing group through its connect website on February 6, 2008, with a build number of 3300. On February 19, 2008 build number 3311 of SP3 Release Candidate 2 was released for public beta testing.[34] In order to be able to download and install SP3 Release Candidate 2 via Windows Update or Microsoft Update, a script must be installed and any earlier version of SP3 must first be removed.[35] SP3 Release Candidate 2 can also be downloaded by way of the Microsoft Download Center.[36] Build 5503 of SP3 was a private release that was leaked on March 12, 2008.[37][38] On March 24, 2008, Microsoft publicly released SP3 RC2 Refresh (build 5508), with only minor updates from the previous public release, build 3311.[39][40]
Microsoft noted SP3 will update both Internet Explorer 6 and version 7 independently, and not require migrating to the next version.[41]
[edit] Support lifecycle
Support for Windows XP without a service pack (RTM) ended on September 30, 2004[42] and support for Windows XP Service Pack 1 and 1a ended on October 10, 2006.[43][44]
Mainstream support for Windows XP Service Pack 2 will end on April 14, 2009, four years after its general availability.[45] As per Microsoft's posted timetable, the company will stop licensing Windows XP to OEMs and terminate retail sales of the operating system June 30, 2008, 17 months after the release of Windows Vista.[46]
On April 14, 2009, Windows XP will begin its "Extended Support" period that will last for 5 years until April 8, 2014.[47]
[edit] Common criticisms
This article needs additional citations for verification.Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (August 2007)
Main article: Criticism of Windows XP
[edit] Security issues
Windows XP has been criticized for its susceptibility to malware, viruses, trojan horses, and worms. Security issues are compounded by the fact that users of the Home edition, by default, receive an administrator account that provides unrestricted access to the underpinnings of the system. If the administrator's account is broken into, there is no limit to the control that can be asserted over the compromised PC.
Windows, with its large market share, has historically been a tempting target for virus creators. Security holes are often invisible until they are exploited, making preemptive action difficult. Microsoft has stated that the release of patches to fix security holes is often what causes the spread of exploits against those very same holes, as crackers figured out what problems the patches fixed, and then launch attacks against unpatched systems. Microsoft recommends that all systems have automatic updates turned on to prevent a system from being attacked by an unpatched bug, but some business IT departments need to test updates before deployment across systems to predict compatibility issues with custom software and infrastructure. This deployment turn-around time also lengthens the time that systems are left unsecure in the event of a released software exploit.
[edit] User interface and performance
Critics have claimed that the default Windows XP user interface (Luna) adds visual clutter and wastes screen space while offering no new functionality and running more slowly. Users can easily switch back to the Windows Classic theme.[48]
[edit] Integration of operating system features
In light of the United States v. Microsoft case which resulted in Microsoft being convicted for abusing its operating system monopoly to overwhelm competition in other markets, Windows XP has drawn fire for integrating user applications such as Windows Media Player and Windows Messenger into the operating system, as well as for its close ties to the Windows Live ID service.
[edit] Backward compatibility
Some users switching from Windows 9x to XP disliked its lack of DOS support. Although XP comes with the ability to run DOS programs in a virtual DOS machine along with the COMMAND.COM program from MS-DOS, XP still has trouble running many old DOS programs. This is largely due to the fact that it is NT-based and does not use DOS as a base OS.
[edit] Product activation and verification
[edit] Windows Genuine Advantage
Main article: Windows Genuine Advantage
A Windows Genuine Advantage notification indicating a failed validation.
While product activation and licensing servers are common for business and industrial software, Windows XP gave many casual computer users their first introduction to it, under the name "Windows Genuine Advantage" (WGA). The system was introduced by Microsoft to curb unauthorized distribution of Windows XP. Activation requires the computer or the user to activate with Microsoft within a certain amount of time in order to continue using the operating system. If the user's computer system ever changes — for example, if two or more relevant components of the computer itself are upgraded — Windows may refuse to run until the user reactivates with Microsoft.
WGA comprises two parts, an activation/verification system based in part upon the computer's hardware, and a user notification system. WGA for Windows was followed by verification systems for Internet Explorer 7, Windows Media Player 11, Windows Defender, and Microsoft Office 2007. Recently Microsoft removed the WGA verification from the installer for Internet Explorer 7 saying that the purpose of the change was to make IE7 available to all Windows users.[49][50]
If the license key is judged not genuine, it displays a nag screen at regular intervals asking the user to buy a license from Microsoft.[51] In addition, the user's access to Microsoft Update is restricted to critical security updates, and as such, new versions of enhancements and other Microsoft products will no longer be able to be downloaded or installed.
Common criticisms of WGA have included its description as a "Critical Security Update", causing Automatic Updates to download it without user intervention, its behavior compared to spyware of "phoning home" to Microsoft every time the computer is connected to the Internet, the failure to inform end users what exactly WGA would do once installed (rectified by a 2006 update[52]), the failure to provide a proper uninstallation method during beta testing (users were given manual removal instructions that did not work with the final build[51]), and its sensitivity to hardware changes which cause repeated need for reactivation in the hands of some developers.
Strictly speaking, neither the download nor the install of the Notifications is mandatory; the user can change their Automatic Update settings to allow them to choose what updates may be downloaded for installation. If the update is already downloaded, the user can choose not to accept the supplemental EULA provided for the Notifications. In both cases, the user can also request that the update not be presented again. Newer Critical Security Updates may still be installed with the update hidden. However this setting will only have effect on the existing version of Notifications, so it can appear again as a new version.
As of 2006, Microsoft is currently involved in a class action lawsuit brought forth in California, on grounds that it violated the spyware laws in the state with its Windows Genuine Advantage Notifications program.[53]
[edit] Product key testing
In addition to activation, Windows XP service packs will refuse to install on Windows XP systems with product keys known to be widely used in unauthorized installations. These product keys are intended to be unique to each boxed (or bundled) copy of Windows XP and are included with the product documentation, but a number of product keys were posted on the Internet and were then used for a large number of unauthorized installations. The service packs contain a list of these keys and will not update copies of Windows XP that use them.
Microsoft developed a new key verification engine for Windows XP Service Pack 2 that could detect illicit keys, even those that had never been used before. After an outcry from security consultants who feared that denying security updates to illegal installations of Windows XP would have wide-ranging consequences even for legal owners, Microsoft elected to disable the new key verification engine. Service Pack 2 only checks for the same small list of commonly used keys as Service Pack 1. This means that while Service Pack 2 will not install on copies of Windows XP which use the older set of copied keys, those who use keys which have been posted more recently may be able to update their systems.
Currently Microsoft provides security updates to Windows XP without validating if it is legal. For all non-security updates, a user must have a verified copy of Windows.
[edit] Protection 'cracking'
"Key generator" programs, commonly called "keygens", exist to randomly generate Windows XP product keys (thus, there are no longer any commonly used keys to block) and then activate Windows without contacting Microsoft. These may or may not allow the user to receive updates although Microsoft has allowed major security updates to be downloaded and applied through Windows Update and its downloads site, even in pirated or non-genuine copies of Windows.[54] In addition, a range of cracks and cracked versions of WGA exist, enabling a computer running a non-genuine copy of Windows to be detected as a genuine Windows system and access all appropriate Microsoft updates and enhancements.
[edit] License and media types
There are three main types of Windows XP licenses: Retail, Volume (VLK), and Original Equipment Manufacturer (OEM).
Each type of license has a different installation CD. For customized or retail media, there is a very tiny difference on each type of disc that will only allow that installation disc to accept one type of product key.
Only retail and volume licenses include support for end-user installation scenarios from Microsoft. OEM software is pre-installed on systems and is supported by the system manufacturer rather than Microsoft. The price of such software is reduced to aid computer manufacturers in reducing costs of their computer system production. The cost of OEM software products bundled with systems is not disclosed by Microsoft or by its partners as each system manufacturer will define its own bundling price. Microsoft does not support OEM licenses because it cannot guarantee compatibility with every system configuration possible and it is the responsibility of each system manufacturer to ensure that its hardware is compatible.
Microsoft recommends that system manufacturers have their systems tested, for a fee, as part of the Windows Quality Online Services (Winqual) which includes extensive testing so that no component will cause instability in the Windows operating system due to incompatibility with the Windows operating system or with other system components or their respective drivers. Having a system tested and approved will allow the manufacturer to bear the "Certified for Windows" logo sticker on the exterior of the system, and there are additional benefits for having a tested product. This includes the product's being listed on the Windows Marketplace. Because of the fees and extensive requirements, Microsoft acknowledges that smaller system manufacturers may not opt in to the program until they produce computer systems at a modest rate and on recurring designs.
[edit] Retail
Retail licenses, those purchased from a retail store in full packaging, are of two sub-types: "Upgrade" and "Full Purchase Product", often abbreviated by Microsoft as FPP. FPP licenses are transferable from one computer to another, provided the previous installation is removed from the old computer. Although upgrade licenses are also transferable, a user must have a previous version of Windows even on the new computer to which they are moving the installation. Retail licenses include installation support for end-users, provided directly by Microsoft.
[edit] Volume License Agreement
A Volume License Agreement, sometimes referred to as a Volume License Key (or "VLK") license is the name given to the versions sold to businesses under a direct purchase agreement with Microsoft, and are sold as upgrade licenses only, meaning that a previous license must be available for each new VLK license. The name "Volume License Key" refers to the ability to use one product key for multiple systems, depending on the type of agreement. Until recently, Microsoft had not required that every VLK license be activated. This led to leaked copies of VLK media and product keys from businesses for the use of piracy and quickly spread across the internet upon early release. Beginning with Service Pack 1, Microsoft's active attempts to search out and blacklist known pirated VLK product keys became well known due to the inability to install the service pack on a system with one of the blacklisted keys. Later, this led into to the Windows Genuine Advantage program. There are numerous Volume License Agreement programs, but most include direct support options provided by Microsoft. Additional program add-ons, such as Software Assurance, also provide extended support options beyond the typical free-period software lifecycle.
[edit] Original Equipment Manufacturer (OEM)
Original Equipment Manufacturer (OEM) licenses are pre-installed on, and sold with, pre-assembled computers from system manufacturers. There are two types of OEM product types: those used for "Direct OEMs" (major name brands that buy through a direct contract with Microsoft and produce and brand their own media from a Microsoft "Gold Master Copy" by using an Authorized Microsoft Duplication Partner), and those used for "System Builders" (local computer shops that buy generic, unbranded kits through Authorized Microsoft Distributors). Direct OEM product keys will often not activate with System Builder installation media because Direct OEMs are now required by Microsoft to pre-activate their copies in the factory using their own internal mechanism before delivery to the customer. It is recommended that System Builders also pre-activate their systems before delivery, but this is not mandatory.
OEM installations can be customized using the Microsoft OEM Preinstallation Kit with branding, logos, additional applications, optional services, alternate applications for certain Windows components, Internet Explorer links, and various other customizations. All OEM customers must include support and contact information for the initial installation of Windows because it is the responsibility for the OEM to support the Windows installation, and is not provided by Microsoft to the end-user. Direct OEMs must create their own media, but have the option of creating their own custom recovery solution, which may or may not be similar to a generic installation. OEMs may provide a recovery partition on the hard drive as the custom recovery solution rather than providing disc-based media with the computer.
Some end-users have found this to be a troublesome option, because in the event of an out-of-warranty hard drive failure, they may not have access to reinstall Windows on a new hard drive. System Builders are not allowed the option to create a custom recovery CD/DVD media. The only deliverable media available for a System Builder to give to the end-user is the unbranded OEM System Builder hologram media kit. Because of this, when end-users reformat their hard drives and re-install from the installation media, they lose all the custom branding and support information that the System Builder would have included.
As a supplemental recovery method to a CD/DVD-based installation, a System Builder may employ a fully customized recovery solution on the hard drive. Whether utilizing a recovery partition or not, a System Builder must still include the original generic OEM System Builder hologram CD/DVD media kit. OEM licenses are not transferable from one computer to another. Every computer sold/resold with an OEM license must include all of the original installation media or recovery solution, documentation, Certificate of Authenticity, and product key sticker with the sale. Microsoft requires that all OEM system manufacturers include as part of the configuration the Windows Out-of-Box Experience (OOBE), which is the initial setup wizard encountered the first time Windows boots-up. It is also required that Value-Added Resellers (VAR's), retailers, and general resellers not tamper with the OEM's customized OOBE mechanism unless under permission by the OEM, and it is a recommended configuration for systems that are privately resold so that a customer will have a like-new computer experience upon first boot-up.
OEM licenses are to be installed by professional system manufacturers only. Under Microsoft's OEM License Agreement, they are not to be sold to end-users under any circumstance, and are to be pre-installed on a computer using the OEM Preinstallation Kit (OPK) before shipment to the customer, and must include at the very least the manufacturer's support contact information. They are therefore designed for installation only on a single computer and are not transferable, even if the original computer is no longer in use. This is not usually an issue for users who purchase new computer systems because most pre-assembled systems ship with a pre-installed operating system. There are few circumstances where Microsoft will allow the transfer of an OEM license from one non-functioning system to another, but the OEM System Builder License Agreement (SBLA), as well as the OEM End User License Agreement (EULA) do not contain any allowance for this, so it is entirely up to Microsoft's discretion, depending on the situation
Microsoft occasionally releases service packs for its Windows operating systems to fix problems and add features. Each service pack is a superset of all previous service packs and patches so that only the latest service pack needs to be installed, and also includes new revisions.[23] Older patches need not be removed before application of the most recent one.
[edit] Service Pack 1
Set Program Access and Defaults was added in Service Pack 1.
Service Pack 1 (SP1) for Windows XP was released on September 9, 2002. It contains post-RTM security fixes and hot-fixes, compatibility updates, optional .NET Framework support, enabling technologies for new devices such as Tablet PCs, and a new Windows Messenger 4.7 version. The most notable new features were USB 2.0 support, and a Set Program Access and Defaults utility that aimed at hiding various middleware products. Users can control the default application for activities such as web browsing and instant messaging, as well as hide access to some of Microsoft's bundled programs. This utility was first brought into the older Windows 2000 operating system with its Service Pack 3. The Microsoft Java Virtual Machine, which was not in the RTM version, appeared in this service pack.[24]
On February 3, 2003, Microsoft released Service Pack 1a (SP1a). This release removed Microsoft's Java virtual machine as a result of a lawsuit with Sun Microsystems. [25]
[edit] Service Pack 2
Windows Security Center was added in Service Pack 2.
Service Pack 2 (SP2) (codenamed "Springboard") was released on August 6, 2004 after several delays, with a special emphasis on security.[26] Unlike the previous service packs, SP2 adds new functionality to Windows XP, including an enhanced firewall, improved Wi-Fi support, such as WPA encryption compatibility, with a wizard utility, a pop-up ad blocker for Internet Explorer 6, and Bluetooth support. Service Pack 2 also introduced a significantly faster kernel boot when the operating system loads. The new welcome screen during the kernel boot removes the subtitles "Professional", and "Home Edition" since Microsoft introduced new Windows XP editions prior to the release of SP2. The green loading bar in Home Edition was replaced with the standard blue bar, seen in Professional and in different version of Windows XP, making the line of operating systems resemble each other.
Service Pack 2 added new security enhancements include a major revision to the included firewall which was renamed to Windows Firewall and is enabled by default, advanced memory protection that takes advantage of the NX bit that is incorporated into newer processors to stop some forms of buffer overflow attacks, and removal of raw socket support (which supposedly limits the damage done by zombie machines). Additionally, security-related improvements were made to e-mail and web browsing. Windows XP Service Pack 2 includes the Windows Security Center, which provides a general overview of security on the system, including the state of anti-virus software, Windows Update, and the new Windows Firewall. Third-party anti-virus and firewall applications can interface with the new Security Center.[27]
On August 10, 2007, Microsoft announced a minor update to Service Pack 2, called Service Pack 2c (SP2c).[28] The update fixes the issue of the lowering number of available product keys for Windows XP. This update will be only available to system builders from their distributors in Windows XP Professional and Windows XP Professional N operating systems. SP2c was released in September 2007.[29]
[edit] Service Pack 3
This article or section contains information about computer software currently in development.The content may change as the software development progresses.
Microsoft has announced that it plans to release Windows XP Service Pack 3 (SP3) in the second half of April 2008.[30] A feature set overview has been posted by Microsoft[31] and details new features available separately as standalone updates to Windows XP, as well as features backported from Windows Vista, such as black hole router detection, Network Access Protection and Windows Imaging Component.
According to a file released with the early beta version and relayed onto the Internet there are a total of 1,073 fixes in SP3.[32]
This update to Windows allows it to be installed without a product key, and be run until the end of the 30-day activation period without a product key.
On December 4, 2007, Microsoft released build 3264 of a release candidate of SP3 to both TechNet and MSDN Subscribers. On December 18, 2007, this version was made publicly available via Microsoft Download Center.[33] The following release of SP3 was Release Candidate 2, which was released to the private beta-testing group through its connect website on February 6, 2008, with a build number of 3300. On February 19, 2008 build number 3311 of SP3 Release Candidate 2 was released for public beta testing.[34] In order to be able to download and install SP3 Release Candidate 2 via Windows Update or Microsoft Update, a script must be installed and any earlier version of SP3 must first be removed.[35] SP3 Release Candidate 2 can also be downloaded by way of the Microsoft Download Center.[36] Build 5503 of SP3 was a private release that was leaked on March 12, 2008.[37][38] On March 24, 2008, Microsoft publicly released SP3 RC2 Refresh (build 5508), with only minor updates from the previous public release, build 3311.[39][40]
Microsoft noted SP3 will update both Internet Explorer 6 and version 7 independently, and not require migrating to the next version.[41]
[edit] Support lifecycle
Support for Windows XP without a service pack (RTM) ended on September 30, 2004[42] and support for Windows XP Service Pack 1 and 1a ended on October 10, 2006.[43][44]
Mainstream support for Windows XP Service Pack 2 will end on April 14, 2009, four years after its general availability.[45] As per Microsoft's posted timetable, the company will stop licensing Windows XP to OEMs and terminate retail sales of the operating system June 30, 2008, 17 months after the release of Windows Vista.[46]
On April 14, 2009, Windows XP will begin its "Extended Support" period that will last for 5 years until April 8, 2014.[47]
[edit] Common criticisms
This article needs additional citations for verification.Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (August 2007)
Main article: Criticism of Windows XP
[edit] Security issues
Windows XP has been criticized for its susceptibility to malware, viruses, trojan horses, and worms. Security issues are compounded by the fact that users of the Home edition, by default, receive an administrator account that provides unrestricted access to the underpinnings of the system. If the administrator's account is broken into, there is no limit to the control that can be asserted over the compromised PC.
Windows, with its large market share, has historically been a tempting target for virus creators. Security holes are often invisible until they are exploited, making preemptive action difficult. Microsoft has stated that the release of patches to fix security holes is often what causes the spread of exploits against those very same holes, as crackers figured out what problems the patches fixed, and then launch attacks against unpatched systems. Microsoft recommends that all systems have automatic updates turned on to prevent a system from being attacked by an unpatched bug, but some business IT departments need to test updates before deployment across systems to predict compatibility issues with custom software and infrastructure. This deployment turn-around time also lengthens the time that systems are left unsecure in the event of a released software exploit.
[edit] User interface and performance
Critics have claimed that the default Windows XP user interface (Luna) adds visual clutter and wastes screen space while offering no new functionality and running more slowly. Users can easily switch back to the Windows Classic theme.[48]
[edit] Integration of operating system features
In light of the United States v. Microsoft case which resulted in Microsoft being convicted for abusing its operating system monopoly to overwhelm competition in other markets, Windows XP has drawn fire for integrating user applications such as Windows Media Player and Windows Messenger into the operating system, as well as for its close ties to the Windows Live ID service.
[edit] Backward compatibility
Some users switching from Windows 9x to XP disliked its lack of DOS support. Although XP comes with the ability to run DOS programs in a virtual DOS machine along with the COMMAND.COM program from MS-DOS, XP still has trouble running many old DOS programs. This is largely due to the fact that it is NT-based and does not use DOS as a base OS.
[edit] Product activation and verification
[edit] Windows Genuine Advantage
Main article: Windows Genuine Advantage
A Windows Genuine Advantage notification indicating a failed validation.
While product activation and licensing servers are common for business and industrial software, Windows XP gave many casual computer users their first introduction to it, under the name "Windows Genuine Advantage" (WGA). The system was introduced by Microsoft to curb unauthorized distribution of Windows XP. Activation requires the computer or the user to activate with Microsoft within a certain amount of time in order to continue using the operating system. If the user's computer system ever changes — for example, if two or more relevant components of the computer itself are upgraded — Windows may refuse to run until the user reactivates with Microsoft.
WGA comprises two parts, an activation/verification system based in part upon the computer's hardware, and a user notification system. WGA for Windows was followed by verification systems for Internet Explorer 7, Windows Media Player 11, Windows Defender, and Microsoft Office 2007. Recently Microsoft removed the WGA verification from the installer for Internet Explorer 7 saying that the purpose of the change was to make IE7 available to all Windows users.[49][50]
If the license key is judged not genuine, it displays a nag screen at regular intervals asking the user to buy a license from Microsoft.[51] In addition, the user's access to Microsoft Update is restricted to critical security updates, and as such, new versions of enhancements and other Microsoft products will no longer be able to be downloaded or installed.
Common criticisms of WGA have included its description as a "Critical Security Update", causing Automatic Updates to download it without user intervention, its behavior compared to spyware of "phoning home" to Microsoft every time the computer is connected to the Internet, the failure to inform end users what exactly WGA would do once installed (rectified by a 2006 update[52]), the failure to provide a proper uninstallation method during beta testing (users were given manual removal instructions that did not work with the final build[51]), and its sensitivity to hardware changes which cause repeated need for reactivation in the hands of some developers.
Strictly speaking, neither the download nor the install of the Notifications is mandatory; the user can change their Automatic Update settings to allow them to choose what updates may be downloaded for installation. If the update is already downloaded, the user can choose not to accept the supplemental EULA provided for the Notifications. In both cases, the user can also request that the update not be presented again. Newer Critical Security Updates may still be installed with the update hidden. However this setting will only have effect on the existing version of Notifications, so it can appear again as a new version.
As of 2006, Microsoft is currently involved in a class action lawsuit brought forth in California, on grounds that it violated the spyware laws in the state with its Windows Genuine Advantage Notifications program.[53]
[edit] Product key testing
In addition to activation, Windows XP service packs will refuse to install on Windows XP systems with product keys known to be widely used in unauthorized installations. These product keys are intended to be unique to each boxed (or bundled) copy of Windows XP and are included with the product documentation, but a number of product keys were posted on the Internet and were then used for a large number of unauthorized installations. The service packs contain a list of these keys and will not update copies of Windows XP that use them.
Microsoft developed a new key verification engine for Windows XP Service Pack 2 that could detect illicit keys, even those that had never been used before. After an outcry from security consultants who feared that denying security updates to illegal installations of Windows XP would have wide-ranging consequences even for legal owners, Microsoft elected to disable the new key verification engine. Service Pack 2 only checks for the same small list of commonly used keys as Service Pack 1. This means that while Service Pack 2 will not install on copies of Windows XP which use the older set of copied keys, those who use keys which have been posted more recently may be able to update their systems.
Currently Microsoft provides security updates to Windows XP without validating if it is legal. For all non-security updates, a user must have a verified copy of Windows.
[edit] Protection 'cracking'
"Key generator" programs, commonly called "keygens", exist to randomly generate Windows XP product keys (thus, there are no longer any commonly used keys to block) and then activate Windows without contacting Microsoft. These may or may not allow the user to receive updates although Microsoft has allowed major security updates to be downloaded and applied through Windows Update and its downloads site, even in pirated or non-genuine copies of Windows.[54] In addition, a range of cracks and cracked versions of WGA exist, enabling a computer running a non-genuine copy of Windows to be detected as a genuine Windows system and access all appropriate Microsoft updates and enhancements.
[edit] License and media types
There are three main types of Windows XP licenses: Retail, Volume (VLK), and Original Equipment Manufacturer (OEM).
Each type of license has a different installation CD. For customized or retail media, there is a very tiny difference on each type of disc that will only allow that installation disc to accept one type of product key.
Only retail and volume licenses include support for end-user installation scenarios from Microsoft. OEM software is pre-installed on systems and is supported by the system manufacturer rather than Microsoft. The price of such software is reduced to aid computer manufacturers in reducing costs of their computer system production. The cost of OEM software products bundled with systems is not disclosed by Microsoft or by its partners as each system manufacturer will define its own bundling price. Microsoft does not support OEM licenses because it cannot guarantee compatibility with every system configuration possible and it is the responsibility of each system manufacturer to ensure that its hardware is compatible.
Microsoft recommends that system manufacturers have their systems tested, for a fee, as part of the Windows Quality Online Services (Winqual) which includes extensive testing so that no component will cause instability in the Windows operating system due to incompatibility with the Windows operating system or with other system components or their respective drivers. Having a system tested and approved will allow the manufacturer to bear the "Certified for Windows" logo sticker on the exterior of the system, and there are additional benefits for having a tested product. This includes the product's being listed on the Windows Marketplace. Because of the fees and extensive requirements, Microsoft acknowledges that smaller system manufacturers may not opt in to the program until they produce computer systems at a modest rate and on recurring designs.
[edit] Retail
Retail licenses, those purchased from a retail store in full packaging, are of two sub-types: "Upgrade" and "Full Purchase Product", often abbreviated by Microsoft as FPP. FPP licenses are transferable from one computer to another, provided the previous installation is removed from the old computer. Although upgrade licenses are also transferable, a user must have a previous version of Windows even on the new computer to which they are moving the installation. Retail licenses include installation support for end-users, provided directly by Microsoft.
[edit] Volume License Agreement
A Volume License Agreement, sometimes referred to as a Volume License Key (or "VLK") license is the name given to the versions sold to businesses under a direct purchase agreement with Microsoft, and are sold as upgrade licenses only, meaning that a previous license must be available for each new VLK license. The name "Volume License Key" refers to the ability to use one product key for multiple systems, depending on the type of agreement. Until recently, Microsoft had not required that every VLK license be activated. This led to leaked copies of VLK media and product keys from businesses for the use of piracy and quickly spread across the internet upon early release. Beginning with Service Pack 1, Microsoft's active attempts to search out and blacklist known pirated VLK product keys became well known due to the inability to install the service pack on a system with one of the blacklisted keys. Later, this led into to the Windows Genuine Advantage program. There are numerous Volume License Agreement programs, but most include direct support options provided by Microsoft. Additional program add-ons, such as Software Assurance, also provide extended support options beyond the typical free-period software lifecycle.
[edit] Original Equipment Manufacturer (OEM)
Original Equipment Manufacturer (OEM) licenses are pre-installed on, and sold with, pre-assembled computers from system manufacturers. There are two types of OEM product types: those used for "Direct OEMs" (major name brands that buy through a direct contract with Microsoft and produce and brand their own media from a Microsoft "Gold Master Copy" by using an Authorized Microsoft Duplication Partner), and those used for "System Builders" (local computer shops that buy generic, unbranded kits through Authorized Microsoft Distributors). Direct OEM product keys will often not activate with System Builder installation media because Direct OEMs are now required by Microsoft to pre-activate their copies in the factory using their own internal mechanism before delivery to the customer. It is recommended that System Builders also pre-activate their systems before delivery, but this is not mandatory.
OEM installations can be customized using the Microsoft OEM Preinstallation Kit with branding, logos, additional applications, optional services, alternate applications for certain Windows components, Internet Explorer links, and various other customizations. All OEM customers must include support and contact information for the initial installation of Windows because it is the responsibility for the OEM to support the Windows installation, and is not provided by Microsoft to the end-user. Direct OEMs must create their own media, but have the option of creating their own custom recovery solution, which may or may not be similar to a generic installation. OEMs may provide a recovery partition on the hard drive as the custom recovery solution rather than providing disc-based media with the computer.
Some end-users have found this to be a troublesome option, because in the event of an out-of-warranty hard drive failure, they may not have access to reinstall Windows on a new hard drive. System Builders are not allowed the option to create a custom recovery CD/DVD media. The only deliverable media available for a System Builder to give to the end-user is the unbranded OEM System Builder hologram media kit. Because of this, when end-users reformat their hard drives and re-install from the installation media, they lose all the custom branding and support information that the System Builder would have included.
As a supplemental recovery method to a CD/DVD-based installation, a System Builder may employ a fully customized recovery solution on the hard drive. Whether utilizing a recovery partition or not, a System Builder must still include the original generic OEM System Builder hologram CD/DVD media kit. OEM licenses are not transferable from one computer to another. Every computer sold/resold with an OEM license must include all of the original installation media or recovery solution, documentation, Certificate of Authenticity, and product key sticker with the sale. Microsoft requires that all OEM system manufacturers include as part of the configuration the Windows Out-of-Box Experience (OOBE), which is the initial setup wizard encountered the first time Windows boots-up. It is also required that Value-Added Resellers (VAR's), retailers, and general resellers not tamper with the OEM's customized OOBE mechanism unless under permission by the OEM, and it is a recommended configuration for systems that are privately resold so that a customer will have a like-new computer experience upon first boot-up.
OEM licenses are to be installed by professional system manufacturers only. Under Microsoft's OEM License Agreement, they are not to be sold to end-users under any circumstance, and are to be pre-installed on a computer using the OEM Preinstallation Kit (OPK) before shipment to the customer, and must include at the very least the manufacturer's support contact information. They are therefore designed for installation only on a single computer and are not transferable, even if the original computer is no longer in use. This is not usually an issue for users who purchase new computer systems because most pre-assembled systems ship with a pre-installed operating system. There are few circumstances where Microsoft will allow the transfer of an OEM license from one non-functioning system to another, but the OEM System Builder License Agreement (SBLA), as well as the OEM End User License Agreement (EULA) do not contain any allowance for this, so it is entirely up to Microsoft's discretion, depending on the situation