summary
This article describes how to install multiple Windows product updates that use HotFix.exe (Microsoft Windows NT 4.0) or Update.exe (Microsoft Windows 2000, Microsoft Windows XP or Microsoft Windows Server 2003) in the case of only restarting. Key updates, security patches, or fixes). The readers facing this article are administrators and IT professionals. You can install Windows product updates to use HotFix.exe or Update.exe alone, you can also install a combination of Windows product updates with Hotows (with or without service pack) with HotFix.exe or Update.exe. Note: The procedures described herein are not applicable to product updates that do not use HotFix.exe or Update.exe as the installer. For example, Windows NT 4.0, Windows 2000, and Windows XP Internet Explorer update use INF-based installation instead of Update.exe. Therefore, you cannot use this process to install multiple Microsoft Internet Explorer updates on Windows NT 4.0, Windows 2000, or Windows XP only on the case of restarting. Because Windows Server 2003 Internet Explorer updates use Update.exe as the installer, you can use this procedure to install them. For additional information about these topics, visit the following Microsoft Web site: Windows 2000
Microsoft Windows 2000 HotFix Installation and Deployment Guide (HFDeploy.htm) (Microsoft Windows 2000 Fix Installation and Deployment Guide)
http://www.microsoft.com/windows2000/downloads/servicePacks/sp4/hfdeploy.htm
Windows XP
Microsoft Windows XP HotFix Installation and Deployment Guide (Microsoft Windows XP Fix Installation and Deployment Guide)
http://www.microsoft.com/windowsxp/pro/downloads/servicePacks/sp1/hfdeploy.asp
Windows Server 2003 and Windows XP 64-Bit Edition 2003
Guide for Installing and Deploying Updates for Microsoft Windows Server 2003 And Windows XP 64-Bit Edition Version 2003 (Microsoft Windows Server 2003 and Update Installation and Deployment Guide for Microsoft Windows Server 2003 and Windows XP 64)
http://www.microsoft.com/technet/security/topics/patch/hfdeploy.asp
More information
Windows product updates (for example, key updates, security patches, or fixes) are an executable (.exe) file containing one or more system files that can be applied to Windows to correct specific issues. "Microsoft Product Support Services" will distribute the repair program to customers who are seriously affected by a particular question. Key updates and security patches are Microsoft's updates recommended for all customers. You can get critical updates and security patches from a Windows Update Web site, Microsoft Download Center, or other Microsoft Web site. Windows Server 2003 updates or Windows XP and Windows 2000 updates after December 2002
Note: To determine an updated creation time, review the "Modify Date" of the update.exe or HotFix.exe installer in the Update package. To install Windows product updates on a computer, run the product update on your computer to update. To install multiple product updates, do not restart your computer between each installation, use the / z switch.
Command line option for update.exe programs
The following table identifies the command line option (or switch) supported by the Update.exe program:
Switch Description --------------- / F Force other programs are turned off when turning off. / N does not back up files for the removal of the fix. The computer is not restarted after the / z installation is complete. / q Use the "quiet" mode without user interaction. / m Use "unattended" installation mode (Windows 2000). / u Use "unattended" installation mode (Windows XP). / L lists the installed fixes.
The following code example is a batch file that can be installed with multiple product updates and make sure that replacing the correct file after restarting your computer.
@echo off
SetLocal
SET PATHTOFIXES = E: / HotFix
% PATHTOFIXES% / Q123456_W2K_SP4_X86.EXE / Z / M
% PATHTOFIXES% / Q123321_W2K_SP4_X86.EXE / Z / M
% PATHTOFIXES% / Q123789_W2K_SP4_X86.EXE / Z / M
Note: All Windows Server 2003, Windows Server 2003, Windows Server 2003, Windows XP, and Windows 2000 product updates that use Update.exe and May 18, 2001 contain QChain.exe feature. However, there is a problem in product updates issued in December 2002. In some cases, this problem may apply an error binarily on the computer. In March 2003, Microsoft released the updated version of QChain.exe to resolve this issue. For this issue or about how to get additional QChain.exe tools, click the article number below to see the article in the Microsoft Knowledge Base:
815062
The correct file is not installed in series multiple fixes
All Windows NT 4.0 updates or Windows XP and Windows 2000 updates before December 2002
Note: To determine the creation date of the product update, check the "Modify Date" of the update.exe or Hotfix.exe installer in the update package. Microsoft has released a command line tool called QChain.exe. Using QChain.exe, the system administrator can connect the update together. If you connect the update series, you don't have to restart your computer when you install multiple updates. If this is not, the only supported method is to restart your computer after each update is installed. The QChain.exe tool has the following benefits: • Because the computer is not restarted between the various updates, it can increase the running time of the server. • Use it to install multiple updates more quickly on a single computer. • It can run in Windows 2000 and Windows NT 4.0.
Note: All Windows XP and Windows 2000 updates released from May 18th, 2001, there is a problem in the update issued before December 2002, in some cases, this problem may It will result in an incorrect binarily in the computer. In March 2003, Microsoft released the updated version of QChain.exe to resolve this issue. For this issue or about how to get additional QChain.exe tools, click the article number below to see the article in the Microsoft Knowledge Base:
815062
The correct file is not installed in series multiple fixes
Do not use qChain.exe when updating installation is unsafe
When installing updates, if a file is locked or is being used, it cannot be replaced. Therefore, this file will be placed in the "Sliding File Rename" queue and replaced after the computer is restarted. This problem occurs in the case:
• Install updates A and B, but there is no restart between the two installations. • These two packages contain file x. The file x of the package A is version 3; the file X of the package B is version 2. The version of the file X in the computer is 1. • When installing the package A, it places its file x version in the "Snaps Rename" queue. • When installing the package B, it places its file x version in the "Snaps Rename" queue. • When restarting your computer, because the package B is finally installed, it is installed, so the version of the file X is installed (in the "Rename Rename" queue, the last file is the file used). Therefore, version 2 is installed instead of installing version 3 as you expect.
If the previously connected update is installed without restarting
Although this situation is rare, it is best to verify that the computer has all the fix you think is installed. To verify this, use the QFecheck.exe tool. For additional information about QFecheck.exe, click the article number below to see the article in the Microsoft Knowledge Base:
282784
QFecheck.exe Verifies the installation of Windows 2000 and Windows XP fixes
QChain.exe will clean up the "Suspended File Rename" registry key in the registry to ensure that only the latest version of the file is installed after the computer is restarted.
Install multiple updates only when you restart once
1. Use the -z switch to run the update installer to indicate not to restart after installation. If you don't want to display a prompt or message during the installation, add the -m switch (indicating "quiet" mode). Update the installer is one of the following programs:
• Self-solve the compressed package program file (for example, QNNNNNN_W2K_SPX_X86_EN.EXE). - or - • HotFix.exe (if you have already decompressed all files in the package). 2. After installing all fixes, run qchain.exe. 3. Restart your computer. You can also create a batch file to complete this task. The following sample batch file demonstrates this method:
@echo off
SetLocal
SET PATHTOFIXES = Some Path
% PATHTOFIXES% / Q123456_W2K_SP2_X86.EXE -Z -M
% PATHTOFIXES% / Q123321_W2K_SP2_X86.EXE -Z -M
% PATHTOFIXES% / Q123789_W2K_SP2_X86.EXE -Z -M
% PATHTOFIXES% / QChain.exe
How to get QChain.exe
All Windows XPs and Windows 2000 updates released from May 18, 2001, there is a problem in the update issued before December 2002, in some cases, this problem may result in Place the wrong binary in your computer. In March 2003, Microsoft released the updated version of QChain.exe to resolve this issue. For this issue or about how to get additional QChain.exe tools, click the article number below to see the article in the Microsoft Knowledge Base:
815062
The correct file is not installed in series multiple fixes
QChain.exe command syntax
QChain [log file name]
Optional [Log Filing Name] parameters creates files using the "Suspended File Rename" registry key.
QChain.exe output example
---- Old Information in The Registry ------ Source: C: /Winnt/INF/Acpi.infversion: 5.0.2183.1Destination: D: /ntsust/testregchech/1394.infversion: 5.0.2183.1source: c : /Winnt/inf/adm_mult.infversion: 5.0.2184.1Destination: D: /ntsust/testregchech/1394.infversion: 5.0.2183.1source: c: /winnt/inf/banshee.infversion: 5.0.2080.1destination: D: / NTSUST / TESTREGCHECH / 1394.INFVERSION: 5.0.2183.1 ---- New Information in the registry ------ Source: C: /WinNNINF/ADM_MULT.INFVERSION: 5.0.2184.1DESTINATION: D: / NTSUST / TESTREGCHECH /1394.INFVERSION: 5.0.2183.1
Limitations of QChain.exe
Although QCHAIN is suitable for most Windows NT 4.0 and Windows 2000 updates, qChain.exe may not apply to updates to binary files listed in the following registry items:
HKEY_LOCAL_MACHINE / SYSTEM / CURRENTCONTROLSET / CONTROL / Session Manager / KNowndlls
When starting, the binary files listed in this registry key will be loaded into memory. When the update installer calls the GetFileVersionInfo function for the binary in this list, the Update Setup references the already loaded binaries instead of the reference to actually appear in the target location. Because the binary files listed in the knowndlls registry entry will be loaded into memory during startup, the update the installer must replace the target binarily with the repair binary file before the computer restarts. Therefore, when restarting, the update installer does not create the "Suspended File Rename" to replace the binary file. Instead, the update will move the current binary to a temporary location, place the repair binary in the current binary, then place the "Suspend the file rename operation" to delete the current time when the computer is restarted Binary file. QChain only affects the "suspend file rename action" that affects the replacement of binary files. It does not have any impact on the "suspend file rename operation" that performs delete operation. All Windows NT 4.0 updates and all Windows 2000 updates earlier than SP2 use GetFileVersionInfo to identify files. If you install two or more Windows NT 4.0 updates or earlier Windows 2000 updates, and these updates contain overlapping KNOWNDLLs, use QCHAIN to connect these updates to the installation to ensure that the latest version of the fix is installed. The following statements illustrate the reason why QChain may not be able to place the correct binary on the system: • You have installed the update packages A and B, and no restart between the two installations. • Both packages contain kernel32.dll, which is a file in the KnowNDLL list. Package A contains kernel32.dll version 3, package B contains kernel32.dll version 2, and kernel32.dll version 1 is installed in your computer. • When installing the package A, getFileVersionInfo reports that there is a kernel32.dll version 1 in your computer. Because the package A contains version 3, the update installer determines that the file needs to be replaced.
• Updating the installer moves the kernel32.dll version 1 on your computer to a temporary location and creates a "Suspend file rename operation" to remove the kernel32.dll file from the temporary location when the computer is restarted. • The kernel32.dll version 3 of the package A will be copied to your computer. • When installing the package B, GetFileVersionInfo will still report the installed kernel32.dll version 1 in your computer, because getFileVersionInfo reads version information from the loaded kernel32.dll loaded into the memory. The package B has version 2, so the repair program determines that the file needs to be replaced.
• Updating the installer will move the kernel32.dll in your computer (Kernel32.dll version 3) to a temporary location, and create a "hanging file rename action" to restart next time from the next time This temporary location deletes (version 3) kernel32.dll. • The kernel32.dll version 2 of the package B will be copied into the computer. • QCHAIN will run, but there is no "suspend file rename operation" for replacing files, so QCHAIN does not perform any operation. • Because the package B is recently installed, the package B kernel32.dll version 2 is located in the correct location on the computer. Therefore, when the computer is restarted, it will be loaded into memory. "Hanging File Rename Action" will also delete the original kernel32.dll version 1 and the kernel32.dll version 3 of the package A. Therefore, the computer now has kernel32.dll version 2 instead of version 3. With a Windows 2000 SP2 fix, in this hotfix, you no longer use GetFileVersionInfo for Knowndll loaded into memory. Instead, the update installer maps the file that actually appears in the target location, and then call GetFileVersionInfo for the mapped file. Therefore, you can use qChain.exe to connect the post SP2 update of Windows 2000. When you do this, you will install the latest version of the file without considering all updated installation order. If you redeemed the situation in front and use the WINDOWS 2000 update, the repair program in the package B will map the kernel32.dll of the program package A and identify version 3 (this version is higher than the package B "kernel32. DLL version 2). Therefore, the package B does not replace the kernel32.dll in the system, and the kernel32.dll version 3 of the package A is a version that the computer is used correctly after restart.
The information in this article applies to:
