Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Patch Manager > How to deploy a Microsoft hotfix from an MSU file

How to deploy a Microsoft hotfix from an MSU file

Updated November 1, 2017


This article describes how to deploy Microsoft Hotfixes (.msu) packages via Patch Manager.

Patch manager does not support native .msu. It has to be converted to an executable (.exe) file first.


  • Patch manager, all versions
  • Windows


Method 1

  1. Extract the .msu file through Windows Remote Shell with WUSA using the following command:
    winrs.exe -r:<computername> wusa.exe <update> /extract:<destination>
  2. When complete, install the .cab package with dism.exe or Package Manager. To use dism.exe, use the command below:
    winrs.exe -r:<computername> dism.exe /online /add-package /PackagePath:<Path_To_Package>\
  3. What's key here is the local portion of the second command:
    dism.exe /online /add-package /PackagePath:<Path_To_Package>\
  4. So, in addition to self-extracting archives, and auto-executing WUSA, another option may be to run DISM.EXE against the CAB file directly.

Method 2

  1. Download the hotfix from Microsoft (they will email you a link).
  2. Extract the download to a folder. It will create an .msu file.
  3. If you don't have WinRAR, download and install it.  Right click the .msu file and select the option to open it in WinRAR ("Add to archive").
  4. On the General tab, select the checkbox "Create SFX archive".
  5. On the Advanced tab, select the SFX options... button:
    • General tab: Path to extract: %SYSTEMROOT% (or directory of your choice)
    • Setup tab: Run after extraction: %SYSTEMROOT%\System32\WUSA.exe %SYSTEMROOT%\<msuname.msu> /quiet
    • Modes tab: Hide all
    • Update tab: Extract and replace files; Overwrite all files

You now have an EXE that can be deployed with Eminentware/PackageManager as a single EXE without any parameters and without Package Boot.



Last modified