How to Install a CAB File on Windows 10/11: 3 Proven Methods

You've just downloaded a .cab file for a critical Windows Update or a hardware driver, and you double-click it, expecting a friendly installer wizard. Instead, nothing happens—or worse, Windows asks you what program should open it. If you've been there, you know the frustration. CAB files aren't like EXE installers; they're compressed archives that Windows treats as system components, and installing them requires a different approach.

The good news? Once you understand how the CAB format works, the process becomes straightforward. In this guide, I'll walk you through three proven methods to install a CAB file on Windows 10/11, covering everything from command-line tools to manual driver extraction. I've used all three approaches in real-world scenarios—sometimes because a Windows Update failed to install automatically, other times because I needed to deploy a specific driver across multiple machines. Each method has its place, and I'll help you figure out which one fits your situation.

---

What Is a CAB File and Why Do You Need to Install It?

A CAB (Cabinet) file is Microsoft's native compressed archive format, dating back to the early 1990s. Think of it as a ZIP file's older, more reserved sibling—it compresses files into a single package, but it's designed primarily for system-level components rather than user-facing applications. When you download a standalone update from the Microsoft Update Catalog, it almost always arrives as a .cab file. The same goes for many device drivers, especially those for network adapters, printers, and chipset components.

The tricky part is that Windows doesn't treat CAB files like regular installers. You can't just double-click and expect a setup wizard to appear. The operating system sees a CAB file as a payload to be deployed through specific servicing tools, which is why so many users get stuck at the download stage.

CAB vs. MSI vs. EXE: Understanding the Difference

To make sense of why CAB files behave differently, it helps to compare them with the other formats you're likely familiar with:

Common Scenarios: Windows Updates and Driver Installation

In my experience, there are two main reasons you'll need to install a CAB file manually:

1. Windows Update failures: Sometimes the automatic update mechanism fails, or you need to apply a specific KB (Knowledge Base) update that isn't being pushed to your machine yet. The Microsoft Update Catalog is the official repository for these files—you search for the KB number, download the .cab, and install it manually.

2. Driver updates: Hardware manufacturers often distribute drivers as CAB files, particularly for enterprise deployment. If you're setting up a printer or a network card and the manufacturer's website only offers a .cab download, you'll need to extract it and point Device Manager to the extracted folder.

Both scenarios are more common than you might think. I've lost count of how many times I've helped colleagues apply a critical security patch that Windows Update kept failing to install—the manual CAB route was the only reliable workaround.

---

Method 1: Install a CAB File Using DISM Command

DISM is the Swiss Army knife of Windows servicing. It's a command-line tool that can handle everything from mounting Windows images to installing updates, and it's been my go-to for CAB file installation since Windows 8. The command syntax is straightforward, but you need to be careful with the exact parameters.

Step-by-Step: DISM /Online /Add-Package

Here's the process I use every time:

1. Open Command Prompt as Administrator. Right-click the Start button and select "Terminal (Admin)" or "Command Prompt (Admin)" depending on your Windows version. You can also press Win + X and choose the appropriate option. If you see a User Account Control prompt, click "Yes."

2. Navigate to the directory containing your .cab file. Use the cd command to change directories. For example, if your file is in the Downloads folder and your username is "John," type:

cd C:\Users\John\Downloads

3. Execute the DISM command. The basic syntax is:

dism /online /add-package /packagepath:filename.cab

Replace filename.cab with the actual name of your file. For instance, if you downloaded windows10.0-kb5025221.cab, you'd run:

dism /online /add-package /packagepath:windows10.0-kb5025221.cab

4. Wait for the process to complete. You'll see a progress bar in the Command Prompt window. Depending on the size of the update and your system's speed, this can take anywhere from a few minutes to half an hour. Don't close the window during this time—I've made that mistake once, and it left the system in an inconsistent state.

5. Restart if prompted. When the installation finishes, DISM may ask you to restart your computer. Type Y and press Enter to proceed.

How to Verify the Installation Was Successful

After the restart, you'll want to confirm the update actually applied. Here's what I check:

• Windows Update history: Go to Settings > Windows Update > Update history. Look for the KB number you installed—it should appear in the list.
• DISM package list: Open Command Prompt as Administrator and run:

dism /online /get-packages

This outputs a long list of installed packages. Scroll through and look for the package name or KB number you just installed. If it's there with a "Package State: Installed" status, you're good.

One thing to note: the get-packages output can be overwhelming because it lists every servicing package on your system. I usually pipe it through findstr to filter for the specific KB number:

dism /online /get-packages | findstr /i "kb5025221"

This saves you from scrolling through hundreds of lines.

---

Method 2: Install a CAB File with PowerShell

If you prefer PowerShell over the classic Command Prompt—or if you're automating installations across multiple machines—this method is your best bet. PowerShell gives you the same underlying functionality as DISM but with a more scriptable interface.

Using the Add-WindowsPackage Cmdlet

The process mirrors the DISM approach but uses PowerShell's native cmdlet:

1. Open PowerShell as Administrator. Click the Start menu, type "PowerShell," right-click "Windows PowerShell," and select "Run as Administrator."

2. Navigate to your file's location. Use the cd command just like in Command Prompt:

cd C:\Users\John\Downloads

3. Run the Add-WindowsPackage cmdlet. The syntax is:

Add-WindowsPackage -Online -PackagePath "filename.cab"

For example:

Add-WindowsPackage -Online -PackagePath "windows10.0-kb5025221.cab"

The -Online parameter tells PowerShell to apply the package to the currently running Windows installation. If you were servicing an offline image (like a WIM file for deployment), you'd use -Path instead.

4. Wait for completion. You'll see a progress bar similar to DISM. The process takes roughly the same amount of time.

Silent Installation and Automation Tips

Here's where PowerShell really shines. Because the cmdlet doesn't require any user interaction after execution, you can embed it in scripts for batch processing. For example, I've used this snippet to install multiple CAB files in sequence:

$cabFiles = Get-ChildItem "C:\Updates\*.cab"
foreach ($cab in $cabFiles) {
    Write-Host "Installing $($cab.Name)..."
    Add-WindowsPackage -Online -PackagePath $cab.FullName
}

This script grabs every .cab file in the C:\Updates folder and installs them one by one. It's saved me hours when deploying cumulative updates across test machines.

You can also combine this with logging to track what was installed:

Add-WindowsPackage -Online -PackagePath "update.cab" | Out-File -FilePath "C:\Logs\install.log"

The cmdlet outputs a result object that includes the package name and restart status, which is useful for auditing.

---

Method 3: Install a CAB File as a Driver (Manual Extraction)

The first two methods work perfectly for Windows Updates, but what if your CAB file contains a device driver? In that case, you don't want to "install" the CAB itself—you want to extract its contents and let Windows load the driver from the extracted files. This is the approach I recommend for hardware drivers, and it's the one that trips up most users.

Extracting the CAB File Contents

The extraction process is surprisingly simple:

1. Double-click the .cab file. Windows File Explorer can open CAB files natively, displaying their contents like a regular folder.

2. Select all files. Press Ctrl + A to highlight everything inside the archive.

3. Right-click and choose "Extract." Windows will ask you where to save the files. Pick a folder you'll remember—I usually create a dedicated folder like C:\Drivers\Printer to keep things organized.

4. Click "Extract" to confirm. The files will be decompressed to your chosen location.

That's it. You now have the driver files ready for installation.

Updating the Driver via Device Manager

With the files extracted, here's how to complete the driver installation:

1. Open Device Manager. Right-click the Start button and select "Device Manager" from the menu.

2. Locate the target device. Look for the hardware component that needs the driver. It might be under "Printers," "Network adapters," "Display adapters," or "Other devices" (if the driver isn't installed yet, the device often appears with a yellow warning icon).

3. Right-click the device and select "Update Driver."

4. Choose "Browse my computer for drivers." This is the second option in the wizard.

5. Click "Browse" and select the folder where you extracted the CAB file. Make sure "Include subfolders" is checked—some drivers are organized in nested directories.

6. Click "Next" and let Windows do its thing. The installation wizard will search the folder for compatible driver files and install them. When it's done, click "Close."

I've used this method countless times for network adapters and printers, especially when the manufacturer's auto-installer was buggy or outdated. It's also the only way to install drivers on Windows 10/11 when you're working with enterprise deployment images.

---

Troubleshooting: Fix Common CAB File Installation Errors

No guide would be complete without addressing the errors you're likely to encounter. I've hit most of these myself, and they're almost always fixable with the right approach.

Error 0x800f0831 and Other DISM Failures

This error code is one of the most common DISM failures. It typically means "update not found"—the system couldn't locate the package you're trying to install. Here's what I check when I see it:

DISM /Online /Cleanup-Image /RestoreHealth

This scans for corruption in the Windows component store and fixes it using Windows Update as the source. It can take 15-20 minutes, but it resolves a surprising number of DISM failures.

If the error persists, the CAB file itself might be corrupted. Re-download it from the Microsoft Update Catalog and try again. I also recommend checking the file's digital signature—right-click the file, go to Properties > Digital Signatures, and verify that the signer is "Microsoft Windows" or the relevant hardware manufacturer.

What to Do If You Don't Have Administrator Rights

This is a common roadblock, especially on corporate-managed machines. DISM and PowerShell methods both require elevated privileges—there's no way around that. If you're not an administrator, you have two options:

1. Contact your IT department. They can either install the update for you or grant you temporary admin rights. In most enterprise environments, this is the only sanctioned path.

2. Use the manual extraction method for drivers. Extracting a CAB file and installing a driver through Device Manager sometimes works without admin rights, depending on how your system is configured. It's worth a try, but don't be surprised if Windows blocks it.

In my experience, trying to bypass admin restrictions is more trouble than it's worth. A quick ticket to IT usually resolves the issue faster than any workaround.

---

CAB File Safety: How to Avoid Malicious Packages

I need to be blunt here: CAB files can be dangerous. Because they're essentially archives that Windows will process at a system level, they're an attractive vector for malware. A malicious CAB file could contain a driver that compromises your system or a script that runs with elevated privileges.

Risks of Installing CAB Files from Untrusted Sources

The most significant risk is sideloading—installing a package from outside the official Microsoft ecosystem. While sideloading isn't inherently malicious, it bypasses the security checks that Windows Update normally performs. A CAB file from a random website could contain:

• Malicious drivers that intercept your keystrokes or network traffic
• Modified system files that disable security features
• Scripts that execute during the installation process

I've seen too many users download "driver update" CAB files from third-party sites, only to end up with adware or worse. The Microsoft Update Catalog is the only source I trust for Windows Updates, and for hardware drivers, I stick to the manufacturer's official website.

Before installing any CAB file, I run through this checklist:

• Downloaded from an official source (Microsoft, hardware manufacturer)
• File has a valid digital signature
• Scanned with Windows Defender or your antivirus
• File size matches the expected size listed on the download page

Best Practices for Safe Installation

Beyond verifying the source, here are the habits I've developed over years of handling CAB files:

Create a system restore point first. This is non-negotiable for me. If something goes wrong, you can roll back to a working state in minutes. Go to Control Panel > System > System Protection > Create, and give it a descriptive name.

Verify the digital signature. Right-click the file, go to Properties > Digital Signatures, and check that the signer is legitimate. A valid signature doesn't guarantee safety, but its absence is a red flag.

Keep a backup. If you're installing a driver for critical hardware, make sure you have a backup of your current driver. Device Manager lets you roll back drivers (right-click the device > Properties > Driver > Roll Back Driver), but only if the previous driver is still available.

---

FAQ

Is it safe to install a CAB file?

It's safe only if the file comes from a trusted source. CAB files from the Microsoft Update Catalog or official hardware manufacturer websites are generally safe. Before installing, verify the digital signature and scan the file with your antivirus software. If you downloaded the file from a random website or received it via email, don't install it—the risk of malware is simply too high.

What is the difference between CAB and MSI files?

MSI files are Windows Installer packages designed for application installation. They contain installation logic, registry modifications, and uninstall routines. CAB files, on the other hand, are pure compressed archives—they hold files but don't contain any installation instructions. You need tools like DISM or PowerShell to apply CAB files as system updates, or you extract them manually for driver installation.

How do I uninstall a CAB file update?

Go to Settings > Windows Update > Update history > Uninstall updates. Find the KB number associated with the CAB file, select it, and click "Uninstall." Note that not all updates can be removed—some are permanent servicing updates. If the option is grayed out, the update is likely a permanent component of the system.

Can I install a CAB file on Android?

No. CAB files are a Windows-specific format and aren't natively supported on Android. Android uses APK files for applications and various archive formats for data. If you've encountered a CAB file on Android, it's likely a mislabeled file or something from a Windows emulator. There's no practical way to install a CAB file on Android, and you shouldn't try.

---

Final Thoughts

Installing a CAB file on Windows 10/11 doesn't have to be a headache. The three methods I've covered here—DISM, PowerShell, and manual extraction—cover virtually every scenario you'll encounter. For Windows Updates, DISM or PowerShell are your best options. For device drivers, manual extraction through Device Manager is the way to go.

The key takeaways I want you to remember:

• Always download CAB files from official sources. The Microsoft Update Catalog is your friend.
• Verify the installation afterward. A quick check of Windows Update history or the DISM package list confirms success.
• Create a restore point before installing. It's a five-minute step that can save you hours of troubleshooting.

I've installed hundreds of CAB files over the years, and these methods have never let me down. If you run into an error I didn't cover, or if you have a tip of your own, leave a comment below—I'd love to hear how it goes. And if this guide helped you out, share it with someone else who's wrestling with a stubborn .cab file. We've all been there, and a little shared knowledge goes a long way.