A CAB file can contain a Windows update, driver package, language component, or another type of Windows package. The correct installation method depends on what the CAB actually contains. For a Windows servicing package that is intended for your version and architecture of Windows 11, DISM or the DISM PowerShell module is usually the supported approach. Do not install an unknown CAB file simply because Windows allows the command.
Before You Install a CAB File
Confirm where the CAB came from and what it is intended to install. A package can fail because it is for the wrong Windows version, build, edition, language, or processor architecture, or because another prerequisite package is required. Prefer packages from Microsoft, Windows Update, your PC manufacturer, or another trusted hardware/software vendor.
Create a backup or restore point when appropriate, especially before manually servicing Windows. Save your work because some packages require a restart.
How to Install a Windows CAB Package with DISM
- Move the CAB file to a simple local path. For example, create
C:\Packagesand place the file there. This makes the command easier to type. - Open Terminal as administrator. Right-click Start and choose Terminal (Admin), then approve the User Account Control prompt.
- Run DISM with the CAB path. Enter
DISM /Online /Add-Package /PackagePath:"C:\Packages\package.cab", replacing the example filename with the real CAB filename. - Wait for DISM to finish. Do not close the terminal while the package is being applied.
- Read the final result. DISM should report whether the operation completed successfully or provide an error code that can be used for troubleshooting.
- Restart if required. Some Windows packages do not fully apply until the PC restarts.
PowerShell Method
Windows also provides the DISM PowerShell module. In an elevated PowerShell session, a package intended for the running Windows installation can be added with a command such as:
Add-WindowsPackage -Online -PackagePath "C:\Packages\package.cab"
This is another supported servicing interface for compatible Windows packages. It does not make an incompatible package compatible.
How to Verify the Package
For Windows servicing packages, you can review installed packages with DISM:
DISM /Online /Get-Packages
Look for the relevant package identity and its state. Windows Update history or the associated feature/driver version may also provide a clearer verification method depending on what the CAB installed.
What If the CAB Contains a Driver?
A driver CAB may contain INF driver packages rather than a Windows update package. In that situation, extracting the CAB and installing the appropriate signed driver package through Device Manager or pnputil may be the correct method. Do not assume DISM /Add-Package is appropriate for every CAB file.
If the CAB came from your PC or hardware manufacturer, follow that vendor’s installation instructions. Manufacturer installers often handle device detection and dependencies more safely than manual extraction.
Common CAB Installation Errors
The package is not applicable
This usually means the package does not match the current Windows build, architecture, edition, language, or installed prerequisite state. Verify the package documentation instead of forcing installation with ignore-check options.
Access denied or elevation errors
DISM servicing of the running Windows installation normally requires administrator rights. Open Terminal as administrator and try again only if you are authorized to modify the PC.
DISM reports a pending operation
Restart Windows and complete any pending Windows Update work before trying the package again. Stacking manual servicing operations while Windows is waiting for a restart can complicate troubleshooting.
The CAB came from an untrusted download site
Do not install it. System packages and drivers operate with significant privileges. Obtain the package from Microsoft, Windows Update, the device manufacturer, or the software vendor that actually provides the component.
Can You Double-Click a CAB File to Install It?
File Explorer can open many CAB archives so you can inspect or extract their contents, but double-clicking a CAB is not a universal installation method. Whether the contents should be installed with DISM, a driver tool, an application installer, or not installed manually at all depends on the package type.
Summary
For a trusted Windows servicing CAB that is explicitly intended for your Windows 11 installation, use an elevated DISM or Add-WindowsPackage command and verify the result afterward. If the CAB contains drivers or application files, use the installation method specified by the vendor instead. Never force an incompatible or untrusted CAB package onto Windows just to get past an applicability error.
Matt Jacobs has been working as an IT consultant for small businesses since receiving his Master’s degree in 2003. While he still does some consulting work, his primary focus now is on creating technology support content for SupportYourTech.com.
His work can be found on many websites and focuses on topics such as Microsoft Office, Apple devices, Android devices, Photoshop, and more.