Microsoft KB Archive/828930

= How to integrate software updates into your Windows installation source files =

Article ID: 828930

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition
 * Microsoft Windows Server 2003, 64-Bit Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows XP Home Edition
 * Microsoft Windows XP Media Center Edition 2002
 * Microsoft Windows XP Professional x64 Edition
 * Microsoft Windows XP Professional
 * Microsoft Windows XP Tablet PC Edition
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Server

-



SUMMARY
This article discusses how an administrator can integrate Windows software updates that use Update.exe with their Windows installation source files. (Software updates include critical updates, feature packs, hotfixes, security updates, service packs, updates, and update rollups.) These procedures may be useful when an administrator must apply one or more software updates during installations from a Windows distribution folder that the administrator creates. These procedures are also useful if you want to integrate a security update so that a new installation does not become infected by a virus when it is set up.

Notes  These procedures do not work for software updates that do not use Update.exe as the installation program. For example, some Microsoft Internet Explorer updates for Microsoft Windows 2000 and Microsoft Windows XP use an INF-based installation instead of Update.exe. As a result, you cannot use these procedures to integrate these Internet Explorer updates for Windows 2000 or Windows XP.  registry keys are not created correctly when you use these procedures to integrate software updates. For example, if you integrate the 824146 security patch into your Microsoft Windows Server 2003 installation source files, the following registry key is not created correctly:

 When you use either of these this procedures to integrate updates, an entry is added for each update in the Add or Remove Programs control panel. However, the Remove button is not available because there is no earlier version of the updated files to restore if you remove the updates. Administrators may also have to apply software updates to the Microsoft Windows Preinstallation Environment (Windows PE) if the following conditions are true:  The administrator uses the Windows PE to run Windows Setup. The administrator uses an operating system that has integrated software updates on a network share.

For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

828217 How to apply the 824146 Security Patch to your Windows Preinstallation Environment

 The instructions in this article can be used for Remote Installation Services (RIS) RISETUP based images also. The I386 directory structure for a RISETUP image is the same as a network distribution folder. For RIPREP images, pull the image down to a client computer, install the software update, and then RIPREP the image back to the server.</li> When you use these procedures to prevent a virus infection, we recommend that you integrate only software updates that require no action by the user. If you integrate software updates that do not prevent the Windows installation program from completing, use a &quot;[guirunonce]&quot; section in the Unattend.txt file, or use Software Update Services (SUS) to deploy the updates after the installation is completed.</li> This procedure is designed for new installs only. The procedure does not work for upgrade installs.</li></ul>

<div class="moreinformation_section">

MORE INFORMATION
The &quot;Update.exe 5.4.15.0 or later versions&quot; section describes the procedure to integrate software packages that use Update.exe version 5.4.15.0 or later versions. The &quot;Earlier versions of Update.exe&quot; section describes the procedure to integrate software packages that use earlier versions of Update.exe.

To determine whether a software update package uses Update.exe version 5.4.15.0 or a later version as the Setup program, follow these steps:
 * 1) Extract the software update package to a unique temporary folder. For example, to extract the files for an update package that is named KB .exe to a folder that is named ExtractedPackage on drive C, type the following at a command prompt: KB  /X:C:\ExtractedPackage
 * 2) Open the temporary folder that contains the extracted files for the software update package. For example, open C:\ExtractedPackage.
 * 3) Right-click the Update.exe file in the folder, and then click Properties.
 * 4) On the Version tab, note the value for File version. If the version number is 5.4.15.0 or a later version, the new features that are mentioned in this article are supported.

Update.exe will determine whether the update is appropriate for your installation source. For example, a fix that is included with Windows 2000 Service Pack 4 (SP4) will not integrate in a Windows 2000 installation source that already has SP4 integrated. Update.exe also determines whether the installation source is for the correct hardware platform. The /integrate switch cannot be used with extracted packages.

If you do not want to integrate software updates that use Update.exe versions that are earlier than 5.4.15.0 as the Setup program, do not perform steps 6 through 13. If you do want to integrate software updates that use Update.exe versions earlier than 5.4.15.0, follow steps 6 through 13 to integrate these updates.

Update.exe 5.4.15.0 or later versions
To integrate software updates that use Update.exe 5.4.15.0 or later versions into your Windows installation source files, follow these steps: <ol> Map a drive to the network share where you want to create the distribution folder. Or, log on to the computer where you want to create the distribution folder. These steps assume that you create the distribution folder on drive .</li> Create the distribution folder. For example, to create a distribution folder named Winflat on drive, type the following command at a command prompt:

mkdir :\Winflat\

</li> Set permissions on the Winflat distribution folder so that only administrators have Full Control and so that all other users have Read and Execute permissions only.</li> Insert the Windows product CD into the CD Drive, and then copy the contents of the CD to the Winflat distribution folder that you created in step 2. To do this, type the following command at a command prompt:

xcopy /E /I /V D: :\Winflat\

</li> To integrate software updates that use Update.exe version 5.4.15.0 or a later version as the Setup program, type the following at a command prompt for each update that you want to integrate:

KB /integrate:

Note For, specify the path of your distribution folder. For example, to integrate the KB123456.exe file in a distribution folder at :\Winflat, type the following:

KB123456 /integrate:x:\winflat

</li></ol>

Earlier versions of Update.exe
To integrate software updates that use earlier versions of Update.exe into your Windows installation source files, follow these steps: <ol> Map a drive to the network share where you want to create the distribution folder or log on to the computer where you want to create the distribution folder. These steps assume that you create the distribution folder on drive .</li> Create the distribution folder. For example, to create a distribution folder named Winflat on drive, type the following command at a command prompt:

mkdir :\Winflat\

</li> Set permissions on the Winflat distribution folder so that only administrators have Full Control and all other users have Read and Execute permissions only.</li> Insert the Windows product CD into the CD Drive, and then copy the contents of the CD to the Winflat distribution folder that you created in step 2. To do this, type the following command at a command prompt:

xcopy /E /I /V D: :\Winflat\

</li> Edit :\Winflat\i386\dosnet.inf, and add &quot;svcpack&quot; to the [OptionalSrcDirs] section. For example:

[OptionalSrcDirs]

uniproc

svcpack

Note For Windows XP or Windows Server 2003 distribution folders, you may have to create the [OptionalSrcDirs] section in the Dosnet.inf file. The Dosnet.inf file included with Windows 2000 already contains this section.</li> Create a :\Winflat\i386\svcpack folder. To do so, type the following command at a command prompt:

mkdir :\Winflat\i386\svcpack

</li> Copy the update packages that you want to integrate ( -KB - - .exe ) to the :\Winflat\i386\svcpack folder. To do so, use the 8.3 naming format (KB .exe), where  is the Microsoft Knowledge Base article number associated with the update. If you are applying multiple updates, copy and rename all the update packages.</li> Extract each of the update packages to a unique temporary folder. For example, to extract the files for an update package to a folder named ExtractedPackage on drive, type the following command at a command prompt:

C:\i386\svcpack\KB / : :\ExtractedPackage

</li> <li>From :\ExtractedPackage, for each update, copy the catalog file (KB .cat) and updated binary files (such as .exe, .dll, or .sys files). To do so, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Copy KB .cat from :\ExtractedPackage, for each update, to the  :\Winflat\i386\svcpack folder. Use the same name for the .cat file as the update package (KB .cat) uses, and do not copy Empty.cat.</li> <li>If the same binary file exists in :\ExtractedPackage, for each update, keep only the file with the highest version number.</li> <li>For each binary file included in :\ExtractedPackage, for each update, determine whether the same file exists in the  :\Winflat\I386 folder. If the file exists in the I386 folder, delete the file from :\Winflat\I386.

Note The files in the I386 folder may have an underscore (_) for the last character in the file's extension. For example, Rpcss.dll is named Rpcss.dl_ in the I386 folder.</li> <li>Copy the updated binary files from :\ExtractedPackage, for each update, to  :\Winflat\I386.</li> <li>Look in :\ExtractedPackage, for each update, for any subfolders that have the same name as a subfolder of  :\Winflat\I386. If a folder contains any such subfolders, copy the updated binary files from the :\ExtractedPackage subfolder to the appropriate subfolder of  :\Winflat\I386. For example, if :\ExtractedPackage contains a folder named Uniproc, copy the files in  :\ExtractedPackage\Uniproc to  :\Winflat\I386\Uniproc.</li></ol>

Notes <ul> <li>Because Microsoft provides support for the current and the next most recent service pack ( and  -1), Microsoft packages some updates as dual-mode updates that you can apply to computers that have different service pack levels. For example, a Windows XP update may have both a SP1 and SP2 subdirectory with updated files for the original version of Windows XP in the SP1 folder and updated files for Windows XP SP1 in the SP2 folder. In this example, you must use the files from the SP1 directory if your installation source is the original version of Windows XP (Version 2600). If your installation source is Windows XP SP1, you must use the files from the SP2 directory. For more information about Windows XP dual-mode update packages, click the following article number to view the article in the Microsoft Knowledge Base:

328848 Description of dual-mode update packages for Windows XP

Microsoft may also package Windows Server 2003 updates as dual-mode updates after Service Pack 1 is released.</li> <li>Windows Server 2003 update packages also contain two sets of updated binary files for the current and the next most recent service pack ( and  -1) in  QFE and  GDR folders, where   is the original released version, &quot;SP1,&quot; &quot;SP2,&quot; and so on for the current and the next most recent service pack (  and  -1). In this case, you must use the files from the appropriate QFE folder. For more information about the contents of a Windows Server 2003 update package, click the following article number to view the article in the Microsoft Knowledge Base:

824994 Description of the contents of Windows XP Service Pack 2 and Windows Server 2003 software update packages

</li> <li>You do not have to copy files in the Common or Update folders, such as Update.exe, Update*.inf, SPmsg.dll, SPcustom.dll, SPuninst.exe, Update.ver, or symbols (.dbg files).</li></ul> </li> <li>For each file that you copy in step 9 (except KB .cat), look in the :\Winflat\I386\Dosnet.inf file to determine if the file name is listed in the [Files] section. All the files that are listed in the [Files] section are preceded by &quot;d1,&quot;. For example:

d1,

If the file name is not listed for any files that you copied in Step 9, use this syntax to add an entry. For example, if a hotfix contains Win32k.sys, because Win32k.sys is not listed in Dosnet.inf, add d1,win32k.sys to the [Files] section of :\Winflat\I386\Dosnet.inf. This addition makes sure that the updated version of Win32k.sys is copied during Windows Setup.</li> <li>Delete the :\Winflat\I386\Svcpack.in_ file.</li> <li>Create a Svcpack.inf file in the :\Winflat\I386 folder. To do so, use the appropriate following content, depending on whether you want to deploy a single update or multiple updates. (Replace  with the Knowledge Base article numbers for your update .cat file):

Windows 2000
[Version]

Signature=&quot;$Windows NT$&quot;

MajorVersion=5

MinorVersion=0

BuildNumber=2195

[SetupData]

CatalogSubDir=&quot;\i386\svcpack&quot;

[ProductCatalogsToInstall]

KB .cat

[SetupHotfixesToRun]

KB .exe /

Windows XP
[Version]

Signature=&quot;$Windows NT$&quot;

MajorVersion=5

MinorVersion=1

BuildNumber=2600

[SetupData]

CatalogSubDir=&quot;\i386\svcpack&quot;

[ProductCatalogsToInstall]

KB .cat

[SetupHotfixesToRun]

KB .exe /

Windows Server 2003
[Version]

Signature=&quot;$Windows NT$&quot;

MajorVersion=5

MinorVersion=2

BuildNumber=3790

[SetupData]

CatalogSubDir=&quot;\i386\svcpack&quot;

[ProductCatalogsToInstall]

KB .cat

[SetupHotfixesToRun]

KB .exe /

Notes <ul> <li>The recommended options for installing updates are /Q, /N, and /Z. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

262841 Command-line switches for Windows software update packages

824687 Command-line switches for Microsoft software update packages

</li> <li>If you are applying multiple updates, add an entry for each update under both the [ProductCatalogsToInstall] and [SetupHotfixesToRun] sections. The following example is a sample of these sections for an installation where multiple updates are installed:

[ProductCatalogsToInstall]

KB123456.cat

KB123478.cat

KB123490.cat

[SetupHotfixesToRun]

KB123456.exe /

KB123478.exe /

KB123490.exe /

</li> <li>If you are installing a service pack, you do not have to include details about the service pack because a different process handles the service pack installation.</li></ul> </li></ol>

Installing updates on computers that are running Windows Server 2003
To install an update on a single computer, run the update program, WindowsServer2003-KB -x86-LLL.exe, on that computer. If you want to install the update on more than one computer, you can create a distribution folder for the update on the network. The following procedure describes how to install one or more updates by usung this method. Important: You must install SP1 either in combination with or before you install updates released after SP1. Installing more recently-released updates before you install SP1 can cause problems with the system.

Note For the following procedure, :\ represents the drive of the network or computer on which your distribution folder is located.

To install an update by running the Update.exe program, follow these steps:
 * 1) Connect to the network or computer on which you want to create the distribution folder.
 * 2) In the shared network distribution folder, create a distribution folder for the update files. For example, to create a distribution folder named Update, type the following: mkdir  :\Update
 * 3) Copy the Windows Server 2003 Update.exe program to the distribution folder that you created in Step 2. For example, to copy the SP1 Update.exe program to the distribution folder named Update, type the following: xcopy C:\WindowsServer2003-KB -x86-LLL.exe  :\Update
 * 4) To install the update from the shared network distribution folder, run the WindowsServer2003-KB######-x86-LLL.exe program. For example, to install the update from the distribution folder named Update, type the following:  :\Update\WindowsServer2003-KB -x86-LLL.exe
 * 5) To make sure that your updates take effect, restart your computer after you finish installing all the updates.

Note The WindowsServer2003-KB -x86-LLL.exe file supports the same command-line options as Update.exe.

Technical support for x64-based versions of Microsoft Windows
If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:

http://www.microsoft.com/windowsxp/64bit/default.mspx

For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:

http://www.microsoft.com/windowsserver2003/64bit/x64/default.mspx

<div class="references_section">