Microsoft Security Bulletin MS08-076 - Important
Vulnerabilities in Windows Media Components Could Allow Remote Code Execution (959807)
Published: | Updated:
Version: 5.0
General Information
Executive Summary
This security update resolves two privately reported vulnerabilities in the following Windows Media components: Windows Media Player, Windows Media Format Runtime, and Windows Media Services. The most severe vulnerability could allow remote code execution. If a user is logged on with administrative user rights, 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.
This security update is rated Important for Windows Media Player 6.4, Windows Media Format Runtime 7.1, Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, Windows Media Format Runtime 11, Windows Media Services 4.1, Windows Media Services 9 Series, and Windows Media Services 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the first vulnerability by modifying the way that Windows Media authentication replies are validated. The security update addresses the second vulnerability by ensuring that Windows Media clients treat servers using ISATAP addresses as external. 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. Microsoft recommends that customers apply the update at the earliest opportunity.
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
| Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|---|
| Windows Media Player 6.4 | ||||
| Microsoft Windows 2000 Service Pack 4 | Windows Media Player 6.4 (KB954600) | Remote Code Execution | Important | None |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Windows Media Player 6.4 (KB954600) | Remote Code Execution | Important | None |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Windows Media Player 6.4 (KB954600) | Remote Code Execution | Important | None |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Windows Media Player 6.4 (KB954600) | Remote Code Execution | Important | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Windows Media Player 6.4 (KB954600) | Remote Code Execution | Important | None |
| Windows Media Format Runtime 7.1, Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 | ||||
| Microsoft Windows 2000 Service Pack 4 | Windows Media Format Runtime 7.1 and Windows Media Format Runtime 9.0 (KB952069) | Remote Code Execution | Important | None |
| Windows XP Service Pack 2 | Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 (KB952069) | Remote Code Execution | Important | None |
| Windows XP Service Pack 3 | Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 (KB952069) | Remote Code Execution | Important | None |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Windows Media Format Runtime 9.5 (KB952069) | Remote Code Execution | Important | None |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Windows Media Format Runtime 9.5 x64 Edition (KB952069) | Remote Code Execution | Important | None |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Windows Media Format Runtime 11 (KB952069) | Remote Code Execution | Important | None |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Windows Media Format Runtime 9.5 (KB952069) | Remote Code Execution | Important | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Windows Media Format Runtime 9.5 (KB952069) | Remote Code Execution | Important | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Windows Media Format Runtime 9.5 x64 Edition (KB952069) | Remote Code Execution | Important | None |
| Windows Vista and Windows Vista Service Pack 1 | Windows Media Format Runtime 11 (KB952069) | Remote Code Execution | Important | None |
| Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Windows Media Format Runtime 11 (KB952069) | Remote Code Execution | Important | None |
| Windows Server 2008 for 32-bit Systems | Windows Media Format Runtime 11 (KB952069) | Remote Code Execution | Important | None |
| Windows Server 2008 for x64-based Systems | Windows Media Format Runtime 11 (KB952069) | Remote Code Execution | Important | None |
| Windows Media Services | ||||
| Microsoft Windows 2000 Service Pack 4 | Windows Media Services 4.1 (KB952068) | Remote Code Execution | Important | None |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Windows Media Services 9 Series (KB952068) | Remote Code Execution | Important | MS07-068 |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Windows Media Services 9 Series (KB952068) | Remote Code Execution | Important | MS07-068 |
| Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* | Windows Media Services 2008 (KB952068) | Remote Code Execution | Important | None |
| Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* | Windows Media Services 2008 (KB952068) | Remote Code Execution | Important | None |
*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
Non-Affected Software
| Operating System | Component |
|---|---|
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Not applicable |
| Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Not applicable |
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin re-released on November 24, 2009?
Microsoft re-released this bulletin to offer a new update package specific to Windows XP Embedded systems to address detection and installation issues with the original Windows XP update packages included with this bulletin.
In addition, Microsoft revised the existing update packages for Windows XP Service Pack 2 (KB952069) and Windows XP Service Pack 3 (KB952069) to prevent the packages from being offered to Windows XP Embedded systems. Customers who have already installed this security update are protected and do not need to take any action.
Customers using the Windows XP Embedded operating system should apply the update at the earliest opportunity. Customers can also manually download the update for Windows XP Embedded Service Pack 2 (KB972187) or the update for Windows XP Embedded Service Pack 3 (KB972187). No other updates are affected by this re-release.
What is the Windows XP Embedded operating system?
Microsoft Windows XP Embedded is a componentized version of the Windows XP Professional operating system that brings the rich feature set of Windows XP Professional to embedded devices. Windows XP Embedded is optimized for the retail industry, with built-in networking capabilities and standards-based plug-and-play support. Windows XP Embedded lets you connect a variety of retail or hospitality device peripherals onto a single point of service (POS) system. For more information about Windows XP Embedded operating systems, visit the Microsoft Windows Embedded Developer Center.
Why was this bulletin re-released on January 13, 2009?
Microsoft re-released this bulletin to offer new update packages for Windows Media Format Runtime 9.5 on Windows XP Service Pack 2 (KB952069) and on Windows XP Service Pack 3 (KB952069). The new update packages fix an installation issue that would result in an incomplete installation on Windows XP systems running Windows Media Format Runtime 9.5 where the customer installed KB944110, a separate update, before installing KB952069. Such customers are still vulnerable and need to download and install the re-released update packages. No other update packages are affected by this re-release. Customers running all other supported and affected versions of Windows Media Player, Windows Media Format Runtime, and Windows Media Services who have already successfully applied the original security update packages do not need to take any further action. The re-released security update packages are available through all of the same distribution channels as the original security update, including Automatic Updates, Windows Update, and Windows Server Update Services.
Microsoft also revised this bulletin to list Windows Media Player 6.4 and Windows Media Services 4.1 as affected on all editions of Microsoft Windows 2000 Service Pack 4 (not just Microsoft Windows 2000 Server Service Pack 4). The same update applies; there were no new update packages for this operating system. However, customers who were offered but have not applied this update, KB954600 for Windows Media Player 6.4, or KB952068 for Windows Media Services 4.1, need to do so.
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 959807.
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. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.
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. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.
Customers who require custom support for older releases 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 Microsoft Worldwide Information, select the country, 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 Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | SPN Vulnerability - CVE-2008-3009 | ISATAP Vulnerability - CVE-2008-3010 | Aggregate Severity Rating |
|---|---|---|---|
| Windows Media Player 6.4 | |||
| Windows Media Player 6.4 on Microsoft Windows 2000 Service Pack 4 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Player 6.4 on Windows XP Service Pack 2 and Windows XP Service Pack 3 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Player 6.4 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Player 6.4 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Player 6.4 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Format Runtime 7.1, Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 | |||
| Windows Media Format Runtime 7.1 and Windows Media Format Runtime 9.0 on Microsoft Windows 2000 Service Pack 4 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 2 and Windows XP Service Pack 3 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Format Runtime 9.5, Windows Media Format Runtime 9.5 x64 Edition, and Windows Media Format Runtime 11 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Format Runtime 9.5 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Format Runtime 9.5 and Windows Media Format Runtime 9.5 x64 Edition on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Format Runtime 11 on Windows Vista and Windows Vista Service Pack 1 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Format Runtime 11 on Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Format Runtime 11 on Windows Server 2008 for 32-bit Systems | Important Remote Code Execution | Low Information Disclosure | Important |
| Windows Media Format Runtime 11 on Windows Server 2008 for x64-based Systems | Important Remote Code Execution | Low Information Disclosure | Important |
| Windows Media Services | |||
| Windows Media Services 4.1 on Microsoft Windows 2000 Service Pack 4 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Services 9 Series on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Services 9 Series on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Important Remote Code Execution | Moderate Information Disclosure | Important |
| Windows Media Services 2008 on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* | Important Remote Code Execution | Not applicable | Important |
| Windows Media Services 2008 on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* | Important Remote Code Execution | Not applicable | Important |
*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
SPN Vulnerability - CVE-2008-3009
A credential reflection vulnerability exists in the Windows Media components that could allow an attacker to execute code with the same rights as the local user or with Windows Media Services distribution credentials. The vulnerability exists due to weaknesses in Service Principal Name (SPN) implementations within Windows Media components.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-3009.
Mitigating Factors for SPN Vulnerability - CVE-2008-3009
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:
- Windows Media Services is an optional component on all Windows Server platforms and is not installed by default.
- In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
- For Windows Server 2008 and Windows Server 2008 x64-based Systems, Windows Media Format Runtime 11 is only present on the system when Desktop Experience is installed.
Workarounds for SPN Vulnerability - CVE-2008-3009
Microsoft has not identified any workarounds for this vulnerability.
FAQ for SPN Vulnerability - CVE-2008-3009
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could execute code with the same rights as the logged-on user. If a user is logged on with administrative user rights, 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. An attacker who successfully exploited this vulnerability could also execute code with Windows Media Services distribution credentials. In this instance, an attacker could execute code with the same rights as the NETWORK SERVICE account.
What causes the vulnerability?
Windows Media components do not correctly opt-in to NTLM credential-reflection protections to ensure that a user's credentials are not reflected back at the user’s system and used to impersonate the user.
What are Service Principle Names (SPNs)?
A service principal name (SPN) is the name by which a client uniquely identifies an instance of a service. The SPN provides a service identity type used for authenticating the service to the client. When a client wants to connect to a service, it locates an instance of the service, composes an SPN for that instance, connects to the service, and presents the SPN for the service to authenticate. For additional information on SPN, see Service Identity and Authentication. For additional information on how SPNs should be formatted, see Name Formats for Unique SPNs.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. If a user is logged on with administrative user rights, 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.
How could an attacker exploit the vulnerability?
This vulnerability requires that a user with an affected version of Windows Media components access a malicious server. An attacker could host a malicious server share or Web site that requires authentication. When the client connects and authenticates to the malicious server, the attacker can use the credentials provided by the client to reflect back to the client, or forward the credentials on to other servers, thereby mimicking the client. An attacker would have no way to force users to visit a specially crafted server share or Web site. Instead, an attacker would have to convince them to visit the server share or Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.
What systems are primarily at risk from the vulnerability?
Any system using the affected versions of Windows Media Player, Windows Media Format Runtime, or Windows Media Services is at risk from this vulnerability. Any systems that these components use frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
What does the update do?
The security update addresses the vulnerability by modifying the way that Windows Media Component authentication replies are validated to prevent the replay of credentials.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
ISATAP Vulnerability - CVE-2008-3010
An information disclosure vulnerability exists in supported versions of Windows Media components that could result in the disclosure of NTLM credentials. Any Windows Media component that accesses a URL that uses an ISATAP address could leak the user’s NTLM credentials to the server that hosts the URL. This could allow an attacker who is external to the intranet zone to gather NTLM credentials for an enterprise environment.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-3010.
Mitigating Factors for ISATAP Vulnerability - CVE-2008-3010
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:
- Firewall best practices and standard default firewall configurations can help protect network resources from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports and protocols exposed.
- In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
- For Windows Server 2008 and Windows Server 2008 x64-based Systems, Windows Media Format Runtime 11 is only present on the system when Desktop Experience is installed.
Workarounds for ISATAP Vulnerability - CVE-2008-3010
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:
- Block IP Protocol Type 41 (ISATAP) at the firewall
The ISATAP protocol is defined as protocol type 41 by RFC4214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP). Blocking this protocol type 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 or protocols.
FAQ for ISATAP Vulnerability - CVE-2008-3010
What is the scope of the vulnerability?
This is an information disclosure vulnerability. An attacker who successfully exploited this vulnerability could gain the NTLM credentials of the logged-on user. These credentials may be subsequently reflected back to the user’s system to execute code with the same rights as the logged-on user.
What causes the vulnerability?
The affected Windows Media components incorrectly treat Internet resources as a part of the Local Intranet zone when connecting to a server that is using an ISATAP address.
What is ISATAP?
The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) provides IPv6 connectivity within an IPv4 Intranet. The RFC for ISATAP is hosted by the Internet Engineering Task Force (IETF). For information on ISATAP, see RFC4214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP).
What is NTLM?
NTLM is an authentication protocol based on a challenge/response mechanism.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the user’s NTLM credentials. These credentials may be subsequently reflected back to the user’s system to execute code with the same rights as the logged-on user.
How could an attacker exploit the vulnerability?
This vulnerability requires that a user with an affected version of Windows Media components access a malicious server. An attacker could host a malicious server share or Web site that requires authentication. When the Client connects and authenticates to the malicious server the attacker can use the credentials provided by the client to reflect back to the client, or forward the credentials on to other servers, thereby mimicking the client. An attacker would have no way to force users to visit a specially crafted server share or Web site. Instead, an attacker would have to convince them to visit the server share or Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.
What systems are primarily at risk from the vulnerability?
Any system using the affected versions of Windows Media Player, Windows Media Format Runtime, or Windows Media Services is at risk from this vulnerability. Any systems these components use frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
What does the update do?
The update removes the vulnerability by ensuring that Windows Media Component clients treat servers using ISATAP addresses as external and do not pass off user credentials.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
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, Windows Update, and Office 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 has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.
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 |
|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Windows Vista and Windows Vista Service Pack 1 | Yes |
| Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | 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 |
For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Yes | Yes | Yes |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Vista and Windows Vista Service Pack 1 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes 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. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other 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.
Note for Windows Vista and Windows Server 2008 Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 manageability.
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 5.0.
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 2000 (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 may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | For Windows Media Player 6.4 on Microsoft Windows 2000 Service Pack 4: WindowsMedia64-KB954600-x86-ENU /quiet |
| For Windows Media Format Runtime 7.1 and Windows Media Format Runtime 9.0 on Microsoft Windows 2000 Service Pack 4 Windows2000-WindowsMedia-KB952069-x86-ENU /quiet | |
| For Windows Media Services 4.1 on Microsoft Windows 2000 Service Pack 4 WindowsMedia41-KB952068-x86-ENU /quiet | |
| Installing without restarting | For Windows Media Player 6.4 on Microsoft Windows 2000 Service Pack 4: WindowsMedia64-KB954600-x86-ENU /norestart |
| For Windows Media Format Runtime 7.1 and Windows Media Format Runtime 9.0 on Microsoft Windows 2000 Service Pack 4 Windows2000-WindowsMedia-KB952069-x86-ENU /norestart | |
| For Windows Media Services 4.1 on Microsoft Windows 2000 Service Pack 4 WindowsMedia41-KB952068-x86-ENU /norestart | |
| Update log file | For Windows Media Player 6.4 on Microsoft Windows 2000 Service Pack 4: Kb954600.log For Windows Media Format Runtime 7.1 and Windows Media Format Runtime 9.0 on Microsoft Windows 2000 Service Pack 4 kb952069.log For Windows Media Services 4.1 on Microsoft Windows 2000 Service Pack 4 Kb952068.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 | For Windows Media Player 6.4 on Microsoft Windows 2000 Service Pack 4: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB954600_WM41$\Spuninst folder |
| For Windows Media Format Runtime 7.1 and Windows Media Format Runtime 9.0 on Microsoft Windows 2000 Service Pack 4 Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB952069_WM71$\Spuninst folder | |
| For Windows Media Services 4.1 on Microsoft Windows 2000 Service Pack 4 Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB952068_WM41$\Spuninst folder | |
| File Information | See Microsoft Knowledge Base Article 959807 |
| Registry Key Verification | For Windows Media Player 6.4 on Microsoft Windows 2000 Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player 6.4\SP0\KB954600_WM41\Filelist |
| For Windows Media Format Runtime 7.1 and Windows Media Format Runtime 9.0 on Microsoft Windows 2000 Service Pack 4 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB952069_WM71\Filelist | |
| For Windows Media Services 4.1 on Microsoft Windows 2000 Service Pack 4 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Services 4.1\SP0\KB952068_WM41\Filelist |
Deployment Information
Installing the Update
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.
| 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. |
| /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 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 Media Player 6.4 on Windows XP Service Pack 2 and Windows XP Service Pack 3: Windowsxp-kb954600-x86-enu /quiet |
| For Windows Media Player 6.4 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-kb954600-x64-enu /quiet | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 2 WindowsXP-SP2-WindowsMedia-KB952069-x86-enu /quiet | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 3 WindowsXP-WindowsMedia-KB952069-x86-enu /quiet | |
| For Windows Media Format Runtime 9.5 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 WindowsServer2003.WindowsXP-kb952069-x64-enu /quiet | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 WindowsMedia10-KB952069-x64-enu /quiet | |
| For Windows Media Format Runtime 11 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 WindowsMedia11-KB952069-x64-enu /quiet | |
| Installing without restarting | For Windows Media Player 6.4 on Windows XP Service Pack 2 and Windows XP Service Pack 3: Windowsxp-kb954600-x86-enu /norestart |
| For Windows Media Player 6.4 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-kb954600-x64-enu /norestart | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 2 WindowsXP-SP2-WindowsMedia-KB952069-x86-enu /norestart | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 3 WindowsXP-WindowsMedia-KB952069-x86-enu /norestart | |
| For Windows Media Format Runtime 9.5 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 WindowsServer2003.WindowsXP-kb952069-x64-enu /norestart | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 WindowsMedia10-KB952069-x64-enu /norestart | |
| For Windows Media Format Runtime 11 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 WindowsMedia11-KB952069-x64-enu /norestart | |
| Update log file | For Windows Media Player 6.4 on Windows XP Service Pack 2 and Windows XP Service Pack 3: KB954600.log |
| For Windows Media Player 6.4 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: KB954600.log | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 2 KB952069.log | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 3 KB952069.log | |
| For Windows Media Format Runtime 9.5 and Windows Media Format Runtime 11 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 KB952069.log | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 KB952069.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. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | For Windows Media Player 6.4 on Windows XP Service Pack 2 and Windows XP Service Pack 3: Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB954600$\Spuninst folder |
| For Windows Media Player 6.4 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB954600$\Spuninst folder | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 2 Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB952069_WM9$\Spuninst folder | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 3 Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB952069_WM9$\Spuninst folder | |
| For Windows Media Format Runtime 9.5 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB952069$\Spuninst folder For Windows Media Format Runtime 11 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB952069_WM11x64$\Spuninst folder | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB952069_WM10Lx64$\Spuninst folder | |
| File Information | See Microsoft Knowledge Base Article 959807 |
| Registry Key Verification | For Windows Media Player 6.4 on Windows XP Service Pack 2 and Windows XP Service Pack 3: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB954600\Filelist |
| For Windows Media Player 6.4 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB954600\Filelist | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 2 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB952069_WM9\Filelist | |
| For Windows Media Format Runtime 9.0, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 on Windows XP Service Pack 3 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB952069_WM9\Filelist | |
| For Windows Media Format Runtime 9.5 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB952069\Filelist For Windows Media Format Runtime 11 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 11 SDK\SP0\KB952069_WM11x64\Filelist | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 9.5 SDK\SP0\KB952069_WM10Lx64\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 SP2QFE, or SP3QFE files to your system. Otherwise, the installer copies SP2GDR, or SP3GDR 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.
| 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 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 Windows Media Player 6.4 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Windowsserver2003-kb954600-x86-enu /quiet |
| For Windows Media Player 6.4 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Windowsserver2003.WindowsXP-KB954600-x64-enu /quiet | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Windowsserver2003-kb952069-x86-enu /quiet | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Windowsserver2003.WindowsXP-KB952069-x64-enu /quiet | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: WindowsMedia10-KB952069-x64-enu /quiet | |
| For Windows Media Services 9 Series on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Windowsserver2003-kb952068-x86-enu /quiet | |
| For Windows Media Services 9 Series on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Windowsserver2003.WindowsXP-KB952068-x64-enu /quiet | |
| Installing without restarting | For Windows Media Player 6.4 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Windowsserver2003-kb954600-x86-enu /norestart |
| For Windows Media Player 6.4 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Windowsserver2003.WindowsXP-KB954600-x64-enu /norestart | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Windowsserver2003-kb952069-x86-enu /norestart | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Windowsserver2003.WindowsXP-KB952069-x64-enu /norestart | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: WindowsMedia10-KB952069-x64-enu /norestart | |
| For Windows Media Services 9 Series on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Windowsserver2003-kb952068-x86-enu /norestart | |
| For Windows Media Services 9 Series on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Windowsserver2003.WindowsXP-KB952068-x64-enu /norestart | |
| Update log file | For Windows Media Player 6.4 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: KB954600.log |
| For Windows Media Player 6.4 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: KB954600.log | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: KB952069.log | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: KB952069.log | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: KB952069.log | |
| For Windows Media Services 9 Series on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: KB952068.log | |
| For Windows Media Services 9 Series on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: KB952068.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. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
| Removal Information | For Windows Media Player 6.4 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB954600$\Spuninst folder |
| For Windows Media Player 6.4 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB954600$\Spuninst folder | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB952069$\Spuninst folder | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB952069$\Spuninst folder | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB952069_WM10Lx64$\Spuninst folder | |
| For Windows Media Services 9 Series on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB952068$\Spuninst folder | |
| For Windows Media Services 9 Series on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB952068$\Spuninst folder | |
| File Information | See Microsoft Knowledge Base Article 959807 |
| Registry Key Verification | For Windows Media Player 6.4 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB954600\Filelist |
| For Windows Media Player 6.4 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB954600\Filelist | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB952069\Filelist | |
| For Windows Media Format Runtime 9.5 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB952069\Filelist | |
| For Windows Media Format Runtime 9.5 x64 Edition on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 9.5 SDK\SP0\KB952069_WM10Lx64\Filelist | |
| For Windows Media Services 9 Series on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB952068\Filelist | |
| For Windows Media Services 9 Series on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB952068\Filelist |
Deployment Information
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 SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the 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.
| 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.
| 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 Windows Media Format Runtime 11 on Windows Vista and Windows Vista Service Pack 1: Windows6.0-KB952069-x86 /quiet Windows Media Format Runtime 11 on Windows Vista x64-based Edition and Windows Vista x64-based Edition Service Pack 1: Windows6.0-KB952069-x64 /quiet |
| Installing without restarting | For Windows Media Format Runtime 11 on Windows Vista and Windows Vista Service Pack 1: Windows6.0-KB952069-x86 /norestart Windows Media Format Runtime 11 on Windows Vista x64-based Edition and Windows Vista x64-based Edition Service Pack 1: Windows6.0-KB952069-x64 /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 | 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 959807 |
| 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 Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- 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.
- 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.
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 Windows Media Format Runtime 11 on Windows Server 2008 for 32-bit Systems: Windows6.0-KB952069-x86 /quiet For Windows Media Format Runtime 11 on Windows Server 2008 for x64-based Systems: Windows6.0-KB952069-x64 /quiet For Windows Media Services 2008 on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2: Windows6.0-KB952068-x86 /quiet For Windows Media Services 2008 on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2: Windows6.0-KB952068-x64 /quiet |
| Installing without restarting | For Windows Media Format Runtime 11 on Windows Server 2008 for 32-bit Systems: Windows6.0-KB952069-x86 /norestart For Windows Media Format Runtime 11 on Windows Server 2008 for x64-based Systems: Windows6.0-KB952069-x64 /norestart For Windows Media Services 2008 on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2: Windows6.0-KB952068-x86 /norestart For Windows Media Services 2008 on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2: Windows6.0-KB952068-x64 /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 | 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 959807 |
| 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 Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- 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.
- 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.
Other Information
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 Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- 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 (December 9, 2008): Bulletin published.
- V2.0 (December 10, 2008): Corrected Affected Software table to list Windows Media Format Runtime 9.5 and Windows Media Format Runtime 11 as separate updates on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2. Also removed erroneous references to Windows Media Format Runtime 11 x64 Edition on Windows XP Professional x64 Edition, Windows XP Professional x64 Edition Service Pack 2, Windows Server 2003 x64 Edition, and Windows Server 2003 x64 Edition Service Pack 2.
- V3.0 (January 13, 2009): Added entry to the Frequently Asked Questions (FAQ) Related to This Security Update section explaining that Microsoft has re-released the update packages for Windows Media Format Runtime 9.5 on Windows XP Service Pack 2 (KB952069) and on Windows XP Service Pack 3 (KB952069). Customers running all other supported and affected versions of Windows Media components who have already applied the original security update packages do not need to take any further action. Also, listed Windows Media Player 6.4 and Windows Media Services 4.1 as affected on all editions of Microsoft Windows 2000 Service Pack 4; customers who were offered but have not applied this update, KB954600 for Windows Media Player 6.4, or KB952068 for Windows Media Services 4.1, need to do so.
- V3.1 (February 25, 2009): Corrected registry key verification in the reference tables of this bulletin.
- V4.0 (April 29, 2009): Added Windows Media Services 2008 (KB952068) on 32-bit and x64-based editions of Windows Server 2008 Service Pack 2 as affected software. Also, added Windows Server 2008 for Itanium-based Systems Service Pack 2 as non-affected software. This is a detection change only; there were no changes to the binaries. Customers who have already successfully installed KB952068 do not need to reinstall.
- V5.0 (November 24, 2009): Added entries to the Frequently Asked Questions (FAQ) Related to This Security Update section announcing the re-release of this update for the Windows XP Embedded operating system. Customers using the Windows XP Embedded operating system should install this automatically offered security update at the earliest opportunity. Customers of all other operating systems who have already installed this update do not need to take further action.