One of the common questions we receive is “How does one go about deploying and installing multiple updates to offline computers?” First, we are excited to let you know that we’ve been working on new functionality specifically designed for offline updating of detached network environments. We expect the new offline updates options to be available in approximately a month from now. While it will address the bulk of requirements that most users have for deploying Windows Updates to computers that do not have access to the internet or a WSUS server, there is still an open question of how does one go about deploying multiple .MSU files to a computer without having to do one deployment for each .MSU file.
The ‘Deployment’ feature of BatchPatch enables you to install multiple Windows Updates in the form of .MSU files (or could be any other type of installation file such as .MSI or .EXE, though most Windows Update standalone files nowadays come in the .MSU flavor) on your target computers. Below is a step-by-step tutorial:
- Prepare the script. In this example we are going to install 5 .MSU files in succession, with a single script that will be deployed with BatchPatch. I’ve already downloaded the 5 .MSU files from Microsoft. They are stored in a folder on my computer called “5_MSU_Files.” Additionally, I’ve created a batch file called “Install_Multiple_MSU_Files.cmd” which is included in the same directory. Note the directory contents and the script contents below:
![Install_Multiple_MSU_Files_Batch]()
- Prepare the deployment. Select Actions > Deploy software/patch/script/regkey etc > Create/modify deployment. Note that after we select the Install_Multiple_MSU_Files.cmd in the first field, we also check the box to “Copy entire directory contents in addition to the specified file.”
- Execute the deployment. When we click the ‘Execute’ button, BatchPatch will copy the script file along with the 5 .MSU files to the target computer’s working directory. BatchPatch will then remotely execute the script, which will install the 5 update files sequentially.
That’s all there is to it. As you can see, the process is actually pretty simple. Now of course when we installed these updates we used the /norestart option, so now that the script completed, we will want to finalize the installation by rebooting the target machine. We can do this using the Actions > Reboot option in BatchPatch.



