You just downloaded a driver or a Windows update, but it arrived as a mysterious .cab file. Double-clicking it does nothing—or worse, it opens a folder full of files you don't recognize. So, how do I install a CAB file?
I've been there. Over the years, I've probably installed hundreds of these cabinet files across every Windows version from XP through 11. The truth is, CAB files aren't like EXE installers. They're a compressed archive format that Microsoft uses to package everything from driver packages to standalone updates. And depending on what's inside, you have several ways to get them working.
This guide walks through every reliable method I know—from the quick right-click trick to command-line tools like DISM and PowerShell—plus troubleshooting for when things go sideways.
What Is a CAB File and Why Do You Need to Install It?
A CAB file (short for cabinet) is Microsoft's native compressed archive format. Think of it like a ZIP file, but with a few technical differences under the hood. It's been around since the mid-90s, and Microsoft still uses it extensively for distributing software components.
The key thing to understand: a CAB file is a container, not an installer. It holds files—drivers, update payloads, system components—but it doesn't know how to install itself. That's why double-clicking it just opens it like a folder instead of launching a setup wizard.
CAB vs. MSI vs. EXE: Understanding the Differences
| Format | What It Is | Typical Use Case | Self-Installing? |
|---|---|---|---|
| CAB | Compressed archive container | Driver packages, Windows Update standalone files, font storage | No—needs DISM, PowerShell, or manual extraction |
| MSI | Windows Installer package | Application installation with logic, rollback, and repair options | Yes—runs via Windows Installer service |
| EXE | Executable program | Full application installers, setup wizards | Yes—self-contained or bootstrapped |
| The practical difference matters. When you download an MSI, you double-click and a guided installer appears. An EXE might do anything from launching a setup wizard to running a portable app. But a CAB file just sits there, waiting for you to tell Windows what to do with it. |
Common Scenarios: Windows Updates, Driver Packages, and More
You'll most often encounter CAB files in two situations:
Microsoft Update Catalog downloads. When you search for a specific update on the Microsoft Update Catalog, you'll often get a CAB file instead of the standalone installer. For example, a file like KB5032906.cab contains the payload for that specific cumulative update. This is common for IT professionals who need to deploy updates manually across multiple machines.
Hardware driver packages. Many manufacturers—especially for printers, network adapters, and chipset components—package their drivers as CAB files. These typically contain an INF file (the installation instructions) plus the actual driver binaries.
Less commonly, you might see CAB files used for storing fonts, system files, or even game assets. But for 95% of users, it's updates and drivers.
Method 1: Install CAB File Using DISM Command (Windows 10 & 11)
The Deployment Image Servicing and Management (DISM) tool is my go-to for installing CAB files. It's built into Windows, handles both updates and drivers, and gives you clear feedback about what went wrong if something fails.
Step-by-Step: DISM Command with Parameters Explained
-
Open Command Prompt as Administrator. Press
Win + Xand select "Terminal (Admin)" or "Command Prompt (Admin)" depending on your Windows version. If User Account Control prompts you, click "Yes." -
Run the DISM command with the following syntax:
dism /Online /Add-Package /PackagePath:"C:\path\to\file.cab"
For example, if your file is in the Downloads folder:
dism /Online /Add-Package /PackagePath:"C:\Users\YourName\Downloads\KB5032906.cab"
-
Wait for the process to complete. DISM will show a progress bar. When it finishes, you'll see "The operation completed successfully."
-
Restart if prompted. If you're installing a Windows update, a restart is usually required to finalize the installation.
Here's what each parameter does:
/Online— Targets the currently running Windows installation. Use/Imageinstead for offline images (more on that below)./Add-Package— Tells DISM to install the package rather than just inspect it./PackagePath— Points to the location of your CAB file. The quotes are essential if your path contains spaces.
One thing I've learned the hard way: make sure the file path is correct. DISM doesn't give you a friendly "file not found" message—it just throws an error code that can be confusing if you're not expecting it.
Using DISM for Offline Images (Windows Server & PE)
If you're managing Windows Server 2019/2022 or deploying custom Windows images, you'll need the offline variant. This installs the CAB into a mounted WIM or VHD image rather than the running system:
dism /Image:"C:\mount\path" /Add-Package /PackagePath:"C:\path\to\file.cab"
The /Image parameter points to the mounted image directory. This is how IT admins inject updates into deployment images before rolling them out to multiple machines. It's a powerful technique, but it requires the Windows Assessment and Deployment Kit (ADK) and some familiarity with image servicing.
Method 2: Install CAB File with Windows PowerShell
PowerShell offers a cleaner syntax for the same operation. If you're already comfortable in the PowerShell environment, this might feel more natural than Command Prompt.
Using Add-WindowsPackage Cmdlet
-
Open PowerShell as Administrator. Right-click the Start button and select "Windows PowerShell (Admin)" or "Terminal (Admin)."
-
Run the Add-WindowsPackage command:
Add-WindowsPackage -Online -PackagePath "C:\path\to\file.cab"
For example:
Add-WindowsPackage -Online -PackagePath "C:\Users\YourName\Downloads\KB5032906.cab"
- Wait for the output. PowerShell will display a progress bar and then confirm the operation.
The -Online parameter targets the running system, and -PackagePath specifies the CAB file location. It's essentially the PowerShell equivalent of the DISM command—same underlying functionality, different interface.
I personally prefer PowerShell for scripting scenarios. If you're deploying CAB files to multiple machines, you can wrap this command in a loop or a foreach statement to process several files at once.
Method 3: Install CAB File via Right-Click and Device Manager (For Drivers)
Not every CAB file needs a command-line tool. If you're dealing with a driver package, there's often a simpler path.
The Simple Right-Click 'Install' Option
Some CAB files—particularly driver packages—include an INF file that registers an "Install" option in the right-click context menu.
- Right-click the CAB file.
- Look for "Install" in the context menu. If it's there, click it.
- Follow any prompts. Windows will process the INF file and install the driver.
This works best for driver packages that follow Microsoft's standard structure. But here's the catch: this option isn't always present. If you don't see "Install," don't panic—it just means the CAB doesn't have the right metadata for this shortcut. Move on to the manual method below.
Manual Driver Installation via Device Manager
When the right-click option is missing, or when DISM fails for driver packages, this is my reliable fallback:
-
Extract the CAB file contents. Double-click the CAB file in File Explorer to open it like a folder. Select all contents (
Ctrl + A), right-click, and choose "Extract." Pick a destination folder likeC:\Drivers\YourDevice. -
Open Device Manager. Press
Win + Xand select "Device Manager." -
Find the device with the issue. Look for devices with a yellow warning icon, or right-click the specific device you're updating.
-
Right-click the device and select "Update driver."
-
Choose "Browse my computer for drivers."
-
Click "Browse" and navigate to the extracted folder. Make sure "Include subfolders" is checked.
-
Click "Next" and let Windows search. It will find the INF file and install the driver.
-
Click "Close" when done.
This method is particularly useful when DISM throws an error like 0x800f081f (source not found). Extracting the files and pointing Device Manager directly at them often bypasses whatever issue the command-line tool was hitting.
Method 4: Extract CAB File Without Installing – A Practical Alternative
Sometimes you don't need to install the CAB file at all. You just need one file from inside it—maybe a DLL, a font, or a configuration file.
Using File Explorer's Built-in Extraction
Windows has native CAB extraction built into File Explorer:
- Double-click the CAB file. It opens like a folder, showing the contents.
- Select all contents (
Ctrl + A). - Right-click the selection and choose "Extract."
- Choose a destination folder and click "Extract."
That's it. The files are now available in your chosen location.
This is handy when you only need a specific file from a driver package or update. For example, if you're troubleshooting a printer driver and just need the PPD file, you can extract it without touching the rest of the system.
Using Third-Party Tools like 7-Zip for Extraction
If you prefer a more robust extraction tool, 7-Zip is my recommendation. It's free, open-source, and handles CAB files flawlessly.
- Install 7-Zip if you haven't already.
- Right-click the CAB file.
- Select "7-Zip > Extract Here" or "Extract to [filename]" for a dedicated folder.
7-Zip also lets you peek inside the CAB file without extracting everything—just open it in the 7-Zip File Manager and browse the contents.
Other options include WinRAR (paid but popular) and cabextract (a command-line tool for Linux and macOS). For most Windows users, though, 7-Zip is the sweet spot between functionality and simplicity.
Troubleshooting: Why Can't I Install a CAB File on Windows?
When things go wrong, they usually go wrong in predictable ways. Here are the most common errors I've encountered and how to fix them.
Common Error Codes and Their Fixes
| Error Code | Meaning | Fix |
|---|---|---|
| 0x800f081f | Source not found—DISM can't locate the package or its dependencies | Verify the file path is correct; check file integrity; try extracting and using Device Manager instead |
| 0x80070005 | Access denied—permissions issue | Run Command Prompt or PowerShell as Administrator; check folder permissions |
| 0x80070002 | File not found—the system can't find the specified file | Double-check the path; ensure the file wasn't renamed or moved; try copying the CAB to a simpler path like C:\Temp |
| 0x800f0831 | Package not applicable—the update doesn't match your system | Verify you downloaded the correct CAB for your Windows version and architecture (x64 vs. x86) |
For 0x800f081f, the most common culprit is a typo in the file path or a corrupted download. I've also seen cases where the CAB file requires a prerequisite update that isn't installed yet. In that scenario, extracting the contents and installing via Device Manager often works around the issue. |
For 0x80070005, the fix is almost always running the command as Administrator. If you're already running elevated and still getting this error, check whether your user account has write permissions to the system directories DISM needs to modify.
Checking Digital Signatures and File Integrity
Before installing any CAB file, especially from third-party sources, verify its digital signature:
- Right-click the CAB file and select "Properties."
- Go to the "Digital Signatures" tab.
- Check that the signer is a trusted publisher. For Microsoft updates, this should be "Microsoft Windows" or "Microsoft Corporation."
- Click "Details" to view the signature information.
If the file has no digital signature, or the signature is invalid, don't install it. I've seen malicious CAB files circulating that mimic legitimate driver packages—checking the signature takes ten seconds and can save you from a serious headache.
If you suspect system file corruption is blocking the installation, run the System File Checker:
sfc /scannow
This scans protected system files and repairs corrupted ones. It's not a direct fix for CAB installation issues, but it can resolve underlying problems that prevent packages from installing correctly.
How to Install CAB Files from Microsoft Update Catalog
The Microsoft Update Catalog is the official source for standalone Windows updates. Here's how to use it effectively.
Downloading the Right CAB File for Your System
- Go to the Microsoft Update Catalog.
- Search for the specific KB number or update name in the search box.
- Review the search results. You'll see multiple entries for different Windows versions and architectures.
- Identify the correct file for your system. Check the "Products" column for your Windows version (e.g., "Windows 10 Version 22H2") and the "Architecture" column for x64 or x86.
- Click "Download" next to the correct file. You'll get a link to download the CAB file.
The catalog can be overwhelming at first—there are often dozens of entries for a single update. The key is matching the product name and architecture to your system. If you're unsure, check your Windows version by pressing Win + R, typing winver, and pressing Enter.
Installing the Downloaded Update CAB File
Once you have the CAB file downloaded, installation follows the same methods covered earlier:
- DISM:
dism /Online /Add-Package /PackagePath:"C:\path\to\file.cab" - PowerShell:
Add-WindowsPackage -Online -PackagePath "C:\path\to\file.cab"
You'll need an administrator account for both methods. And after installation, a system restart is typically required to complete the update.
One tip from experience: if you're downloading multiple updates, keep them organized in a single folder with clear names. It makes the installation process much smoother, especially if you're deploying to several machines.
FAQ
Can I install a CAB file by double-clicking it?
Usually no. Double-clicking a CAB file opens it like a folder, showing its contents—it doesn't trigger an installation. The exception is driver CAB files that include an INF file with an "Install" option in the right-click context menu. For Windows updates, you must use DISM or PowerShell to install the package.
What is the difference between CAB and MSI files?
A CAB file is a compressed archive format used for distributing multiple files—it's a container with no installation logic. An MSI file is a Windows Installer package that contains both the files and the installation instructions, including registry changes, shortcuts, and uninstall logic. MSI files are self-installing; CAB files require a separate tool or command to install.
Is it safe to install CAB files from the internet?
It depends on the source. CAB files from official Microsoft sources—like the Microsoft Update Catalog—are safe. Files from third-party websites are riskier; they could contain malicious drivers or modified system files. Always check the digital signature before installing. If the file isn't signed by a trusted publisher, don't install it.
How do I install a CAB file on Windows 11?
The methods are identical to Windows 10. You can use DISM (dism /Online /Add-Package /PackagePath:"path"), PowerShell (Add-WindowsPackage -Online -PackagePath "path"), or Device Manager for driver packages. Windows 11 uses the same underlying architecture, so the commands and steps are exactly the same.
Conclusion
Installing a CAB file doesn't have to be a mystery. The method you choose depends on what's inside the file and what you're trying to accomplish:
- For Windows updates: Use DISM or PowerShell. Both work reliably, and DISM gives you more detailed output.
- For driver packages: Try the right-click "Install" option first. If that's not available, extract the contents and use Device Manager.
- For extracting specific files: Use File Explorer's built-in extraction or 7-Zip for more control.
Before you install anything, verify the source. Check the digital signature, make sure the file comes from a trusted publisher, and confirm it matches your Windows version and architecture.
Start with the simplest method that fits your situation. If the right-click option works, great—you're done in seconds. If not, move to Device Manager or the command-line tools. And if you hit an error, the troubleshooting table above covers the most common issues.
If you found this guide helpful, share it with someone who might be struggling with CAB files. Have a question or a method we missed? Leave a comment below, and we'll help you out!