Error -102 (Do not connect to any Win. Update Internet Locations)

[BatchPatchAA]

I am receiving the following error message when trying to check for updates on my Win 2016 servers. I do not receive this error message when working with Win 2k12R2 or Win 2008R2 servers. The exact error is -102: Failed to execute the search. HRESULT: -2145103860. I do have the GP option enabled for “Do not connect to any Windows Update Internet Locations.”

I have two questions regarding the error message.

1) Why does this only impact Win 2016 servers and not 2008 or 2012? They are both under the same Group Policy objects.

2) We definitely want to refrain from having servers contact Windows Update service for updates directly. Would disabling the “Do not connect to any Windows Update Internet Locations” cause the servers to reach out to Windows public update service if we still have the intranet site specified in group policy with client side targeting enabled?

[doug]

I would direct you to the Microsoft documentation that describes the behavior of this policy:

https://docs.microsoft.com/en-us/windows/deployment/update/waas-wu-settings#do-not-connect-to-any-windows-update-internet-locations

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:

dual-scan-difficulties-with-windows-update-on-windows-10-versions-1607-anniversary-update-and-1703-creators-update

deciphering-dual-scan-behavior-in-windows-10

[BatchPatchAA]

I will look over some of the links you have provided and update the thread thereafter.

Thanks!

[doug]

For other HRESULT values please see: https://batchpatch.com/batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx

[Author]

Posts