You can install a driver from a CAB file in Windows, but not by double-clicking it: extract the CAB first, then point Device Manager at the extracted folder. A driver CAB is a compressed Cabinet archive that holds the files and information Windows needs to install a driver, and drivers are often offered this way in the Microsoft Update Catalog. [1] For the next step, see How to Install a CAB File on Windows 11 (Step by Step).
The extraction step uses the built-in expand command, which unpacks the archive into a regular folder. [1] Device Manager can then pick up the driver from that folder. The same approach works on Windows 11 and Windows 10.
Below you will find what to prepare, how to extract the CAB, how to finish the install, and the mistakes that cause most failures.
What should you know before you start?
Before you touch a driver, know where the CAB comes from, make sure it fits your hardware, and set up a safety net. A few minutes here prevents most headaches later.
Where driver CABs come from
Drivers are often available in the Microsoft Update Catalog as CAB (Cabinet) archives. [1] These files hold the files and information Windows needs to install a driver. [1] The catalog lives at catalog.update.microsoft.com, and you find a driver by searching for it there. [1]
A CAB may also come from your device maker’s support page. Either way, the same extract-then-install approach applies.
Pick the right CAB
Search using the device or chipset name, such as your network adapter or touchpad model. Then choose the entry that matches both your hardware and your Windows version, including whether you run Windows 11 or 10. A driver built for a different device or version may not install, or may not work properly.
If you are unsure what hardware you have, open Device Manager and check the device’s name and properties before you download anything.
Use an administrator account
You need to be signed in with an administrator account. Extracting the CAB from an elevated Command Prompt and installing the driver both require those permissions. If you use a standard account, sign in as an administrator first or have the PC’s owner do it. Learn more in CAB File vs MSU File.
Safety: create a restore point first
A bad driver can cause crashes, a lost network connection, or a device that stops working. Protect yourself before you change anything:
Press the Start button, type Create a restore point, and open the result.
On the System Protection tab, select your Windows drive and click Create.
Name it something clear, such as “Before driver install,” and click Create again.
Also copy any important documents to an external drive or cloud storage. A restore point rolls back system changes, but it is not a substitute for a real backup of your personal files.
Keep the original CAB file too, so you can retry or reinstall if something goes wrong.
How do you extract the driver CAB file?
Extracting a driver CAB takes one command in an elevated Command Prompt. The command unpacks the files into a folder you choose, ready for Device Manager.
Create a destination folder. Make an empty folder with a short path, such as
C:\Drivers\MyDriver. In File Explorer, right-click an empty spot, choose New, then Folder, and rename it.Open Command Prompt as administrator. Search for Command Prompt in the Start menu, right-click it, and choose Run as administrator. Approve the User Account Control prompt.
Run the extract command. Replace the first path with the location of your downloaded CAB file and the second with your new folder:
expand -F:* "Path\to\cab\file.cab" "Path\to\destination\folder"
The -F:* part tells expand to extract every file in the archive. The quotation marks keep the command working if a path contains spaces. For example, if the file is in your Downloads folder, the command might look like this, with your own user name and file name:
expand -F:* "C:\Users\Sam\Downloads\driver.cab" "C:\Drivers\MyDriver"
Confirm the folder holds an .inf file. Open
C:\Drivers\MyDriverin File Explorer. You should see at least one file ending in.inf, usually alongside.sysor.catfiles. The.inffile is the setup information Windows reads when you point Device Manager at the folder in the next section.
If the command prints a list of files being expanded, it worked. Keep the folder where it is, because you will select it in the next step.
How do you install the driver in Device Manager?
Once the CAB is extracted, you install the driver by pointing Device Manager at the extracted folder. The steps are below.
Right-click Start and select Device Manager.
Find the device that needs the driver, such as a network adapter, display adapter, or an item with a yellow warning icon. Expand its category if needed.
Right-click the device and choose Update driver.
Choose Browse my computer for drivers.
Select Browse, pick the folder you extracted the CAB into (for example
C:\Drivers\MyDriver), and keep the option to include subfolders turned on. Then select Next.Let Windows scan the folder and install the matching driver. When the wizard reports success, select Close.
Restart your PC if Windows asks you to. Some drivers don’t take effect until you do.
If you extracted the CAB with expand -F:* "Path\to\cab\file.cab" "Path\to\destination\folder", the destination folder is the one you select in step 5. [1]
After the restart, the device should appear in Device Manager without a warning icon. If it still shows one, right-click it and open Properties to read the device status message.
Windows 11 and Windows 10
The steps are the same on Windows 11 and Windows 10.
Windows 10 is past its end of support, so it no longer receives regular security updates from Microsoft. If you can, plan a move to Windows 11 on hardware that supports it.
Is DISM an option for driver CABs?
DISM can install a CAB, but it is meant for update packages, so for a driver CAB the extract-and-install method is usually the safer choice.
The command looks like this, run from Command Prompt as administrator:
DISM /Online /Add-Package /PackagePath:"PATH\TO\CAB"
It installs a CAB onto the running copy of Windows, using /Online for the current system, /Add-Package to add the package, and /PackagePath to point to your CAB file. [2]
Why extraction is the better fit for drivers
/Add-Package treats the CAB as a Windows package, which suits updates. A driver CAB is just a set of driver files with an .inf file, and many of them are not built as servicing packages. Running DISM on one may simply fail with an error.
With the extract method, you choose the exact device in Device Manager and point Windows at the folder. You see which hardware is getting the driver, and Windows tells you if the files do not match. That control is useful when you are fixing one device, such as a network adapter or a printer.
For example, if you downloaded a CAB for a touchpad, extracting it and updating only the touchpad entry keeps the change limited to that device. DISM gives you no such choice.
When DISM makes sense
Use DISM when the CAB is a Windows update or feature package, not a driver you want to assign to a particular device. The full walkthrough, including its risks and what to do before running it, is covered in the separate article on installing a CAB file with the DISM command.
What mistakes should you avoid?
Most failed driver installs come down to four avoidable mistakes. Each one is easy to prevent once you know what to look for.
Using the wrong hardware or Windows version
A driver built for a different device or Windows build will not work, even if it installs. The Microsoft Update Catalog lists many drivers, so read the product name and supported version before you download. [1]
The same applies to packages with many drivers. One Dell CAB in a forum thread held six or seven drivers, and the user wanted only the network driver. [3] If you are unsure which one you need, point Device Manager at the folder and let Windows choose from the files it finds there. [3]
Extracting into a folder with no .inf file
A driver folder is only useful if Windows can find the driver inside it. One user got a “file not found” error and did not know where the files were supposed to go. [3]
Extract the CAB completely by running this command in Command Prompt or PowerShell: [1]
expand -F:* "Path\to\cab\file.cab" "Path\to\destination\folder"
The -F:* part extracts every file, not just one. Then point Device Manager at that folder, not at the CAB itself. [3]
Installing a driver from an untrusted site
Get driver CABs from the Microsoft Update Catalog or your device maker, such as Dell in the forum example. [1][3] A random download site can bundle unwanted software in a package that looks like a normal driver. A driver runs with deep access to your system, so the source matters more than convenience.
Skipping a restart
If the wizard asks you to restart, do it. A driver may not fully load until Windows restarts, so the device can keep misbehaving and make you think the install failed. Restart first, then test the hardware again before you try a different driver.
What is the short version?
Remember the two-step pattern: extract the CAB, then install the driver from the extracted folder. Run expand -F:* with your CAB path and destination folder, then point Device Manager at that folder through Update driver. [1]
If the install stops with an error, the article on why a CAB file install failed lists the common causes and a fix for each. Start there before trying a different driver package.
