Windows Update stuck at 0 percent on Windows 10 or Windows Server 2016
Applies to: Windows Server 2016Windows 10, version 1607
NEED TO ENABLE WINDOWS FIREWALL IN SERVICES AND DISABLE FIREWALL LIKE HERE.
On Windows 10 or Windows Server 2016, when you try to download updates by using Windows Update (stand-alone or WSUS), the process hangs at 0 percent completion, as shown in the following screen shot:
This issue occurs for either of the following reasons.
A proxy was configured in Internet Explorer (User level) but not in WinHTTP (System level). This configuration causes the connections to Windows Update to fail.
You are using the RTM version (10.0.14393.0) of the Windows Update Agent, and have configured the computer to connect to a Windows Server Update Services (WSUS) server.
This issue can be caused if the Windows Firewall service is disabled on the computer. This is an unsupported method of turning off the firewall functionality.
To resolve the issue, follow these steps:
For Cause 1
Configure a proxy in WinHTTP by using the following netsh command:
netsh winhttp set proxy ProxyServerName:PortNumber
Note You can also import the proxy settings from Internet Explorer by using the following command:
netsh winhttp import proxy source=ie
For Cause 2
Update the Windows Update Agent to version 10.0.14393.187. To do this, install the September 2016 Cumulative Update for Windows 10 or Windows Server 2016 (3193494), or any later cumulative update.
For Cause 3
To correctly turn off the firewall functionality, see: I Need to Disable Windows Firewall.
Third-party firewall software that is compatible with Windows Vista and Windows Server 2008 can programmatically disable only the parts of Windows Firewall with Advanced Security that have to be disabled for compatibility. You should not disable the firewall yourself for this purpose. Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft.
We recommend verifying your firewall solution vendor if disabling of the service is necessary because usually third-party Firewall software usually turn off the Windows Firewall functionality in a supported way already. You may not disable the service which is not a supported configuration.