CAB File vs MSU File: Differences and Which to Use

MSU files are self-installing update packages, while CAB files are archives that often hold drivers, system files or update components. Here is how they differ and which install method fits each.

7-Zip window open inside a Windows 10 .msu update package, with the SSU-19041.1704-x64.cab file highlighted in yellow.
In this article

A CAB file is a compressed archive, while an MSU file is a Microsoft Update Standalone Package that Windows installs for you. If you are weighing a cab file vs msu file for your PC, the quick test is where it came from: a manual security update or hotfix download is usually an MSU. [1] For more detail, see How to Install a Driver From a CAB File in Windows.

CAB files typically contain drivers, system files and other Windows components. [2] MSU files are more or less self-installing, and they run through the Windows Update Standalone Installer, WUSA.EXE. [2][1] An MSU is also essentially an archive of CAB files, so the CABs you may need are packed inside it. [3][1]

Below, you will see how the two compare, how each installs, and which to download. The steps focus on Windows 11, with Windows 10 differences noted.

CAB vs MSU at a glance

A CAB file is a compressed archive of components, while an MSU file is a self-installing update package that wraps CAB files. The table compares them on the criteria that matter most.

Criterion

CAB file

MSU file

What it is

A compressed archive

A Microsoft Update Standalone package [1]

Typical contents

Drivers, system files and other Windows components [2]

CAB files inside [1]

Installer

A tool is needed to work with its contents

Windows Update Standalone Installer, WUSA.EXE [1]

Self-installing?

No

More or less self-installing [2]

Common source

Extracted from an MSU, or found in the Windows Update download folder [4]

Manual download of a Microsoft security update or hotfix [1]

The express CAB variant

You may also run into an express CAB. It appears in Windows\SoftwareDistribution\Download after you install updates through Windows Update [4]. It holds only the update manifest files plus an XML file, which Windows Update uses to identify the original package contents and decide which parts your system needs [4]. You may also find this useful: How to Install a CAB File with the DISM Command.

Because of that, an express CAB is not a complete package. A forum reply says it cannot be used for integration, since only Windows Update knows how to handle that mechanism [4]. If you are choosing a file to use by hand, the full CAB or the MSU is the one you want.

What the table means in practice

The main difference is packaging. An MSU is essentially an archive of CAB files, so a tool like 7-Zip or WinRAR can open it [3]. A CAB is one of the pieces inside, or a standalone archive of drivers and components [2].

For a one-off manual update, an MSU is the easier download because it largely runs itself [2]. A CAB suits cases where you need the raw components, such as drivers.

What is an MSU file and how does it install?

An MSU file is a Microsoft Update Standalone Package, and Windows installs it through the Windows Update Standalone Installer, WUSA.EXE. When you download a security update or hotfix by hand, an MSU is typically what you get. [1]

How it installs

MSU files are more or less self-installing. [2] You double-click the file, and Windows hands it to WUSA.EXE, which lives in the C:\Windows\system32 folder. [1] You do not need to unpack anything first.

The package carries what the installer needs to decide whether to proceed. Its metadata lets Windows check whether the update applies to your PC. If it does not, you may see the prompt “The update is not applicable to your computer.” [5]

What is inside

An MSU is a wrapper around CAB files. [1] One Reddit poster described the structure as a kind of archive of .cab files. [3] According to one breakdown, a package holds these parts: [5]

  • Windows Update metadata describing the individual update file

  • .cab files, each containing one update

  • an .xml file describing the .msu package

  • a properties file with details such as the KB ID, package type and the title of the related Knowledge Base article

The installer reads those properties when installation begins. [5]

Installing many MSU files at once

If you have a folder full of updates, you can script the job. This example from an IT admin blog sets the source folder, moves into it, and runs WUSA.EXE on every MSU file: [1]

SET HOTFIXSRC=
CD /D %HOTFIXSRC%
FORFILES /P %HOTFIXSRC% /M *.MSU /C "cmd /c wusa @file /quiet /norestart"

Put your folder path after SET HOTFIXSRC=. In the last line, /quiet runs the install without prompts and /norestart stops an automatic reboot. [1]

For a single update, double-clicking is simpler. You only need the script approach when you are installing several packages in a row.

What is a CAB file and when do you need one?

A CAB file (cabinet file) is a compressed archive that typically holds drivers, system files and other Windows components. [2] You need one when a driver or component is distributed as a CAB rather than as a ready-to-run installer.

It does not install itself

Unlike an MSU, a CAB is not self-installing. [2] Double-clicking it will not apply an update. You either extract its contents or pass it to a tool that knows how to install it.

That is why CABs show up mostly in technical situations. For example, a driver vendor may hand you a CAB so you can unpack it and point Windows at the files inside, or an administrator may need to add a single update or component to a system.

Standard CAB vs. express CAB

Not every CAB is a full package. Windows Update also uses a lighter variant called an express CAB. One forum example shows how big the gap can be:

File

Size

windows6.1-kb2533552-x64.cab

9 MB

windows6.1-kb2533552-x64-express.cab

0.6 MB

[4]

The full CAB in that example also held extra files, named 1 to 75 with no file extension. [4] The express version is so small because it holds only the update manifest files and an XML file. [4]

Windows Update uses those files to work out which parts of the original package your system needs, then downloads only those. For a multilingual update, that means just the language resources matching your system. [4]

The practical takeaway: an express CAB is not a complete package, and one forum reply describes it as unusable for integration. [4] If you need something to install manually, use the full CAB or the MSU.

Where CAB files appear on your PC

After Windows Update installs updates, you can find CAB files in this folder: [4]

Windows\SoftwareDistribution\Download

The folder sits inside your Windows directory, typically C:\Windows. If you spot CABs there, they are leftovers from updates Windows has already handled, and they may include express CABs rather than full packages. [4]

When you actually need a CAB

  • You have a driver or component delivered as a CAB.

  • You want the individual update files that sit inside an MSU. Each CAB inside an MSU contains one update. [5]

  • You are working on a system image or deployment and the update is supplied in CAB form.

If you just want to patch a single PC with a security update, the MSU is usually the simpler file to work with.

Which install method suits each file?

Use the MSU for a simple manual update and treat a CAB as something you install with a tool or extract first. Which route you take depends on the file you have.

MSU: double-click or WUSA.EXE

An MSU is the easy case: double-click it and the install runs as you would expect. [6] Behind the scenes, Microsoft Update Standalone Packages are installed through the Windows Update Standalone Installer, WUSA.EXE, which lives in C:\Windows\system32. [1]

If you have many MSU files, a script can run them in a batch. This line installs each MSU in the current folder without a prompt or restart:

FORFILES /P %HOTFIXSRC% /M *.MSU /C "cmd /c wusa @file /quiet /norestart"

The source folder is set in %HOTFIXSRC%, /quiet hides prompts, and /norestart stops an automatic reboot. [1] If the update doesn’t apply to your PC, you may see “The update is not applicable to your computer.” [5]

CAB: DISM or extract first

Double-clicking a CAB doesn’t install it. It only opens the archive and shows the packaged content, none of which looks actionable. [6] To install a CAB as an update, use a command-line tool such as DISM from an elevated prompt (the full steps are in the dedicated DISM walkthrough), or extract the CAB and work with what’s inside.

Extracting an MSU to get CABs

Sometimes you need the CABs, for example when a tool accepts only CAB files. They are included inside the MSU, so you extract them. [1] On Windows 7 and later, WUSA.EXE has an /extract option:

wusa /extract:c:\temp\cab

The path after the colon is where the CAB files are written. [1] Add the MSU file path before the switch. Microsoft also documents a PowerShell script that extracts .msu and .cab files to a folder you choose, including nested CABs. [7] You run it from an administrator PowerShell window with .\Extract-MSUAndCAB.ps1. [7]

Windows 10 vs 11

The MSU and CAB methods above are the same on Windows 10 and 11, but Windows 10 is past or near its end of support, so moving to Windows 11 matters more than which package you pick.

Safety first

Back up important data or create a restore point before installing a manual update package, so you can roll back if something goes wrong.

So, which should you download?

Pick the MSU when you just want to apply a manual update: it is more or less self-installing, so you can open it and let Windows handle the rest. [2]

Reach for a CAB when you are working with drivers, system files or other Windows components. [2]

Whichever you choose, download the package that matches your Windows version and system type. An MSU checks its own metadata, and if the update doesn’t fit your PC you may see “The update is not applicable to your computer.” [5]

Sources

  1. Extracting CAB files from Microsoft Update Standalone Package (MSU)

  2. Windows Updates: CAB vs MSU Files

  3. modifying .msu files : r/ReverseEngineering

  4. Differences between cab and express cab files

  5. How To Install Windows Updates From MSU And CAB Files

  6. How to install SCCM patches manually on Vista/Server 2008

  7. Scripts to extract .msu and .cab files – Windows Server