How to download updates that include drivers and hotfixes from the Windows Update Catalog

This article discusses how to download updates from the Windows Update Catalog.

Original product version: В Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 10 — all editions
Original KB number: В 323166

Introduction

The Windows Update Catalog offers updates for all operating systems that we currently support. These updates include the following:

• Device drivers
• Hotfixes
• Updated system files
• New Windows features

We guide you through the steps to search the Windows Update Catalog to find the updates that you want. Then, you can download the updates to install them across your home or corporate network of Microsoft Windows-based computers.

We also discuss how IT Professionals can use Software Update Services, such as Windows Update and Automatic Updates.

This content is designed for an advanced computer user. We recommend that only advanced users and administrators download updates from the Windows Update Catalog. If you are not an advanced user or an administrator, visit the following Microsoft Web site to download updates directly:
Windows Update: FAQ

Steps to download updates from the Windows Update Catalog

To download updates from the Windows Update Catalog, follow these steps:

Step 1: Access the Windows Update Catalog

To access the Windows Update Catalog, visit the following Microsoft Web site:
Windows Update Catalog

To view a list of frequently asked questions about Windows Update Catalog, visit the following Microsoft Web site:
Microsoft Update Catalog Frequently Asked Questions

Step 2: Search for updates from the Windows Update Catalog

To search for updates from the Windows Update Catalog, follow these steps:

1. In the Search text box, type your search terms. For example, you might type Windows Vista Security.
2. Click Search, or press Enter.
3. Browse the list that is displayed to select the updates that you want to download.
4. Click Download to download the updates.
5. To search for additional updates to download, repeat steps 2a through 2d.

Step 3: Download updates

To download updates from the Windows Update Catalog, follow these steps:

Click the Download button under Search box.

Click the updates link on the pop-up page and Save to the default path, or right-click the link and select Save target as to the specified path. You can either type the full path of the folder, or you can click Browse to locate the folder.

Close the Download and the Windows Update Catalog Window.

Find the location that you specified in step 3b.

If you have downloaded device drivers for installation, go to «Installing Drivers.»

Double-click each update, and then follow the instructions to install the update. If the updates are intended for another computer, copy the updates to that computer, and then double-click the updates to install them.

If all the items that you added to the download list are installed successfully, you are finished.

If you want to learn about additional update services, please see the «Software Update Services for IT Professionals» section.

Installing drivers

Open a command prompt from the Start menu.

To extract the driver files, type the following command at the command prompt, and then press Enter:

To stage the driver for plug and play installation or for the Add Printer Wizard, use PnPutil Software Update Services for IT Professionals.

To install a cross-architecture print driver, you must already have installed the local architecture driver, and you will still need the cross-architecture copy of Ntprint.inf from another system.

Software Update Services for IT Professionals

For general information about Software Update Services, visit the following Microsoft Web site:
Overview of Windows as a service

Windows Update

IT Professionals can use the Windows Update service to configure a server on their corporate network to provide updates to corporate servers and clients. This functionality can be useful in environments where some clients and servers do not have access to the Internet. This functionality can also be useful where the environment is highly managed, and the corporate administrator must test the updates before they are deployed.

For information about using Windows Update, visit the following Microsoft Web site:
Windows Update: FAQ

Automatic Updates

IT Professionals can use the Automatic Updates service to keep computers up to date with the latest critical updates from a corporate server that is running Software Update Services.

Automatic Updates works with the following computers:

• Microsoft Windows 2000 Professional
• Windows 2000 Server
• Windows 2000 Advanced Server (Service Pack 2 or later versions)
• Windows XP Professional
• Windows XP Home Edition computer

For more information about how to use Automatic Updates in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
306525 How to configure and use Automatic Updates in Windows XP

Troubleshooting

You may experience one or more of the following issues when you use Windows Update or Microsoft Update:

You may receive the following error message:

Software update incomplete, this Windows Update software did not update successfully.

You may receive the following error message:

Administrators Only (-2146828218) To install items from Windows Update, you must be logged on as an administrator or a member of the Administrators group. If your computer is connected to a network, network policy settings may also prevent you from completing this procedure.

For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 316524 You receive an «Administrators only» error message when you try to visit the Windows Update Web site or the Microsoft Update Web site

You may be unable to view the Windows Update site or the Microsoft Update site if you connect to the Web site through an authenticating Web proxy that uses integrated (NTLM) proxy authentication.

Similar problems and solutions

You can visit the Microsoft Web sites in the following sections for more information:
Windows Update troubleshooting

Installing multiple updates with only one restart

The hotfix installer that is included with Windows XP and with Windows 2000 post-Service Pack 3 (SP3) updates includes functionality to support multiple hotfix installations. For earlier versions of Windows 2000, the command-line tool that is named «QChain.exe» is available for download.

For more information about how to install multiple updates or multiple hotfixes without restarting the computer between each installation, click the following article number to view the article in the Microsoft Knowledge Base:
296861 How to install multiple Windows updates or hotfixes with only one reboot

Microsoft security resources

For the latest Microsoft security resources such as security tools, security bulletins, virus alerts, and general security guidance, visit the following Microsoft Web site:
Microsoft Docs

For more information about the Microsoft Baseline Security Analyzer tool (MBSA), visit the following Microsoft Web site:
What is Microsoft Baseline Security Analyzer and its uses?

The Microsoft Download Center

For more information about how to download files from the Microsoft Download Center, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services

Product-specific download pages

Internet Explorer

For Internet Explorer downloads, visit the following Microsoft Web site:
Internet Explorer Downloads

Windows Media Player

For Windows Media Player downloads, visit the following Microsoft Web site:
Windows Media Player

Office Updates

For Office updates, visit the following Microsoft Web site:
Install Office updates

Download the Windows Driver Kit (WDK)

The WDK is used to develop, test, and deploy Windows drivers.

Runtime requirements

You can run the Windows 10, version 2004 WDK on Windows 7 and later, and use it to develop drivers for these operating systems:

Client OS	Server OS
Windows 10	Windows Server 2019, Windows Server 2016
Windows 8.1	Windows Server 2012 R2
Windows 8	Windows Server 2012
Windows 7	Windows Server 2008 R2 SP1

WDK for Windows 10, version 2004

Step 1: Install Visual Studio 2019

The WDK requires Visual Studio. For more information about system requirements for Visual Studio, see Visual Studio 2019 System Requirements.

The following editions of Visual Studio 2019 support driver development for this release:

When you install Visual Studio 2019, select the Desktop development with C++ workload. The Windows 10 Software Development Kit (SDK) is automatically included, and is displayed in the right-hand Summary pane. Note that the version of the SDK that is compatible with the WDK for Windows 10, version 2004 may not be the default SDK. To select the correct SDK:

In Visual Studio Installer, on the Individual components tab, search for Windows 10 SDK (10.0.19041.0), select this version and continue with install. Note that Visual Studio will automatically install Windows 10 SDK (10.0.19041.1) on your machine.

If you already have Visual Studio 2019 installed, you can install the Windows 10 SDK (10.0.19041.1) by using the Modify button in Visual Studio install.

WDK has Spectre mitigation enabled by default but requires spectre mitigated libraries to be installed with Visual Studio for each architecture you are developing for. Additionally, developing drivers for ARM/ARM64 require the build tools for these architectures to also be installed with Visual Studio. To locate these items you will need to know the latest version of MSVC installed on your system.

To find the latest version of MSVC installed on your system, in Visual Studio Installer go to workload page, on the right pane under installation details, expand Desktop development with C++ and locate the MSVC v142 — VS 2019 C++ x64/x86 build tools (V14.xx) — note where xx should be the highest version available.

With this information (v14.xx), go to Individual components and search for v14.xx. This will return the tool sets for all architectures, including Spectre mitigated libs. Select the driver architecture you are developing for.

For example, searching for v14.25 returns the following:

Step 1.5 Install Refreshed Windows SDK 10.0.19041.685 for Windows 10, version 2004

This SDK is strongly recommended and will eventually be made available through Visual Studio

Step 2: Install Refreshed WDK for Windows 10, version 2004

The WDK Visual Studio extension is included in the default WDK installation.

If you can’t find driver project templates in Visual Studio, the WDK Visual Studio extension didn’t install properly. To resolve this, run the WDK.vsix file from this location: C:\Program Files (x86)\Windows Kits\10\Vsix\VS2019\WDK.vsix.

Enterprise WDK (EWDK) for Windows 10, version 2004

The EWDK is a standalone, self-contained command-line environment for building drivers. It includes the Visual Studio Build Tools, the SDK, and the WDK. The latest public version of the EWDK contains Visual Studio 2019 Build Tools 16.7.0 and MSVC toolset v14.23. To get started, mount the ISO and run LaunchBuildEnv.

The EWDK also requires the .NET Framework version 4.7.2. For more information about other requirements for the .NET Framework, see .NET Framework system requirements.

EWDK with Visual Studio Build Tools

You can use the Visual Studio interface with the build tools provided in the EWDK.

1. Mount the EWDK ISO.
2. Run LaunchBuildEnv.cmd .
3. In the environment created in step 2, type SetupVSEnv, and then press Enter.
4. Launch devenv.exe from the same environment, using the full file path. Example: «C:\Program Files (x86)\Microsoft Visual Studio\2019\\%Community|Professional|Enterprise%\Common7\IDE\devenv.exe»

Note that the Visual Studio major version should match with the version in the EWDK. For example, Visual Studio 2019 works with the EWDK that contain VS16.X build tools.

Driver samples for Windows 10

To download the driver samples, do one of the following:

• Go to the driver samples page on GitHub, click Clone or download, and then click Download ZIP.
• Download the GitHub Extension for Visual Studio, and then connect to the GitHub repositories.
• Browse the driver samples on the Microsoft Samples portal.

Redistributable Framework Components

If your driver only targets Windows 10, you do not need to redistribute WDF or provide a Coinstaller in your driver package. To target Windows 10:

1. In Visual Studio, in the Project Settings property page, under Driver Settings ->Target OS Version, select Windows 10 or higher. This is equivalent to adding the following to the .vcxproj file:

1. In the INF Manufacturer Section, specify 10.0 as target OS version, as follows:

This topic describes the Microsoft-supplied redistributable framework updates that are included as part of the Windows Driver Kit (WDK), and how to determine which ones to add to your driver package.

The redistributable framework updates make it possible to run a driver built with a later framework version than the one included in an operating system. For example, KMDF 1.11 is included in WindowsВ 8. But you can run a KMDF 1.11 driver on WindowsВ Vista or WindowsВ 7. Before you can do so, however, you must ensure that the KMDF 1.11 framework library replaces the framework library included in the earlier operating system (in this case, KMDF 1.7 and KMDF 1.9 respectively). You do this by redistributing a Microsoft-supplied co-installer or .msu file with your driver package.

When do I need to include a co-installer or .msu in my driver package?

First, decide which versions of Windows your driver will support. Based on that, determine which framework version to use.

If the chosen WDF version is more recent than the version that shipped with the target OS, include the co-installer or .msu file in your driver package.

For example, you want your driver to run on Windows 7. You can choose to build your driver using either WDF 1.11 or WDF 1.9. If you choose 1.9, which is provided with Windows 7, there is no need to update the system. On the other hand, if you choose 1.11, you would need to include a WDF 1.11 update package with your driver.

Should I include the co-installer or the .msu file?

If your driver installation is triggered by plugging in a new hardware device to a system and you are installing only the driver, include the co-installer in your driver package. Then reference the co-installer in your INF file, as described in Specifying the KMDF Co-installer in an INF File.

If you need to install an application in addition to your driver, you should instead redistribute the relevant MSU package (for example kmdf-1.11-Win.6.0.msu) along with a setup application that calls it. In this case, no INF entries are needed.

You never need both the co-installer and the .msu file.

Where can I find these files, and what’s included?

The co-installers are located in %program files%\Windows Kits\ \redist\wdf .

This directory contains the following files, for x86 and x64:

• WdfCoinstaller01007.dll, WdfCoinstaller01009.dll, WdfCoinstaller01011.dll (co-installers for KMDF 1.7/1.9/1.11).
• WUDFUpdate_01007.dll, WUDFUpdate_01009.dll, WUDFUpdate_01011.dll (co-installers for UMDF).
• winusbcoinstaller.dll, winusbcoinstaller2.dll (co-installers for WinUSB 1.5/1.9).

If you would like the MSU file, please download and install the package (in MSI format) from WDK 8 redistributable components. After installation, the MSU and co-installers can be found in %program files%\Windows Kits\8.0\redist\wdf .

Co-installer Naming and Versioning

The co-installer is named WdfCoInstallerMMmmm.dll.

• MM is the major version number.
• mmm is the minor version number.

For example, the filename for version 1.0 of the co-installer is WdfCoInstaller01000.dll, and the filename for version 1.11 is WdfCoInstaller01011.dll.

The version of the co-installer that you include with your driver package must match the version of the framework library that you use to develop your driver.

Note that the framework library’s file name includes only the major version number. For more information about library file names, see Framework Library Versioning.