- This topic has 3 replies, 2 voices, and was last updated 3 years, 5 months ago by .
-
Posts
-
I would direct you to the Microsoft documentation that describes the behavior of this policy:
Do not connect to any Windows Update Internet locations
Even when Windows Update is configured to receive updates from an intranet update service, it will periodically retrieve information from the public Windows Update service to enable future connections to Windows Update, and other services like Microsoft Update or the Microsoft Store.
Use Computer Configuration\Administrative Templates\Windows Components\Windows update\Do not connect to any Windows Update Internet locations to enable this policy. When enabled, this policy will disable the functionality described above, and may cause connection to public services such as the Microsoft Store, Windows Update for Business and Delivery Optimization to stop working.
Note
This policy applies only when the device is configured to connect to an intranet update service using the “Specify intranet Microsoft update service location” policy.
I’m not sure why you are experiencing it only on your 2016 machines. It might be the specific combination of policies applied. I would start by evaluating every single applied policy to see if any one or combination of policies is causing the discrepancy.
If you have the “Specify intranet Microsoft update service location” policy set, then you should not need the “Do not connect to any Windows Update Internet Locations” policy. However, I would suggest that you pay attention to the possibility of “Dual Scan” being enabled on your 2016 computers. I would suggest that you consider enabling “Do not allow update deferral policies to cause scans against Windows Update”.
More on Dual Scan:
For other HRESULT values please see: https://batchpatch.com/batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx
- You must be logged in to reply to this topic.