| Previous | Next |
| WU_E_SERVICE_STOP | WU_E_NO_INTERACTIVE_USER |
WU_E_NO_CONNECTION
WU_E_NO_CONNECTION means that the Windows Update operation did not complete because the required network connection was unavailable. It does not identify a specific HTTP response or certificate error.
What to check
- Verify basic network connectivity and the configured update service or WSUS endpoint.
- Check proxy, name-resolution, and policy settings only after confirming which update source the client uses.
- Retry after connectivity is restored; preserve any more specific nested HRESULT from the logs.
Locate the failing phase before changing the network
WUA search, download, and installation are separate operations, and MS-WUSP uses HTTP and SOAP for client-server update communication. A no-connection result during metadata synchronization has a different boundary from a download failure after search already succeeded. Record the operation phase, service endpoint, and the first networking HRESULT in the event sequence.
On WSUS-managed clients, validate reachability to the configured update service rather than only testing Microsoft public endpoints. Microsoft’s scan troubleshooting guidance specifically calls out the WSUS web services used during scan. If connectivity returns, perform a fresh operation; avoid assuming that a partially completed search or download object is still current.
References
References
- Microsoft Open Specifications: Windows Update protocol overview
- Microsoft: troubleshoot WSUS client scan connectivity
- Microsoft: common Windows Update connectivity errors
Looking for a different code? Search another status or error code.