Microsoft Security Bulletin MS06-009: Vulnerability in the Korean Input Method Editor Could Allow Elevation of Privilege (901190)
Description: This update resolves a newly-discovered, privately-reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Click Here to Install Silverlight |
United States | Change | | | All Microsoft Sites |

| Search Microsoft.com for:

TechNet Home | | | TechCenters | | | Downloads | | | TechNet Program | | | Subscriptions | | | Security Bulletins | | | Archive |

Search for
TechNet Security Security Bulletin Search Products Guidance Tools Understanding Security Partners Downloads Community Events & Webcasts Virtual Labs Scripting for Security Small Business Security Midsize Business Security Additional Resources Events & Errors Knowledge Base Search | TechNet Home > TechNet Security > Bulletins # Microsoft Security Bulletin MS06-009 ## Vulnerability in the Korean Input Method Editor Could Allow Elevation of Privilege (901190) Published: February 14, 2006 | Updated: March 8, 2006 Version: 1.1 ### Summary Who should read this document: Customers who use Microsoft Windows or Microsoft Office 2003 Impact of Vulnerability: Elevation of Privilege Maximum Severity Rating: Important Recommendation: Customers should apply the update at the earliest opportunity. Security Update Replacement: This security update replaces MS06-003 specifically for the Korean version of the Microsoft Office 2003 Multilingual User Interface Pack. Caveats: None Tested Software and Security Update Download Locations: Affected Software:
• | Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 – 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 Office 2003 Software:
• | Microsoft Office 2003 Service Pack 1 and Service Pack 2 - Download the update (KB905645)
• | Microsoft Office 2003 Multilingual User Interface Packs – Download the update (KB905645)
• | Microsoft Office Visio 2003 Multilingual User Interface Packs – Download the update (KB909115)
• | Microsoft Office Project 2003 Multilingual User Interface Packs – Download the update (KB909118)
• | Microsoft Office 2003 Proofing Tools – Download the update (KB905645)
• | Microsoft Office Visio 2003 - Download the update (KB905645)
• | Microsoft Office OneNote 2003 - Download the update (KB905645)
• | Microsoft Office Project 2003 - Download the update (KB905645)
Note The security updates for Microsoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 x64 Edition also apply to Microsoft Windows Server 2003 R2. Note Only the Korean language versions of Windows are by default affected by this vulnerability. Customers running East Asian language versions of Windows have the affected component present on the system, but are only vulnerable if the Korean language IME is enabled. Customers running any other language version of Windows only need to take action if they have installed and enabled the Korean language IME. Note Only the Korean language versions of the listed Office 2003 products are affected, with the exception of Office 2003 Proofing Tools. Customers who have installed the Microsoft Office 2003 Proofing Tools product will need to install this security update even if they did not specifically install the Korean Proofing Tools component. When this security bulletin was issued, the most recent update for non-Korean versions of Microsoft Office 2003 Multilingual User Interface Pack was Microsoft Security Bulletin MS06-003. Non-Affected Software:
• | Microsoft Windows 2000 Service Pack 4
• | Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)
• | Microsoft Office XP Service Pack 3
• | Microsoft Office 2000 Service Pack 3
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. Top of section ## General Information
| ### Executive Summary
Executive Summary: This update resolves a newly-discovered, privately-reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin. 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. For an attack to be successful an attacker must be able to access the interactive logon screen on an affected system. We recommend that customers apply the update at the earliest opportunity. Severity Ratings and Vulnerability Identifiers:
Vulnerability Identifiers | Impact of Vulnerability | Microsoft Office 2003 Software | Windows XP Service Pack 1 | Windows XP Service Pack 2 | Windows Server 2003 | Windows Server 2003 Service Pack 1
Korean IME Vulnerability - CVE-2006-0008 | Elevation of Privilege | Important | Important | Important | Important | Important
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 Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 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.
Top of section
| ### Frequently asked questions (FAQ) related to this security update
Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required? Yes, but for local scans only. MBSA uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this issue. For more information about MBSA, visit the MBSA Web site. For more information about MBSA support, visit the Microsoft Baseline Security Analyzer 1.2 Q&A Web site. Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required? Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. 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 can be used by SMS for detecting security updates that are offered by Windows Update, that are supported by Software Update Services, and other security updates that are supported by MBSA 1.2.1. For more information about the Security Update Inventory Tool, see the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS for detecting security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, see the following Microsoft Web site. For more information about SMS, visit the SMS Web site. Top of section
| ### Vulnerability Details
| #### Korean IME Vulnerability - CVE-2006-0008:
A privilege elevation vulnerability exists in the Windows and Office Korean Input Method Editor (IME). This vulnerability could allow a malicious user to take complete control of an affected system. For an attack to be successful an attacker must be able to interactively logon to the affected system.
| ##### Mitigating Factors for Korean IME Vulnerability - CVE-2006-0008:
• | To exploit this vulnerability an attacker must have access to the system to perform an interactive logon, either locally or via a Remote Desktop Protocol (RDP) session.
• | Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
• | By default, RDP is not enabled on any operating system version. On Windows XP and Windows Server 2003, Remote Assistance can enable RDP. On Windows XP Media Center Edition, RDP is enabled if a Media Center Extender has been installed. For information about Media Center Extenders, visit the following Web site. On Small Business Server 2000 and on Windows Small Business Server 2003, RDP in enabled by default. However, by default, on Windows Small Business Server 2003 and earlier versions, the RDP Protocol communication ports are blocked from the Internet. RDP is available only on the local network unless Terminal Services or the Remote Web Workplace features have been enabled by using the Configure E-mail and Internet Connection Wizard (CEICW).
• | If Remote Desktop is manually enabled, the following Windows Firewall changes will occur, depending on the operating system version:
• | On Windows XP Service Pack 2 systems that have Windows Firewall enabled, enabling the Remote Desktop feature will automatically enable the Remote Desktop exception in the firewall, with the scope of All computers (including those on the Internet). When you disable Remote Desktop, this firewall exception is automatically disabled. On Windows XP Service Pack 1, Windows Server 2003, and Windows Server 2003 Service Pack 1, enabling the Remote Desktop Feature does not enable the Remote Desktop exception in the firewall. Enabling Remote Desktop causes a dialog box to appear that indicates that you must manually enable this exception. There is a Remote Desktop entry in the exception in the list of the firewall exceptions that a user would have to manually enable. Disabling Remote Desktop does not change the exception status in the firewall. However, although the system is no longer vulnerable to this issue through Remote Desktop, it could still be vulnerable through Remote Assistance and Terminal Services, where available.
Top of section
| ##### Workarounds for Korean IME Vulnerability - CVE-2006-0008:
Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known remote attack vectors. When a workaround reduces functionality, it is identified in the following section.
• | Disable Terminal Services, Remote Desktop, Remote Assistance, and Windows Small Business Server 2003 Remote Web Workplace if they are no longer required. If you no longer need these services on your system, consider disabling them as a security best practice. Disabling unused and unneeded services helps reduce your exposure to security vulnerabilities. For information about how to disable Remote Desktop manually, visit the following Web site. For information about how to disable Remote Desktop by using Group Policy, see the following Microsoft Knowledge Base Article. For information about Remote Assistance, including instructions on how to disable Remote Assistance manually and by using Group Policy, visit the following Web site. For information about how to disable the Windows Small Business Server 2003 Terminal Services and Remote Web Workplace features, visit the following Web site.
• | Block TCP port 3389 at the enterprise perimeter firewall. This port is used to initiate a connection with the affected component. Blocking it at the network perimeter firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. This can help protect networks from attacks that originate outside the enterprise perimeter. Blocking the affected ports at the enterprise perimeter is the best defense to help avoid Internet-based attacks. However, systems could still be vulnerable to attacks from within their enterprise perimeter. Additionally, on Windows XP and Windows Server 2003, Windows Firewall can help protect individual systems. By default, Windows Firewall does not allow connections to this port, except in Windows XP Service Pack 2 when the Remote Desktop feature is enabled. For information about how to disable the Windows Firewall exception for Remote Desktop on these platforms, visit the following Web site. If you cannot disable the Windows Firewall exception for Remote Desktop, you may be able to reduce the scope of this vulnerability by setting the default value of All computers (Including those on the Internet), to the local network. Doing this helps reduce the likelihood of attacks from the Internet. Note Windows Small Business Server 2003 uses a feature named Remote Web Workplace. This feature uses TCP port 4125 for RDP connections, but only once a user has been successfully authenticated. If you are using this feature, you should validate that this port is also blocked from the Internet in addition to port 3389. Note It is possible to manually change the affected components to use other ports. If you have performed these actions, you should also block those additional ports.
• | Help secure Remote Desktop connections by using an IPsec policy. Specific configurations would be dependent upon the individual environment. For information about Internet Protocol Security (IPsec), visit the following Web site. Detailed information about IPsec and about how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.
• | Help secure Remote Desktop connections by using a virtual private network (VPN) connection. Specific configurations depend on the individual environment. For information about Virtual Private Networks, visit the following Web site.
Top of section
| ##### FAQ for Korean IME Vulnerability - CVE-2006-0008:
What is the scope of the vulnerability? This is a privilege elevation vulnerability. 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. What causes the vulnerability? Under certain conditions, the Input Method Editor (IME) for the Korean language inappropriately exposes functionality that runs in the LocalSystem context. What is the Korean IME? IMEs help solve a problem associated with entering information in certain languages via a keyboard. Languages like Korean contain thousands of different characters, and it isn't feasible to build a keyboard that includes all of them. IMEs allow the characters to be built using a standard 101-key keyboard, by specifying the strokes that compose each character. An IME consists of an engine that converts keystrokes into phonetic and ideographic characters and a dictionary of commonly-used ideographic words. As the user enters keystrokes via the keyboard, the IME identifies the keystrokes and converts them into characters. Which IMEs are affected by this vulnerability? Only the Korean language IME is affected. All other languages' IMEs correctly identify when they're running as part of the logon screen and only expose the appropriate functions. Why Is Office 2003 also affected by the Korean IME vulnerability? Office 2003 as part of its multilingual capabilities can install its own Korean IME which overwrites the version of the Korean IME provided by the operating system. It is highly recommended that customers who have installed the Office 2003 Korean IME apply the Office security update in this security bulletin at the earliest opportunity. 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? Users who can access an affected system’s logon screen, either locally or remotely. How could an attacker exploit the vulnerability? A malicious user who could access the logon screen either locally or via Remote Desktop or Terminal Services on an affected system, could use this functionality to run code to take any desired action on the system. What systems are primarily at risk from the vulnerability? Workstations and terminal servers that have the Korean language IME installed are primarily at risk. Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by this vulnerability? No. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do not contain the affected component. Could the vulnerability be exploited over the Internet? Yes. An attacker could try to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet. Microsoft has provided information about how you can help protect your PC. End users can visit the Protect Your PC Web site. IT professionals can visit the TechNet Security Center Web site. What does the update do? The update removes the vulnerability by disabling the affected Korean IME functionality that runs in the LocalSystem context. 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. Top of section Top of section Top of section
| ### Security Update Information
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 a future service pack or update rollup. Installation Information This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch | Description
/help | Displays the command-line options
Setup Modes |
/passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options |
/norestart | Does not restart when installation has completed
/forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart | 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 computer shuts down
/log: path | Allows the redirection of installation log files
/integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] | Extracts files without starting the Setup program
/ER | Enables extended error reporting
/verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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-kb901190-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 KB901190.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-kb901190-x86-enu /norestart For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site. Restart Requirement You must restart the system after you apply this security update. 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%\$NTUninstallKB901190$\Spuninst folder.
Supported Spuninst.exe Switches
Switch | Description
/help | Displays the command-line options
Setup Modes |
/passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options |
/norestart | Does not restart when installation has completed
/forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart | Display a dialog box prompting the local user to allow a restart
Special Options |
/forceappsclose | Forces other programs to close when the computer shuts down
/log:path | Allows the redirection of installation log files
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, Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:
File Name | Version | Date | Time | Size | Folder
Imekr61.ime | 6.1.3790.1 | 18-Oct-2005 | 23:41 | 92,160 | RTMGDR\LANG
Imekr61.ime | 6.1.3790.1 | 18-Oct-2005 | 23:44 | 92,160 | RTMQFE\LANG
Imekr61.ime | 6.2.2551.0 | 19-Oct-2005 | 20:36 | 108,032 | SP1GDR\LANG
Imekr61.ime | 6.2.2551.0 | 19-Oct-2005 | 00:24 | 96,768 | SP1QFE\LANG
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 Name | Version | Date | Time | Size | Folder
Imekr61.ime | 6.1.3790.1 | 20-Oct-2005 | 00:26 | 244,736 | RTMGDR\LANG
Wimekr61.ime | 6.1.3790.1 | 20-Oct-2005 | 00:26 | 92,160 | RTMGDR\WOW\LANG
Imekr61.ime | 6.1.3790.1 | 20-Oct-2005 | 00:26 | 244,736 | RTMQFE\LANG
Wimekr61.ime | 6.1.3790.1 | 20-Oct-2005 | 00:26 | 92,160 | RTMQFE\WOW\LANG
Imekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:26 | 267,264 | SP1GDR\LANG
Wimekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:26 | 108,032 | SP1GDR\WOW\LANG
Imekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:26 | 267,264 | SP1QFE\LANG
Wimekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:26 | 96,768 | SP1QFE\WOW\LANG
Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition, Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
File Name | Version | Date | Time | Size | Folder
Imekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:25 | 139,264 | SP1GDR\LANG
Wimekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:25 | 108,032 | SP1GDR\WOW\LANG
Imekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:25 | 139,264 | SP1QFE\LANG
Wimekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:26 | 96,768 | SP1QFE\WOW\LANG
Notes 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 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 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 can 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\KB901190\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 901190 security update into the Windows installation source files.
Top of section
| #### 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
Switch | Description
/help | Displays the command-line options
Setup Modes |
/passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options |
/norestart | Does not restart when installation has completed
/forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart | 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 computer shuts down
/log:path | Allows the redirection of installation log files
/integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] | Extracts files without starting the Setup program
/ER | Enables extended error reporting
/verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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-kb901190-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 KB901190.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-kb901190-x86-enu /norestart For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site. Restart Requirement You must restart the system after you apply this security update. 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%\$NTUninstallKB901190$\Spuninst folder.
Supported Spuninst.exe Switches
Switch | Description
/help | Displays the command-line options
Setup Modes |
/passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options |
/norestart | Does not restart when installation has completed
/forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart | Display a dialog box prompting the local user to allow a restart
Special Options |
/forceappsclose | Forces other programs to close when the computer shuts down
/log:path | Allows the redirection of installation log files
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 Name | Version | Date | Time | Size | Folder
Imekr61.ime | 6.1.2600.3 | 18-Oct-2005 | 03:34 | 89,088 | SP1QFE\LANG
Imekr61.ime | 6.1.2600.3 | 18-Oct-2005 | 17:56 | 94,720 | SP2GDR\LANG
Imekr61.ime | 6.1.2600.3 | 18-Oct-2005 | 03:34 | 94,720 | SP2QFE\LANG
Windows XP Professional x64:
File Name | Version | Date | Time | Size | Folder
Imekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:25 | 139,264 | SP1GDR\LANG
Wimekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:25 | 108,032 | SP1GDR\WOW\LANG
Imekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:25 | 139,264 | SP1QFE\LANG
Wimekr61.ime | 6.2.2551.0 | 20-Oct-2005 | 00:26 | 96,768 | SP1QFE\WOW\LANG
Notes 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 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 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 can 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 been 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\KB901190\Filelist For Windows XP Professional x64 Edition: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB901190\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 901190 security update into the Windows installation source files.
Top of section
| #### Office 2003
| ##### Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
• | Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP, and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit one of the following Microsoft Web sites: Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
• | Office 2003 Service Pack 1 or Microsoft Office 2003 Multilingual User Interface Packs Service Pack 1 must be installed. Before you install this update, install Office 2003 SP1. In addition, if you are installing Office 2003 Multilingual User Interface Packs, you must install Multilingual User Interface Packs Service Pack 1 (SP1). For additional information about how to install Office 2003 Service Pack 1, see Microsoft Knowledge Base Article 842532.
For additional information about how to determine the version of Office 2003 that is installed on your computer, see Microsoft Knowledge Base Article 821549. For additional information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294. Inclusion in Future Service Packs The fix for this issue will be included in a future service pack. Restart Requirement 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. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. Removal Information To remove this security update, use the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771. Top of section
| ##### Automated Client Installation Information
Microsoft Update Web Site This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates provided by Windows Update and Office Update into one location and enables you to choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date. To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process. Top of section
| ##### Manual Client Installation Information
For detailed information about how to manually install this update, review the following section. Installation Information The security update supports the following setup switches.
Supported Security Update Installation Switches
Switch | Description
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u | Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path | Specifies the target folder for extracting files.
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n | Never restarts the computer after installation.
/r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:a | Always restarts the computer after installation.
/r:s | Restarts the computer after installation without prompting the user.
/n:v | No version checking - Install the program over any earlier version.
Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install. For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Client Deployment Information
1. | Download the appropriate client version of this security update: Office 2003 or Office 2003 MUI
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
5. | If you are prompted to install the update, click Yes.
6. | Click Yes to accept the License Agreement.
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK.
8. | When you receive a message that states the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied. Client Installation File Information The English version of this 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. Office 2003:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Office 2003 Multilingual User Interface Packs:
File Name | Version | Date | Time | Size
Contab32.dll | 11.0.8000.0 | 22-Oct-2005 | 23:15 | 116,424
Dumpster.dll | 11.0.6550.0 | 17-Mar-2005 | 21:32 | 31,944
Emablt32.dll | 11.0.8003.0 | 23-Nov-2005 | 13:10 | 106,696
Emsabp32.dll | 11.0.8003.0 | 23-Nov-2005 | 13:10 | 264,904
Emsmdb32.dll | 11.0.8006.0 | 16-Dec-2005 | 07:39 | 705,224
Emsui32.dll | 11.0.8000.0 | 22-Oct-2005 | 23:15 | 132,296
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Mapir.dll | 11.0.6550.0 | 17-Mar-2005 | 21:32 | 779,968
Msain.dll | 11.0.6565.0 | 05-Jul-2005 | 19:09 | 636,608
Msmapi32.dll | 11.0.8002.0 | 10-Nov-2005 | 20:01 | 1,414,344
Msointl.dll | 11.0.6565.0 | 05-Jul-2005 | 19:22 | 1,864,392
Mspst32.dll | 11.0.8001.0 | 01-Nov-2005 | 22:58 | 724,680
Outex.dll | 11.0.8000.0 | 22-Oct-2005 | 23:15 | 654,528
Outllibr.dll | 11.0.8003.0 | 23-Nov-2005 | 13:11 | 2,997,960
Owci10.dll | 10.0.6765.0 | 03-Jun-2005 | 16:13 | 506,568
Pstprx32.dll | 11.0.8000.0 | 22-Oct-2005 | 23:15 | 280,264
Scanpst.exe | 11.0.6802.0 | 05-Oct-2005 | 04:51 | 58,568
Wwintl.dll | 11.0.6565.0 | 05-Jul-2005 | 19:08 | 877,256
Xlintl32.dll | 11.0.8000.0 | 22-Oct-2005 | 23:50 | 712,392
Verifying that the Update Has Been Applied
• | Microsoft Baseline Security Analyzer To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which 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.
Top of section
| ##### Administrative Installation Information
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer. Installation Information The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from the security update.
Supported Security Update Installation Switches
Switch | Description
/? | Displays the command-line options
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/t:path | Specifies the target folder for extracting files
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Administrative Deployment Information To update your administrative installation, perform the following procedure:
1. | Download the appropriate administrative version of this security update: Office 2003 or Office 2003 MUI
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, locate the folder that contains the saved file and run the following command line to extract the .msp file: [path\name of EXE file] /c /t:C:\AdminUpdate Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.
5. | Click Yes to accept the License Agreement.
6. | Click Yes if you are prompted to create the folder.
7. | If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box: msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp). Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
8. | Click Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
9. | Click I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations that were originally installed from this administrative installation. To do this, please review the Workstation Deployment section. Any new installations that you run from this administrative installation point will include the update. Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation. Workstation Deployment Information To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box: msiexec /i Admin Path \ MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features.
Product | Feature
Office 2003 | IMEMain
Office 2003 MUI | OutlookMAPICONTAB2 OutlookMAPIEMS2 OutlookMAPILDAP2 IMEMain OutlookMAPI2 ACCESSFiles ProductFiles OutlookMAPIPST2 OutlookMessaging OUTLOOKFiles OfficeWebComponents10 WORDFiles EXCELFiles
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the product version you are updating. The Windows Installer Documentation also provides additional information about the parameters supported by Windows Installer. For more information on how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. Administrative Installation File Information The English version of this 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. Office 2003:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Office 2003 Multilingual User Interface Packs:
File Name | Version | Date | Time | Size
Contab32.dll | 11.0.8000.0 | 22-Oct-2005 | 23:15 | 116,424
Dumpster.dll | 11.0.6550.0 | 17-Mar-2005 | 21:32 | 31,944
Emablt32.dll | 11.0.8003.0 | 23-Nov-2005 | 13:10 | 106,696
Emsabp32.dll | 11.0.8003.0 | 23-Nov-2005 | 13:10 | 264,904
Emsmdb32.dll | 11.0.8006.0 | 16-Dec-2005 | 07:39 | 705,224
Emsui32.dll | 11.0.8000.0 | 22-Oct-2005 | 23:15 | 132,296
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Mapir.dll | 11.0.6550.0 | 17-Mar-2005 | 21:32 | 779,968
Msain.dll | 11.0.6565.0 | 05-Jul-2005 | 19:09 | 636,608
Msmapi32.dll | 11.0.8002.0 | 10-Nov-2005 | 20:01 | 1,414,344
Msointl.dll | 11.0.6565.0 | 05-Jul-2005 | 19:22 | 1,864,392
Mspst32.dll | 11.0.8001.0 | 01-Nov-2005 | 22:58 | 724,680
Outex.dll | 11.0.8000.0 | 22-Oct-2005 | 23:15 | 654,528
Outllibr.dll | 11.0.8003.0 | 23-Nov-2005 | 13:11 | 2,997,960
Owci10.dll | 10.0.6765.0 | 03-Jun-2005 | 16:13 | 506,568
Pstprx32.dll | 11.0.8000.0 | 22-Oct-2005 | 23:15 | 280,264
Scanpst.exe | 11.0.6802.0 | 05-Oct-2005 | 04:51 | 58,568
Wwintl.dll | 11.0.6565.0 | 05-Jul-2005 | 19:08 | 877,256
Xlintl32.dll | 11.0.8000.0 | 22-Oct-2005 | 23:50 | 712,392
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.
Top of section Top of section
| #### OneNote 2003
| ##### Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
• | Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites: Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
• | OneNote 2003 Service Pack 1 must be installed. Before you install this update, install OneNote SP1. For additional information about how to install OneNote Service Pack 1, see Microsoft Knowledge Base Article 842774.
For additional information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294. Inclusion in Future Service Packs The fix for this issue will be included in a future service pack. Restart Requirement 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. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. Removal Information To remove this security update, use the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771. Top of section
| ##### Automated Client Installation Information
Microsoft Update Web Site This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates provided by Windows Update and Office Update into one location and enables you to choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date. To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process. Top of section
| ##### Manual Client Installation Information
For detailed information about how to manually install this update, review the following section. Installation Information The security update supports the following setup switches.
Supported Security Update Installation Switches
Switch | Description
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u | Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path | Specifies the target folder for extracting files.
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n | Never restarts the computer after installation.
/r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:a | Always restarts the computer after installation.
/r:s | Restarts the computer after installation without prompting the user.
/n:v | No version checking - Install the program over any earlier version.
Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install. For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Client Deployment Information
1. | Download the client version of this security update.
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
5. | If you are prompted to install the update, click Yes.
6. | Click Yes to accept the License Agreement.
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK.
8. | When you receive a message that states the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied. Client Installation File Information The English version of this 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. OneNote 2003:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Verifying that the Update Has Been Applied
• | Microsoft Baseline Security Analyzer To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which 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.
Top of section
| ##### Administrative Installation Information
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer. Installation Information The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from the security update.
Supported Security Update Installation Switches
Switch | Description
/? | Displays the command-line options
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/t:path | Specifies the target folder for extracting files
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Administrative Deployment Information To update your administrative installation, perform the following procedure:
1. | Download the appropriate administrative version of this security update from the following list: OneNote 2003
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, locate the folder that contains the saved file and run the following command line to extract the .msp file: [path\name of EXE file] /c /t:C:\AdminUpdate Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.
5. | Click Yes to accept the License Agreement.
6. | Click Yes if you are prompted to create the folder.
7. | If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box: msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp). Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
8. | Click Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
9. | Click I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations that were originally installed from this administrative installation. To do this, please review the Workstation Deployment section. Any new installations that you run from this administrative installation point will include the update. Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation. Workstation Deployment Information To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box: msiexec /i Admin Path \ MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features.
Product | Feature
OneNote 2003 | IMEMain
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization on the Office Admin Update Center. On that site, scroll down and look under the Update Resources section for the product version you are updating. The Windows Installer Documentation also provides additional information about the parameters supported by the Windows Installer. For more information on how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. Administrative Installation File Information The English version of this 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. OneNote 2003:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
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.
Top of section Top of section
| #### Office 2003 Proofing Tools
| ##### Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
• | Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP, and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites: Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
• | Office 2003 Service Pack 1 for Proofing Tools. Before you install this update, install Office 2003 SP1 for Proofing Tools. For additional information about how to install Office 2003 Service Pack 1 for Proofing Tools, see Microsoft Knowledge Base Article 843188.
For additional information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294. Inclusion in Future Service Packs The fix for this issue will be included in a future service pack. Restart Requirement 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. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. Removal Information To remove this security update, use the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771. Top of section
| ##### Automated Client Installation Information
Microsoft Update Web Site This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates provided by Windows Update and Office Update into one location and enables you to choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date. To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process. Top of section
| ##### Manual Client Installation Information
For detailed information about how to manually install this update, review the following section. Installation Information The security update supports the following setup switches.
Supported Security Update Installation Switches
Switch | Description
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u | Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path | Specifies the target folder for extracting files.
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n | Never restarts the computer after installation.
/r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:a | Always restarts the computer after installation.
/r:s | Restarts the computer after installation without prompting the user.
/n:v | No version checking - Install the program over any earlier version.
Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install. For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Client Deployment Information
1. | Download the client version of this security update.
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
5. | If you are prompted to install the update, click Yes.
6. | Click Yes to accept the License Agreement.
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK.
8. | When you receive a message that states the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied. Client Installation File Information The English version of this 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. Office 2003 Proofing Tools:
File Name | Version | Date | Time | Size
Batimt.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 71,168
Batimtnp.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 43,520
Chimie.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 103,424
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Jurid.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 73,216
Juridnp.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 99,328
Juridsch.dic |  | 30-Sep-2005 | 19:17 | 93,727
Maatsch.dic |  | 30-Sep-2005 | 19:37 | 162,288
Medic.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 143,872
Medicnp.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 74,752
Medisch.dic |  | 30-Sep-2005 | 19:17 | 238,139
Msgr3en.dll | 5.1.3019.1 | 20-Jun-2004 | 18:11 | 6,215,168
Msgr3en.lex |  | 20-Jun-2004 | 09:04 | 25
Msgren32.dll | 3.2.0.3 | 08-Jan-2004 | 00:56 | 139,337
Msgren32.dll | 3.0.0.49 | 25-May-2005 | 15:15 | 1,572,864
Msgren32.dll | 7.0.1.2 | 15-Aug-2005 | 21:39 | 529,984
Msgr_en.lex |  | 19-Jan-2005 | 20:51 | 4,889,775
Mso.acl |  | 15-Sep-2004 | 20:23 | 43,828
Mssp3en.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 2,982,400
Msspell3.dll | 3.0.1.4 | 03-Jan-2005 | 19:00 | 98,304
Msspell3.dll | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 542,208
Msspell3.dll | 3.0.7.8 | 10-Oct-2005 | 17:28 | 181,824
Msspell3.dll | 2.53.0.0 | 24-Nov-2004 | 22:08 | 163,840
Msth3am.lex |  | 27-Jan-2005 | 00:13 | 1,154,681
Msth3am.lex |  | 14-Sep-2005 | 19:40 | 753,046
Msthes3.dll | 7.0.2.12 | 27-Jan-2005 | 00:49 | 364,627
Techni.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 221,184
Techninp.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 46,080
Techwet.dic |  | 30-Sep-2005 | 19:17 | 168,270
Zakelijk.dic |  | 30-Sep-2005 | 19:17 | 259,080
Verifying that the Update Has Been Applied
• | Microsoft Baseline Security Analyzer To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which 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.
Top of section
| ##### Administrative Installation Information
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer. Installation Information The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from the security update.
Supported Security Update Installation Switches
Switch | Description
/? | Displays the command-line options
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/t:path | Specifies the target folder for extracting files
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Administrative Deployment Information To update your administrative installation, perform the following procedure:
1. | Download the administrative version of this security update.
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, locate the folder that contains the saved file and run the following command line to extract the .msp file: [path\name of EXE file] /c /t:C:\AdminUpdate Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.
5. | Click Yes to accept the License Agreement.
6. | Click Yes if you are prompted to create the folder.
7. | If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box: msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp). Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
8. | Click Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
9. | Click I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations that were originally installed from this administrative installation. To do this, please review the Workstation Deployment section. Any new installations that you run from this administrative installation point will include the update. Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation. Workstation Deployment Information To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box: msiexec /i Admin Path \ MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features.
Product | Feature
Office 2003 PTK | SpellingAndGrammarFiles_1036 IMEMain_1042 SpellingAndGrammarFiles_1043 SpellingAndGrammarFiles_1038 SpellingAndGrammarFiles_1040 SpellingAndGrammarFiles_1029,SpellingAndGrammarFiles_1053 ThesaurusFiles_1036 ThesaurusFiles_1043
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the product version you are updating. The Windows Installer Documentation also provides additional information about the parameters supported by Windows Installer. For more information on how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. Administrative Installation File Information The English version of this 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. Office 2003 Proofing Tools:
File Name | Version | Date | Time | Size
Batimt.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 71,168
Batimtnp.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 43,520
Chimie.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 103,424
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Jurid.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 73,216
Juridnp.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 99,328
Juridsch.dic |  | 30-Sep-2005 | 19:17 | 93,727
Maatsch.dic |  | 30-Sep-2005 | 19:37 | 162,288
Medic.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 143,872
Medicnp.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 74,752
Medisch.dic |  | 30-Sep-2005 | 19:17 | 238,139
Msgr3en.dll | 5.1.3019.1 | 20-Jun-2004 | 18:11 | 6,215,168
Msgr3en.lex |  | 20-Jun-2004 | 09:04 | 25
Msgren32.dll | 3.2.0.3 | 08-Jan-2004 | 00:56 | 139,337
Msgren32.dll | 3.0.0.49 | 25-May-2005 | 15:15 | 1,572,864
Msgren32.dll | 7.0.1.2 | 15-Aug-2005 | 21:39 | 529,984
Msgr_en.lex |  | 19-Jan-2005 | 20:51 | 4,889,775
Mso.acl |  | 15-Sep-2004 | 20:23 | 43,828
Mssp3en.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 2,982,400
Msspell3.dll | 3.0.1.4 | 03-Jan-2005 | 19:00 | 98,304
Msspell3.dll | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 542,208
Msspell3.dll | 3.0.7.8 | 10-Oct-2005 | 17:28 | 181,824
Msspell3.dll | 2.53.0.0 | 24-Nov-2004 | 22:08 | 163,840
Msth3am.lex |  | 27-Jan-2005 | 00:13 | 1,154,681
Msth3am.lex |  | 14-Sep-2005 | 19:40 | 753,046
Msthes3.dll | 7.0.2.12 | 27-Jan-2005 | 00:49 | 364,627
Techni.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 221,184
Techninp.lex | 5.0.6466.0 | 22-Jan-2005 | 06:02 | 46,080
Techwet.dic |  | 30-Sep-2005 | 19:17 | 168,270
Zakelijk.dic |  | 30-Sep-2005 | 19:17 | 259,080
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.
Top of section Top of section
| #### Project 2003
| ##### Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
• | Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP, and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit one of the following Microsoft Web sites: Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
• | Project 2003 Service Pack 2 or Project 2003 Multilingual User Interface Packs Service Pack 2 must be installed. Before you install this update, install Project 2003 SP2. In addition, if you are installing Project 2003 Multilingual User Interface Packs, you must install Project 2003 Multilingual User Interface Packs Service Pack 2 (SP2). For additional information about how to install Project 2003 Service Pack 2, see Microsoft Knowledge Base Article 887620.
For additional information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294. Inclusion in Future Service Packs The fix for this issue will be included in a future service pack. Restart Requirement 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. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. Removal Information To remove this security update, use the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771. Top of section
| ##### Automated Client Installation Information
Microsoft Update Web Site This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates provided by Windows Update and Office Update into one location and enables you to choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date. To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process. Top of section
| ##### Manual Client Installation Information
For detailed information about how to manually install this update, review the following section. Installation Information The security update supports the following setup switches.
Supported Security Update Installation Switches
Switch | Description
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u | Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path | Specifies the target folder for extracting files.
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n | Never restarts the computer after installation.
/r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:a | Always restarts the computer after installation.
/r:s | Restarts the computer after installation without prompting the user.
/n:v | No version checking - Install the program over any earlier version.
Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install. For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Client Deployment Information
1. | Download the appropriate client version of this security update: Project 2003 or Project 2003 MUI
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
5. | If you are prompted to install the update, click Yes.
6. | Click Yes to accept the License Agreement.
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK.
8. | When you receive a message that states the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied. Client Installation File Information The English version of this 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. Project 2003 and Project 2003 Multilingual Interface Packs:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Verifying that the Update Has Been Applied
• | Microsoft Baseline Security Analyzer To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which 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.
Top of section
| ##### Administrative Installation Information
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer. Installation Information The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from the security update.
Supported Security Update Installation Switches
Switch | Description
/? | Displays the command-line options
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/t:path | Specifies the target folder for extracting files
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Administrative Deployment Information To update your administrative installation, perform the following procedure:
1. | Download the appropriate administrative version of this security update: Project 2003 or Project 2003 MUI
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, locate the folder that contains the saved file and run the following command line to extract the .msp file: [path\name of EXE file] /c /t:C:\AdminUpdate Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.
5. | Click Yes to accept the License Agreement.
6. | Click Yes if you are prompted to create the folder.
7. | If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box: msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp). Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
8. | Click Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
9. | Click I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations that were originally installed from this administrative installation. To do this, please review the Workstation Deployment section. Any new installations that you run from this administrative installation point will include the update. Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation. Workstation Deployment Information To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box: msiexec /i Admin Path \ MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features.
Product | Feature
Project 2003 | IMEMain
Project 2003 MUI | IMEMain
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the product version you are updating. The Windows Installer Documentation also provides additional information about the parameters supported by Windows Installer. For more information on how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. Administrative Installation File Information The English version of this 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. Project 2003 and Project 2003 Multilingual Interface Packs:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
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.
Top of section Top of section
| #### Visio 2003
| ##### Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
• | Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP, and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit one of the following Microsoft Web sites: Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
• | Visio 2003 Service Pack 1 or Visio 2003 Multilingual User Interface Packs Service Pack 1 must be installed. Before you install this update, install Visio 2003 SP1. In addition, if you are installing Visio 2003 Multilingual User Interface Packs, you must install Visio 2003 Multilingual User Interface Packs Service Pack 1 (SP1). For additional information about how to install Visio 2003 Service Pack 1, see Microsoft Knowledge Base Article 840663.
For additional information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294. Inclusion in Future Service Packs The fix for this issue will be included in a future service pack. Restart Requirement 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. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. Removal Information To remove this security update, use the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771. Top of section
| ##### Automated Client Installation Information
Microsoft Update Web Site This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates provided by Windows Update and Office Update into one location and enables you to choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date. To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process. Top of section
| ##### Manual Client Installation Information
For detailed information about how to manually install this update, review the following section. Installation Information The security update supports the following setup switches.
Supported Security Update Installation Switches
Switch | Description
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u | Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path | Specifies the target folder for extracting files.
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n | Never restarts the computer after installation.
/r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:a | Always restarts the computer after installation.
/r:s | Restarts the computer after installation without prompting the user.
/n:v | No version checking - Install the program over any earlier version.
Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install. For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Client Deployment Information
1. | Download the appropriate client version of this security update: Visio 2003 or Visio 2003 MUI
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
5. | If you are prompted to install the update, click Yes.
6. | Click Yes to accept the License Agreement.
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK.
8. | When you receive a message that states the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied. Client Installation File Information The English version of this 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. Visio 2003:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Visio 2003 Multilingual User Interface Packs:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Orgchart.vsl | 11.0.5819.0 | 20-Oct-2005 | 12:12 | 374,984
Timesoln.vsl | 11.0.5819.0 | 20-Oct-2005 | 12:12 | 166,600
Uml.vsl | 11.0.4301.0 | 01-Jul-2004 | 18:17 | 241,856
Visintl.dll | 11.0.4301.0 | 01-Jul-2004 | 18:17 | 737,992
Verifying that the Update Has Been Applied
• | Microsoft Baseline Security Analyzer To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which 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.
Top of section
| ##### Administrative Installation Information
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer. Installation Information The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from the security update.
Supported Security Update Installation Switches
Switch | Description
/? | Displays the command-line options
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted.
/t:path | Specifies the target folder for extracting files
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Administrative Deployment Information To update your administrative installation, perform the following procedure:
1. | Download the appropriate administrative version of this security update: Visio 2003 or Visio 2003 MUI
2. | Click Save this program to disk, and then click OK.
3. | Click Save.
4. | Using Windows Explorer, locate the folder that contains the saved file and run the following command line to extract the .msp file: [path\name of EXE file] /c /t:C:\AdminUpdate Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.
5. | Click Yes to accept the License Agreement.
6. | Click Yes if you are prompted to create the folder.
7. | If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box: msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp). Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
8. | Click Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
9. | Click I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations that were originally installed from this administrative installation. To do this, please review the Workstation Deployment section. Any new installations that you run from this administrative installation point will include the update. Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation. Workstation Deployment Information To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box: msiexec /i Admin Path \ MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu where Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeADM), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features.
Product | Feature
Visio 2003 | IMEMain
Visio 2003 MUI | IMEMain VisMOrganization_Charts VisMProject_Schedules VisMSoftware_Design VisioCore
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the product version you are updating. The Windows Installer Documentation also provides additional information about the parameters supported by Windows Installer. For more information on how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. Administrative Installation File Information The English version of this 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. Visio 2003:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Visio 2003 Multilingual User Interface Packs:
File Name | Version | Date | Time | Size
Imekr70.ime | 7.0.8002.0 | 10-Nov-2005 | 20:14 | 103,624
Orgchart.vsl | 11.0.5819.0 | 20-Oct-2005 | 12:12 | 374,984
Timesoln.vsl | 11.0.5819.0 | 20-Oct-2005 | 12:12 | 166,600
Uml.vsl | 11.0.4301.0 | 01-Jul-2004 | 18:17 | 241,856
Visintl.dll | 11.0.4301.0 | 01-Jul-2004 | 18:17 | 737,992
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.
Top of section Top of section Top of section Acknowledgments Microsoft thanks the following for working with us to help protect customers:
• | Ryan Lee of VMCraft Inc. for reporting the Korean IME Vulnerability (CAN-2006-0008).
Obtaining Other Security Updates: Updates for other security issues are available at the following locations:
• | Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
• | Updates for consumer platforms are available at the Microsoft Update Web site.
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:
• | The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
• | Microsoft Software Update Services
• | Microsoft Windows Server Update Services
• | Microsoft Baseline Security Analyzer (MBSA)
• | Windows Update
• | Microsoft Update
• | Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
• | Office Update
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 based servers, to 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 security updates by using Software Update Services, visit the Software Update Services Web site. Windows Server Update Services: By using Windows Server Update Services (WSUS), administrators can quickly and reliably 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 onto Windows 2000 and later operating systems. For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server 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 Analyzer, the Office Detection Tool, and the Enterprise Update Scan 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 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 (February 14, 2006): Bulletin published. V1.1 (March 8, 2006): Bulletin revised: Executive Summary updated to clarify the criteria for a successful attack, updated the workarounds section to provide clarity for TCP port 4125.
Top of page

Manage Your Profile | Contact Us | Newsletter © 2008 Microsoft Corporation. All rights reserved. Contact Us | Terms of Use | Trademarks | Privacy Statement |