Windows Update troubleshooting

If you run into problems when using Windows Update, start with the following steps:

Run the built-in Windows Update troubleshooter to fix common issues. Navigate to Settings > Update & Security > Troubleshoot > Windows Update.

Install the most recent Servicing Stack Update (SSU) that matches your version of Windows from the Microsoft Update Catalog. See Servicing stack updates for more details on servicing stack updates.

Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system:

Advanced users can also refer to the log generated by Windows Update for further investigation.

You might encounter the following scenarios when using Windows Update.

Why am I offered an older update?

The update that is offered to a device depends on several factors. The following are some of the most common attributes:

• OS Build
• OS Branch
• OS Locale
• OS Architecture
• Device update management configuration

If the update you’re offered isn’t the most current available, it might be because your device is being managed by a WSUS server, and you’re being offered the updates available on that server. It’s also possible, if your device is part of a deployment group, that your admin is intentionally slowing the rollout of updates. Since the deployment is slow and measured to begin with, all devices will not receive the update on the same day.

My device is frozen at scan. Why?

The Settings UI communicates with the Update Orchestrator service that in turn communicates with to Windows Update service. If these services stop unexpectedly, then you might see this behavior. In such cases, follow these steps:

Close the Settings app and reopen it.

Start Services.msc and check if the following services are running:

• Update State Orchestrator
• Windows Update

Feature updates are not being offered while other updates are

Devices running Windows 10, version 1709 through Windows 10, version 1803 that are configured to update from Windows Update (including Windows Update for Business) are able to install servicing and definition updates but are never offered feature updates.

Checking the WindowsUpdate.log reveals the following error:

The 0x80070426 error code translates to:

Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. The DCAT Flighting service (ServiceId: 855E8A7C-ECB4-4CA3-B045-1DFA50104289) relies on MSA to get the global device ID for the device. Without the MSA service running, the global device ID won’t be generated and sent by the client and the search for feature updates never completes successfully.

To resolve this issue, reset the MSA service to the default StartType of «manual.»

Issues related to HTTP/Proxy

Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download updates and applications from Windows Update servers or on-premises WSUS servers. Therefore proxy servers on the network must support HTTP RANGE requests. If a proxy was configured in Internet Explorer (User level) but not in WinHTTP (System level), connections to Windows Update will fail.

To fix this issue, configure a proxy in WinHTTP by using the following netsh command:

You can also import the proxy settings from Internet Explorer by using the following command: netsh winhttp import proxy source=ie

If downloads through a proxy server fail with a 0x80d05001 DO_E_HTTP_BLOCKSIZE_MISMATCH error, or if you notice high CPU usage while updates are downloading, check the proxy configuration to permit HTTP RANGE requests to run.

You might choose to apply a rule to permit HTTP RANGE requests for the following URLs:

*.download.windowsupdate.com
*.dl.delivery.mp.microsoft.com *.delivery.mp.microsoft.com

If you can’t allow RANGE requests, you’ll be downloading more content than needed in updates (as delta patching will not work).

The update is not applicable to your computer

The most common reasons for this error are described in the following table:

Cause	Explanation	Resolution
Update is superseded	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.	Check that the package that you are installing contains newer versions of the binaries. Or, check that the package is superseded by another new package.
Update is already installed	If the update that you’re trying to install was previously installed, for example, by another update that carried the same payload, you may encounter this error message.	Verify that the package that you are trying to install was not previously installed.
Wrong update for architecture	Updates are published by CPU architecture. If the update that you’re trying to install does not match the architecture for your CPU, you may encounter this error message.	Verify that the package that you’re trying to install matches the Windows version that you are using. The Windows version information can be found in the «Applies To» section of the article for each update. For example, Windows Server 2012-only updates cannot be installed on Windows Server 2012 R2-based computers. Also, verify that the package that you are installing matches the processor architecture of the Windows version that you are using. For example, an x86-based update cannot be installed on x64-based installations of Windows.
Missing prerequisite update	Some updates require a prerequisite update before they can be applied to a system. If you are missing a prerequisite update, you may encounter this error message. For example, KB 2919355 must be installed on Windows 8.1 and Windows Server 2012 R2 computers before many of the updates that were released after April 2014 can be installed.	Check the related articles about the package in the Microsoft Knowledge Base (KB) to make sure that you have the prerequisite updates installed. For example, if you encounter the error message on Windows 8.1 or Windows Server 2012 R2, you may have to install the April 2014 update 2919355 as a prerequisite and one or more pre-requisite servicing updates (KB 2919442 and KB 3173424). To determine if these prerequisite updates are installed, run the following PowerShell command: get-hotfix KB3173424,KB2919355, KB2919442 . If the updates are installed, the command will return the installed date in the InstalledOn section of the output.

Issues related to firewall configuration

Error that you might see in Windows Update logs:

Go to Services.msc and ensure that Windows Firewall Service is enabled. Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft. For more information, see I need to disable Windows Firewall.

Issues arising from configuration of conflicting policies

Windows Update provides a wide range configuration policy to control the behavior of the Windows Update service in a managed environment. While these policies let you configure the settings at a granular level, misconfiguration or setting conflicting policies may lead to unexpected behaviors.

Device cannot access update files

Ensure that devices can reach necessary Windows Update endpoints through the firewall. For example, for Windows 10, version 2004, the following protocols must be able to reach these respective endpoints:

Protocol	Endpoint URL
TLS 1.2	*.prod.do.dsp.mp.microsoft.com
HTTP	emdl.ws.microsoft.com
HTTP	*.dl.delivery.mp.microsoft.com
HTTP	*.windowsupdate.com
HTTPS	*.delivery.mp.microsoft.com
TLS 1.2	*.update.microsoft.com
TLS 1.2	tsfe.trafficshaping.dsp.mp.microsoft.com

Be sure not to use HTTPS for those endpoints that specify HTTP, and vice versa. The connection will fail.

The specific endpoints can vary between Windows 10 versions. See, for example, Windows 10 2004 Enterprise connection endpoints. Similar articles for other Windows 10 versions are available in the table of contents nearby.

Updates aren’t downloading from the intranet endpoint (WSUS or Configuration Manager)

Windows 10 devices can receive updates from a variety of sources, including Windows Update online, a Windows Server Update Services server, and others. To determine the source of Windows Updates currently being used on a device, follow these steps:

1. Start Windows PowerShell as an administrator.
2. Run $MUSM = New-Object -ComObject «Microsoft.Update.ServiceManager».
3. Run $MUSM.Services.

Check the output for the Name and OffersWindowsUPdates parameters, which you can interpret according to this table.

Output	Meaning
— Name: Microsoft Update -OffersWindowsUpdates: True	— The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered. — Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.)
— Name: DCat Flighting Prod — OffersWindowsUpdates: True	— Starting with Windows 10 1709, feature updates are always delivered through the DCAT service. — Indicates that the client is configured to receive feature updates from Windows Update.
— Name: Windows Store (DCat Prod) — OffersWindowsUpdates: False	-The update source is Insider Updates for Store Apps. — Indicates that the client will not receive or is not configured to receive these updates.
— Name: Windows Server Update Service — OffersWindowsUpdates: True	— The source is a Windows Server Updates Services server. — The client is configured to receive updates from WSUS.
— Name: Windows Update — OffersWindowsUpdates: True	— The source is Windows Update. — The client is configured to receive updates from Windows Update Online.

You have a bad setup in the environment

In this example, per the Group Policy set through registry, the system is configured to use WSUS to download updates (note the second line):

From Windows Update logs:

In the above log snippet, we see that the Criteria = «IsHidden = 0 AND DeploymentAction=*» . «*» means there is nothing specified from the server. So, the scan happens but there is no direction to download or install to the agent. So it just scans the update and provides the results.

As shown in the following logs, automatic update runs the scan and finds no update approved for it. So it reports there are no updates to install or download. This is due to an incorrect configuration. The WSUS side should approve the updates for Windows Update so that it fetches the updates and installs them at the specified time according to the policy. Since this scenario doesn’t include Configuration Manager, there’s no way to install unapproved updates. You’re expecting the operational insight agent to do the scan and automatically trigger the download and installation but that won’t happen with this configuration.

High bandwidth usage on Windows 10 by Windows Update

Users might see that Windows 10 is consuming all the bandwidth in the different offices under the system context. This behavior is by design. Components that might consume bandwidth expand beyond Windows Update components.

The following group policies can help mitigate this situation:

Other components that connect to the internet:

Fix problems with apps from Microsoft Store

If you’re in Windows 10 and you’re having problems with an app from Microsoft Store, consider these updates and fixes.

First, sign in to your Microsoft account. Next, work through these possible solutions in the order presented.

Make sure Windows has the latest update: Select check for updates now, and then select Check for updates. Or, select the Start button, then select Settings > Update & Security > Windows Update > Check for Updates. If there is an available update, select Install now.

Make sure that your app works with Windows 10. For more info, see Your app doesn’t work with Windows 10.

Update Microsoft Store: Select the Start button, and then from the apps list, select Microsoft Store. In Microsoft Store, select See more > Downloads and updates > Get updates. If an update for Microsoft Store is available, it will start installing automatically.

Troubleshoot games: If you’re having issues installing a game, see Troubleshoot game installations on Windows 10.

Reinstall your apps: In Microsoft Store, select See more > My Library. Select the app you want to reinstall, and then select Install.

Run the troubleshooter: Select the Start button, and then select Settings > Update & Security > Troubleshoot, and then from the list select Windows Store apps > Run the troubleshooter.

Here’s more help

If you’re having trouble launching Microsoft Store, see Microsoft Store doesn’t launch.

If you can launch the Microsoft Store but you are just having trouble finding or installing an app, see I can’t find or install an app from Microsoft Store.

Troubleshooting Applications Problems with Windows Store Apps Troubleshooter

Some Windows 8/10 users complained about several application problems. Some applications cannot be installed, run, updated or simply crashed. All these versions of Windows are pre-releases, but millions of people use these versions of Windows every day. Microsoft has significantly improved the Windows store and applications with each version. If your applications are not working properly, you can also reset Windows store applications with a single click.

If you try to run a Windows application, you will notice that it is not working properly – you may receive an error message App Can’t Open – you may run Windows Application Troubleshooting.

Windows Store Apps troubleshooting

April 2021 Update:

We now recommend using this tool for your error. Additionally, this tool fixes common computer errors, protects you against file loss, malware, hardware failures and optimizes your PC for maximum performance. You can fix your PC problems quickly and prevent others from happening with this software:

• Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
• Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
• Step 3 : Click “Repair All” to fix all issues.

However, Microsoft has developed a Windows Store Apps Troubleshooter to solve many known problems that could prevent it from working properly under Windows 8/10.

When this application runs, it automatically fixes some of the basic problems that might prevent your applications from running – such as lower screen resolution, incorrect security or account settings, etc.

You receive the troubleshooting report.

There will be cases where some unknown problems cannot be solved even after this troubleshooting has been performed.

Troubleshooting problems with Windows Store applications

Here are some points that can be studied based on users’ experience with application problems.

After starting troubleshooting, reboot and check your system.

According to Windows 8 Release Preview system requirements, you must have an active Internet connection and a screen resolution of at least 1024 x 768 to access the Windows store and download and run applications. Please check the resolution.

To get applications, you need a screen resolution of at least 1366 x 768, but do not worry about this snap application function – if your monitor does not support this resolution. It has no influence on the operation or installation of the application.

Change your account to Local and then return to the Live Account from the Control Panel.

Check that Windows is up to date. Also try synchronizing application licenses. Open the Store application, open Charms (WinKey+C), choose Settings > App Updates and click Synchronize Licenses under App Licenses.

If you installed certain applications in your previous version of Windows 8 as Windows 8 CP, they have been registered to your account. Therefore, there is a new option in the version preview to display the installed applications. If you are using the same Live account to login to the preview version, simply right-click on the bar above to get the Your Applications option.

Just click on it to list all your applications – those that have already been installed and those that you have already installed, so try installing from there and see if it makes a difference.

These are some additional troubleshooting steps you may want to try to solve your Windows 8 problems – in addition to trying the troubleshooting application.

What I recommend is, if you are only trying and testing Windows 8 Release Preview, to perform a clean installation of Windows 8 Release Preview instead of upgrading from the previous version of Windows. Try it and install your favorite applications from the store.

You can download Windows Troubleshooting from here. This is a Troubleshooting Pack Cabinet file.

If you need additional help, this Windows Store error code list can help you solve problems.

We have already written some articles that will help you solve problems with Windows Store applications:

1. 1. 1. Applications cannot be installed from the Windows store
      2. Your trial period for this application has expired
      3. Error 0x80073cf9 When installing applications from the Windows store
      4. Error code 0x8024600e When testing, Install or update Windows Store applications
      5. Windows Store applications cannot be updated
      6. Random Windows Metro application crashes and freezes
      7. Windows Store application crashes by running Clean Uninstall with PowerShell
      8. Reset Windows memory cache in Windows
      9. Something bad happens, unknown layout in manifest
      10. Windows applications do not work? – Repair Windows Applications
      11. Windows Tiles Do Not Work
      12. How to Re-Register Windows Store Applications
      13. Windows Live Tiles Do Not Work or Are Empty
      14. Windows Store Does Not Open.