You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/mem/configmgr/client-management/configmgr-client-left-in-provisioning-mode.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,14 @@
2
2
title: Configuration Manager client left in provisioning mode after an upgrade to Windows 10
3
3
description: Describes an issue that causes the Configuration Manager client to be left in provisioning mode after an upgrade to Windows 10. Provides a resolution.
Copy file name to clipboardExpand all lines: support/windows-client/installing-updates-features-roles/additional-resources-for-windows-update.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.collection: highpri
8
8
ms.custom:
9
9
- sap:windows servicing,updates and features on demand\windows update configuration,settings and management
10
10
- pcy:WinComm Devices Deploy
11
-
ms.reviewer: dougeby,aaroncz
11
+
ms.reviewer: dougeby
12
12
audience: itpro
13
13
---
14
14
# Windows Update - additional resources
@@ -50,7 +50,7 @@ If all else fails, try resetting the Windows Update Agent by running these comma
50
50
```console
51
51
net stop bits
52
52
net stop wuauserv
53
-
net stop cryptsvc
53
+
net stop cryptsvc
54
54
```
55
55
56
56
3. Delete the *qmgr\*.dat* files. Type the following command at a command prompt, and then press Enter:
@@ -148,8 +148,8 @@ If all else fails, try resetting the Windows Update Agent by running these comma
148
148
149
149
```console
150
150
net start bits
151
-
net start wuauserv
152
-
net start cryptsvc
151
+
net start wuauserv
152
+
net start cryptsvc
153
153
```
154
154
155
155
10. If you're running Windows Vista or Windows Server 2008, clear the BITS queue. Type the following command at a command prompt, and then press Enter:
Copy file name to clipboardExpand all lines: support/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting.md
+44-44Lines changed: 44 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.custom:
8
8
- sap:windows servicing,updates and features on demand\windows update fails - installation rolls back
9
9
- pcy:WinComm Devices Deploy
10
10
ms.collection: highpri
11
-
ms.reviewer: dougeby, aaroncz, warrenw, astoica
11
+
ms.reviewer: dougeby, warrenw, astoica
12
12
audience: itpro
13
13
---
14
14
# Windows Update issues troubleshooting
@@ -29,36 +29,36 @@ If you run into problems when using Windows Update, start with the following ste
29
29
-[Windows 10, version 1909 and Windows Server, version 1909](https://support.microsoft.com/help/4529964)
30
30
-[Windows 10, version 1903 and Windows Server, version 1903](https://support.microsoft.com/help/4498140)
31
31
-[Windows 10, version 1809 and Windows Server 2019](https://support.microsoft.com/help/4464619/windows-10-update-history)
32
-
-[Windows 10, version 1803](https://support.microsoft.com/help/4099479/windows-10-update-history)
33
-
-[Windows 10, version 1709](https://support.microsoft.com/help/4043454)
34
-
-[Windows 10, version 1703](https://support.microsoft.com/help/4018124)
35
-
-[Windows 10 and Windows Server 2016](https://support.microsoft.com/help/4000825/windows-10-windows-server-2016-update-history)
36
-
-[Windows 8.1 and Windows Server 2012 R2](https://support.microsoft.com/help/4009470/windows-8-1-windows-server-2012-r2-update-history)
37
-
-[Windows Server 2012](https://support.microsoft.com/help/4009471/windows-server-2012-update-history)
38
-
-[Windows 7 SP1 and Windows Server 2008 R2 SP1](https://support.microsoft.com/help/4009469/windows-7-sp1-windows-server-2008-r2-sp1-update-history)
32
+
-[Windows 10, version 1803](https://support.microsoft.com/help/4099479/windows-10-update-history)
33
+
-[Windows 10, version 1709](https://support.microsoft.com/help/4043454)
34
+
-[Windows 10, version 1703](https://support.microsoft.com/help/4018124)
35
+
-[Windows 10 and Windows Server 2016](https://support.microsoft.com/help/4000825/windows-10-windows-server-2016-update-history)
36
+
-[Windows 8.1 and Windows Server 2012 R2](https://support.microsoft.com/help/4009470/windows-8-1-windows-server-2012-r2-update-history)
37
+
-[Windows Server 2012](https://support.microsoft.com/help/4009471/windows-server-2012-update-history)
38
+
-[Windows 7 SP1 and Windows Server 2008 R2 SP1](https://support.microsoft.com/help/4009469/windows-7-sp1-windows-server-2008-r2-sp1-update-history)
39
39
40
-
Advanced users can also refer to the [log](/windows/deployment/update/windows-update-logs) generated by Windows Update for further investigation.
40
+
Advanced users can also refer to the [log](/windows/deployment/update/windows-update-logs) generated by Windows Update for further investigation.
41
41
42
42
You might encounter the following scenarios when using Windows Update.
43
43
44
44
## Why am I offered an older update?
45
45
46
-
The update that is offered to a device depends on several factors. The following are some of the most common attributes:
46
+
The update that is offered to a device depends on several factors. The following are some of the most common attributes:
47
47
48
48
- OS Build
49
49
- OS Branch
50
50
- OS Locale
51
51
- OS Architecture
52
52
- Device update management configuration
53
53
54
-
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 won't receive the update on the same day.
54
+
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 won't receive the update on the same day.
55
55
56
56
## My device is frozen at scan. Why?
57
57
58
-
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:
58
+
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:
59
59
60
-
1. Close the Settings app and reopen it.
61
-
2. Start Services.msc and check if the following services are running:
60
+
1. Close the Settings app and reopen it.
61
+
2. Start Services.msc and check if the following services are running:
62
62
63
63
- Update State Orchestrator
64
64
- Windows Update
@@ -110,17 +110,17 @@ Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download u
110
110
To fix this issue, configure a proxy in WinHTTP by using the following netsh command:
111
111
112
112
```console
113
-
netsh winhttp set proxy ProxyServerName:PortNumber
113
+
netsh winhttp set proxy ProxyServerName:PortNumber
114
114
```
115
115
116
116
>[!NOTE]
117
117
> You can also import the proxy settings from Internet Explorer by using the following command: `netsh winhttp import proxy source=ie`.
118
118
119
-
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.
119
+
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.
120
120
121
121
You might choose to apply a rule to permit HTTP RANGE requests for the following URLs:
122
122
123
-
-`*.download.windowsupdate.com`
123
+
-`*.download.windowsupdate.com`
124
124
-`*.dl.delivery.mp.microsoft.com`
125
125
-`*.delivery.mp.microsoft.com`
126
126
@@ -144,19 +144,19 @@ You observe that the download for updates is stuck at 0%, especially in Windows
144
144
Error that you might see in Windows Update logs:
145
145
146
146
```output
147
-
DownloadManager Error 0x800706d9 occurred while downloading update; notifying dependent calls.
147
+
DownloadManager Error 0x800706d9 occurred while downloading update; notifying dependent calls.
148
148
```
149
149
150
150
Or
151
151
152
152
```output
153
-
[DownloadManager] BITS job {A4AC06DD-D6E6-4420-8720-7407734FDAF2} hit a transient error, updateId = {D053C08A-6250-4C43-A111-56C5198FE142}.200 <NULL>, error = 0x800706D9
153
+
[DownloadManager] BITS job {A4AC06DD-D6E6-4420-8720-7407734FDAF2} hit a transient error, updateId = {D053C08A-6250-4C43-A111-56C5198FE142}.200 <NULL>, error = 0x800706D9
154
154
```
155
155
156
156
Or
157
157
158
158
```output
159
-
DownloadManager [0]12F4.1FE8::09/29/2017-13:45:08.530 [agent]DO job {C6E2F6DC-5B78-4608-B6F1-0678C23614BD} hit a transient error, updateId = 5537BD35-BB74-40B2-A8C3-B696D3C97CBA.201 <NULL>, error = 0x80D0000A
159
+
DownloadManager [0]12F4.1FE8::09/29/2017-13:45:08.530 [agent]DO job {C6E2F6DC-5B78-4608-B6F1-0678C23614BD} hit a transient error, updateId = 5537BD35-BB74-40B2-A8C3-B696D3C97CBA.201 <NULL>, error = 0x80D0000A
160
160
```
161
161
162
162
Go to **Services.msc** and ensure that the **Windows Defender Firewall** service is enabled. Stopping the service associated with Windows Firewall with Advanced Security isn't supported by Microsoft. For more information, see [I need to disable Windows Firewall](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766337(v=ws.10)).
@@ -194,7 +194,7 @@ Windows client devices can receive updates from various sources, including Windo
@@ -210,7 +210,7 @@ Check the output for the Name and OffersWindowsUPdates parameters, which you can
210
210
|-|-|
211
211
|- Name: Microsoft Update <br>-OffersWindowsUpdates: True| - The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered.<br>- Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.) |
212
212
|- <a name="BKMK_DCAT"></a>Name: DCat Flighting Prod <br>- OffersWindowsUpdates: True |- Starting with Windows 10, version 1709, feature updates are always delivered through the DCAT service.<br>- Indicates that the client is configured to receive feature updates from Windows Update. |
213
-
|- Name: Windows Store (DCat Prod) <br>- OffersWindowsUpdates: False |-The update source is Insider Updates for Store Apps.<br>- Indicates that the client won't receive or isn't configured to receive these updates.|
213
+
|- Name: Windows Store (DCat Prod) <br>- OffersWindowsUpdates: False |-The update source is Insider Updates for Store Apps.<br>- Indicates that the client won't receive or isn't configured to receive these updates.|
214
214
|- Name: Windows Server Update Service <br>- OffersWindowsUpdates: True |- The source is a Windows Server Updates Services server. <br>- The client is configured to receive updates from WSUS. |
215
215
|- Name: Windows Update<br>- OffersWindowsUpdates: True|- The source is Windows Update. <br>- The client is configured to receive updates from Windows Update Online.|
216
216
@@ -219,40 +219,40 @@ Check the output for the Name and OffersWindowsUPdates parameters, which you can
219
219
In this example, per the Group Policy set through registry, the system is configured to use WSUS to download updates (note the second line):
2018-08-06 09:33:32:554 480 1118 Agent * Found 83 updates and 83 categories in search; evaluated appl. rules of 517 out of 1473 deployed entities
237
+
2018-08-06 09:33:32:554 480 1118 Agent *********
238
+
2018-08-06 09:33:32:554 480 1118 Agent ** END ** Agent: Finding updates [CallerId = OperationalInsight Id = 49]
239
239
```
240
240
241
241
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.
242
242
243
-
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.
243
+
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.
2018-08-06 10:58:45:992 480 5d8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2018-08-06 10:58:45:992 480 5d8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
0 commit comments