| Attribute | Details |
|---|---|
| Error Code | 0x80244017 |
| Target OS | Windows Server 2022 |
| Common Cause | Proxy Authentication, WSUS Misconfiguration, Corrupt Update Cache |
| Difficulty Level | Intermediate |
What is Windows Server 2022 Update Error 0x80244017?
Error 0x80244017 is a common issue in Windows Server 2022 that typically occurs during the Windows Update process. Technically, this error translates to WU_E_PT_HTTP_STATUS_DENIED, which signifies that the update client was denied access to the server.
In most enterprise environments, this happens when a proxy server or a Windows Server Update Services (WSUS) instance blocks the communication. It can also stem from corrupted local update components or incorrect system time settings.
Step-by-Step Solutions
1. Reset Windows Update Components
Often, the local update cache becomes corrupted. Resetting the services and clearing the SoftwareDistribution folder can resolve this.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver2. Configure Proxy Settings
If your server uses a proxy, the update agent might be failing because it cannot authenticate. You should check if the proxy is preventing the connection. Try resetting the WinHTTP proxy settings.
netsh winhttp reset proxyAfter running this, restart the Windows Update service and try again. If you must use a proxy, ensure the server has the correct credentials mapped for the System account.
3. Verify WSUS Connectivity
If your Windows Server 2022 is managed via WSUS, ensure the client can reach the WSUS server. Check the registry for the correct update server URL.
reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdateEnsure the WUServer and WUStatusServer keys point to the correct internal server address and that port 8530 or 8531 is open.
4. Run DISM and SFC Scans
System file corruption can lead to update failures. Use the Deployment Image Servicing and Management tool to repair the Windows image.
dism /online /cleanup-image /restorehealth
sfc /scannowOnce the scans are complete, reboot the server and attempt the update process once more.
5. Check System Time and Date
Incorrect time settings can cause SSL/TLS handshake failures, leading to access denied errors. Ensure your server is synchronized with a reliable NTP source.
w32tm /resync