Security Bulletin
Microsoft Security Bulletin MS07-056 - Critical
Security Update for Outlook Express and Windows Mail (941202)
Published: October 09, 2007 | Updated: October 10, 2007
Version: 2.0
General Information
Executive Summary
This critical security update resolves one privately reported vulnerability. The vulnerability could allow remote code execution due to an incorrectly handled malformed NNTP response. An attacker could exploit the vulnerability by constructing a specially crafted Web page.
This is a critical security update for all supported versions of Microsoft Outlook express and Microsoft Windows Mail. For more information, see the subsection, Affected and Non-Affected Software, in this section.
This security update removes the vulnerability by changing the newsgroup client to handle malformed responses correctly. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update immediately.
Known Issues. None
Affected and Non-Affected Software
The software listed here have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
| Operating System | Component | Maximum Security Impact | Severity Rating | Bulletins Replaced by This Update |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Outlook Express 5.5 Service Pack 2 | Remote Code Execution | Critical | MS06-076 |
| Microsoft Windows 2000 Service Pack 4 | Outlook Express 6 Service Pack 1 | Remote Code Execution | Critical | MS06-076 |
| Windows XP Service Pack 2 | Microsoft Outlook Express 6 | Remote Code Execution | Critical | Not Applicable |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft Outlook Express 6 | Remote Code Execution | Critical | Not Applicable |
| Windows Server 2003 Service Pack 1 | Microsoft Outlook Express 6 | Remote Code Execution | Critical | Not Applicable |
| Windows Server 2003 Service Pack 2 | Microsoft Outlook Express 6 | Remote Code Execution | Critical | Not Applicable |
| Windows Server 2003 x64 Edition | Microsoft Outlook Express 6 | Remote Code Execution | Critical | Not Applicable |
| Windows Server 2003 x64 Edition Service Pack 2 | Microsoft Outlook Express 6 | Remote Code Execution | Critical | Not Applicable |
| Windows Server 2003 with SP1 for Itanium-based Systems | Microsoft Outlook Express 6 | Remote Code Execution | Critical | Not Applicable |
| Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft Outlook Express 6 | Remote Code Execution | Critical | Not Applicable |
| Windows Vista | Windows Mail | Remote Code Execution | Important | Not Applicable |
| Windows Vista x64 Edition | Windows Mail | Remote Code Execution | Important | Not Applicable |
Frequently Asked Questions (FAQ) Related to This Security Update
Why did Microsoft reissue this bulletin on October 10, 2007?
Windows XP Professional x64 Edition has been added to the “Affected Software” section. This change only affects the bulletin text and does not affect the security update itself. Customers who have already installed this update will not need to reapply it. When initially published, existing detection and deployment tools (EST, MBSA 2.0.1, SMS 2.0 with EST and SMS 2003) correctly offered this package for Windows XP Professional x64 Edition.
I am using an older version or edition 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 versions or editions are affected. Other versions or editions are past their support life cycle. To determine the support life cycle for your software versions or editions, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older versions or editions of the software to migrate to supported versions or editions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit the Microsoft Product Support Services Web site.
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, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | Network News Transfer Protocol Memory Corruption Vulnerability - CVE-2007-3897 |
|---|---|
| Windows 2000 | |
| Outlook Express 5.5 Service Pack 2 on Microsoft Windows 2000 Service Pack 4 | Critical Remote Code Execution |
| Outlook Express 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4 | Critical Remote Code Execution |
| Windows XP | |
| Outlook Express 6 on Windows XP Service Pack 2 | Critical Remote Code Execution |
| Outlook Express 6 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution |
| Windows Server | |
| Outlook Express 6 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Critical Remote Code Execution |
| Outlook Express 6 on Windows Server 2003 x64 Edition and Outlook Express 6 on Windows Server 2003 x64 Edition Service Pack 2 | Critical Remote Code Execution |
| Outlook Express 6 on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Critical Remote Code Execution |
| Windows Vista | |
| Windows Mail in Windows Vista | Important Remote Code Execution |
| Windows Mail in Windows Vista x64 Edition | Important Remote Code Execution |
Network News Transfer Protocol Memory Corruption Vulnerability - CVE-2007-3897
A remote code execution vulnerability exists in Outlook Express and Windows Mail for Microsoft Vista, due to an incorrectly handled malformed NNTP response. An attacker could exploit the vulnerability by constructing a specially crafted Web page. If a user viewed the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-3897.
Mitigating Factors for Network News Transfer Protocol Memory Corruption Vulnerability - CVE-2007-3897
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, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers 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 persuade 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.
- 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.
- Internet Explorer 7 Protect Mode on Microsoft Windows Vista displays a warning dialogue that a Web page is attempting to access Windows Mail. The user would have to click allow before the vulnerability could be exploited.
Workarounds for Network News Transfer Protocol Memory Corruption - CVE-2007-3897
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 news protocol handler.
You can disable the news protocol handler by removing the application associated with it in the registry.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\news\shell\open\command]
@=""[HKEY_CLASSES_ROOT\snews\shell\open\command]
@=""You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:
Impact of workaround: This workaround removes the associated application that is used to run NNTP.
Remove News Accounts.
Removing all registered news accounts in Outlook Express or Windows Mail client.
- In Windows Mail or Outlook Express select the Tools menu and then Accounts
- Select a News account and click remove then OK or Yes
- Repeat step 2 for all News accounts
**Impact of workaround:**Removing newsgroups that have been registered will make them unavailable for use unless you reregister them again.
FAQ for Network News Transfer Protocol Memory Corruption - CVE-2007-3897
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged on user.
What causes the vulnerability?
The vulnerability is present due to incorrect handling of malformed responses in the Network News Transfer Protocol (NNTP).
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the logged on user.
How could an attacker exploit the vulnerability?
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability and then convince a user to view the Web site. This can also include Web sites that accept user-provided content or advertisements, Web sites that host user-provided content or advertisements, and compromised Web sites. These Web sites could contain specially crafted content that could exploit this vulnerability. In no case, however, would an attacker have a 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 in an Instant Messenger request that takes users to the attacker's Web site.
What systems are primarily at risk from the vulnerability?
These vulnerabilities require that a user is logged on and visits a Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from these vulnerabilities.
What does the update do?
The update removes the vulnerability by changing the news client to handle malformed responses correctly.
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.
Update Information
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). For more information, see Microsoft Knowledge Base Article 910723.
Microsoft Baseline Security Analyzer and Enterprise Update Scan Tool (EST)
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.
MBSA 1.2.1 does not support detection for this security update. The Enterprise Update Scan Tool does, and is what customers can use instead of MBSA 1.2.1. For download links and more information about the version of EST that is being released this month, see Microsoft Knowledge Base Article 894193. SMS customers should also see the heading, Systems Management Server, for more information about SMS and EST.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA 1.2.1 | Enterprise Update Scan Tool (EST) | MBSA 2.0.1 |
|---|---|---|---|
| Outlook Express 6 on Windows XP Service Pack 2 | No | Yes | Yes |
| Outlook Express 6 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes |
| Outlook Express 5.5 Service Pack 2 on Microsoft Windows 2000 Service Pack 4 | No | Yes | Yes |
| Outlook Express 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4 | No | Yes | Yes |
| Outlook Express 6 on Windows Server 2003 Service Pack 1 | No | Yes | Yes |
| Outlook Express 6 on Windows Server 2003 Service Pack 2 | No | Yes | Yes |
| Outlook Express 6 on Windows Server 2003 x64 Edition | No | No | Yes |
| Outlook Express 6 on Windows Server 2003 with SP1 on Itanium-based Systems and Microsoft Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes |
| Windows Mail in Windows Vista | No | No | See Note for Windows Vista below |
| Windows Mail in Windows Vista x64 Edition | No | No | See Note for Windows Vista below |
Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on systems that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based system remotely. For additional information about MBSA support for Windows Vista, visit the Microsoft Baseline Security Analyzer. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.
For more information about MBSA, visit the Microsoft Baseline Security Analyzer. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the 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 |
|---|---|---|
| Outlook Express 6 on Windows XP Service Pack 2 | Yes (with EST) | Yes |
| Outlook Express 6 on Microsoft Windows XP Professional x64 Edition and Microsoft Windows XP Professional x64 Edition Service Pack 2 | Yes (with EST) | Yes |
| Outlook Express 5.5 Service Pack 2 on Microsoft Windows 2000 Service Pack 4 | Yes (with EST) | Yes |
| Outlook Express 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4 | Yes (with EST) | Yes |
| Outlook Express 6 on Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 | Yes (with EST) | Yes |
| Outlook Express 6 on Microsoft Windows Server 2003 x64 Edition | Yes (with EST) | Yes |
| Outlook Express 6 Microsoft Windows Server 2003 on Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems | Yes (with EST) | Yes |
| Windows Mail on Microsoft Windows Vista | No | See Note for Windows Vista below |
| Windows Mail on Microsoft Windows Vista x64 Edition | No | See Note for Windows Vista below |
SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation listed earlier relating to programs that MBSA 1.2.1 does not detect.
For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Knowledge Base Article 894154. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
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, visit SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
Note for Windows VistaMicrosoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.
For more information about SMS, visit the SMS Web site.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Outlook Express 6 on Windows XP
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 | Windowsxp-kb941202-x86-enu /quiet |
| Installing without restarting | Windowsxp-kb941202-x86-enu /norestart |
| Update log file | KB941202.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
| Hotpatching | Not applicable |
| Removal Information | To remove this security update, use the Add or Remove Programs tool in Control Panel.System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%$NTUninstallKB941202$\Spuninst folder. |
| File Information | See the heading, File Information, below for the full file manifest. |
| Registry Key Verification | For all supported versions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB941202\Filelist |
| For all supported versions of Windows XP Professional x64 Edition:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB941202\Filelist |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all supported 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Inetcomm.dll | 6.0.2900.3198 | 21-Aug-2007 | 06:15 | 683,520 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
For all supported x64-based editions of Windows XP Professional:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Inetcomm.dll | 6.0.3790.4133 | 17-Aug-2007 | 20:51 | 1,179,136 | x64 | |
| Winetcomm.dll | 6.0.3790.4133 | 17-Aug-2007 | 20:51 | 694,784 | x86 | WOW |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the 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 Package installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the system 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 system 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 system will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display 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 system 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. For more information about the Package installer, visit the Microsoft TechNet Web site.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the system 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 system 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 system will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the system 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 versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Outlook Express 6 Service Pack 1 and Outlook Express 5.5 Service Pack 2 on Microsoft Windows 2000 Service Pack 4
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 | OE6.0sp1-KB941202-Windows2000-x86-ENU /quiet\ \ OE5.5sp2-KB941202-Windows2000-x86-ENU /quiet |
| Installing without restarting | OE6.0sp1-KB941202-Windows2000-x86-ENU /norestart\ \ OE5.5sp2-KB941202-Windows2000-x86-ENU /norestartt |
| Update log file | KB941202.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
| Removal Information | To remove this security update, use the Add or Remove Programs tool in Control Panel.\ \ System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%$NTUninstallKB941202$\Spuninst folder. |
| File Information | See the heading, File Information, below for the full file manifest |
| Registry Key Verification | For all supported and affected versions of Outlook Express 5.5 Service Pack 2 on Windows 2000 Service Pack 4:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Outlook Express 5.50\SP2\KB941202-OE55SP2-20070820.120000\Filelist\ \ For all supported and affected versions of Outlook Express 6 Service Pack 1 on Windows 2000 Service Pack 4:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Outlook Express 6\SP1\KB941202-OE6SP1-20070820.120000\Filelist |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For Outlook Express 6.0 Service Pack 1 on Windows 2000 Service pack 4:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| directdb.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 75,776 |
| iecustom.dll | 6.0.2800.1585 | 14-Oct-2006 | 06:50 | 43,984 |
| inetcomm.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 596,992 |
| inetres.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 47,616 |
| msident.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:52 | 44,032 |
| msimn.exe | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 56,832 |
| msoe.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 1,176,064 |
| msoeacct.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 229,376 |
| msoeres.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 2,479,616 |
| msoert2.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 91,136 |
| oeimport.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 93,184 |
| oemig50.exe | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 55,808 |
| oemiglib.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 31,744 |
| wab.exe | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 42,496 |
| wab32.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 465,920 |
| wabfind.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 30,208 |
| wabimp.dll | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 77,824 |
| wabmig.exe | 6.0.2800.1914 | 20-Aug-2007 | 07:55 | 27,648 |
| iecustom.dll | 6.0.2800.1585 | 14-Oct-2006 | 06:50 | 43,984 |
For Outlook Express 5.5 Service Pack 2 on Windows 2000 Service pack 4:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| iecustom.dll | 6.0.2800.1585 | 14-Oct-2006 | 06:50 | 43,984 |
| inetcomm.dll | 5.50.4980.1600 | 16-Aug-2007 | 23:03 | 575,760 |
| msoe.dll | 5.50.4980.1600 | 16-Aug-2007 | 23:03 | 1,147,664 |
| wab.exe | 5.50.4980.1600 | 16-Aug-2007 | 23:03 | 20,752 |
| wab32.dll | 5.50.4980.1600 | 16-Aug-2007 | 23:03 | 452,368 |
| wabimp.dll | 5.50.4980.1600 | 16-Aug-2007 | 23:03 | 85,264 |
| iecustom.dll | 6.0.2800.1585 | 14-Oct-2006 | 06:50 | 43,984 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the 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 Package installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the system 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 system 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 system will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display 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 system 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. For more information about the Package installer, visit the Microsoft TechNet Web site.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the system 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 system 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 system will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the system 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 versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Outlook Express 6 on Windows Server 2003 (all versions and 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 | Windowsserver2003-kb941202-x86-enu /quiet |
| Installing without restarting | Windowsserver2003-kb941202-x86-enu /norestart |
| Update log file | KB941202.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
| Hot patching | This security update does not support HotPatching. For more information about Hot Patching see Microsoft Knowledge Base Article 897341. |
| Removal Information | To remove this update, use the Add or Remove Programs tool in Control Panel.\ \ System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%$NTUninstallKB941202$\Spuninst folder. |
| File Information | See the heading, File Information, below for the full file manifest |
| Registry Key Verification | For all supported and affected versions and editions of Windows Server 2003 Service Pack 1:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB941202\Filelist\ \ For all supported and affected versions and editions of Windows Server 2003 Service Pack 2:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB941202\Filelist |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all supported 32-bit editions of Windows Server 2003 Service pack 1:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Inetcomm.dll | 6.0.3790.2992 | 17-Aug-2007 | 07:49 | 686,592 |
For all supported 32-bit editions of Windows Server 2003 Service pack 2:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Inetcomm.dll | 6.0.3790.4133 | 16-Aug-2007 | 21:13 | 694,784 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
For all supported Itanium-based editions of Windows Server 2003 Service pack 1:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Inetcomm.dll | 6.0.3790.2992 | 17-Aug-2007 | 20:41 | 2,384,384 | IA-64 | |
| Winetcomm.dll | 6.0.3790.2992 | 17-Aug-2007 | 20:41 | 686,592 | x86 | WOW |
For all supported Itanium-based editions of Windows Server 2003 Service pack 2:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Inetcomm.dll | 6.0.3790.4133 | 17-Aug-2007 | 20:53 | 2,411,008 | IA-64 | |
| Winetcomm.dll | 6.0.3790.4133 | 17-Aug-2007 | 20:54 | 694,784 | x86 | WOW |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
For all supported x64-based editions of Windows Server 2003 Service pack 1:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Inetcomm.dll | 6.0.3790.2992 | 17-Aug-2007 | 20:41 | 1,165,824 | x64 | |
| Winetcomm.dll | 6.0.3790.2992 | 17-Aug-2007 | 20:41 | 686,592 | x86 | WOW |
For all supported x64-based editions of Windows Server 2003 Service pack 2:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Inetcomm.dll | 6.0.3790.4133 | 17-Aug-2007 | 20:51 | 1,179,136 | x64 | |
| Winetcomm.dll | 6.0.3790.4133 | 17-Aug-2007 | 20:51 | 694,784 | x86 | WOW |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the 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 Package installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the system 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 system 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 system will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display 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 system 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. For more information about the Package installer, visit the Microsoft TechNet Web site.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the system 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 system 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 system will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the system 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 versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Vista (all versions)
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 | Windows Mail and Windows Contacts in Windows Vista:\ Windows6.0-KB941202.msu /quiet |
| Installing without restarting | Windows Mail and Windows Contacts in Windows Vista:\ Windows6.0-KB941202.msu /norestart |
| Update log file | Windows6.0-KB941202-x86.msu |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart |
| Removal Information | To remove this update, click Control Panel, click Security, then under Windows Update, click View installed updates and select from the list of updates. |
| File Information | See the subsection, File Information, below for the full file manifest |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all supported 32-bit editions of Windows Vista:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| Inetcomm.dll | 6.0.6000.16545 | 16-Aug-2007 | 02:14 | 737,792 | .\Windows6.0-KB941202-x86\x86_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.0.6000.16545_none_77a4aba05b8204c8 |
| Inetres.dll | 6.0.6000.16545 | 16-Aug-2007 | 01:14 | 84,480 | \Windows6.0-KB941202-x86\x86_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.0.6000.16545_none_77a4aba05b8204c8 |
| Inetcomm.dll | 6.0.6000.20662 | 16-Aug-2007 | 11:54 | 737,792 | .\Windows6.0-KB941202-x86\x86_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.0.6000.20662_none_7815a7b574b2906f |
| Inetres.dll | 6.0.6000.20662 | 16-Aug-2007 | 10:57 | 84,480 | .\Windows6.0-KB941202-x86\x86_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.0.6000.20662_none_7815a7b574b2906f |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
For all supported x64-based editions of Windows Vista:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| inetcomm.dll | 6.0.6000.16545 | 16-Aug-2007 | 10:22 | 996,352 | X64 | Windows6.0-KB941202-x64\amd64_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.0.6000.16545_none_d3c3472413df75fe |
| inetres.dll | 6.0.6000.16545 | 16-Aug-2007 | 08:42 | 84,480 | X64 | Windows6.0-KB941202-x64\amd64_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.0.6000.16545_none_d3c3472413df75fe |
| inetcomm.dll | 6.0.6000.20662 | 16-Aug-2007 | 19:56 | 996,352 | X64 | Windows6.0-KB941202-x64\amd64_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.0.6000.20662_none_d43443392d1001a5 |
| inetres.dll | 6.0.6000.20662 | 16-Aug-2007 | 18:19 | 84,480 | X64 | Windows6.0-KB941202-x64\amd64_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.0.6000.20662_none_d43443392d1001a5 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
When you install this security update, Windows checks to see if one or more of the files that are being updated on your system have previously been updated by a Windows hotfix. If you have previously installed a hotfix to update one of these files, the installer will apply the LDR version of this update. Otherwise, the installer will apply the GDR version of the update.
For more information about the installer, see Microsoft Knowledge Base Article 934307
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Note Because there are several versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided earlier in this section.
- You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided earlier in this section.
- Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Greg MacManus of VeriSign iDefense Labs for reporting the Network News Transfer Protocol Memory Corruption Vulnerability - CVE-2007-3897.
Support
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 (October 09, 2007): Bulletin published.
- V2.0 (October 10, 2007): Bulletin revised to include Windows XP Professional x64 Edition in the "Affected Software" section; Known Issues set to none; Corrected missing file information to the bulletin text for Outlook Express 6.0 Service Pack 1 on Windows 2000 Service pack 4 and Outlook Express 5.5 Service Pack 2 on Windows 2000 Service pack 4.
Built at 2014-04-18T13:49:36Z-07:00