Yes, DISM can install a CAB file. Run it with the /Add-Package option from an elevated prompt and point /PackagePath at the .cab, and Windows installs it as an update package. [1][2] The same command works on Windows 11 and Windows 10. [3][2] Related reading: How to Install a Driver From a CAB File in Windows.
This is handy when Windows Update fails to show an update or hotfix you need. [3] Microsoft often ships standalone updates as .cab files, usually wrapped inside .msu files, and DISM lets you install the .cab directly. [3][2]
Below you will find what to prepare, the exact command, a PowerShell alternative, how to confirm the install, and what to do when DISM reports an error.
Key takeaways
/Add-Packageis the DISM option that installs a .cab update package.It helps when Windows Update lists nothing.
The command is the same on Windows 11 and 10.
What should you know before you start?
Before you run anything, make sure you have three things in place: an elevated prompt, a package that matches your PC, and a short, simple file path.
Safety first
Installing a package changes your system files, so protect yourself before you start. Back up important files or create a restore point first. Only use CAB files from trusted sources, such as the Microsoft Update Catalog, which lets you search by KB number and download the standalone package. [4]
Use an elevated prompt
DISM needs administrator rights to service a running system. Open Command Prompt or PowerShell as administrator, not a regular window. The command you run later targets the running system with /Online. [1]
Match the package to your PC
The package must apply to your Windows version and processor architecture. If it does not, the installer refuses it and reports that the update is not applicable to your computer. [4]
The same KB number often appears several times in the Catalog, with a separate package per processor type and sometimes per Windows version. [4] On most modern PCs you want the x64 package, and the file name usually shows it, as in windows11.0-kb#######-x64.cab. [4]
A manual install also does not skip Windows’ own checks, such as prerequisites and supersedence, so it will not fix every failure. [4]
Keep the CAB at a short path
Save the file in a simple folder, such as C:\Updates. A short path with no unusual characters is easier to type correctly and easy to wrap in quotes. The example file path in Microsoft-style guides uses exactly this layout. [4]
Create the folder in File Explorer, move the downloaded CAB into it, and the file is ready for the install step.
How do you install a CAB file with DISM?
Installing a CAB update takes one command in an elevated Command Prompt. Here are the steps in order.
Open Start, search for Command Prompt, right-click the top result, and select Run as administrator. [2]
Type the command below, replacing the path and file name with your own CAB file, and press Enter. [4]
DISM /Online /Add-Package /PackagePath:"C:\Updates\windows11.0-kb#######-x64.cab"
/Online targets the Windows installation you are running, /Add-Package installs a package, and /PackagePath points to the CAB file. Keep the quotes around the path. [2] 3. Wait for the operation to complete and read the result message. DISM reports whether the operation finished successfully or returned an error. A progress bar appears while it works, so give it time before closing the window. 4. Restart if prompted. Many updates only finish applying after a reboot.
For example, if you saved a Windows 11 update as C:\Updates\windows11.0-kb5012592-x64.cab, that exact path goes inside the quotes. [2]
VERSIONS
The steps are the same on Windows 11 and Windows 10. On Windows 10, you open Command Prompt as administrator and run the same dism /Online /Add-Package /PackagePath: command. [5] Windows 10 is past end of support, so updates available for it may be limited.
Can you use PowerShell instead?
Yes, PowerShell can do the same job. The Add-WindowsPackage cmdlet installs a CAB on the running system, and Windows 11 supports it alongside the DISM command [2]. Run it from an elevated PowerShell window:
Add-WindowsPackage -Online -PackagePath "MY_FILE.cab"
-Online targets the Windows installation you are using, and -PackagePath points to the CAB file. Replace MY_FILE.cab with your real path, such as C:\Updates\yourpackage.cab. Keep the quotes around it. [6]
Installing several packages
With DISM, you add more packages by repeating the /PackagePath switch in one command. Microsoft’s example installs two CABs this way, with /IgnoreCheck added at the end: [1]
Dism /Image:C:\test\offline /Add-Package /PackagePath:C:\packages\package1.cab /PackagePath:C:\packages\package2.cab /IgnoreCheck
Working on an offline image
To service a Windows image that is not running, swap /Online for /Image: followed by the folder holding the mounted image. Microsoft’s example uses C:\test\offline: [1]
Dism /Image:C:\test\offline /Add-Package /PackagePath:C:\packages\package1.cab
Writing a log file
Add /LogPath to save the operation’s log to a file of your choice. Microsoft’s example writes to AddPackage.log: [1]
Dism /Image:C:\test\offline /LogPath:AddPackage.log /Add-Package /PackagePath:C:\packages\package.msu
The same switch works with /Online, so you can keep a record of a live install and read it if something goes wrong.
Pick whichever tool you prefer. DISM is quicker to type in Command Prompt, while PowerShell suits you if you already work in it or write scripts.
How do you check the package installed?
Run dism /online /get-packages from the same elevated prompt to see every package Windows currently has, including the one you just added. [6]
dism /online /get-packages
The /online switch tells DISM to work on the running Windows installation, and /get-packages lists the packages in it. [1] If the list is long, you can ask for a specific layout with the /Format:Table or /Format:List option. [1]
Find your package in the list
Scan the output for the package you installed. Each entry shows a package identity, which is a long name that usually includes the update or feature name, a version number, and the architecture. For a Windows update, look for the KB number from your CAB file name.
The entry also shows a state. A package that installed correctly is listed with that state, and a package that is waiting on a restart will say so. If you were prompted to restart earlier, do that first and run the command again.
To narrow a long list on screen, you can pipe the output through the Windows find command, for example dism /online /get-packages | find "KB", though that filter is a general Command Prompt trick rather than a DISM option.
Remove a package if you need to
If the package causes problems, copy its exact identity from the list and remove it with this command, replacing PACKAGENAME with that identity. [6]
dism /online /remove-package /packagename:PACKAGENAME
The /remove-package option uninstalls the package, and /packagename points to the one you want gone. [1] Use the full name exactly as DISM printed it, since a partial name will not match.
For CAB-based updates, you can also remove them through Settings, using Windows Update > Update history > Uninstall updates. [6]
Why does DISM say it cannot find the file or the update is not applicable?
Most DISM failures with a CAB file come down to four causes: a bad path, a package that does not match your PC, a prompt without admin rights, or an MSU file used in the wrong place.
Wrong path or missing quotes
The message “cannot find the file specified” usually means DISM could not locate the file you named. One Windows 10 user who downloaded a CAB from the Update Catalog hit exactly this error when running the command. [7] Check that the folder and file name are spelled exactly as they appear in File Explorer, including the KB number and -x64 ending.
Put the full path in quotes, as the working example does:
DISM /Online /Add-Package /PackagePath:"C:\Updates\windows11.0-kb#######-x64.cab"
Quotes matter most when a folder name contains spaces, so keep the file in a simple folder like C:\Updates.
The update is not applicable
If DISM or the installer says the update is not applicable, the package does not fit your PC. The package must match your Windows version and processor architecture, and one KB number often has several separate downloads. [4] Go back to the Microsoft Update Catalog and confirm you downloaded the right one. [7]
The prompt is not elevated
DISM needs an administrator session. Microsoft’s instructions begin with opening an administrative Command Prompt, and the same applies to the other install commands. [7][3] If you opened a normal prompt, close it and reopen it as administrator, then run the command again.
You have an MSU file, not a CAB
An .msu file is a self-contained installer run by the Windows Update Standalone Installer, wusa.exe, not by DISM. [4] For example:
wusa.exe "C:\Updates\windows11.0-kb#######-x64.msu"
CAB files are normally packaged inside MSU files, so a CAB you have extracted from one can be installed directly with DISM. [3]
Wrapping up
Remember three things: run DISM from an elevated prompt, point /PackagePath at the exact CAB location, and use a package that matches your Windows version and architecture. Get those right and the install is usually uneventful.
When it finishes, confirm the result by running dism /online /get-packages and looking for the package name in the list. [6] If something goes wrong, our separate guides on CAB install failures and on CAB versus MSU files cover those cases in detail. For more detail, see How to Install a CAB File on Windows 11 (Step by Step).
