mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
resolving conflicts
This commit is contained in:
@ -1,12 +1,10 @@
|
||||
---
|
||||
title: Windows Update troubleshooting
|
||||
description: In this article, learn how to troubleshoot issues with Windows Update, such as why a device is frozen at scan.
|
||||
description: Learn about troubleshooting Windows Update, issues related to HTTP/Proxy, and why some features are offered and others aren't.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
audience: itpro
|
||||
itproauthor: jaimeo
|
||||
author: jaimeo
|
||||
ms.localizationprioauthor: jaimeo
|
||||
ms.audience: itpro
|
||||
author: jaimeo
|
||||
ms.reviewer:
|
||||
@ -22,9 +20,13 @@ ms.custom: seo-marvel-apr2020
|
||||
If you run into problems when using Windows Update, start with the following steps:
|
||||
|
||||
1. Run the built-in Windows Update troubleshooter to fix common issues. Navigate to **Settings > Update & Security > Troubleshoot > Windows Update**.
|
||||
|
||||
2. Install the most recent Servicing Stack Update (SSU) that matches your version of Windows from the Microsoft Update Catalog. See [Servicing stack updates](servicing-stack-updates.md) for more details on SSU.
|
||||
|
||||
3. 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:
|
||||
|
||||
- [Windows 10, version 2004 and Windows Server, version 2004](https://support.microsoft.com/help/4555932)
|
||||
- [Windows 10, version 1909 and Windows Server, version 1909](https://support.microsoft.com/help/4529964)
|
||||
- [Windows 10, version 1903 and Windows Server, version 1903](https://support.microsoft.com/help/4498140)
|
||||
- [Windows 10, version 1809 and Windows Server 2019](https://support.microsoft.com/help/4464619/windows-10-update-history)
|
||||
- [Windows 10, version 1803](https://support.microsoft.com/help/4099479/windows-10-update-history)
|
||||
@ -52,13 +54,16 @@ If the update you're offered isn't the most current available, it might be becau
|
||||
|
||||
## My device is frozen at scan. Why?
|
||||
The Settings UI is talking to the Update Orchestrator service which in turn is talking to Windows Update service. If these services stop unexpectedly then you might see this behavior. In such cases, do the following:
|
||||
|
||||
1. Close the Settings app and reopen it.
|
||||
|
||||
2. Launch 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
|
||||
On computers running [Windows 10 1709 or higher](#BKMK_DCAT) configured to update from Windows Update (usually WUfB scenario) servicing and definition updates are being installed successfully, but feature updates are never offered.
|
||||
Devices running Windows 10, version 1709 through Windows 10, version 1803 that are [configured to update from Windows Update](#BKMK_DCAT) (including Windows Update for Business scenarios) are able to install servicing and definition updates but are never offered feature updates.
|
||||
|
||||
Checking the WindowsUpdate.log reveals the following error:
|
||||
```console
|
||||
@ -111,7 +116,8 @@ If downloads through a proxy server fail with a 0x80d05001 DO_E_HTTP_BLOCKSIZE_M
|
||||
You may choose to apply a rule to permit HTTP RANGE requests for the following URLs:
|
||||
|
||||
*.download.windowsupdate.com
|
||||
*.dl.delivery.mp.microsoft.com
|
||||
*.dl.delivery.mp.microsoft.com
|
||||
*.delivery.mp.microsoft.com
|
||||
*.emdl.ws.microsoft.com
|
||||
|
||||
If you cannot permit RANGE requests, keep in mind that this means you are downloading more content than needed in updates (as delta patching will not work).
|
||||
@ -162,12 +168,16 @@ Check that your device can access these Windows Update endpoints:
|
||||
- `http://*.download.windowsupdate.com`
|
||||
- `http://wustat.windows.com`
|
||||
- `http://ntservicepack.microsoft.com`
|
||||
- `https://*.prod.do.dsp.mp.microsoft.com`
|
||||
- `http://*.dl.delivery.mp.microsoft.com`
|
||||
- `https://*.delivery.mp.microsoft.com`
|
||||
- `https://tsfe.trafficshaping.dsp.mp.microsoft.com`
|
||||
|
||||
Whitelist these endpoints for future use.
|
||||
Allow these endpoints for future use.
|
||||
|
||||
## 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
|
||||
1. Start Windows PowerShell as an administrator.
|
||||
2. Run \$MUSM = New-Object -ComObject "Microsoft.Update.ServiceManager".
|
||||
3. Run \$MUSM.Services.
|
||||
|
||||
|
Reference in New Issue
Block a user