|
Microsoft Security Bulletin MS10-019 - CriticalVulnerabilities in Windows Could Allow Remote Code Execution (981210)Published: April 13, 2010 | Updated: April 14, 2010 Version: 1.1 Executive SummaryThis security update resolves two privately reported vulnerabilities in Windows Authenticode Verification that could allow remote code execution. An attacker who successfully exploited either 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. This security update is rated Critical for all supported versions of Microsoft Windows. For more information, see the subsection, Affected and Non-Affected Software, in this section. The security update addresses the vulnerabilities by performing additional verification operations when signing and verifying a portable executable or cabinet file. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information. Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871. For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service. See also the section, Detection and Deployment Tools and Guidance, later in this bulletin. Known Issues. None Affected and Non-Affected SoftwareThe 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 *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 MSDN articles, Server Core and Server Core for Windows Server 2008 R2. 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. | Frequently Asked Questions (FAQ) Related to This Security Update |
Are both updates required for my system?
Yes, the update for each component, Authenticode Signature Verification and Cabinet File Viewer Shell Extension, are required for each operating system. You must install both updates as applies to the operating system that you have. 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. 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. Does this update contain any security-related changes to functionality?
Yes. In addition to the changes that are listed in the Vulnerability Information section of this bulletin, this update includes a change that disables Authenticode version 1 signature on portable executable files and performs additional verification on cabinet files. 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. | 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 April bulletin summary. For more information, see Microsoft Exploitability Index. |
Authenticode Signature Verification 5.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 5.1 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 5.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 5.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 5.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 5.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 5.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.0 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.0 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.0* | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.0* | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.0 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.0 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.1 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.1 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.1* | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.1 | Not applicable | Critical
Remote Code Execution | Critical | Authenticode Signature Verification 6.1 | Critical
Remote Code Execution | Not applicable | Critical | Cabinet File Viewer Shell Extension 6.1 | Not applicable | Critical
Remote Code Execution | Critical |
*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 and Windows Server 2008 R2, whether or not installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, Server Core and Server Core for Windows Server 2008 R2. 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. | WinVerifyTrust Signature Validation Vulnerability - CVE-2010-0486 |
A remote code execution vulnerability exists in the Windows Authenticode Signature Verification function used for portable executable (PE) and cabinet file formats. An anonymous attacker could exploit the vulnerability by modifying an existing signed executable file to manipulate unverified portions of the signature and file in such a way as to add malicious code to the file without invalidating the signature. 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. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-0486. | Mitigating Factors for WinVerifyTrust Signature Validation Vulnerability - CVE-2010-0486 |
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation: | • | An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. |
| Workarounds for WinVerifyTrust Signature Validation Vulnerability - CVE-2010-0486 |
Microsoft has not identified any workarounds for this vulnerability. | FAQ for WinVerifyTrust Signature Validation Vulnerability - CVE-2010-0486 |
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could run arbitrary code with elevated privileges on vulnerable systems. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights. What causes the vulnerability?
The vulnerability is caused when the Windows Authenticode Signature Verification function omits fields from the file digest when signing and verifying a PE or cabinet file. What is the Windows Authenticode Signature Verification function?
The Windows Authenticode Signature Verification function, or WinVerifyTrust, performs a trust verification action on a specified object. The function passes the inquiry to a trust provider that supports the action identifier, if one exists. The WinVerifyTrust function performs two actions: signature checking on a specified object and trust verification action. For more information, see the MSDN article, WinVerifyTrust Function. What is the Windows Authenticode Portable Executable Signature Format?
Authenticode is a digital signature format that is used to determine the origin and integrity of software binaries. Authenticode uses Public-Key Cryptography Standards (PKCS) #7 signed data and X.509 certificates to bind an Authenticode-signed binary to the identity of a software publisher. The term "Authenticode" signature refers to a digital signature format that is generated and verified using the Authenticode Signature Verification Function. For more information on this format, see the Windows article, Windows Authenticode Portable Executable Signature Format. What is a cabinet file?
A cabinet is a single file, usually suffixed with .CAB, that stores compressed files in a file library. A compressed file can be spread over several cabinet files. During installation, the setup application decompresses the files stored in a cabinet and copies them to the user's system. For more information, see the MSDN article, Cabinet Files. What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause Windows to install or run arbitrary code. 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?
Exploitation of this vulnerability requires that a user, Windows feature, or application run or install a specially crafted, signed PE or cabinet file. An attacker could modify an existing signed file to include malicious code without invalidating the signature. This code would execute in the context of the privilege in which it was launched. What systems are primarily at risk from the vulnerability?
All affected operating systems are at risk. What does the update do?
The update addresses the vulnerability by performing additional verification when signing and verifying a portable executable or cabinet file. When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible 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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued. | Cabview Corruption Validation Vulnerability - CVE-2010-0487 |
A remote code execution vulnerability exists in the Windows Authenticode Signature verification for cabinet (.cab) file formats. An anonymous attacker could exploit the vulnerability by modifying an existing signed cabinet file to point the unverified portions of the signature to malicious code, and then convincing a user to open or view the specially crafted cabinet file. 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. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-0487. | Mitigating Factors for Cabview Corruption Validation Vulnerability - CVE-2010-0487 |
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation: | • | An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.. |
| Workarounds for Cabview Corruption Validation Vulnerability - CVE-2010-0487 |
Microsoft has not identified any workarounds for this vulnerability. | FAQ for Cabview Corruption Validation Vulnerability - CVE-2010-0487 |
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could run arbitrary code with elevated privileges on vulnerable systems. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights. What causes the vulnerability?
The vulnerability is caused when the Windows Cabinet File Viewer omits fields from the file digest when signing and verifying a cabinet file. What is the Windows Cabinet File Viewer?
The Windows Cabinet File Viewer (cabview.dll) serves as the viewer shell extension of the Windows operating system for cabinet files. This component allows viewing, opening, browsing, and extracting cabinet files and archives. What is a cabinet file?
A cabinet is a single file, usually suffixed with .CAB, that stores compressed files in a file library. A compressed file can be spread over several cabinet files. During installation, the setup application decompresses the files stored in a cabinet and copies them to the user's system. For more information, see the MSDN article, Cabinet Files. What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause Windows to install or run arbitrary code. 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?
Exploitation of this vulnerability requires that a user open a specially crafted cabinet file. An attacker could modify an existing signed cabinet file to point the unverified portions of the signature to malicious code. This code would execute in the context of the privilege in which it was launched. What systems are primarily at risk from the vulnerability?
All affected operating systems are at risk. What does the update do?
The update addresses the vulnerability by enforcing the processing of all fields from the file digest when signing and verifying a cabinet file. When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible 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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued. | Detection and Deployment Tools and Guidance |
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products. Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update." Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ. Note Microsoft discontinued support for Office Update and the Office Update Inventory Tool as of August 1, 2009. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. For more information, see About Microsoft Office Update: Frequently Asked Questions. Detection and Deployment Guidance Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747. Microsoft Baseline Security Analyzer Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer. The following table provides the MBSA detection summary for this security update. Microsoft Windows 2000 Service Pack 4 | Yes | Windows XP Service Pack 2 and 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, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | Yes | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | Yes | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Yes | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes | Windows 7 for 32-bit Systems | Yes | Windows 7 for x64-based Systems | Yes | Windows Server 2008 R2 for x64-based Systems | Yes | Windows Server 2008 R2 for Itanium-based Systems | Yes |
The latest version of MBSA has been released: Microsoft Baseline Security Analyzer 2.1.1. For more information, see Microsoft Baseline Security Analyzer 2.1. Windows Server Update Services By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Microsoft 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. 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 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, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | No | No | Yes | Yes | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | No | No | Yes | Yes | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | Yes | Yes | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | Yes | Yes | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | No | No | Yes | Yes | Windows 7 for 32-bit Systems | No | No | Yes | Yes | Windows 7 for x64-based Systems | No | No | Yes | Yes | Windows Server 2008 R2 for x64-based Systems | No | No | Yes | Yes | Windows Server 2008 R2 for Itanium-based Systems | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0. For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003. System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007. For more information about SMS, visit the SMS Web site. For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles. Update Compatibility Evaluator and Application Compatibility Toolkit Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit. The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment. | 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 Authenticode Signature Verification 5.1:
Windows2000-KB978601-x86-enu /quiet
For Cabinet File Viewer Shell Extension 5.1:
Windows2000-KB979309-x86-enu /quiet | Installing without restarting | For Authenticode Signature Verification 5.1:
Windows2000-KB978601-x86-enu /norestart
For Cabinet File Viewer Shell Extension 5.1:
Windows2000-KB979309-x86-enu /norestart | Update log file | For Authenticode Signature Verification 5.1:
KB978601.log
For Cabinet File Viewer Shell Extension 5.1:
KB979309.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | For Authenticode Signature Verification 5.1:
Yes, you must restart your system after you apply this security update.
For Cabinet File Viewer Shell Extension 5.1:
This update does not require a restart. However, 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 | For Authenticode Signature Verification 5.1:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB978601$\Spuninst folder
For Cabinet File Viewer Shell Extension 5.1:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB979309$\Spuninst folder | File Information | For Authenticode Signature Verification 5.1:
See Microsoft Knowledge Base Article 978601
For Cabinet File Viewer Shell Extension 5.1:
See Microsoft Knowledge Base Article 979309 | Registry Key Verification | For Authenticode Signature Verification 5.1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB978601
For Cabinet File Viewer Shell Extension 5.1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB979309 |
Installing the Update When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994. For more information about the installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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. | /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. |
/help | Displays the command-line options. | /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. | /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. | /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. |
| 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 Authenticode Signature Verification 5.1 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB978601-x86-ENU /quiet
For Cabinet File Viewer Shell Extension 6.0 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB979309-x86-ENU /quiet | | For Authenticode Signature Verification 5.1 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB978601-x64-ENU /quiet
For Cabinet File Viewer Shell Extension 6.0 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB979309-x64-ENU /quiet
| Installing without restarting | For Authenticode Signature Verification 5.1 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB978601-x86-ENU / norestart
For Cabinet File Viewer Shell Extension 6.0 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB979309-x86-ENU /norestart | | For Authenticode Signature Verification 5.1 on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB978601-x64-ENU /norestart
For Cabinet File Viewer Shell Extension 6.0 Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB979309-x64-ENU /norestart | Update log file | For Authenticode Signature Verification 5.1:
KB978601.log
For Cabinet File Viewer Shell Extension 6.0:
KB979309.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | For Authenticode Signature Verification 5.1:
Yes, you must restart your system after you apply this security update.
For Cabinet File Viewer Shell Extension 6.0:
This update does not require a restart. However, 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 | For Authenticode Signature Verification 5.1:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB978601$\Spuninst folder
For Cabinet File Viewer Shell Extension 6.0:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB979309$\Spuninst folder | File Information | For Authenticode Signature Verification 5.1:
See Microsoft Knowledge Base Article 978601
For Cabinet File Viewer Shell Extension 6.0:
See Microsoft Knowledge Base Article 979309 | Registry Key Verification | For Authenticode Signature Verification 5.1 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB978601
For Cabinet File Viewer Shell Extension 6.0 on Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB979309 | | For Authenticode Signature Verification 5.1 on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB978601
For Cabinet File Viewer Shell Extension 6.0 Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB979309 |
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. Installing the Update When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994. For more information about the installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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. | /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. |
/help | Displays the command-line options. | /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. | /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. | /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. |
| 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 Authenticode Signature Verification 5.1 on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB978601-x86-ENU /quiet
For Cabinet File Viewer Shell Extension 6.0 on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB979309-x86-ENU /quiet | | For Authenticode Signature Verification 5.1 on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB978601-x64-ENU /quiet
For Cabinet File Viewer Shell Extension 6.0 on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB979309-x64-ENU /quiet | | For Authenticode Signature Verification 5.1 on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB978601-ia64-ENU /quiet
For Cabinet File Viewer Shell Extension 6.0 on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB979309-ia64-ENU /quiet | Installing without restarting | For Authenticode Signature Verification 5.1 on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB978601-x86-ENU /norestart
For Cabinet File Viewer Shell Extension 6.0 on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB979309-x86-ENU /norestart | | For Authenticode Signature Verification 5.1 on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB978601-x64-ENU /norestart
For Cabinet File Viewer Shell Extension 6.0 on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB979309-x64-ENU /norestart | | For Authenticode Signature Verification 5.1 on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB978601-ia64-ENU /norestart
For Cabinet File Viewer Shell Extension 6.0 on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB979309-ia64-ENU /norestart | Update log file | For Authenticode Signature Verification 5.1:
KB978601.log
For Cabinet File Viewer Shell Extension 6.0:
KB979309.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | For Authenticode Signature Verification 5.1:
Yes, you must restart your system after you apply this security update.
For Cabinet File Viewer Shell Extension 6.0:
This update does not require a restart. However, 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 | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. | Removal Information | For Authenticode Signature Verification 5.1:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB978601$\Spuninst folder
For Cabinet File Viewer Shell Extension 6.0:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB979309$\Spuninst folder | File Information | For Authenticode Signature Verification 5.1:
See Microsoft Knowledge Base Article 978601
For Cabinet File Viewer Shell Extension 6.0:
See Microsoft Knowledge Base Article 979309 | Registry Key Verification | For Authenticode Signature Verification 5.1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB978601
For Cabinet File Viewer Shell Extension 6.0:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB979309 |
Installing the Update When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994. For more information about the installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/help | Displays the command-line options. | /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. | /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. | /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. |
/help | Displays the command-line options. | /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. | /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. | /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. |
| 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 Authenticode Signature Verification 6.0 on all supported 32-bit editions of Windows Vista:
Windows6.0-KB978601-x86 /quiet
For Cabinet File Viewer Shell Extension 6.0 on all supported 32-bit editions of Windows Vista:
Windows6.0-KB979309-x86 /quiet | | For Authenticode Signature Verification 6.0 on all supported x64-based editions of Windows Vista:
Windows6.0-KB978601-x64 /quiet
For Cabinet File Viewer Shell Extension 6.0 on all supported x64-based editions of Windows Vista:
Windows6.0-KB979309-x64 /quiet | Installing without restarting | For Authenticode Signature Verification 6.0 on all supported 32-bit editions of Windows Vista:
Windows6.0-KB978601-x86 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.0 on all supported 32-bit editions of Windows Vista:
Windows6.0-KB979309-x86 /quiet /norestart | | For Authenticode Signature Verification 6.0 on all supported x64-based editions of Windows Vista:
Windows6.0-KB978601-x64 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.0 on all supported x64-based editions of Windows Vista:
Windows6.0-KB979309-x64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | For Authenticode Signature Verification 6.0:
Yes, you must restart your system after you apply this security update.
For Cabinet File Viewer Shell Extension 6.0:
This update does not require a restart. However, 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 | For Authenticode Signature Verification 6.0:
See Microsoft Knowledge Base Article 978601
For Cabinet File Viewer Shell Extension 6.0:
See Microsoft Knowledge Base Article 979309 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
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. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307. Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start and then enter an update file name in Start Search. | 2. | When the file appears under Programs, right-click on the file name and click Properties. | 3. | Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. | 4. | You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. | 5. | Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. |
|
| 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 Authenticode Signature Verification 6.0 on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB978601-x86 /quiet
For Cabinet File Viewer Shell Extension 6.0 on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB979309-x86 /quiet | | For Authenticode Signature Verification 6.0 on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB978601-x64 /quiet
For Cabinet File Viewer Shell Extension 6.0 on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB979309-x64 /quiet | | For Authenticode Signature Verification 6.0 on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB978601-ia64 /quiet
For Cabinet File Viewer Shell Extension 6.0on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB979309-ia64 /quiet | Installing without restarting | For Authenticode Signature Verification 6.0 on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB978601-x86 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.0 on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB979309-x86 /quiet /norestart | | For Authenticode Signature Verification 6.0 on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB978601-x64 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.0 on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB979309-x64 /quiet /norestart | | For Authenticode Signature Verification 6.0 on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB978601-ia64 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.0 on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB979309-ia64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | For Authenticode Signature Verification 6.0:
Yes, you must restart your system after you apply this security update.
For Cabinet File Viewer Shell Extension 6.0:
This update does not require a restart. However, 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 | For Authenticode Signature Verification 6.0:
See Microsoft Knowledge Base Article 978601
For Cabinet File Viewer Shell Extension 6.0:
See Microsoft Knowledge Base Article 979309 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
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. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307. Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start and then enter an update file name in Start Search. | 2. | When the file appears under Programs, right-click on the file name and click Properties. | 3. | Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. | 4. | You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. | 5. | Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. |
|
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 Authenticode Signature Verification 6.1 on all supported 32-bit editions of Windows 7:
Windows6.1-KB978601-x86 /quiet
For Cabinet File Viewer Shell Extension 6.1 on all supported 32-bit editions of Windows 7:
Windows6.1-KB979309-x86 /quiet | | For Authenticode Signature Verification 6.1 on all supported x64-based editions of Windows 7:
Windows6.1-KB978601-x64 /quiet
For Cabinet File Viewer Shell Extension 6.1 on all supported x64-based editions of Windows 7:
Windows6.1-KB979309-x64 /quiet | Installing without restarting | For Authenticode Signature Verification 6.1 on all supported 32-bit editions of Windows 7:
Windows6.1-KB978601-x86 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.1 on all supported 32-bit editions of Windows 7:
Windows6.1-KB KB979309-x86 /quiet /norestart | | For Authenticode Signature Verification 6.1 on all supported x64-based editions of Windows 7:
Windows6.1-KB978601-x64 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.1 on all supported x64-based editions of Windows 7:
Windows6.1-KB979309-x64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | For Authenticode Signature Verification 6.1:
Yes, you must restart your system after you apply this security update.
For Cabinet File Viewer Shell Extension 6.1:
This update does not require a restart. However, 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 | For Authenticode Signature Verification 6.1:
See Microsoft Knowledge Base Article 978601
For Cabinet File Viewer Shell Extension 6.1:
See Microsoft Knowledge Base Article 979309 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
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. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307. Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start and then enter an update file name in Start Search. | 2. | When the file appears under Programs, right-click on the file name and click Properties. | 3. | Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. | 4. | You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. | 5. | Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. |
|
| 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 Authenticode Signature Verification 6.1 on all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB978601-x64 /quiet
For Cabinet File Viewer Shell Extension 6.1 on all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB979309-x64 /quiet | | For Authenticode Signature Verification 6.1 on all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB978601-ia64 /quiet
For Cabinet File Viewer Shell Extension 6.1 on all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB979309-ia64 /quiet | Installing without restarting | For Authenticode Signature Verification 6.1 on all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB978601-x64 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.1 on all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB979309-x64 /quiet /norestart | | For Authenticode Signature Verification 6.1 on all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB978601-ia64 /quiet /norestart
For Cabinet File Viewer Shell Extension 6.1 on all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB979309-ia64 /quiet /norestart | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required? | For Authenticode Signature Verification 6.1:
Yes, you must restart your system after you apply this security update.
For Cabinet File Viewer Shell Extension 6.1:
This update does not require a restart. However, 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 | For Authenticode Signature Verification 6.1:
See Microsoft Knowledge Base Article 978601
For Cabinet File Viewer Shell Extension 6.1:
See Microsoft Knowledge Base Article 979309 | Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
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. |
/?, /h, /help | Displays help on supported switches. | /quiet | Suppresses the display of status or error messages. | /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307. Verifying That the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. | | • | File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. | Click Start and then enter an update file name in Start Search. | 2. | When the file appears under Programs, right-click on the file name and click Properties. | 3. | Under the General tab, compare the file size with the file information tables provided in the bulletin KB article. | 4. | You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. | 5. | Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. |
|
Microsoft Active Protections Program (MAPP)To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners. Support| • | Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support. | | • | International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site. |
DisclaimerThe 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 (April 13, 2010): Bulletin published. | | • | V1.1 (April 14, 2010): Corrected the server core notation, for Windows Server 2008 and Windows Server 2008 R2, to apply only to the KB978601 update. |
|