Edit

Share via

Windows Update troubleshooting guidance

  • Article

Try our Virtual Agent - It can help you quickly identify and fix common Windows Update issues

These solutions designed to get you started on Windows Update troubleshooting scenarios.

Troubleshooting checklist

Step 1: Run the diagnostic tool for your version of Windows

For any supported versions of Windows, open an administrative command prompt window, and then run the following command:

Dism /online /cleanup-image /restorehealth

Step 2: Restart the computer

If the computer didn't restart after a previous update, pending actions may still have to be completed before you can apply new updates.

Step 3: Install the latest servicing stack update

For more information, see Latest Servicing Stack Updates or look for the latest servicing stack required for the latest cumulative update in the update history for your Windows version.

Step 4: Check for and fix any Windows file corruption

For more information, see Fix Windows file corruption.

Step 5: Download the update package and try to install the update manually

To do this, follow these steps:

  1. Open Microsoft Update Catalog.
  2. In the search box, type the update number that you want to download, and then select Search.
  3. Find the update that applies to your operating system in the search results. Next to that update, select Add to add the update to your basket.
  4. Select View basket, and then select Download.
  5. To choose a destination for the update, select Browse, and then select Continue.
  6. When the download process finishes, select Close.
  7. Browse to the download location, and then double-click the download package to install the update.

Note

To skip Windows Update agent applicability checks and make the installation go further or quicker, open an elevated command prompt and run the following command:

Dism /online /add-package /packagepath:<path_to_package>

Common issues and solutions

Error: The update is not applicable to your computer

This error has several possible causes. The following instructions help you identify the specific cause that affects you.

Step 1: Has the update been superseded?

Make sure that the update package contains newer versions of the binaries than the system that you're updating. Alternatively, check that the package is superseded by another new package.

As updates for a component are released, the updated component will supersede an older component that is already on the system. When this occurs, the previous update is marked as superseded. If the update that you're trying to install already has a newer version of the payload on your system, you might receive this error message.

Step 2: Has the update already been installed?

Verify that the package that you're trying to install isn't already installed.

Step 3: Is the update appropriate for this architecture?

  1. Verify that the package that you're trying to install matches the Windows version that you're using.

    The Windows version information can be found in the "Applies To" section of the article for each update. For example, Windows Server 2019 updates can't be installed on Windows Server 2016, or Windows Server updates on a Windows client.

  2. Verify that the package you want to install matches the processor architecture of the Windows version that you're using.

    For example, an x86-based update can't be installed on x64-based installations of Windows.

Step 4: Have all prerequisite updates been installed?

Read the package's related article to find out if the prerequisite updates are installed. For example, if you receive the error message in Windows 10, version 22H2 update Windows July 23, 2024—KB5040525 (OS Build 19045.4717) Preview, you might have to install KB50282445, KB5031539, or more prerequisite servicing updates.

To determine whether these prerequisite updates are installed, open a Windows PowerShell window and run the following command:

Get-HotFix KB50282445, KB5031539

If the updates are installed, the command returns the installed date in the InstalledOn section of the output.

The device isn't receiving an update that you deployed

Follow these steps to troubleshoot this issue.

  1. Check that the device's updates for the relevant category aren't paused.

    For more information, see Pause feature updates and Pause quality updates.

  2. Feature updates only: Check to see if the device might have a safeguard hold applied for the given feature update version.

    For more information about safeguard holds, see Safeguard holds and Opt out of safeguard holds.

  3. Check that the deployment to which the device is assigned has the state offering. Deployments that have the states paused or scheduled won't deploy content to devices.

  4. Check that the device has scanned for updates and is scanning the Windows Update service.

    To learn more about scanning for updates, see Scanning updates.

  5. Feature updates only: Verify that the device is successfully enrolled in feature update management by the deployment service. A device that's successfully enrolled is represented by a Microsoft Entra ID device resource. That resource documents an update management enrollment for feature updates, and has no Microsoft Entra ID device registration errors.

  6. Expedited quality updates only: Check that the device has the Update Health Tools installed (available for Windows 10 version 1809 or later in the update described in KB 4023057 - Update for Windows 10 Update Service components, or a more recent quality update).

    The Update Health Tools are required for a device to receive an expedited quality update. The program's location on the device is C:\Program Files\Microsoft Update Health Tools. To verify its presence, view the installed programs list or run the following PowerShell script:

    Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -Match "Microsoft Update Health Tools"}

The device is receiving an update that you didn't deploy

To troubleshoot this issue, follow these steps:

  1. Check that the device is scanning the Windows Update service and not a different endpoint.

    For example, if the device is scanning for updates from a WSUS endpoint, it might receive different updates. To learn more about scanning for updates, see Scanning updates.

  2. Feature updates only: Check that the device is successfully enrolled in feature update management by the deployment service.

    A device that isn't successfully enrolled might receive different updates according to its feature update deferral period. A device that's successfully enrolled is represented by a Microsoft Entra ID device resource. That resource documents an update management enrollment for feature updates, and has no Microsoft Entra ID device registration errors.

Data collection

If you need assistance from Microsoft support, we recommend you collect the information by following the steps mentioned in Gather information by using TSS for deployment-related issues.

References