Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x80072EE2 (WININET_E_TIMEOUT) | WindowsUpdate.log and CBS.log | -> Indicates a timeout when contacting Microsoft Update servers. |
| Affected OS builds | Windows 10 / Windows 11 | Microsoft documentation | -> Applies to all versions of Windows 10 and 11. |
| Registry key involved | HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate | Windows Registry | -> Check WUServer and WUStatusServer values for WSUS configuration. |
| Relevant service/endpoint URL | *.windowsupdate.com, *.update.microsoft.com, delivery.mp.microsoft.com | Microsoft Update endpoints documentation | -> These URLs must be reachable on ports 443 and 80. |
| Log file signature | HRESULT=0x80072EE2, WININET_E_TIMEOUT | WindowsUpdate.log | -> Log entry indicating the timeout failure. |
Log Files to Check
C:\Users\%USERNAME%\Desktop\WindowsUpdate.logC:\Windows\Logs\CBS\CBS.log
What This Error Actually Means
The error code0x80072EE2, also known as WININET_E_TIMEOUT, indicates a timeout occurred while the Windows Update client was attempting to communicate with Microsoft's update servers. This specific error is raised by the Windows Update service (wuauserv) when it fails to establish or maintain a connection to endpoints such as *.windowsupdate.com, *.update.microsoft.com, or delivery.mp.microsoft.com. The timeout can occur during either metadata retrieval or actual update file downloads.
Affected Versions and Scope
This error is documented in Microsoft's official resources and affects all builds of Windows 10 and Windows 11. It is not limited to specific versions but can impact any installation where network connectivity to Microsoft Update endpoints is intermittent or blocked. The issue is particularly common in enterprise environments with strict firewall policies, proxy servers, or DNS configurations that may inadvertently block access to necessary update resources.Where To Look First: Logs and Event IDs
To diagnose this error, examine the following log files:C:\Windows\Logs\WindowsUpdate\WindowsUpdate.etl (converted to C:\Users\%USERNAME%\Desktop\WindowsUpdate.log using Get-WindowsUpdateLog)
C:\Windows\Logs\CBS\CBS.log
Search for these exact strings:
HRESULT=0x80072EE2, WININET_E_TIMEOUT
In Event Viewer (eventvwr.msc), look under Windows Logs > System for events with the following IDs:
- Event ID 20: Installation Failure
- Event ID 25: Download Failure
These events will include details about the specific URL that timed out, such as https://fe2.update.microsoft.com.
Root Causes
Network Connectivity Issues
The most common cause is a network configuration blocking access to Microsoft Update endpoints. This can be due to: - Firewalls or proxies intercepting HTTPS traffic on ports 443 or 80 - Network appliances dropping idle connections before the update process completes - Incorrect firewall rules that block *.windowsupdate.com, *.update.microsoft.com, or delivery.mp.microsoft.comWSUS Configuration Errors
If the system is configured to use an internal WSUS server (HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer), but that server is offline or unreachable, all update attempts will fail with this timeout error.
DNS Resolution Problems
DNS issues can prevent the Windows Update client from resolving Microsoft's update domains. This could be due to: - Corrupted DNS cache on the local machine - Misconfigured DNS servers in the network - DNS filtering that blocks access to windowsupdate.comDelivery Optimization Bandwidth Throttling
Windows 10 and 11 use Delivery Optimization to share update files between devices. If this feature is misconfigured, it may throttle bandwidth to a point where updates cannot complete within the expected timeframe.Fix Procedure
- Test Network Connectivity:
Run these PowerShell commands to verify reachability:
Test-NetConnection -ComputerName windowsupdate.microsoft.com -Port 443Test-NetConnection -ComputerName delivery.mp.microsoft.com -Port 443EnsureTcpTestSucceeded: Truefor both tests. - Check WSUS Configuration:
Use PowerShell to inspect the Windows Update policy:
Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' | Select-Object WUServer, WUStatusServer, DisableWindowsUpdateAccessIfWUServeris set, verify connectivity to that URL. - Inspect DNS Resolution:
Run:
Resolve-DnsName windowsupdate.microsoft.comEnsure it returns valid Microsoft IP addresses. Flush the DNS cache if necessary:ipconfig /flushdns - Bypass Proxy for Update Domains:
If a proxy is configured, add exceptions:
netsh winhttp set proxy proxy-server=: bypass-list='*.microsoft.com;*.windowsupdate.com' - Review Delivery Optimization Settings:
Check the current mode:
Get-DeliveryOptimizationStatus | Select-Object DownloadMode, RestrictionsAdjust settings as needed to ensure sufficient bandwidth. - Reset Windows Update Components:
Stop services and clear cache:
net stop wuauserv; net stop cryptSvc; net stop bits; net stop msiserverRemove-Item 'C:\Windows\SoftwareDistribution\Download' -Recurse -ForceRestart the services:net start wuauserv; net start cryptSvc; net start bits; net start msiserver - Check for Group Policy Issues:
If WSUS is unreachable, temporarily remove the policy:
Remove-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' -Name WUServer, WUStatusServerForce a Windows Update check:wuauclt /detectnow - Inspect Event Viewer Logs:
After applying fixes, look for successful update events:
Event ID 19: Installation Success
Error Code Variants
| Error Code | Description |
|---|---|
0x80072EE2 | WININET_E_TIMEOUT - Connection to update server timed out |
0x800700C1 | Network connectivity issues (general) |
0x8024402C | Windows Update service not responding |
0x800705B4 | Connection reset by server (possible proxy issue) |
Verification
After applying fixes, verify success by: - Checking Event Viewer forEvent ID 19 (Installation Success)
- Running Test-NetConnection windowsupdate.microsoft.com -Port 443 to confirm connectivity
- Manually triggering an update check via Settings > Windows Update
Prevention
To avoid recurrence: - Ensure all Microsoft Update endpoints are whitelisted in firewalls/proxies - Monitor WSUS server availability if used - Regularly flush DNS cache or configure clients to use reliable public DNS (e.g., 8.8.8.8) - Review and adjust Delivery Optimization policies as needed
Important: Temporarily disabling WSUS configuration may affect enrolled devices managed via Intune or other MDM solutions. Ensure you have appropriate fallback mechanisms in place.
A quick diagnostic shortcut is to test connectivity directly from the command line:
curl -I https://fe2.update.microsoft.com
This provides immediate feedback on whether the server is reachable.