FW: ::NEWSBANK:: MS10-046 released out of band, CRITICAL update

-------------------------------------------
寄件者: David Perry (MKT-US)
傳送日期: Tuesday, August 03, 2010 1:52:46 AM
收件者: Newsbank
主旨: ::NEWSBANK:: MS10-046 released out of band, CRITICAL update
自動依照規則轉寄

Microsoft Security Bulletin MS10-046 - Critical

Vulnerability in Windows Shell Could Allow Remote Code Execution (2286198)

Published: August 02, 2010

Version: 1.0

General Information

Executive Summary

This security update resolves a publicly disclosed vulnerability in Windows Shell. The vulnerability could allow remote code execution if the icon of a specially crafted shortcut is displayed. An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Critical for all supported editions of Microsoft Windows. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by correcting validation of shortcut icon references. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

This security update addresses the vulnerability first described in Microsoft Security Advisory 2286198.

Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. None

Top of section

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

Operating System	Maximum Security Impact	Aggregate Severity Rating	Bulletins Replaced by this Update
Windows XP Service Pack 3	Remote Code execution	Critical	None
Windows XP Professional x64 Edition Service Pack 2	Remote Code execution	Critical	None
Windows Server 2003 Service Pack 2	Remote Code execution	Critical	None
Windows Server 2003 x64 Edition Service Pack 2	Remote Code execution	Critical	None
Windows Server 2003 with SP2 for Itanium-based Systems	Remote Code execution	Critical	None
Windows Vista Service Pack 1 and Windows Vista Service Pack 2	Remote Code execution	Critical	None
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2	Remote Code execution	Critical	None
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*	Remote Code execution	Critical	None
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*	Remote Code execution	Critical	None
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2	Remote Code execution	Critical	None
Windows 7 for 32-bit Systems	Remote Code execution	Critical	None
Windows 7 for x64-based Systems	Remote Code execution	Critical	None
Windows Server 2008 R2 for x64-based Systems*	Remote Code execution	Critical	None
Windows Server 2008 R2 for Itanium-based Systems	Remote Code execution	Critical	None

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

Top of section

Frequently Asked Questions (FAQ) Related to This Security Update

Where are the file information details? 
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

How are the Windows 7 Service Pack 1 Beta and Windows Server 2008 R2 Service Pack 1 Beta releases affected by this vulnerability? 
Windows 7 Service Pack 1 Beta and Windows Server 2008 R2 Service Pack 1 Beta are affected by the vulnerability described in this bulletin. Customers running these beta releases are encouraged to download and apply the update to their systems. Security updates are available from Microsoft Update and Windows Update. The security update is also available for download from the Microsoft Download Center.

I am using an older release of the software discussed in this security bulletin. What should I do? 
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.

Top of section

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the August bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software	Shortcut Icon Loading Vulnerability - CVE-2010-2568	Aggregate Severity Rating
Windows XP Service Pack 3	Critical  Remote Code Execution	Critical
Windows XP Professional x64 Edition Service Pack 2	Critical  Remote Code Execution	Critical
Windows Server 2003 Service Pack 2	Critical  Remote Code Execution	Critical
Windows Server 2003 x64 Edition Service Pack 2	Critical  Remote Code Execution	Critical
Windows Server 2003 with SP2 for Itanium-based Systems	Critical  Remote Code Execution	Critical
Windows Vista Service Pack 1 and Windows Vista Service Pack 2	Critical  Remote Code Execution	Critical
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2	Critical  Remote Code Execution	Critical
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*	Critical  Remote Code Execution	Critical
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*	Critical  Remote Code Execution	Critical
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2	Critical  Remote Code Execution	Critical
Windows 7 for 32-bit Systems	Critical  Remote Code Execution	Critical
Windows 7 for x64-based Systems	Critical  Remote Code Execution	Critical
Windows Server 2008 R2 for x64-based Systems*	Critical  Remote Code Execution	Critical
Windows Server 2008 R2 for Itanium-based Systems	Critical  Remote Code Execution	Critical

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

Top of section

Shortcut Icon Loading Vulnerability - CVE-2010-2568

A remote code execution vulnerability exists in affected versions of Microsoft Windows. The vulnerability exists because Windows incorrectly parses shortcuts in such a way that malicious code may be executed when the operating system displays the icon of a malicious shortcut file. An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. This update addresses a vulnerability previously discussed in Microsoft Security Advisory 2286198.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-2568.

Mitigating Factors for Shortcut Icon Loading Vulnerability - CVE-2010-2568

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

•	An attacker who successfully exploits this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
•	For the USB removable device attack vector, when AutoPlay is disabled, the user would manually have to launch Windows Explorer or a similar application and browse to the affected folder of the removable disk.

Top of section

Workarounds for Shortcut Icon Loading Vulnerability - CVE-2010-2568

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

•

Disable the displaying of icons for shortcuts Note See Microsoft Knowledge Base Article 2286198 to use the automated Microsoft Fix it solution to enable or disable this workaround. This Fix it solution requires a restart upon completion in order to be effective. This Fix it solution deploys the workaround, and thus has the same user impact. We recommend that administrators review the KB article closely prior to deploying this Fix it solution. Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. 1. Click Start, click Run, type Regedit in the Open box, and then click OK. 2. Locate and then select the following registry key: HKEY_CLASSES_ROOT\lnkfile\shellex\IconHandler 3. Click the File menu and then click Export. 4. In the Export Registry File dialog box, enter LNK_Icon_Backup.reg and then click Save. Note This will create a backup of this registry key in the My Documents folder by default. 5. Select the value (Default) on the right pane in the Registry Editor. Press Enter to edit the value of the key. Delete the value, so that the value is blank, and press Enter. 6. Locate and then select the following registry key: HKEY_CLASSES_ROOT\piffile\shellex\IconHandler 7. Click the File menu and then click Export. 8. In the Export Registry File dialog box, enter PIF_Icon_Backup.reg and then click Save. Note This creates a backup of this registry key in the My Documents folder by default. 9. Select the value (Default) on the right pane in the Registry Editor. Press Enter to edit the value of the key. Delete the value, so that the value is blank, and press Enter. 10. Log all users off and on again, or restart the computer. Impact of workaround. Disabling icons from being displayed for shortcuts prevents the issue from being exploited on affected systems. When this workaround is implemented, the system may display most icons as a "white" default object icon, which does impact usability. We recommend that system administrators test this workaround thoroughly prior to deployment. When the workaround is undone, all icons will reappear. How to undo the workaround. Using the interactive method 1. Click Start, click Run, type Regedit in the Open box, and then click OK. 2. Click the File menu and then click Import. 3. In the Import Registry File dialog box, select LNK_Icon_Backup.reg, and then click Open. 4. Click the File menu and then click Import. 5. In the Import Registry File dialog box, select PIF_Icon_Backup.reg, and then click Open. 6. Exit Registry Editor, and then restart the computer. Manually resetting the Registry key values to the default values 1. Click Start, click Run, type Regedit in the Open box, and then click OK. 2. Locate and then click the following registry key: HKEY_CLASSES_ROOT\lnkfile\shellex\IconHandler 3. Reset the registry key value to: {00021401-0000-0000-C000-000000000046} 4. Locate and then click the following registry key: HKEY_CLASSES_ROOT\piffile\shellex\IconHandler 5. Reset the registry key value to: {00021401-0000-0000-C000-000000000046} 6. Restart the computer

 

•

Disable the WebClient service Disabling the WebClient service helps protect affected systems from attempts to exploit this vulnerability by blocking the most likely remote attack vector through the Web Distributed Authoring and Versioning (WebDAV) client service. After applying this workaround it is still possible for remote attackers who successfully exploit this vulnerability to cause Microsoft Office Outlook to run programs located on the targeted user's computer or the Local Area Network (LAN), but users will be prompted for confirmation before opening arbitrary programs from the Internet. To disable the WebClient Service, follow these steps: 1. Click Start, click Run, type Services.msc and then click OK. 2. Right-click WebClient service and select Properties. 3. Change the Startup type to Disabled. If the service is running, click Stop. 4. Click OK and exit the management application. Impact of workaround. When the WebClient service is disabled, Web Distributed Authoring and Versioning (WebDAV) requests are not transmitted. In addition, any services that explicitly depend on the Web Client service will not start, and an error message will be logged in the System log. For example, WebDAV shares will be inaccessible from the client computer. How to undo the workaround. To re-enable the WebClient Service, follow these steps: 1. Click Start, click Run, type Services.msc and then click OK. 2. Right-click WebClient service and select Properties. 3. Change the Startup type to Automatic. If the service is not running, click Start. 4. Click OK and exit the management application.

 

•	Block the download of LNK and PIF files from the Internet Blocking the download of LNK and PIF files on the Internet Gateway provides protection against remote exploitation of these attacks. Note that the files can be transferred over WebDAV, so any blocking solution should take this protocol into account.
•	Block outbound SMB connections on the perimeter firewall Blocking outbound SMB connections on the perimeter firewall reduces the risk of remote exploitation using file shares.

Top of section

FAQ for Shortcut Icon Loading Vulnerability - CVE-2010-2568

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? 
When attempting to load the icon of a shortcut, the Windows Shell does not correctly validate specific parameters of the shortcut.

What is the Windows Shell? 
The Windows user interface (UI) provides users with access to a wide variety of objects necessary for running applications and managing the operating system. The most numerous and familiar of these objects are the folders and files that reside on computer disk drives. There are also a number of virtual objects that allow the user to perform tasks such as sending files to remote printers or accessing the Recycle Bin. The Shell organizes these objects into a hierarchical namespace and provides users and applications with a consistent and efficient way to access and manage objects.

What is a shortcut? 
A shortcut is a link to a file or program, represented by an icon. If you double-click a shortcut, the file or program opens. The shortcut is a mechanism often used to keep frequently used files in a single, easily accessed location, such as a folder or the desktop. Shortcuts are implemented as files with the LNK extension. In addition, shortcuts can also appear as PIF files when they are related to MS-DOS programs.

Will this security update disable the workaround or Microsoft Fix it solution, if I have previously implemented it? 
No, the workaround and Microsoft Fix it solution operate independently from the security update. After the security update has been implemented, users who have applied the workaround need to undo it.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could present a removable drive to the user with a malicious shortcut file, and an associated malicious binary. When the user opens this drive in Windows Explorer, or any other application that parses the icon of the shortcut, the malicious binary will execute code of the attacker’s choice on the target system.

An attacker could also set up a malicious Web site or a remote network share and place the malicious components on this remote location. When the user browses the Web site using a Web browser such as Internet Explorer or a file manager such as Windows Explorer, Windows attempts to load the icon of the shortcut file, invoking the malicious binary. In addition, an attacker could embed an exploit in a document that supports embedded shortcuts or a hosted browser control (such as but not limited to Microsoft Office documents).

What systems are primarily at risk from the vulnerability? 
Desktop systems used to browse untrusted network shares or untrusted Web sites are most at risk from this vulnerability.

What does the update do? 
The update addresses this vulnerability by correctly validating the icon reference of a shortcut.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2010-2568.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
At the time this security bulletin was released, this vulnerability was being exploited by a number of malware families.

Top of section

Top of section

Update Information

Detection and Deployment Tools and Guidance

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Note Microsoft discontinued support for Office Update and the Office Update Inventory Tool as of August 1, 2009. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. For more information, see About Microsoft Office Update: Frequently Asked Questions.

Detection and Deployment Guidance

Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software	MBSA 2.1.1
Windows XP Service Pack 3	Yes
Windows XP Professional x64 Edition Service Pack 2	Yes
Windows Server 2003 Service Pack 2	Yes
Windows Server 2003 x64 Edition Service Pack 2	Yes
Windows Server 2003 with SP2 for Itanium-based Systems	Yes
Windows Vista Service Pack 1 and Windows Vista Service Pack 2	Yes
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2	Yes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2	Yes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2	Yes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2	Yes
Windows 7 for 32-bit Systems	Yes
Windows 7 for x64-based Systems	Yes
Windows Server 2008 R2 for x64-based Systems	Yes
Windows Server 2008 R2 for Itanium-based Systems	Yes

The latest version of MBSA has been released: Microsoft Baseline Security Analyzer 2.1.1. For more information, see Microsoft Baseline Security Analyzer 2.1.

Windows Server Update Services

Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy this security update using Windows Server Update Services, see the TechNet article, Windows Server Update Services.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

Software	SMS 2.0	SMS 2003 with SUIT	SMS 2003 with ITMU	Configuration Manager 2007
Windows XP Service Pack 3	Yes	Yes	Yes	Yes
Windows XP Professional x64 Edition Service Pack 2	No	No	Yes	Yes
Windows Server 2003 Service Pack 2	Yes	Yes	Yes	Yes
Windows Server 2003 x64 Edition Service Pack 2	No	No	Yes	Yes
Windows Server 2003 with SP2 for Itanium-based Systems	No	No	Yes	Yes
Windows Vista Service Pack 1 and Windows Vista Service Pack 2	No	No	Yes	Yes
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2	No	No	Yes	Yes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2	No	No	Yes	Yes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2	No	No	Yes	Yes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2	No	No	Yes	Yes
Windows 7 for 32-bit Systems	No	No	Yes	Yes
Windows 7 for x64-based Systems	No	No	Yes	Yes
Windows Server 2008 R2 for x64-based Systems	No	No	Yes	Yes
Windows Server 2008 R2 for Itanium-based Systems	No	No	Yes	Yes

For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Top of section

Security Update Deployment

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For Windows XP Service Pack 3: WindowsXP-KB2286198-x86-enu.exe /quiet
	For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2286198-x64-enu.exe /quiet
Installing without restarting	For Windows XP Service Pack 3: WindowsXP-KB2286198-x86-enu.exe /norestart
	For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2286198-x64-enu.exe /norestart
Update log file	KB2286198.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	Yes, you must restart your system after you apply this security update.
HotPatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2286198$\Spuninst folder
File Information	See Microsoft Knowledge Base Article 2286198
Registry Key Verification	For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2286198\Filelist
	For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2286198\Filelist

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options.
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed.
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Displays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoem	Overwrites OEM files without prompting.
/nobackup	Does not back up files needed for uninstall.
/forceappsclose	Forces other programs to close when the computer shuts down.
/log:path	Allows the redirection of installation log files.
/integrate:path	Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]	Extracts files without starting the Setup program.
/ER	Enables extended error reporting.
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/help	Displays the command-line options.
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Displays a dialog box prompting the local user to allow a restart.
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down.
/log:path	Allows the redirection of installation log files.

Verifying That the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

 

•

Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2286198-x86-enu.exe /quiet
	For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2286198-x64-enu.exe /quiet
	For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2286198-ia64-enu.exe /quiet
Installing without restarting	For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2286198-x86-enu.exe /norestart
	For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2286198-x64-enu.exe /norestart
	For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2286198-ia64-enu.exe /norestart
Update log file	KB2286198.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	Yes, you must restart your system after you apply this security update.
HotPatching	This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information	Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2286198$\Spuninst folder
File Information	See Microsoft Knowledge Base Article 2286198
Registry Key Verification	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2286198\Filelist

 

Deployment Information

Top of section

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options.
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed.
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Displays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoem	Overwrites OEM files without prompting.
/nobackup	Does not back up files needed for uninstall.
/forceappsclose	Forces other programs to close when the computer shuts down.
/log:path	Allows the redirection of installation log files.
/integrate:path	Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]	Extracts files without starting the Setup program.
/ER	Enables extended error reporting.
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/help	Displays the command-line options.
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed.
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Displays a dialog box prompting the local user to allow a restart.
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down.
/log:path	Allows the redirection of installation log files.

Verifying that the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

 

•

Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Windows Vista (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For all supported 32-bit editions of Windows Vista: Windows6.0-KB2286198-x86.msu /quiet
	For all supported x64-based editions of Windows Vista: Windows6.0-KB2286198-x64.msu /quiet
Installing without restarting	For all supported 32-bit editions of Windows Vista: Windows6.0-KB2286198-x86.msu /quiet /norestart
	For all supported x64-based editions of Windows Vista: Windows6.0-KB2286198-x64.msu /quiet /norestart
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	Yes, you must restart your system after you apply this security update.
HotPatching	Not applicable.
Removal Information	WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information	See Microsoft Knowledge Base Article 2286198
Registry Key Verification	Note A registry key does not exist to validate the presence of this update.

 

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/?, /h, /help	Displays help on supported switches.
/quiet	Suppresses the display of status or error messages.
/norestart	When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

Verifying That the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click Start and then enter an update file name in Start Search. 2. When the file appears under Programs, right-click on the file name and click Properties. 3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. 4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Top of section

Top of section

Windows Server 2008 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB2286198-x86.msu /quiet
	For all supported x64-based editions of Windows Server 2008: Windows6.0-KB2286198-x64.msu /quiet
	For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2286198-ia64.msu /quiet
Installing without restarting	For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB2286198-x86.msu /quiet /norestart
	For all supported x64-based editions of Windows Server 2008: Windows6.0-KB2286198-x64.msu /quiet /norestart
	For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2286198-ia64.msu /quiet /norestart
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	Yes, you must restart your system after you apply this security update.
HotPatching	Not applicable.
Removal Information	WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click System and Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information	See Microsoft Knowledge Base Article 2286198
Registry Key Verification	Note A registry key does not exist to validate the presence of this update.

 

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/?, /h, /help	Displays help on supported switches.
/quiet	Suppresses the display of status or error messages.
/norestart	When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

Verifying That the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click Start and then enter an update file name in Start Search. 2. When the file appears under Programs, right-click on the file name and click Properties. 3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. 4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Top of section

Top of section

Windows 7 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For all supported 32-bit editions of Windows 7: Windows6.1-KB2286198-x86.msu /quiet
	For all supported x64-based editions of Windows 7: Windows6.1-KB2286198-x64.msu /quiet
Installing without restarting	For all supported 32-bit editions of Windows 7: Windows6.1-KB2286198-x86.msu /quiet /norestart
	For all supported x64-based editions of Windows 7: Windows6.1-KB2286198-x64.msu /quiet /norestart
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	Yes, you must restart your system after you apply this security update.
HotPatching	Not applicable.
Removal Information	To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File Information	See Microsoft Knowledge Base Article 2286198
Registry Key Verification	Note A registry key does not exist to validate the presence of this update.

 

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/?, /h, /help	Displays help on supported switches.
/quiet	Suppresses the display of status or error messages.
/norestart	When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>	When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestart	When combined with /quiet, the installer will prompt before initiating restart.
/forcerestart	When combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>	Enables logging to specified file.
/extract:<destination>	Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>	Uninstalls the security update.

Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.

Verifying That the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click Start and then enter an update file name in Start Search. 2. When the file appears under Programs, right-click on the file name and click Properties. 3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. 4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Top of section

Top of section

Windows Server 2008 R2 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For all supported x64-based editions of Windows Server 2008 R2: Windows6.1-KB2286198-x64.msu /quiet
	For all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2286198-ia64.msu /quiet
Installing without restarting	For all supported x64-based editions of Windows Server 2008 R2: Windows6.1-KB2286198-x64.msu /quiet /norestart
	For all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2286198-ia64.msu /quiet /norestart
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	Yes, you must restart your system after you apply this security update.
HotPatching	Not applicable.
Removal Information	To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File Information	See Microsoft Knowledge Base Article 2286198
Registry Key Verification	Note A registry key does not exist to validate the presence of this update.

 

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/?, /h, /help	Displays help on supported switches.
/quiet	Suppresses the display of status or error messages.
/norestart	When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>	When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestart	When combined with /quiet, the installer will prompt before initiating restart.
/forcerestart	When combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>	Enables logging to specified file.
/extract:<destination>	Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>	Uninstalls the security update.

Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.

Verifying That the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click Start and then enter an update file name in Start Search. 2. When the file appears under Programs, right-click on the file name and click Properties. 3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. 4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Top of section

Top of section

Top of section

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

•	Sergey I. Ulasen and Uleg Kopreev of VirusBlokAda for reporting the Shortcut Icon Loading Vulnerability (CVE-2010-2568)
•	Andreas Marx and Maik Morgenstern of AV-Test for reporting the Shortcut Icon Loading Vulnerability (CVE-2010-2568)
•	Will Dormann of CERT/CC for working with us on the Shortcut Icon Loading Vulnerability (CVE-2010-2568)
•	Niels Teusink for working with us on the Shortcut Icon Loading Vulnerability (CVE-2010-2568)
•	Stefan Kanthak for working with us on the Shortcut Icon Loading Vulnerability (CVE-2010-2568)

Top of section

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Top of section

Support

•	Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY begin_of_the_skype_highlighting              1-866-PCSAFETY      end_of_the_skype_highlighting. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
•	International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Top of section

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Top of section

Revisions

•	V1.0 (August 2, 2010): Bulletin published.

Top of section

 

 

 

David Perry | Global Director of Education 10101 North De Anza - Cupertino, California 95014 USA Office: +1 (714) 846-5689 | Mobile: +1 (949) 500-2033