Using the Microsoft Update Catalog Safely
The Microsoft Update Catalog hosts signed driver packages for every Windows version. How to search it, pick the right entry, and avoid mismatches.
Sometimes you need a specific signed driver that Windows Update won't offer directly, and the Microsoft Update Catalog is where those packages live. It hosts driver and update files for every supported Windows version, all signed and hosted by Microsoft. The tricky part isn't downloading, it's picking the correct entry out of a long list of near-identical results. Choose the wrong architecture or an entry meant for a different Windows build, and the install fails or misbehaves. Here's how to search precisely, read the columns that matter, and install cleanly.
- 1
Find your device's hardware ID first
The most accurate way to search is by hardware ID, not by product name. Right-click the Start button, open Device Manager, and locate your device. Right-click it, choose Properties, open the Details tab, and change the Property dropdown to Hardware Ids. You'll see one or more strings that usually begin with PCI, USB, or HDAUDIO, containing VEN (vendor) and DEV (device) codes. Copy the top line. This string uniquely identifies the chip, so searching for it returns packages built for that exact part rather than a broad family of loosely related drivers.
- 2
Search the Catalog with the right terms
Open the Microsoft Update Catalog in your browser and paste the hardware ID into the search box. If a full ID returns nothing, trim it back to the VEN and DEV portion and search again, since shorter strings match more entries. You can also search by the driver or component name if you don't have an ID. The goal is a focused list you can compare, not hundreds of unrelated results. Avoid guessing with vague product names alone, because similar names across generations lead straight to a mismatched package.
- 3
Read the version, date, and product columns
The results table shows Title, Products, Classification, Last Updated, Version, and Size. Don't grab the newest date by reflex. Check the Products column to confirm the entry targets your Windows version, and read the Version number, which is the true driver version. A higher version generally means newer code, while Last Updated only shows when the package was republished. Click an entry's title to open its details page, where you can confirm supported products and the architecture before committing. Note the version you pick so you can identify it later if you need to roll back.
- 4
Match the architecture: x64, ARM64, or x86
Architecture mismatches are the most common reason a Catalog driver won't install. Most modern PCs run 64-bit x64 Windows, but ARM-based devices need ARM64 packages, and older systems may need x86. Check yours in Settings under System then About, where 'System type' names the architecture. Entries in the Catalog are labeled, so pick the one that matches exactly. An x64 driver will not install on an ARM64 machine and vice versa. When two entries look identical apart from architecture, the difference in that label is the whole point, so read it carefully.
- 5
Download and extract the .cab file
Catalog driver packages usually download as a .cab file rather than a ready-to-run installer. Create an empty folder, such as one on your desktop named for the driver, and move the .cab there. Extract it with the built-in expand command. Open a Command Prompt in that folder and run expand, giving it the .cab name, the -F:* flag to pull every file, and the folder as the destination. After extraction you should see .inf, .sys, and .cat files. The .inf is the setup information file the next step relies on.
- 6
Create a restore point before installing
Because you're placing a specific driver by hand, give yourself a way back. Search for 'Create a restore point,' pick your system drive, confirm protection is on with Configure, then click Create and name it clearly. If the manually installed driver causes problems, you can roll the device back in Device Manager under the Driver tab, or use the restore point to undo the change. Taking two minutes here saves you from a difficult recovery if the package turns out to be a poor fit for your machine.
- 7
Install the driver with pnputil
To install the extracted package, open a Command Prompt as administrator, then use pnputil to add and install the .inf. Run pnputil with /add-driver, the path to the .inf file, and the /install flag so Windows stages and applies it in one step. You can also use /subdirs if the package spans folders. When it finishes, pnputil reports success and often the published driver name. Reboot if prompted. This method adds the driver to the Windows driver store properly, which is cleaner and more reversible than a manual right-click install.
- 8
Confirm the right version is active
After the reboot, verify the install took hold. Open Device Manager, right-click the device, choose Properties, and open the Driver tab. Compare the Driver Version shown there against the version you picked in the Catalog. If they match, you're done. If Windows swapped in a different driver, the version won't line up, and you may need to reinstall or block automatic replacement separately. Also confirm the device works as expected, since a correct version number still needs the hardware to actually function properly for the job to count as finished.