Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS05-026 - Critical

Vulnerability in HTML Help Could Allow Remote Code Execution (896358)

Published: June 14, 2005 | Updated: April 10, 2007

Version: 1.2

Summary

Who should read this document: Customers who use Microsoft Windows

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately.

Security Update Replacement: This bulletin replaces several prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list.

Caveats: Microsoft Knowledge Base Article 896358 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 896358.

Tested Software and Security Update Download Locations:

Affected Software:

  • Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4 – Download the update
  • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 – Download the update
  • Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) – Download the update
  • Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) – Download the update
  • Microsoft Windows XP Professional x64 Edition – Download the update
  • Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 – Download the update
  • Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems – Download the update
  • Microsoft Windows Server 2003 x64 Edition – Download the update
  • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems.

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

General Information

Executive Summary:

This update resolves a newly-discovered, privately-reported vulnerability. A vulnerability exists in HTML Help that could allow remote code execution on an affected system. The vulnerability is documented in the “Vulnerability Details” section of this bulletin.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityWindows 98, 98 SE, MEWindows 2000Windows XP Service Pack 1Windows XP Service Pack 2Windows Server 2003Windows Server 2003 Service Pack 1
HTML Help Vulnerability - CAN-2005-1208Remote Code ExecutionCriticalCriticalCriticalCriticalCriticalImportant

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:

  • The Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) severity rating is the same as the Windows XP Service Pack 1 severity rating.
  • The Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) severity rating is the same as the Windows XP Service Pack 1 severity rating.
  • The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
  • The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
  • The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
  • The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.

What updates does this release replace?
This security update replaces several prior security updates. The security bulletin IDs and affected operating systems are listed in the following table.

Bulletin IDWindows 2000Windows XPWindows Server 2003
MS02-055ReplacedReplacedNot Applicable
MS03-044ReplacedReplacedReplaced
MS04-023ReplacedReplacedReplaced
MS05-001ReplacedReplacedReplaced

What are the known issues that customers may experience when they install this security update?
Microsoft Knowledge Base Article 896358 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 896358.

Does this update contain any security-related changes to functionality?
Yes. Besides the changes that are listed in the “Vulnerability Details” section of this bulletin, this update includes several security changes.

This security update restricts the use of the InfoTech protocol (ms-its, its, mk:@msitstore) from processing content that is served from outside the Local Machine zone. This change may prevent certain kinds of Web-based applications from functioning correctly. To resolve this issue, the user or administrator can selectively enable this ability on a site-by-site basis. Alternatively, they can enable this ability based on the zone. Examples of zones include the Local intranet zone and the Trusted sites zone. This change is consistent with the default setting for this protocol in Windows Server 2003 Service Pack 1.

For more information about how to allow the use of the InfoTech protocol to process content from sites outside the Local Machine Zone, see Microsoft Knowledge Base Article 896054.

Microsoft Knowledge Base Article 896358 also contains deployment suggestions for mitigating application compatibility issues you many encounter with this security update.

Can I enable the InfoTech protocol to process content outside the Local Machine zone?
Yes. You can enable the InfoTech protocol to process content outside the Local Machine zone. You can allow specific sites or security zones to use this protocol. To do this, follow the steps to enable this behavior, as documented in Microsoft Knowledge Base Article 896054.

How does the extended support for Windows 98, Windows 98 Second Edition, and Windows Millennium Edition affect the release of security updates for these operating systems?
Microsoft will only release security updates for critical security issues. Non-critical security issues are not offered during this support period. For more information about the Microsoft Support Lifecycle policies for these operating systems, visit the following Web site.

For more information about severity ratings, visit the following Web site.

Note Critical security updates for these operating systems may not be available at the same time as the other security updates are included with this security bulletin. They will be made available as soon as possible following the release. When these security updates are available, you will be able to download them only from the Windows Update Web site.

Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?
Yes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. Critical security updates for these platforms may not be available concurrently with the other security updates provided as part of this security bulletin. They will be made available as soon as possible following the release. When these security updates are available, you will be able to download them only from the Windows Update Web site. For more information about severity ratings, visit the following Web site.

Note Updates for localized versions of Microsoft Windows Millennium Edition that are not supported by Windows Update are available for download at the following download locations:

Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. I’m still using one of these operating systems, what should I do?

Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, and Windows 2000 Service Pack 2 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require additional support for Windows NT 4.0 SP6a 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.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
Yes. MBSA will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site.

The Security Update Inventory Tool is required for detecting Microsoft Windows and other affected Microsoft products. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.

HTML Help Vulnerability - CAN-2005-1208:

A remote code execution vulnerability exists in HTML Help that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.

Mitigating Factors for HTML Help Vulnerability - CAN-2005-1208:

  • Windows Server 2003 Service Pack 1 restricts the InfoTech protocol (ms-its, its, mk:@msitstore) from processing content that is served from outside the Local Machine zone. This change helps prevent remote attacks from the Internet zone and reduces the severity of this issue on Windows Server 2003 Service Pack 1 systems.
  • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker could also try to compromise a Web site to have it deliver a Web page that has malicious content to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site or to a site that has been compromised by the attacker.
  • 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.
  • By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally, Outlook 98 and Outlook 2000 open HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability.

    The risk of attack from the HTML e-mail vector can be significantly reduced if you meet all the following conditions:

    • Apply the update that is included with Microsoft Security Bulletin MS03-040 or a later Cumulative Security Update for Internet Explorer.
    • Use Internet Explorer 6 or a later version.
    • Use the Microsoft Outlook E-mail Security Update, use Microsoft Outlook Express 6 or a later version, or use Microsoft Outlook 2000 Service Pack 2 or a later version in its default configuration.

Workarounds for HTML Help Vulnerability - CAN-2005-1208:

Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.

  • Unregister HTML Help InfoTech Protocol

    To help reduce the likelihood of a remote attack you can unregister the HTML Help InfoTech protocol. Follow these steps to unregister this protocol:

    1. Click Start, click Run, type "regsvr32 /u %windir%\system32\itss.dll" (without the quotation marks), and then click OK.

      Note On Windows 98 and Windows Millennium Edition, replace "system32" with "system" in this command.

    2. A dialog box appears and confirms that the unregistration process has succeeded. Click OK to close the dialog box.

      Impact of Workaround: All HTML Help functionality will be unavailable. This will affect the online Help in Windows or in any application that uses HTML Help functionality.

FAQ for HTML Help Vulnerability - CAN-2005-1208:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. If a user is logged on with administrative privileges, 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 privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.

What causes the vulnerability?
The vulnerability occurs because HTML Help does not completely validate input data.

What is HTML Help?
Microsoft HTML Help is the standard help system for the Windows platform. Authors can use HTML Help to create online Help files for a software application or to create content for a multimedia title or for a Web site. For more information about how to create online Help files, visit the following Web site.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

Who could exploit the vulnerability?
Any anonymous attacker who could display a specially crafted Web page to a user could attempt to exploit this vulnerability.

In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. It could also be possible to display malicious Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user view Web sites for an attack to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to visit Web sites, such as most server systems, are at a reduced risk.

Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
Yes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. A critical security update for these platforms is available and is provided as part of this security bulletin and can be downloaded from the Windows Update Web site. For more information about severity ratings, visit the following Web site.

What does the update do?
The update removes the vulnerability by modifying the way that HTML Help validates data.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

How does this vulnerability relate to the HTML Help vulnerability that is addressed by MS05-001?
Both vulnerabilities were in HTML Help. However, this update addresses a new vulnerability that was not addressed as part of MS05-001. MS05-001 helps protect against the vulnerability that is discussed in that bulletin, but does not address this new vulnerability.

Affected Software:

For information about the specific security update for your affected software, click the appropriate link:

Windows Server 2003 (all versions)

Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.

Inclusion in Future Service Packs:
The update for this issue will be included in future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/integrate:pathIntegrates 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
/EREnables extended error reporting
/verboseEnables 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 Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb896358-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB896358.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb896358-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.

Restart Requirement

This update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

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%\$NTUninstallKB896358$\Spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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 switches.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files

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.

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with SP1:

File NameVersionDateTimeSizeFolder
Hh.exe5.2.3790.31522-Apr-200501:5610,752RTMGDR
Hhctrl.ocx5.2.3790.31522-Apr-200507:16519,168RTMGDR
Hhsetup.dll5.2.3790.31522-Apr-200507:1638,912RTMGDR
Itircl.dll5.2.3790.31522-Apr-200507:16143,872RTMGDR
Itss.dll5.2.3790.31522-Apr-200507:16128,000RTMGDR
Hh.exe5.2.3790.31522-Apr-200501:4510,752RTMQFE
Hhctrl.ocx5.2.3790.31522-Apr-200507:22519,168RTMQFE
Hhsetup.dll5.2.3790.31522-Apr-200507:2238,912RTMQFE
Itircl.dll5.2.3790.31522-Apr-200507:22143,872RTMQFE
Itss.dll5.2.3790.31522-Apr-200507:22128,000RTMQFE
Hh.exe5.2.3790.242722-Apr-200501:3710,752SP1GDR
Hhctrl.ocx5.2.3790.242722-Apr-200506:59546,304SP1GDR
Hhsetup.dll5.2.3790.242722-Apr-200506:5941,472SP1GDR
Itircl.dll5.2.3790.242722-Apr-200506:59155,136SP1GDR
Itss.dll5.2.3790.242722-Apr-200506:59137,216SP1GDR
Hh.exe5.2.3790.242722-Apr-200501:3310,752SP1QFE
Hhctrl.ocx5.2.3790.242722-Apr-200506:57546,304SP1QFE
Hhsetup.dll5.2.3790.242722-Apr-200506:5741,472SP1QFE
Itircl.dll5.2.3790.242722-Apr-200506:57155,136SP1QFE
Itss.dll5.2.3790.242722-Apr-200506:57137,216SP1QFE

Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:

File NameVersionDateTimeSizeCPUFolder
Hh.exe5.2.3790.31522-Apr-200515:1713,824IA-64RTMGDR
Hhctrl.ocx5.2.3790.31522-Apr-200515:171,550,336IA-64RTMGDR
Hhsetup.dll5.2.3790.31522-Apr-200515:17104,448IA-64RTMGDR
Itircl.dll5.2.3790.31522-Apr-200515:17614,400IA-64RTMGDR
Itss.dll5.2.3790.31522-Apr-200515:17374,272IA-64RTMGDR
Whh.exe5.2.3790.31522-Apr-200515:1710,752x86RTMGDR\WOW
Whhctrl.ocx5.2.3790.31522-Apr-200515:17519,168x86RTMGDR\WOW
Whhsetup.dll5.2.3790.31522-Apr-200515:1738,912x86RTMGDR\WOW
Witircl.dll5.2.3790.31522-Apr-200515:17143,872x86RTMGDR\WOW
Witss.dll5.2.3790.31522-Apr-200515:17128,000x86RTMGDR\WOW
Hh.exe5.2.3790.31522-Apr-200515:1713,824IA-64RTMQFE
Hhctrl.ocx5.2.3790.31522-Apr-200515:171,550,336IA-64RTMQFE
Hhsetup.dll5.2.3790.31522-Apr-200515:17104,448IA-64RTMQFE
Itircl.dll5.2.3790.31522-Apr-200515:17614,400IA-64RTMQFE
Itss.dll5.2.3790.31522-Apr-200515:17374,272IA-64RTMQFE
Whh.exe5.2.3790.31522-Apr-200515:1710,752x86RTMQFE\WOW
Whhctrl.ocx5.2.3790.31522-Apr-200515:17519,168x86RTMQFE\WOW
Whhsetup.dll5.2.3790.31522-Apr-200515:1738,912x86RTMQFE\WOW
Witircl.dll5.2.3790.31522-Apr-200515:17143,872x86RTMQFE\WOW
Witss.dll5.2.3790.31522-Apr-200515:17128,000x86RTMQFE\WOW
Hh.exe5.2.3790.242722-Apr-200515:1715,360IA-64SP1GDR
Hhctrl.ocx5.2.3790.242722-Apr-200515:171,721,856IA-64SP1GDR
Hhsetup.dll5.2.3790.242722-Apr-200515:17119,808IA-64SP1GDR
Itircl.dll5.2.3790.242722-Apr-200515:17684,544IA-64SP1GDR
Itss.dll5.2.3790.242722-Apr-200515:17420,864IA-64SP1GDR
Whh.exe5.2.3790.242722-Apr-200515:1710,752x86SP1GDR\WOW
Whhctrl.ocx5.2.3790.242722-Apr-200515:17546,304x86SP1GDR\WOW
Whhsetup.dll5.2.3790.242722-Apr-200515:1741,472x86SP1GDR\WOW
Witircl.dll5.2.3790.242722-Apr-200515:17155,136x86SP1GDR\WOW
Witss.dll5.2.3790.242722-Apr-200515:17137,216x86SP1GDR\WOW
Hh.exe5.2.3790.242722-Apr-200515:1715,360IA-64SP1QFE
Hhctrl.ocx5.2.3790.242722-Apr-200515:171,721,856IA-64SP1QFE
Hhsetup.dll5.2.3790.242722-Apr-200515:17119,808IA-64SP1QFE
Itircl.dll5.2.3790.242722-Apr-200515:17684,544IA-64SP1QFE
Itss.dll5.2.3790.242722-Apr-200515:17420,864IA-64SP1QFE
Whh.exe5.2.3790.242722-Apr-200515:1710,752x86SP1QFE\WOW
Whhctrl.ocx5.2.3790.242722-Apr-200515:17546,304x86SP1QFE\WOW
Whhsetup.dll5.2.3790.242722-Apr-200515:1741,472x86SP1QFE\WOW
Witircl.dll5.2.3790.242722-Apr-200515:17155,136x86SP1QFE\WOW
Witss.dll5.2.3790.242722-Apr-200515:17137,216x86SP1QFE\WOW

Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:

File NameVersionDateTimeSizeCPUFolder
Hh.exe5.2.3790.243502-May-200516:2712,288x64SP1GDR
Hhctrl.ocx5.2.3790.243502-May-200516:27859,136x64SP1GDR
Hhsetup.dll5.2.3790.243502-May-200516:2779,872x64SP1GDR
Itircl.dll5.2.3790.243502-May-200516:27264,192x64SP1GDR
Itss.dll5.2.3790.243502-May-200516:27213,504x64SP1GDR
Whh.exe5.2.3790.243502-May-200516:2710,752x86SP1GDR\WOW
Whhctrl.ocx5.2.3790.243502-May-200516:27546,304x86SP1GDR\WOW
Whhsetup.dll5.2.3790.243502-May-200516:2741,472x86SP1GDR\WOW
Witircl.dll5.2.3790.243502-May-200516:27155,136x86SP1GDR\WOW
Witss.dll5.2.3790.243502-May-200516:27137,216x86SP1GDR\WOW
Hh.exe5.2.3790.243502-May-200516:2812,288x64SP1QFE
Hhctrl.ocx5.2.3790.243502-May-200516:28859,136x64SP1QFE
Hhsetup.dll5.2.3790.243502-May-200516:2879,872x64SP1QFE
Itircl.dll5.2.3790.243502-May-200516:28264,192x64SP1QFE
Itss.dll5.2.3790.243502-May-200516:28213,504x64SP1QFE
Whh.exe5.2.3790.243502-May-200516:2810,752x86SP1QFE\WOW
Whhctrl.ocx5.2.3790.243502-May-200516:28546,304x86SP1QFE\WOW
Whhsetup.dll5.2.3790.243502-May-200516:2841,472x86SP1QFE\WOW
Witircl.dll5.2.3790.243502-May-200516:28155,136x86SP1QFE\WOW
Witss.dll5.2.3790.243502-May-200516:28137,216x86SP1QFE\WOW

Note When you install this security update on Windows Server 2003, 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 an affected file, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system.

For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe 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.

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 version of the operating system or programs installed, 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 computer 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 following registry keys.

    Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB896358\Filelist

    Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 896358 security update into the Windows installation source files.

Windows XP (all versions)

Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.

Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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 switches.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not backup files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/integrate:pathIntegrates 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
/EREnables extended error reporting
/verboseEnables 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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:

Windowsxp-kb896358-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB896358.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:

Windowsxp-kb896358-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.

Restart Requirement

This update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

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%\$NTUninstallKB896358$\Spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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 switches.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files

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.

Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

File NameVersionDateTimeSizeFolder
Hh.exe5.2.3790.31525-May-200522:4410,752SP1QFE
Hhctrl.ocx5.2.3790.31527-May-200501:59519,168SP1QFE
Hhsetup.dll5.2.3790.31527-May-200501:5938,912SP1QFE
Itircl.dll5.2.3790.31527-May-200501:59143,872SP1QFE
Itss.dll5.2.3790.31527-May-200501:59128,000SP1QFE
Hh.exe5.2.3790.245326-May-200523:2210,752SP2GDR
Hhctrl.ocx5.2.3790.245327-May-200502:04546,304SP2GDR
Hhsetup.dll5.2.3790.245327-May-200502:0441,472SP2GDR
Itircl.dll5.2.3790.245327-May-200502:04155,136SP2GDR
Itss.dll5.2.3790.245327-May-200502:04137,216SP2GDR
Hh.exe5.2.3790.245326-May-200523:2610,752SP2QFE
Hhctrl.ocx5.2.3790.245327-May-200502:08546,304SP2QFE
Hhsetup.dll5.2.3790.245327-May-200502:0841,472SP2QFE
Itircl.dll5.2.3790.245327-May-200502:08155,136SP2QFE
Itss.dll5.2.3790.245327-May-200502:08137,216SP2QFE

Windows XP 64-Bit Edition Service Pack 1 (Itanium):

File NameVersionDateTimeSizeCPUFolder
Hh.exe5.2.3790.31528-Apr-200523:3213,824IA-64SP1QFE
Hhctrl.ocx5.2.3790.31527-May-200501:591,550,336IA-64SP1QFE
Hhsetup.dll5.2.3790.31527-May-200501:59104,448IA-64SP1QFE
Itircl.dll5.2.3790.31527-May-200501:59614,400IA-64SP1QFE
Itss.dll5.2.3790.31527-May-200501:59374,272IA-64SP1QFE
Whh.exe5.2.3790.31525-May-200522:4410,752x86SP1QFE\WOW
Whhctrl.ocx5.2.3790.31527-May-200501:59519,168x86SP1QFE\WOW
Whhsetup.dll5.2.3790.31527-May-200501:5938,912x86SP1QFE\WOW
Witircl.dll5.2.3790.31527-May-200501:59143,872x86SP1QFE\WOW
Witss.dll5.2.3790.31527-May-200501:59128,000x86SP1QFE\WOW

Windows XP 64-Bit Edition Version 2003 (Itanium):

File NameVersionDateTimeSizeCPUFolder
Hh.exe5.2.3790.31522-Apr-200515:1713,824IA-64RTMGDR
Hhctrl.ocx5.2.3790.31522-Apr-200515:171,550,336IA-64RTMGDR
Hhsetup.dll5.2.3790.31522-Apr-200515:17104,448IA-64RTMGDR
Itircl.dll5.2.3790.31522-Apr-200515:17614,400IA-64RTMGDR
Itss.dll5.2.3790.31522-Apr-200515:17374,272IA-64RTMGDR
Whh.exe5.2.3790.31522-Apr-200515:1710,752x86RTMGDR\WOW
Whhctrl.ocx5.2.3790.31522-Apr-200515:17519,168x86RTMGDR\WOW
Whhsetup.dll5.2.3790.31522-Apr-200515:1738,912x86RTMGDR\WOW
Witircl.dll5.2.3790.31522-Apr-200515:17143,872x86RTMGDR\WOW
Witss.dll5.2.3790.31522-Apr-200515:17128,000x86RTMGDR\WOW
Hh.exe5.2.3790.31522-Apr-200515:1713,824IA-64RTMQFE
Hhctrl.ocx5.2.3790.31522-Apr-200515:171,550,336IA-64RTMQFE
Hhsetup.dll5.2.3790.31522-Apr-200515:17104,448IA-64RTMQFE
Itircl.dll5.2.3790.31522-Apr-200515:17614,400IA-64RTMQFE
Itss.dll5.2.3790.31522-Apr-200515:17374,272IA-64RTMQFE
Whh.exe5.2.3790.31522-Apr-200515:1710,752x86RTMQFE\WOW
Whhctrl.ocx5.2.3790.31522-Apr-200515:17519,168x86RTMQFE\WOW
Whhsetup.dll5.2.3790.31522-Apr-200515:1738,912x86RTMQFE\WOW
Witircl.dll5.2.3790.31522-Apr-200515:17143,872x86RTMQFE\WOW
Witss.dll5.2.3790.31522-Apr-200515:17128,000x86RTMQFE\WOW
Hh.exe5.2.3790.242722-Apr-200515:1715,360IA-64SP1GDR
Hhctrl.ocx5.2.3790.242722-Apr-200515:171,721,856IA-64SP1GDR
Hhsetup.dll5.2.3790.242722-Apr-200515:17119,808IA-64SP1GDR
Itircl.dll5.2.3790.242722-Apr-200515:17684,544IA-64SP1GDR
Itss.dll5.2.3790.242722-Apr-200515:17420,864IA-64SP1GDR
Whh.exe5.2.3790.242722-Apr-200515:1710,752x86SP1GDR\WOW
Whhctrl.ocx5.2.3790.242722-Apr-200515:17546,304x86SP1GDR\WOW
Whhsetup.dll5.2.3790.242722-Apr-200515:1741,472x86SP1GDR\WOW
Witircl.dll5.2.3790.242722-Apr-200515:17155,136x86SP1GDR\WOW
Witss.dll5.2.3790.242722-Apr-200515:17137,216x86SP1GDR\WOW
Hh.exe5.2.3790.242722-Apr-200515:1715,360IA-64SP1QFE
Hhctrl.ocx5.2.3790.242722-Apr-200515:171,721,856IA-64SP1QFE
Hhsetup.dll5.2.3790.242722-Apr-200515:17119,808IA-64SP1QFE
Itircl.dll5.2.3790.242722-Apr-200515:17684,544IA-64SP1QFE
Itss.dll5.2.3790.242722-Apr-200515:17420,864IA-64SP1QFE
Whh.exe5.2.3790.242722-Apr-200515:1710,752x86SP1QFE\WOW
Whhctrl.ocx5.2.3790.242722-Apr-200515:17546,304x86SP1QFE\WOW
Whhsetup.dll5.2.3790.242722-Apr-200515:1741,472x86SP1QFE\WOW
Witircl.dll5.2.3790.242722-Apr-200515:17155,136x86SP1QFE\WOW
Witss.dll5.2.3790.242722-Apr-200515:17137,216x86SP1QFE\WOW

Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
Hh.exe5.2.3790.243502-May-200516:2712,288x64SP1GDR
Hhctrl.ocx5.2.3790.243502-May-200516:27859,136x64SP1GDR
Hhsetup.dll5.2.3790.243502-May-200516:2779,872x64SP1GDR
Itircl.dll5.2.3790.243502-May-200516:27264,192x64SP1GDR
Itss.dll5.2.3790.243502-May-200516:27213,504x64SP1GDR
Whh.exe5.2.3790.243502-May-200516:2710,752x86SP1GDR\WOW
Whhctrl.ocx5.2.3790.243502-May-200516:27546,304x86SP1GDR\WOW
Whhsetup.dll5.2.3790.243502-May-200516:2741,472x86SP1GDR\WOW
Witircl.dll5.2.3790.243502-May-200516:27155,136x86SP1GDR\WOW
Witss.dll5.2.3790.243502-May-200516:27137,216x86SP1GDR\WOW
Hh.exe5.2.3790.243502-May-200516:2812,288x64SP1QFE
Hhctrl.ocx5.2.3790.243502-May-200516:28859,136x64SP1QFE
Hhsetup.dll5.2.3790.243502-May-200516:2879,872x64SP1QFE
Itircl.dll5.2.3790.243502-May-200516:28264,192x64SP1QFE
Itss.dll5.2.3790.243502-May-200516:28213,504x64SP1QFE
Whh.exe5.2.3790.243502-May-200516:2810,752x86SP1QFE\WOW
Whhctrl.ocx5.2.3790.243502-May-200516:28546,304x86SP1QFE\WOW
Whhsetup.dll5.2.3790.243502-May-200516:2841,472x86SP1QFE\WOW
Witircl.dll5.2.3790.243502-May-200516:28155,136x86SP1QFE\WOW
Witss.dll5.2.3790.243502-May-200516:28137,216x86SP1QFE\WOW

Notes The Windows XP security update is packaged as a dual-mode package. Dual-mode packages contain files for the original version of Windows XP Service Pack 1 (SP1) and files for Windows XP Service Pack 2 (SP2).

For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.

When you install these security updates, 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 an affected file, one of the following conditions occurs, depending on your operating system:

  • Windows XP SP2

    The installer copies the SP2QFE files to your system.
  • Windows XP 64-Bit Edition Version 2003 (Itanium)

    The installer copies the RTMQFE files to your system.

If you have not previously installed a hotfix to update an affected file, one of the following conditions occurs, depending on your operating system:

  • Windows XP SP2

    The installer copies the SP2GDR files to your system.
  • Windows XP 64-Bit Edition Version 2003 (Itanium)

    The installer copies the RTMGDR files to your system.

For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe 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.

Note For Windows XP 64-Bit Edition Version 2003 (Itanium), this security update is the same as the Windows Server 2003 for Itanium-based Systems security update. For Microsoft Windows XP Professional x64 Edition, this security update is the same as the Microsoft Windows Server 2003 x64 Edition security update.

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 version of the operating system or programs installed, 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 computer 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 following registry keys.

    For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB896358\Filelist

    For Windows XP 64-Bit Edition Version 2003 (Itanium):

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB896358\Filelist

    For Windows XP Professional x64

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB896358\Filelist

    Note These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 896358 security update into the Windows installation source files.

Windows 2000 (all versions)

Prerequisites
For Windows 2000, this security update requires Service Pack 3 (SP3) or Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).

The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.

Inclusion in Future Service Packs:
The update for this issue may be included in a future Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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 switches.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not backup files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/integrate:pathIntegrates 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
/EREnables extended error reporting
/verboseEnables 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. For more information about the Update.exe 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.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:

Windows2000-kb896358-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB896358.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:

Windows2000-kb896358-x86-enu /norestart

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.

Restart Requirement

This update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

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%\$NTUninstallKB896358$\Spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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 switches.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files

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.

Windows 2000 Service Pack 3, Windows 2000 Service Pack 4, and Small Business Server 2000:

File NameVersionDateTimeSize
Hh.exe5.2.3790.30915-Apr-200501:0810,752
Hhctrl.ocx5.2.3790.30915-Apr-200501:08519,168
Hhsetup.dll5.2.3790.30921-Apr-200514:1638,912
Itircl.dll5.2.3790.30921-Apr-200514:16143,872
Itss.dll5.2.3790.30921-Apr-200514:16128,000

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 version of the operating system or programs installed, 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 computer 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 following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB896358\Filelist

    Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 896358 security update into the Windows installation source files.

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

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.

Security Resources:

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.

Systems Management Server:

Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyze, Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

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 (June 14, 2005): Bulletin published
  • V1.1 (June 29, 2005): Bulletin “Security Update Information” section revised with updated details for the Windows XP x64 Professional Edition registry key verification information.
  • V1.2 (April 10, 2007): Bulletin supersedence table in the FAQ section revised to include MS02-055.

Built at 2014-04-02T23:59:26Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.