Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x80244022 (WU_E_PT_HTTP_STATUS_PROXY_AUTH_REQ) | WindowsUpdate.log, Event Viewer | Indicates proxy authentication failure. |
| Affected OS builds | Windows 10 and Windows 11 | Microsoft Documentation | -> |
| Registry key involved | HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings | Registry Editor | Contains WinINet proxy settings. |
| Relevant service/endpoint URL | *.windowsupdate.com, *.update.microsoft.com, *.delivery.mp.microsoft.com | Microsoft Learn | -> |
| Log line signature | HTTP 407 Proxy Authentication Required | WindowsUpdate.log | Indicates proxy authentication failure. |
Log Files to Check
%userprofile%\Desktop\WindowsUpdate.logEvent Viewer > Windows Logs > Application (Event ID 16)
What This Error Actually Means
The error code0x80244022 (WU_E_PT_HTTP_STATUS_PROXY_AUTH_REQ) indicates that the Windows Update client encountered a proxy authentication requirement while attempting to connect to Microsoft Update servers. Specifically, this occurs when the Windows Update process attempts to communicate through an HTTP proxy server that requires username/password or NTLM/Kerberos authentication. However, Windows Update does not support prompting for proxy credentials and fails at this stage before reaching the actual Microsoft Update endpoints.
This error is raised by the WindowsUpdateClient service, which handles update detection and installation. The failure occurs during the initial connection attempt to Microsoft's update infrastructure, including domains like *.windowsupdate.com, *.update.microsoft.com, and *.delivery.mp.microsoft.com.
Affected Versions and Scope
This error affects: - Windows 10 (all builds) - Windows 11 (all builds) It does NOT affect: - Windows 7 or earlier - Devices not configured to use a proxy server for Microsoft Update traffic The issue is common in enterprise environments where network traffic is routed through corporate proxies that enforce authentication, especially when those proxies are not explicitly configured to bypass authentication for Microsoft Update endpoints.Where To Look First: Logs and Event IDs
To diagnose this error, examine the following logs and event IDs: 1. **WindowsUpdate.log**: - Path:%userprofile%\Desktop\WindowsUpdate.log
- Generate using PowerShell: Get-WindowsUpdateLog
- Look for: HTTP 407 Proxy Authentication Required
2. **Event Viewer**:
- Navigate to: Event Viewer > Windows Logs > Application
- Search for Event ID: 16 (Windows Update Agent)
- Source: WindowsUpdateClient
- Error code: 80244022
3. **Registry**:
- Check proxy settings at: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Root Causes
1. Proxy Server Requires Authentication for Microsoft Update Domains
The corporate network's proxy server requires authentication for traffic destined to *.windowsupdate.com, *.update.microsoft.com, or *.delivery.mp.microsoft.com. Windows Update does not handle proxy authentication prompts and fails at this stage. **Diagnostic Steps**: - Usenetsh winhttp show proxy to check current WinHTTP proxy settings.
- Review Event Viewer for Event ID 16 with error code 80244022.
2. Misconfigured WinHTTP Proxy Settings
Windows Update uses the WinHTTP stack, which may not inherit proxy settings from Internet Explorer (WinINet). If WinHTTP is configured differently than WinINet, updates may fail due to incorrect proxy handling. **Diagnostic Steps**: - Compare WinHTTP and WinINet proxy settings: - WinHTTP:netsh winhttp show proxy
- WinINet: reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyServer
3. Delivery Optimization Proxy Conflict
Windows Delivery Optimization (DO) may use a different proxy configuration, causing conflicts with Windows Update. **Diagnostic Steps**: - Check DO settings in: Settings > Windows Update > Advanced options > Delivery Optimization - Verify if a custom DO proxy is configured and requires authentication.4. Group Policy or WSUS Configuration
If the device is managed via Group Policy or uses an internal WSUS server, misconfigured policies may force updates through an unauthorized proxy.
**Diagnostic Steps**:
- Check Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows Update
- Verify WSUS configuration if applicable.
Fix Procedure
- Import WinINet Proxy Settings into WinHTTP:
- Run PowerShell as Administrator and execute:
netsh winhttp import proxy source=ie
- This copies browser proxy settings (including PAC files) to WinHTTP.
- Manually Configure WinHTTP Proxy:
- Use the following command, replacing placeholders with your proxy details:
netsh winhttp set proxy proxy-server='http=proxyserver:port;https=proxyserver:port' bypass-list='*.windowsupdate.com;*.update.microsoft.com;*.delivery.mp.microsoft.com'
- Bypass Proxy for Microsoft Update Domains:
- Add the following registry entry to bypass proxy for update domains:
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyOverride /t REG_SZ /d "*.windowsupdate.com;*.update.microsoft.com;*.delivery.mp.microsoft.com" /f
- Configure Delivery Optimization:
- Open Settings > Windows Update > Advanced options > Delivery Optimization.
- Set "Download from other PCs" to Off and clear any custom proxy settings.
- Group Policy Configuration (Optional):
- Navigate to: Intune admin center > Devices > Policies > Create Policy > Windows > Administrative Templates > Windows Components > Windows Update
- Configure "Configure Automatic Updates" with the appropriate WSUS server if applicable.
Warning: Modifying Group Policy without proper testing can affect enrolled devices. Always test changes in a controlled environment before full deployment.
- Test Direct Connectivity:
- Temporarily bypass the proxy:
netsh winhttp set proxy DIRECT
- Attempt an update check to confirm if the issue resolves.
- Revert Proxy Settings (if direct test succeeds):
- Reapply proxy settings after confirming the fix.
Error Code Variants
netsh winhttp import proxy source=ie
- This copies browser proxy settings (including PAC files) to WinHTTP.
netsh winhttp set proxy proxy-server='http=proxyserver:port;https=proxyserver:port' bypass-list='*.windowsupdate.com;*.update.microsoft.com;*.delivery.mp.microsoft.com'
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyOverride /t REG_SZ /d "*.windowsupdate.com;*.update.microsoft.com;*.delivery.mp.microsoft.com" /f
Warning: Modifying Group Policy without proper testing can affect enrolled devices. Always test changes in a controlled environment before full deployment.
netsh winhttp set proxy DIRECT
- Attempt an update check to confirm if the issue resolves.
| Error Code | Description | Distinguishing Factor |
|---|---|---|
| 0x8024401F (WU_E_PT_HTTP_STATUS_PROXY_AUTH_REQ) | Proxy authentication required for Windows Store updates | Affects Microsoft Store, not Windows Update |
| 0x8024600C (WU_E_DOWNLOAD_FAILED HRESULT) | General download failure during update installation | Occurs after proxy authentication phase |
| 0x8024401D (WU_E_PT_HTTP_STATUS_PROXY_AUTH_REQ) | Proxy authentication required for driver updates | Affects Windows Driver Update Service, not core OS updates |
Verification
After applying fixes: - Run an update check via PowerShell:Get-WindowsUpdate -Install
- Verify in Event Viewer that no new Event ID 16 errors occur.
- Check WindowsUpdate.log for HTTP 200 responses instead of 407.
Prevention
To avoid recurrence: 1. Ensure proxy servers allow unauthenticated access to Microsoft Update domains. 2. Use Group Policy or Intune to enforce consistent proxy settings across devices. 3. Configure WinHTTP to automatically import browser proxy settings via:netsh winhttp import proxy source=ie
TIP: Regularly audit proxy configurations and update allowlists to include new Microsoft Update domains as they are introduced.