Jump to content

Vista Guide to Integrating Updates and Hotfixes

Recommended Posts

How to Integrate Vista Updates

This guide shows you how to integrate Vista updates to the installation source, which is install.wim. Much of the credit for this guide goes to FireGeier. His site contains a lot of useful visual guides for automating Vista installations. It is found here: FireGeier's Unattended Vista Guide.

Although others have used peimg.exe, official documentation from Microsoft's WAIK is lacking. Therefore, methods described here use Package Manager. The only place peimg.exe is used in this guide is to create a text file that lists the packages that were integrated.


  • WAIK tools (imagex.exe, pkgmgr.exe, and supporting files); you should leave these files in the install folder (%programfiles%\Windows AIK\) and not copy them to another location. Run them from their original location so all dll's that are necessary are there.
  • Vista DVD
  • ISO extractor
  • Although Windows XP is not required and you can do this in Vista, I had trouble mounting images in Vista. Therefore, I was working in Windows XP.


  1. Create a folder called 'Vista_Work'. You can call it anything you want. I have assigned it a variable %vpath% in my script so I'll refer to it as %vpath% from now on.
  2. Create folders in %vpath% called Mount, Sandbox, Updates, and Current_ISO. I've assigned them the variables %vmount%, %vsandbox%, and %vupdates%, respectively.


  1. Boot to the OS that has WAIK installed. If you installed it in Vista, you'll need to run these scripts in elevated mode.
  2. Extract install.wim from Vista installation DVD to %vpath%.
  3. Create script file called set_variables.cmd, integrate.cmd and expand.cmd in %vpath% from the following code or download them from the links:
    • The script set_variables.cmd allows you to skip editing the scripts with your working folders path (%vpath%). They are automatically assigned based on the current working folder.
    • You may have to change the tokens value in expand.cmd, if you are not using the English version. Change tokens=5 to tokens=4 if that's the case. If you are unsure, leave it and continue, as no damage is done. Only your Integrate.xml will not be properly formed. You'll determine if it is improperly formed in a later step.




:: As long as all your folders are within one folder, you shouldn't have to change
:: these paths since this batch file will assign the paths based on where
:: set_variables.cmd is located. This script is called by expand.cmd & integrate.cmd
:: Also, the Windows AIK folders are added to the path so you can run imagex, expand,
:: and pkgmgr without pointing to those paths.
@echo off
CD /d %~dp0
SET vpath=%CD%
SET vmount=%vpath%\Mount
SET vupdates=%vpath%\Updates
SET vsandbox=%vpath%\Sandbox
SET path=%path%;C:\Program Files\Windows AIK\Tools\x86;C:\Program Files\Windows AIK\Tools\Servicing

expand.cmd (courtesy of FireGeier)

@echo off
TITLE Vista Updates Expansion Process

:: As long as you are this script, integrate.cmd and expand.cmd are in the
:: same folder, you will not have ot change your paths.

CD /d %~dp0
call set_variables.cmd
echo Your vpath is %vpath%. If this is correct, continue.

:: Create an temporary to store expanded cab and xml files from msu files.

IF NOT EXIST "%vupdates%\Temp" (MKDIR "%VUpdates%\Temp")
DEL "%vupdates%\Temp\*.*" /q

PUSHD "%vupdates%"
FOR %%i IN (*) DO (Call :Extract %%i)

:: Check for older file versions created by this batch and delete if exists.

IF EXIST "%vupdates%\Temp\Integrate.xml" DEL /Q "%vupdates%\Temp\Integrate.xml"
IF EXIST "%vupdates%\Temp\Sort.txt" DEL /Q "%vupdates%\Temp\Sort.txt"

:: Create the first 3 lines of Integrate.xml

ECHO ^<^?xml version="1.0" encoding="utf-8"?^>^ >>%VUpdates%\Temp\Integrate.xml
ECHO ^<^unattend xmlns="urn:schemas-microsoft-com:unattend"^>^ >>%VUpdates%\Temp\Integrate.xml
ECHO ^<^servicing^>^ >>%VUpdates%\Temp\Integrate.xml

:: Create sort.txt which is necessary for compiling Integrate.xml.

PUSHD "%vupdates%\Temp"
del *.txt
del WSUSSCAN.cab
Dir /OD > Sort.txt
For /F "Tokens=5" %%i IN ('FINDSTR ".cab" Sort.txt') DO Call :WriteXML %%i

:: Create the last two lines of Integrate.xml.

ECHO ^<^/servicing^>^ >>%VUpdates%\Temp\Integrate.xml
ECHO ^<^/unattend^>^ >>%VUpdates%\Temp\Integrate.xml
echo Finished extracting MSU's and compiling Integrate.xml.
echo Check Integrate.xml to see if it is well-formed before continuing
echo to use Integrate.cmd to begin the integration process.


:: Extract subroutine extracts the msu files for the necessary cab and xml files.

START "Expand" /WAIT expand.exe %1 -f:* "%vupdates%\Temp"

:: WriteXML subroutine writes entries into Integrate.xml, which are specified by the name of
:: coresponding cab file. This is the command line, which will call the installation of the
:: cab during pkgmgr procedure later.

IF "%1"=="WSUSSCAN.cab" Goto :EOF
SET Name=%1
IF ".%Name%"=="." GOTO :EOF
SET XML=%Name:~0,-4%.xml
SET Cab=%Name:~0,-4%.cab
ECHO ^<^package action="install"^>^ >>%vupdates%\Temp\Integrate.xml
FOR /F "Tokens=*" %%i IN ('FINDSTR "assemblyIdentity" %XML%') DO (Echo %%i >>%vupdates%\Temp\Integrate.xml)
ECHO ^<^source location="%vupdates%\Temp\%Cab%" /^>^ >>%VUpdates%\Temp\Integrate.xml
ECHO ^<^/package^>^ >>%vupdates%\Temp\Integrate.xml



@echo off
TITLE Vista Updates Integration Process

CD /d %~dp0
call set_variables.cmd
echo Your vpath is %vpath%. If this is correct, continue.
echo Before beginning, please choose the version of Vista you want to update.
set choice=
set /p choice=Choose 1 for Business, 2 for HomeBasic, 3 for HomePremium, or 4 for Ultimate:
if not '%choice%'=='' set choice=%choice:~0,1%
if '%choice%'=='1' goto BUS
if '%choice%'=='2' goto HB
if '%choice%'=='3' goto HP
if '%choice%'=='4' goto ULT
ECHO "%choice%" invalid! Try again...

SET type=Business

SET type=HomeBasic

SET type=HomePremium

SET type=Ultimate

imagex.exe /mountrw "%vpath%\install.wim" %VERSION% "%vmount%"
ECHO Press any key to begin integration of updates. Once you start the process.
echo you should not cancel it. Make sure you are ready before continuing.
echo Starting integration. This can take several minutes. Please wait until it finishes.

echo on

START "Starting Package Manager" /WAIT pkgmgr.exe /o:"%vmount%;%vmount%\Windows" /n:"%vupdates%\Temp\Integrate.xml" /s:"%vsandbox%" /l:"%vpath%\integrate.txt"

echo The errorlevel is: %errorlevel%.
echo An errorlevel of 0 indicates successful integration. Press any key to save a
echo list of installed packages to a text file.

echo off

peimg.exe /list /image="%vmount%\Windows" >> "%vpath%\Current_ISO\updates_installed_%version%_%type%.txt"
echo The Sandbox folder should be cleared whether integration was successful or not.

REM Delete, then recreate the folder
rd "%vsandbox%" /s /q
mkdir "%vsandbox%"
echo Now, we are ready to commit changes and unmount. Selection an option to
echo unmount while committing or not committing changes.
echo Once you commit, the process can take several minutes as the changes are
echo saved to your installation source.

set choice=
set /p choice=Choose Y to commit changes. Choose N to abandon changes:
if not '%choice%'=='' set choice=%choice:~0,1%
if '%choice%'=='Y' goto COMMIT
if '%choice%'=='y' goto COMMIT
if '%choice%'=='N' goto ABANDON
if '%choice%'=='n' goto ABANDON
ECHO "%choice%" invalid! Try again...

imagex.exe /unmount /commit "%vmount%"
goto END

imagex.exe /unmount "%vmount%"
goto end

echo Done. Press any key to exit.

[*]Copy all of your MSU updates to the %vupdates% folder.

[*]Execute expand.cmd.

  • Expand.cmd will extract the .cab and .xml files from the .msu files in a temporary folder called Temp in %vupdates%. It also compiles a file called Integrate.xml, a necessary file for integration.
  • Note: do not change the spacing in expand.cmd. Some spaces are necessary to build a proper structure for Integrate.xml.

[*]Examine this file (Integrate.xml) using Notepad. It should have as many entries as there are updates of the following nature:

Integrate.xml sample (partial)

<?xml version="1.0" encoding="utf-8"?> 
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<package action="install">
<assemblyIdentity name="Package_for_KB928089" version="" language="neutral" processorArchitecture="x86" publicKeyToken="xxxxxxxxxxxxxxx"/>
<source location="E:\Vista_Work\Updates\Temp\Windows6.0-KB928089-x86.cab" />
and so on

If your file is bare, you may need to change tokens=5 to tokens=4 in expand.cmd.

[*]Execute integrate.cmd once you determine your xml is good. It will prompt you through the steps.

  • Note that if you were successful, you should get an errorlevel of 0.
  • The script will also create a file called Updates_Installed_%#%_%type%.txt, where # and type correspond to the Vista version number (1 to 4) and type (Business, Home Basic, Home Premium, or Ultimate), respectively. This is only for the purpose of auto-generating a text file that shows all the updates. The official way of checking integrated updates is described in step 8.
  • NOTE: You will have to install updates to each version of Vista separately. So, you can repeat integrate.cmd for each version by running integrate.cmd and choosing to mount a different version.
  • NOTE: You don't have to repeat expand.cmd for each version, only integrate.cmd. The script empties the Sandbox folder automatically but does not delete the cab files that are expanded in Temp folder. You can manually delete the cab files later if you prefer.

[*]Start WSIM and open your updated install.wim. If you are asked to create a new catalog file as the current one is missing or outdated, go ahead and create a new catalog file.

  • You will see your packages automatically assigned as either hotfixes, updates, or security updates in the directory structure of Packages.
  • NOTE: This is the official method to check whether your packages were installed. We used peimg only to make a text file that does that automatically for step 9.
  • You'll have to create a new catalog file for each version of Vista if you want to update it in your ISO.

[*]Inject install.wim back into the ISO if you committed changes to finish the process. You may also inject updates_installed_#_type.txt if you want to know which updates are contained in the ISO image.

  • You can also use Microsoft's utility to rebuild the bootable ISO but that involves extracting ALL the files from the DVD, not just install.wim. Therefore, it's easier to use an ISO utility than Microsoft's utility.
  • Injecting the catalog file is options as it is not used by setup.

Edited by Space Surfer
Link to comment
Share on other sites

  • 3 weeks later...


This is a great article but I am having some issues. My integrate.xml file is blank:

<?xml version="1.0" encoding="utf-8"?>

I followed the instructions to the T but I am not sure about the update files. Some of them are .cab and some are .exe file extensions. Is there a specific format the the updates need to be in? I have also changed the tokens=5 to tokens=4 and that has not made a difference.

On another note, is there a way I can download the doc located at http://firegeier.unattended-sponsor.de/en/updates.html

Thanks in advance

Link to comment
Share on other sites

  • 3 weeks later...

Your updates have to be in the .msu format. This is stated in the guide but it's very easy to miss.

When they are extracted, the .cab will be placed in the temp folder.

I haven't seen a .doc file or .pdf of firegeier's guide. If you want to do it manually with SIM, you can follow his guide, but if you want to do it with scripts completely, then his guide is a bit hard to follow since some of his scripts are not necessary to execute, although he wants you to use them.

Therefore, I had to come up with the above.

Edited by Space Surfer
Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...