Security Bulletin
Microsoft Security Bulletin MS11-015 - Critical
Vulnerabilities in Windows Media Could Allow Remote Code Execution (2510030)
Published: March 08, 2011 | Updated: March 16, 2011
Version: 1.2
General Information
Executive Summary
This security update resolves one publicly disclosed vulnerability in DirectShow and one privately reported vulnerability in Windows Media Player and Windows Media Center. The more severe of these vulnerabilities could allow remote code execution if a user opens a specially crafted Microsoft Digital Video Recording (.dvr-ms) file. In all cases, a user cannot be forced to open the file; for an attack to be successful, a user must be convinced to do so.
This security update is rated Critical for affected editions of Windows XP (including Windows XP Media Center Edition 2005); all supported editions of Windows Vista and Windows 7; and Windows Media Center TV Pack for Windows Vista. This security update is also rated Important for all supported editions of Windows Server 2008 R2 for x64-based systems. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by modifying the way library files and Windows media files are opened. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
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
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
[1]See note [2] below about Windows Media Center TV Pack for Windows Vista.
**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when 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.
Affected Software
Other Software | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
---|---|---|---|
Windows Media Center TV Pack for Windows Vista (32-bit editions)[2]\ (KB2494132) | Remote Code Execution | Critical | None |
Windows Media Center TV Pack for Windows Vista (64-bit editions)[2]\ (KB2494132) | Remote Code Execution | Critical | None |
[2]Windows Media Center TV Pack for Windows Vista is available only on Original Equipment Manufacturer (OEM) installations of the Home Premium and Ultimate editions of Windows Vista as an optional component. Customers who have this optional component installed on their systems should install both available updates. In keeping with best practices, Microsoft recommends installing the operating system update (KB2479943) before installing the Windows Media Center TV Pack update (KB2494132).
Non-Affected Software
Operating System |
---|
Windows Server 2003 Service Pack 2 |
Windows Server 2003 x64 Edition Service Pack 2 |
Windows Server 2003 with SP2 for Itanium-based Systems |
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 |
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 |
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 |
Windows Server 2008 R2 for Itanium-based Systems |
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.
Is this update related to Microsoft Security Advisory 2269637?
Yes, one vulnerability addressed by this update is related to the class of vulnerabilities, described in Microsoft Security Advisory 2269637, that affects how applications load external libraries. This security update addresses a particular instance of this type of vulnerability.
What is the Windows Media Center TV Pack for Windows Vista?
Windows Media Center TV Pack for Windows Vista is available only on Original Equipment Manufacturer (OEM) installations of the Home Premium and Ultimate editions of Windows Vista as an optional component. Customers who have this optional component installed on their systems should install both available updates. In keeping with best practices, Microsoft recommends installing the operating system update (KB2479943) before installing the Windows Media Center TV Pack update (KB2494132).
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.
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.
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 March bulletin summary. For more information, see Microsoft Exploitability Index.
Affected Software | DirectShow Insecure Library Loading Vulnerability - CVE-2011-0032 | DVR-MS Vulnerability - CVE-2011-0042 | Aggregate Severity Rating |
---|---|---|---|
Windows XP Media Center Edition 2005 Service Pack 3 | Not applicable | Critical \ Remote Code Execution | Critical |
Windows XP Service Pack 3 | Not applicable | Critical \ Remote Code Execution | Critical |
Windows XP Professional x64 Edition Service Pack 2 | Not applicable | Critical \ Remote Code Execution | Critical |
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 | Important \ Remote Code Execution | Critical \ Remote Code Execution | Critical |
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 | Important \ Remote Code Execution | Critical \ Remote Code Execution | Critical |
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Important \ Remote Code Execution | Critical \ Remote Code Execution | Critical |
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Important \ Remote Code Execution | Critical \ Remote Code Execution | Critical |
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1** | Important \ Remote Code Execution | Not applicable | Important |
Windows Media Center TV Pack for Windows Vista, 32-bit editions | Important \ Remote Code Execution | Critical \ Remote Code Execution | Critical |
Windows Media Center TV Pack for Windows Vista, 64-bit editions | Important \ Remote Code Execution | Critical \ Remote Code Execution | Critical |
**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when 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.
DirectShow Insecure Library Loading Vulnerability - CVE-2011-0032
A remote code execution vulnerability exists in the way that Microsoft DirectShow handles the loading of DLL files. 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. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-0032.
Mitigating Factors for DirectShow Insecure Library Loading Vulnerability - CVE-2011-0032
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:
- For an attack to be successful, a user must visit an untrusted remote file system location or WebDAV share and open a media file (such as .wtv, .drv-ms, or .mpg files).
- The file sharing protocol, Server Message Block (SMB), is often disabled on the perimeter firewall. This limits the potential attack vectors for this vulnerability.
- 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.
Workarounds for DirectShow Insecure Library Loading Vulnerability - CVE-2011-0032
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 loading of libraries from WebDAV and remote network shares
Note See Microsoft Knowledge Base Article 2264107 to deploy a workaround tool that allows customers to disable the loading of libraries from remote network or WebDAV shares. This tool can be configured to disallow insecure loading on a per-application or a global system basis.Customers who are informed by their vendor of an application being vulnerable can use this tool to help protect against attempts to exploit this issue.
Note See Microsoft Knowledge Base Article 2264107 to use the automated Microsoft Fix it solution to deploy the registry key to block the loading of libraries for SMB and WebDAV shares. Note that this Fix it solution does require you to install the workaround tool also described in Microsoft Knowledge Base Article 2264107 first. This Fix it solution only deploys the registry key and requires the workaround tool in order to be effective. We recommend that administrators review the KB article closely prior to deploying this Fix it solution.
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 the system 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:
- Click Start, click Run, type Services.msc and then click OK.
- Right-click WebClient service and select Properties.
- Change the Startup type to Disabled. If the service is running, click Stop.
- 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:
- Click Start, click Run, type Services.msc and then click OK.
- Right-click WebClient service and select Properties.
- Change the Startup type to Automatic. If the service is not running, click Start.
- Click OK and exit the management application.
Block TCP ports 139 and 445 at the firewall
These ports are used to initiate a connection with the affected component. Blocking TCP ports 139 and 445 at the firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Microsoft recommends that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see the TechNet article, TCP and UDP Port Assignments.Impact of workaround. Several Windows services use the affected ports. Blocking connectivity to the ports may cause various applications or services to not function. Some of the applications or services that could be impacted are listed below:
- Applications that use SMB (CIFS)
- Applications that use mailslots or named pipes (RPC over SMB)
- Server (File and Print Sharing)
- Group Policy
- Net Logon
- Distributed File System (DFS)
- Terminal Server Licensing
- Print Spooler
- Computer Browser
- Remote Procedure Call Locator
- Fax Service
- Indexing Service
- Performance Logs and Alerts
- Systems Management Server
- License Logging Service
How to undo the workaround. Unblock TCP ports 139 and 445 at the firewall. For more information about ports, see TCP and UDP Port Assignments.
FAQ for DirectShow Insecure Library Loading Vulnerability - CVE-2011-0032
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?
The vulnerability is caused when Microsoft DirectShow incorrectly restricts the path used for loading external libraries.
What is DirectShow?
DirectShow is a DirectX low-level Application Programming Interface (API) used by Windows programs for multimedia support. Within DirectX, the DirectShow technology performs client-side audio and video sourcing, manipulation and rendering.
Microsoft DirectShow is used for streaming media on Microsoft Windows operating systems. DirectShow is used for high-quality capture and playback of multimedia streams. It automatically detects and uses video and audio acceleration hardware when available, but also supports systems without acceleration hardware. DirectShow is also integrated with other DirectX technologies. Some examples of applications that use DirectShow include DVD players, video editing applications, AVI to ASF converters, MP3 players, and digital video capture applications.
What is DirectX?
Microsoft DirectX is a feature of the Windows operating system. It is used for streaming media on Microsoft Windows operating systems to enable graphics and sound when playing games or watching video.
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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged-on with administrative user rights, an attacker could take complete control of the affected system. 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 convince a user to open a legitimate Windows Media Player file (such as a .wtv, .drv-ms, or .mpg file) that is located in the same network directory as a specially crafted dynamic link library (DLL) file. Then, while opening the media file, Microsoft DirectShow could attempt to load the DLL file and execute any code it contained.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a legitimate media file attachment (such as a .wtv, .drv-ms, or .mpg file) to a user, and convincing the user to place the attachment into a directory containing a specially crafted DLL file and to open the media file. Then, while opening the media file, Microsoft DirectShow could attempt to load the DLL file and execute any code it contained.
In a network attack scenario, an attacker could place a legitimate media file and a specially crafted DLL in a network share, UNC, or WebDAV location and then convince the user to open the media file.
What is a Windows Recorded TV Show (.wtv) file?
The Windows Recorded TV Show (WTV) file format replaces the previously used DVR-MS file format. Video is encoded using the MPEG-2 standard and audio using MPEG-1 Layer II or Dolby Digital AC-3 (ATSC A/52) standards. The format extends these standards by including metadata about the content and digital rights management. Access to WTV file content is made using the Stream Buffer Engine DirectShow source filter. Unlike .dvr-ms files, which are produced by previous versions of Media Center and are based on the ASF file format, WTV files are based on a new file format.
What is a Microsoft Digital Video Recording (.dvr-ms) file?
Microsoft Digital Video Recording files are files created by the Stream Buffer Engine (SBE) that are stored with the .dvr-ms file extension. When the SBE is being controlled from the Video Control, the audio and video elementary streams are examined for copy protection/control information. If this information does not specify that the content should be encrypted, then an unencrypted file will be created that can later be accessed by any DirectShow-based application that uses the SBE. If the information specifies that the content should be encrypted, then the resulting file will not be accessible, except for playback only on the same machine that was used to make the recording. DirectShow applications that are not based on the Video Control can use the SBE directly to create and play back unencrypted dvr-ms files.
What are DirectShow filters?
DirectShow provides a set of default filters that install automatically with Microsoft Windows. These filters support many data formats while providing a high degree of hardware independence. An application can also register and install custom filters on the target system. For a full list of filters and further information, see the MSDN article, DirectShow Filters.
What systems are primarily at risk from the vulnerability?
This vulnerability mainly affects workstations where users may be expected to open attachments from untrusted network locations. Servers could also be at risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update addresses this vulnerability by correcting the manner in which Microsoft DirectShow loads external libraries.
Is this vulnerability related to Microsoft Security Advisory 2269637?
Yes, this vulnerability is related to the class of vulnerabilities, described in Microsoft Security Advisory 2269637, that affects how applications load external libraries. This security update addresses a particular instance of this type of vulnerability.
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-2011-0032.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
DVR-MS Vulnerability - CVE-2011-0042
A remote code execution vulnerability exists in the way that Windows Media Player and Windows Media Center handle .dvr-ms files. This vulnerability could allow an attacker to execute arbitrary code if the attacker convinces a user to open a specially crafted .dvr-ms file. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-0042.
Mitigating Factors for DVR-MS Vulnerability - CVE-2011-0042
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 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.
- The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful a user would have to open a specially crafted .dvr-ms file that was sent as an attachment in an e-mail message. An attacker has no way to force a user to open a specially crafted .dvr-ms file. For an attack to be successful an attacker would have to convince a user to open the file.
- In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
Workarounds for DVR-MS Vulnerability - CVE-2011-0042
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:
Restrict access to the Stream Buffer Engine (SBE.dll)
Run the following commands from a command prompt as an administrator:
takeown /f "%windir%\system32\sbe.dll"cacls "%windir%\system32\sbe.dll" /E /P everyone:N
Impact of workaround. Play back of .dvr-ms files generated by the Stream Buffer Engine is disabled.
How to undo the workaround.
Run the following command from a command prompt as an administrator:
cacls "%windir%\system32\sbe.dll" /E /R everyone
FAQ for DVR-MS Vulnerability - CVE-2011-0042
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?
This vulnerability is caused when Windows Media Player and Windows Media Center do not properly parse specially crafted .dvr-ms media files.
What components are affected by the vulnerability?
Windows Media Center and Windows Media Player are the components affected by the vulnerability.
What might an attacker use the vulnerability to do?
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.
How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted .dvr-ms file.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a media file with a specially crafted .dvr-ms file embedded in it to a user and by convincing the user to open the file.
In a Web-based attack scenario, an attacker would have to host a Web site that contains specially crafted content that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability.
What is a Microsoft Digital Video Recording (.dvr-ms) file?
Microsoft Digital Video Recording (DVR-MS) files are files created by the Stream Buffer Engine (SBE) that are stored with the .dvr-ms file extension. When the SBE is being controlled from the Video Control, the audio and video elementary streams are examined for copy protection/control information. If this information does not specify that the content should be encrypted, then an unencrypted file will be created that can later be accessed by any DirectShow-based application that uses the SBE. If the information specifies that the content should be encrypted, then the resulting file will not be accessible, except for playback only on the same machine that was used to make the recording. DirectShow applications that are not based on the Video Control can use the SBE directly to create and play back unencrypted .dvr-ms files.
What systems are primarily at risk from the vulnerability?
Systems that use Windows Media Player or Windows Media Center to view .dvr-ms files are primarily at risk from the vulnerability.
What does the update do?
This update modifies the way that Windows Media Player and Windows Media Center open specially crafted .dvr-ms files.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Security Central
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.
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 |
---|---|
Windows XP Media Center Edition 2005 Service Pack 3 | No |
Windows XP Service Pack 3 | Yes |
Windows XP Professional x64 Edition Service Pack 2 | 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 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Yes |
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Yes |
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Yes |
Windows Media Center TV Pack for Windows Vista (32-bit editions) | Yes |
Windows Media Center TV Pack for Windows Vista (64-bit editions) | Yes |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
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 security updates 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 Media Center Edition 2005 Service Pack 3 | No | No | No | No |
Windows XP Service Pack 3 | Yes | Yes | Yes | Yes |
Windows XP Professional x64 Edition Service Pack 2 | 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 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | No | No | Yes | Yes |
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | No | No | Yes | Yes |
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | No | No | Yes | Yes |
Windows Media Center TV Pack for Windows Vista (32-bit editions) | No | No | Yes | Yes |
Windows Media Center TV Pack for Windows Vista (64-bit editions) | 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.
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 Media Center Edition 2005 Service Pack 3:\ WindowsXPMediaCenter2005-KB2502898-ENU.exe /quiet |
For Windows XP Service Pack 3:\ WindowsXP-KB2479943-x86-enu.exe /quiet | |
For Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB2479943-x64-enu.exe /quiet | |
Installing without restarting | For Windows XP Media Center Edition 2005 Service Pack 3:\ WindowsXPMediaCenter2005-KB2502898-ENU.exe /norestart |
For Windows XP Service Pack 3:\ WindowsXP-KB2479943-x86-enu.exe /norestart | |
For Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB2479943-x64-enu.exe /norestart | |
Update log file | For Windows XP Media Center Edition 2005 Service Pack 3:\ KB2502898.log |
For Windows XP Service Pack 3:\ KB2479943.log | |
For Windows XP Professional x64 Edition Service Pack 2:\ KB2479943.log | |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
HotPatching | Not applicable |
Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB2479943$\Spuninst folder |
File Information | See Microsoft Knowledge Base Article 2479943 |
Registry Key Verification | For Windows XP Media Center Edition 2005 Service Pack 3:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2502898\Filelist |
For all supported 32-bit editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2479943\Filelist | |
For all supported x64-based editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2479943\Filelist |
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, see Microsoft Knowledge Base Article 832475.
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.
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.
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.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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.
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-KB2479943-x86.msu /quiet |
For all supported x64-based editions of Windows Vista:\ Windows6.0-KB2479943-x64.msu /quiet | |
Installing without restarting | For all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2479943-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows Vista:\ Windows6.0-KB2479943-x64.msu /quiet /norestart | |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
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 2479943 |
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.
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.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
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. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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.
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-KB2479943-x86.msu /quiet |
For all supported x64-based editions of Windows 7:\ Windows6.1-KB2479943-x64.msu /quiet | |
Installing without restarting | For all supported 32-bit editions of Windows 7:\ Windows6.1-KB2479943-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows 7:\ Windows6.1-KB2479943-x64.msu /quiet /norestart | |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
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 2479943 |
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.
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.- Click Start and then enter an update file name in the Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
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. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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.
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-KB2479943-x64.msu /quiet |
Installing without restarting | For all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2479943-x64.msu /quiet /norestart |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
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 2479943 |
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.
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.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
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. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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.
Windows Media Center TV Pack for Windows Vista
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 Media Center TV Pack on 32-bit editions of Windows Vista Home Premium and Windows Vista Ultimate:\ MCETVPack-Windows6.0-KB2494132-x86.msu /quiet |
For Windows Media Center TV Pack on 64-bit editions of Windows Vista Home Premium and Windows Vista Ultimate:\ MCETVPack-Windows6.0-KB2494132-x64.msu /quiet | |
Installing without restarting | For Windows Media Center TV Pack on 32-bit editions of Windows Vista Home Premium and Windows Vista Ultimate:\ MCETVPack-Windows6.0-KB2494132-x86.msu /quiet /norestart |
For Windows Media Center TV Pack on 64-bit editions of Windows Vista Home Premium and Windows Vista Ultimate:\ MCETVPack-Windows6.0-KB2494132-x64.msu /quiet /norestart | |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
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 2494132 |
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.
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.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
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. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Matthew Watchinski of Sourcefire VRT for reporting the DVR-MS Vulnerability (CVE-2011-0042)
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.
Support
- Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. 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.
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.
Revisions
- V1.0 (March 8, 2011): Bulletin published.
- V1.1 (March 9, 2011): Corrected the Systems Management Server table entries for SMS 2.0 and SMS 2003 with SUIT for Windows XP Service Pack 3. These are informational changes only. There were no changes to the security update files or detection logic.
- V1.2 (March 16, 2011): Removed erroneous references to Windows XP Home Edition Service Pack 3 and Windows XP Tablet PC Edition Service Pack 3 in Non-Affected Software. This is an informational change only. There were no changes to the security update files or detection logic. For customers who are running Windows XP Home Edition or Windows XP Table PC Edition and who have not already applied this update, Microsoft recommends applying the update immediately. Customers who have already applied the update do not need to take any action.
Built at 2014-04-18T13:49:36Z-07:00