I’ve come throughout an attention-grabbing “function” or “bug” in Windows Update service on Windows Server 2016 (Windows 10 RTM). If you’re not utilizing an inner and your OS should be up to date straight from Microsoft Update servers within the Internet, if you downloading the updates in Windows Server 2016 through a proxy server, the obtain course of stucks at zero% (Downloading Updates zero%).
What is attention-grabbing, the Windows Update shopper has been in a position to ship/obtain the updates metadata (the checklist of mandatory updates has been fashioned efficiently), however none of them could possibly be downloaded.
Let’s create and open the WindowsUpdate.log utilizing the cmdlet.
2018/11/11 12:32:47.8312332 123 3542 DownloadSupervisor BITS job initialized: JobId =
2018/11/11 12:32:47.8436054 123 3542 DownloadSupervisor Downloading from http://obtain.windowsupdate.com/c/msdownload/replace/software program/defu/2017/09/nis_engine_1af0e4b80bf4028f8dac56ebf186b392e4e72486.exe to C:WindowsSoftwareDistributionDownloadf71ddf93ec2d087c819cf75c55ddfda21af0e4b80bf4028f8dac56ebf186b392e4e72486 (full file)
2018/11/11 12:32:47.8452605 123 3542 DownloadSupervisor New obtain job for UpdateId F608EDA4-2E84-433A-A8C9-8117411F91A8.200
2018/11/11 12:32:47.8545291 123 3542 DownloadSupervisor Download job E3BB42A1C-42B4-221B-1320-8AB433CE1965E resumed.
2018/11/11 12:32:47.8734449 123 3542 DownloadSupervisor Failed to hook up with the DO service; (hr = 80040154)
2018/11/11 12:32:47.8734462 123 3542 DownloadSupervisor GetDOManager() failed, hr=80246008, hrExtended=80040154
2018/11/11 12:32:47.8734472 123 3542 DownloadSupervisor Failed creating DO job with hr 80246008
2018/11/11 12:32:47.8772521 123 3542 DownloadSupervisor DO obtain failed with error 80246008[Extended: 80040154], falling again to BITS and retrying with new Download Job.
As you may see, BITS can’t obtain the information with the error 80246008 (SUS_E_DM_FAILTOCONNECTTOBITS – see the ).
As it turned out, the proxy server settings for the Internet Explorer in Windows Server 2016 RTM (10.zero.14393) doesn’t work in the identical method as in earlier Windows variations. In order the Windows Update shopper can entry the Internet via a proxy, you should pressure set the system proxy for winhttp.
Display the present proxy server settings for WinHTTP:
netsh winhttp present proxy
Direct entry (no proxy server).
As you may see, the proxy settings for WinHTTP should not set. A proxy was configured in Internet Explorer on the User degree however not in System degree (WinHTTP). This configuration causes the connections to Windows Update to fail.
You can set the system proxy parameters for WinHTTP as follows:
netsh winhttp set proxy proxy-server="192.168.100.24:3128" bypass-list="*.woshub.com"
Or like this, by importing the settings from IE (proxy settings within the Internet Explorer should be set manually or upfront):
netsh winhttp import proxy supply=ie
After altering the proxy settings, restart Windows Update service:
After a proxy for WinHTTP had been specified, Windows Server 2016 began to obtain updates from Microsoft Update servers.
The similar downside is typical to RTM model of Windows 10 (RTM model of the Windows Update Agent – 10.zero.14393.zero).
Note. If you manually obtain and set up the latest cumulative replace from Microsoft Update Catalog (launched after November, 2016), the updates might be obtain and put in usually even in case you don’t set WinHTTP proxy. According to Microsoft data, this bug was fastened in Windows Update agent 10.zero.14393.187 and greater.
Also, don’t overlook that you just gained’t be capable of get updates via proxy server that requires authentication, since Windows Update shopper doesn’t assist proxy authentication (). In order Windows Update to work accurately, you should permit nameless entry to Microsoft Update servers on your proxy server. The checklist of URLs is given beneath: