Izdana je revizija sigurnosne preporuke s oznakom MS11-007 koja je prvotno objavljena 9. veljače 2011. Upozorenje je navelo ranjivost vezanu uz upravljački program OpenType Compact Font Format. Otkrivena je greška u provjeri ulaznih vrijednosti posebno oblikovanih OpenType fontova. Ovisno o napadnutom operacijskom sustavu, ranjivost se može iskoristiti udaljeno za potpuno preuzimanje kontrole nad sustavom i pokretanje proizvoljnog programskog koda (Vista, Server 2008 i Windows 7) ili za povećanje ovlasti lokalnog napadača (XP, Server 2003). Revizijom je proširena lista ranjivih platformi. Za više detalja se preporuča pregled originalne preporuke.
Microsoft Security Bulletin MS11-007 - Critical
Vulnerability in the OpenType Compact Font Format (CFF) Driver Could Allow Remote Code Execution (2485376)
Published: February 08, 2011 | Updated: March 08, 2011
Version: 2.0
General Information
Executive Summary
This security update resolves a privately reported vulnerability in the Windows OpenType Compact Font Format (CFF) driver. The vulnerability could allow remote code execution if a user views content rendered in a specially crafted CFF font. In all cases, an attacker would have no way to force users to view the specially crafted content. Instead, an attacker would have to convince users to visit a 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.
This security update is rated Critical for all supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. This security update is also rated Important for all supported editions of Windows XP and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by correcting the manner in which the Windows OpenType Compact Font Format (CFF) driver validates the parameter values of specially crafted OpenType fonts. For more information about the vulnerability, 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
Top of sectionTop of section
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
Operating System Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Windows XP Service Pack 3
Elevation of Privilege
Important
MS10-091
Windows XP Professional x64 Edition Service Pack 2
Elevation of Privilege
Important
MS10-091
Windows Server 2003 Service Pack 2
Elevation of Privilege
Important
MS10-091
Windows Server 2003 x64 Edition Service Pack 2
Elevation of Privilege
Important
MS10-091
Windows Server 2003 with SP2 for Itanium-based Systems
Elevation of Privilege
Important
MS10-091
Windows Vista Service Pack 1 and Windows Vista Service Pack 2
Remote Code Execution
Critical
MS10-091
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2
Remote Code Execution
Critical
MS10-091
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*
Remote Code Execution
Critical
MS10-091
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*
Remote Code Execution
Critical
MS10-091
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2
Remote Code Execution
Critical
MS10-091
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1
Remote Code Execution
Critical
MS10-091
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1
Remote Code Execution
Critical
MS10-091
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1*
Remote Code Execution
Critical
MS10-091
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
Remote Code Execution
Critical
MS10-091
*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Top of sectionTop of section
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin revised on March 8, 2011?
Microsoft clarified the Affected Software to include Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1, and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1.
Customers of the original release version of Windows 7 for 32-bit Systems, Windows 7 for x64-based Systems, Windows Server 2008 R2 for x64-based Systems, and Windows Server 2008 R2 for Itanium-based Systems, who have already applied this security update do not need to take any action. Customers who have updated these operating systems with the corresponding Service Pack 1 need to apply 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.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.
Top of sectionTop of section
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the February bulletin summary. For more information, see Microsoft Exploitability Index.
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software OpenType Font Encoded Character Vulnerability - CVE-2011-0033 Aggregate Severity Rating
Windows XP Service Pack 3
Important
Elevation of Privilege
Important
Windows XP Professional x64 Edition Service Pack 2
Important
Elevation of Privilege
Important
Windows Server 2003 Service Pack 2
Important
Elevation of Privilege
Important
Windows Server 2003 x64 Edition Service Pack 2
Important
Elevation of Privilege
Important
Windows Server 2003 with SP2 for Itanium-based Systems
Important
Elevation of Privilege
Important
Windows Vista Service Pack 1 and Windows Vista Service Pack 2
Critical
Remote Code Execution
Critical
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2
Critical
Remote Code Execution
Critical
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*
Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*
Critical
Remote Code Execution
Critical
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2
Critical
Remote Code Execution
Critical
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1
Critical
Remote Code Execution
Critical
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1
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*
Critical
Remote Code Execution
Critical
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
Critical
Remote Code Execution
Critical
*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Top of sectionTop of section
OpenType Font Encoded Character Vulnerability - CVE-2011-0033
A remote code execution vulnerability exists in the way that the Windows OpenType Compact Font Format (CFF) driver improperly parses specially crafted OpenType fonts. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-0033.
Mitigating Factors for OpenType Font Encoded Character Vulnerability - CVE-2011-0033
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:
•
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.
Top of sectionTop of section
Workarounds for OpenType Font Encoded Character Vulnerability - CVE-2011-0033
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
•
Disable the Preview Pane and Details Pane in Windows Explorer
Disabling the Preview and Details panes in Windows Explorer prevents the automatic display of OTF fonts in Windows Explorer. While this prevents malicious files from being viewed in Windows Explorer, it does not prevent a local, authenticated user from running a specially crafted program to exploit this vulnerability. To disable these panes in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, perform the following steps:
1.
Open Windows Explorer, click Organize, and then click Layout.
2.
Clear both the Details pane and Preview pane menu options.
3.
Click Organize, and then click Folder and search options.
4.
Click the View tab.
5.
Under Advanced settings, check the Always show icons, never thumbnails box.
6.
Close all open instances of Windows Explorer for the change to take effect.
Impact of workaround. Windows Explorer will not automatically display OTF fonts.
How to undo the workaround.
To re-enable the Preview and Details panes in Windows Explorer for Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2:
1.
Open Windows Explorer, click Organize, and then click Layout.
2.
Select both the Details pane and Preview pane menu options.
3.
Click Organize, and then click Folder and search options.
4.
Click the View tab.
5.
Under Advanced settings, clear the Always show icons, never thumbnails box.
6.
Close all open instances of Windows Explorer for the change to take effect.
•
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, perform the following steps:
1.
Click Start, click Run, type Services.msc and then click OK.
2.
Right-click WebClient service and select Properties.
3.
Change the Startup type to Disabled. If the service is running, click Stop.
4.
Click OK and exit the management application.
Impact of workaround. When the WebClient service is disabled, Web Distributed Authoring and Versioning (WebDAV) requests are not transmitted. In addition, any services that explicitly depend on the WebClient 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, perform the following steps:
1.
Click Start, click Run, type Services.msc and then click OK.
2.
Right-click WebClient service and select Properties.
3.
Change the Startup type to Automatic. If the service is not running, click Start.
4.
Click OK and exit the management application.
Top of sectionTop of section
FAQ for OpenType Font Encoded Character Vulnerability - CVE-2011-0033
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 remotely. 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 the Windows OpenType Compact Font Format (CFF) driver does not properly validate the parameter values of specially crafted OpenType fonts.
What is the OpenType Font format?
OpenType is a font format developed jointly by Microsoft and Adobe as an extension of Apple's TrueType font format. An OpenType font file contains data, in table format, that comprises either a TrueType or a PostScript outline font. Rasterizers use combinations of data from the tables contained in the font to render the TrueType or PostScript glyph outlines. For more information, see the Microsoft Typography OpenType FAQ.
What are OpenType Compact Font Format (CFF) fonts?
An OpenType CFF font is an OpenType font that contains PostScript Type 1 outlines. OpenType fonts can contain either PostScript Type 1 or TrueType outlines. All Microsoft Windows fonts contain TrueType outlines. Desktop publishing applications such as Adobe InDesign and QuarkXPress support the largest number of OpenType features. Adobe Photoshop and Adobe Illustrator support many features. Support for common OpenType features has also been added to Microsoft Office Publisher and Microsoft Office Word. For more information, see the Microsoft Typography OpenType FAQ.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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?
On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 systems, an attacker could host a specially crafted OpenType font on a network share. Then, when the user navigates to the share in Windows Explorer, the affected control path is triggered via the Details and Preview panes. The specially crafted OpenType font could then exploit the vulnerability and take complete control over an affected system.
On Windows XP and Windows Server 2003 systems, to exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over an affected system.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
Are third-party Web browsers affected by this vulnerability?
Yes. Third-party Web browsers are affected by this vulnerability if they natively render OpenType fonts. For these applications, this vulnerability may allow remote code execution in the context of the logged on user if used to view a Web site with an embedded, specially crafted OpenType font. By default, Internet Explorer is not affected by this issue.
Can this vulnerability be remotely exploited in Windows XP or Windows Server 2003?
No. On these systems, OpenType fonts are not previewed automatically in Windows Explorer. To successfully exploit this vulnerability on these systems, an attacker would first have to log on to the local system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over an affected system.
What does the update do?
The update addresses the vulnerability by correcting the manner in which the Windows OpenType Compact Font Format (CFF) driver validates the parameter values of specially crafted OpenType fonts.
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.
Top of sectionTop of section
Top of sectionTop of section
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 Service Pack 3
Yes
Windows XP Professional x64 Edition Service Pack 2
Yes
Windows Server 2003 Service Pack 2
Yes
Windows Server 2003 x64 Edition Service Pack 2
Yes
Windows Server 2003 with SP2 for Itanium-based Systems
Yes
Windows Vista Service Pack 1 and Windows Vista Service Pack 2
Yes
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2
Yes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2
Yes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2
Yes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2
Yes
Windows 7 for 32-bit Systems 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 Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
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 Service Pack 3
Yes
Yes
Yes
Yes
Windows XP Professional x64 Edition Service Pack 2
No
No
Yes
Yes
Windows Server 2003 Service Pack 2
Yes
Yes
Yes
Yes
Windows Server 2003 x64 Edition Service Pack 2
No
No
Yes
Yes
Windows Server 2003 with SP2 for Itanium-based Systems
No
No
Yes
Yes
Windows Vista Service Pack 1 and Windows Vista Service Pack 2
No
No
Yes
Yes
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2
No
No
Yes
Yes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2
No
No
Yes
Yes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2
No
No
Yes
Yes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2
No
No
Yes
Yes
Windows 7 for 32-bit Systems 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 Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
No
No
Yes
Yes
For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Top of sectionTop of section
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows XP (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention
For Windows XP Service Pack 3:
WindowsXP-KB2485376-x86-enu.exe /quiet
For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB2485376-x64-enu.exe /quiet
Installing without restarting
For Windows XP Service Pack 3:
WindowsXP-KB2485376-x86-enu.exe /norestart
For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB2485376-x64-enu.exe /norestart
Update log file
KB2485376.log
Further information
See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?
Yes, you must restart your system after you apply this security update.
HotPatching
Not applicable
Removal Information
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB2485376$Spuninst folder
File Information
See Microsoft Knowledge Base Article 2485376
Registry Key Verification
For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesWindows XPSP4KB2485376Filelist
For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesWindows XP Version 2003SP3KB2485376Filelist
Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, 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.
Supported Security Update Installation Switches
Switch Description
/help
Displays the command-line options.
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed.
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
Displays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoem
Overwrites OEM files without prompting.
/nobackup
Does not back up files needed for uninstall.
/forceappsclose
Forces other programs to close when the computer shuts down.
/log:path
Allows the redirection of installation log files.
/integrate:path
Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]
Extracts files without starting the Setup program.
/ER
Enables extended error reporting.
/verbose
Enables verbose logging. During installation, creates %Windir%CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
Supported Spuninst.exe Switches
Switch Description
/help
Displays the command-line options.
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
Displays a dialog box prompting the local user to allow a restart.
Special Options
/forceappsclose
Forces other programs to close when the computer shuts down.
/log:path
Allows the redirection of installation log files.
Verifying That the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
•
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1.
Click Start, and then click Search.
2.
In the Search Results pane, click All files and folders under Search Companion.
3.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
5.
On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
•
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Top of sectionTop of section
Top of sectionTop of section
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention
For all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB2485376-x86-enu.exe /quiet
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB2485376-x64-enu.exe /quiet
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB2485376-ia64-enu.exe /quiet
Installing without restarting
For all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB2485376-x86-enu.exe /norestart
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB2485376-x64-enu.exe /norestart
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB2485376-ia64-enu.exe /norestart
Update log file
KB2485376.log
Further information
See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?
Yes, you must restart your system after you apply this security update.
HotPatching
This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB2485376$Spuninst folder
File Information
See Microsoft Knowledge Base Article 2485376
Registry Key Verification
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesWindows Server 2003SP3KB2485376Filelist
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.
Supported Security Update Installation Switches
Switch Description
/help
Displays the command-line options.
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed.
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
Displays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoem
Overwrites OEM files without prompting.
/nobackup
Does not back up files needed for uninstall.
/forceappsclose
Forces other programs to close when the computer shuts down.
/log:path
Allows the redirection of installation log files.
/integrate:path
Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]
Extracts files without starting the Setup program.
/ER
Enables extended error reporting.
/verbose
Enables verbose logging. During installation, creates %Windir%CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
Supported Spuninst.exe Switches
Switch Description
/help
Displays the command-line options.
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed.
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
Displays a dialog box prompting the local user to allow a restart.
Special Options
/forceappsclose
Forces other programs to close when the computer shuts down.
/log:path
Allows the redirection of installation log files.
Verifying that the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
•
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1.
Click Start, and then click Search.
2.
In the Search Results pane, click All files and folders under Search Companion.
3.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
5.
On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
•
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Top of sectionTop of section
Top of sectionTop of section
Windows Vista (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention
For all supported 32-bit editions of Windows Vista:
Windows6.0-KB2485376-x86.msu /quiet
For all supported x64-based editions of Windows Vista:
Windows6.0-KB2485376-x64.msu /quiet
Installing without restarting
For all supported 32-bit editions of Windows Vista:
Windows6.0-KB2485376-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Vista:
Windows6.0-KB2485376-x64.msu /quiet /norestart
Further information
See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?
Yes, you must restart your system after you apply this security update.
HotPatching
Not applicable.
Removal Information
WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information
See Microsoft Knowledge Base Article 2485376
Registry Key Verification
Note A registry key does not exist to validate the presence of this update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description
/?, /h, /help
Displays help on supported switches.
/quiet
Suppresses the display of status or error messages.
/norestart
When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
•
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1.
Click Start and then enter an update file name in the Start Search box.
2.
When the file appears under Programs, right-click the file name and click Properties.
3.
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.
4.
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.
5.
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.
Top of sectionTop of section
Top of sectionTop of section
Windows Server 2008 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention
For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB2485376-x86.msu /quiet
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2485376-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2485376-ia64.msu /quiet
Installing without restarting
For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB2485376-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2485376-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2485376-ia64.msu /quiet /norestart
Further information
See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?
Yes, you must restart your system after you apply this security update.
HotPatching
Not applicable.
Removal Information
WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information
See Microsoft Knowledge Base Article 2485376
Registry Key Verification
Note A registry key does not exist to validate the presence of this update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description
/?, /h, /help
Displays help on supported switches.
/quiet
Suppresses the display of status or error messages.
/norestart
When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
•
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1.
Click Start and then enter an update file name in the Start Search box.
2.
When the file appears under Programs, right-click the file name and click Properties.
3.
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.
4.
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.
5.
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.
Top of sectionTop of section
Top of sectionTop of section
Windows 7 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention
For all supported 32-bit editions of Windows 7:
Windows6.1-KB2485376-x86.msu /quiet
For all supported x64-based editions of Windows 7:
Windows6.1-KB2485376-x64.msu /quiet
Installing without restarting
For all supported 32-bit editions of Windows 7:
Windows6.1-KB2485376-x86.msu /quiet /norestart
For all supported x64-based editions of Windows 7:
Windows6.1-KB2485376-x64.msu /quiet /norestart
Further information
See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?
Yes, you must restart your system after you apply this security update.
HotPatching
Not applicable.
Removal Information
To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File Information
See Microsoft Knowledge Base Article 2485376
Registry Key Verification
Note A registry key does not exist to validate the presence of this update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description
/?, /h, /help
Displays help on supported switches.
/quiet
Suppresses the display of status or error messages.
/norestart
When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>
When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestart
When combined with /quiet, the installer will prompt before initiating restart.
/forcerestart
When combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>
Enables logging to specified file.
/extract:<destination>
Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>
Uninstalls the security update.
Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
•
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1.
Click Start and then enter an update file name in the Search box.
2.
When the file appears under Programs, right-click the file name and click Properties.
3.
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.
4.
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.
5.
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.
Top of sectionTop of section
Top of sectionTop of section
Windows Server 2008 R2 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention
For all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2485376-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2485376-ia64.msu /quiet
Installing without restarting
For all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2485376-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2485376-ia64.msu /quiet /norestart
Further information
See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?
Yes, you must restart your system after you apply this security update.
HotPatching
Not applicable.
Removal Information
To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File Information
See Microsoft Knowledge Base Article 2485376
Registry Key Verification
Note A registry key does not exist to validate the presence of this update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description
/?, /h, /help
Displays help on supported switches.
/quiet
Suppresses the display of status or error messages.
/norestart
When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>
When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestart
When combined with /quiet, the installer will prompt before initiating restart.
/forcerestart
When combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>
Enables logging to specified file.
/extract:<destination>
Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>
Uninstalls the security update.
Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
•
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1.
Click Start and then enter an update file name in the Start Search box.
2.
When the file appears under Programs, right-click the file name and click Properties.
3.
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.
4.
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.
5.
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.
Top of sectionTop of section
Top of sectionTop of section
Top of sectionTop of section
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.
Top of sectionTop of section
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.
Top of sectionTop of section
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Top of sectionTop of section
Revisions
•
V1.0 (February 8, 2011): Bulletin published.
•
V2.0 (March 8, 2011): Clarified the Affected Software to include Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1, and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1. See the entry to the section, Frequently Asked Questions (FAQ) Related to This Security Update, that explains this revision.
Posljednje sigurnosne preporuke