| Previous | Next |
| WU_E_PT_HTTP_STATUS_DENIED | WU_E_PT_HTTP_STATUS_BAD_METHOD |
WU_E_PT_HTTP_STATUS_FORBIDDEN
WU_E_PT_HTTP_STATUS_FORBIDDEN maps to HTTP 403: the server understood the request but refused to fulfill it. This typically indicates authorization, access-control, URL, or proxy-policy denial.
What to check
- Check WSUS, IIS, reverse-proxy, and proxy access-control rules for the exact requested path.
- Verify that the service URL and port in the client policy match the server deployment.
- Compare a failing client with a working client that uses the same route and policy.
A 403 response is different from a connection failure
HTTP semantics define 403 as a server refusal to fulfill a request it understood. WUA therefore reached an HTTP endpoint and received a response; this is not the same failure boundary as DNS resolution, TCP connection, or WU_E_NO_CONNECTION. Microsoft’s WSUS scan guidance lists 0x80244018 among HTTP authentication or access failures to investigate on the update-service path.
Record the exact WSUS or update-service URL and identify which virtual service was being called. Check server authorization, proxy or web-filter policy, and the configured service location. Do not convert every 403 into a credential prompt: HTTP 403 does not mean that supplying different authentication will necessarily make the server accept the request.
References
References
- RFC 9110: 403 Forbidden semantics
- Microsoft: troubleshoot WSUS scan HTTP failures
- Microsoft: Windows Update protocol-talk error codes
Looking for a different code? Search another status or error code.