Entity too large on regular windows update (not wsus)

Question

We get an error while doing a windows update scan on windows server 2016.
The error is 413 (0x19D) Request entity too large.

I have found articles about adjusting the IIS from WSUS, but this is straight to the Microsoft servers.
How can we solve this issue (since we cannot adjust microsoft's windows update servers ;) )

from windowsupdate.log (dutch):

2021-09-07 11:38:43.9763364 84 6408 WebServices WS error: Er is een fout opgetreden bij het communiceren met het eindpunt op https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx.
2021-09-07 11:38:43.9763373 84 6408 WebServices WS error: De server heeft de HTTP-statuscode 413 (0x19D) met de tekst Request Entity Too Large geretourneerd.
2021-09-07 11:38:43.9763378 84 6408 WebServices WS error: Het antwoord van de HTTP-server wordt niet herkend.
2021-09-07 11:38:43.9763387 84 6408 WebServices Web service call failed with hr = 80240439.

Answer 1

Hello @Hen Savelkoul ,

This seems more like an issue of problematic updates such as superseed updates conflicting with newer version.

First I would recommend a cleanup of the repository of one of the affected clients:
From an elevated command prompt run:
Net stop wuauserv
Net stop bits

then Delete contents of "C:\Windows\SoftwareDistribution Software Distribution" (using Windows explorer, note all the contents).

Net start wuauserv
Net start bits

After that perform a cleanup maintenance for WSUS as described here, one of the latest guides: https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/wsus-maintenance-guide

I would recommend to do a manual and visual check for superseeded or failing updates from the WSUS console:
From the WSUS Console go to:
Updates> All Updates
Set the filter to "Any except Declined"
Then right click on the "title" column head and enable the columns "File Status" and "Supersedence". This will help you detect Superseeded updates not delete and also any failed update, recommendation is to delete them.

Hope this helps with your question,
Best regards,

Answer 2

No one any ideas ?

This is against microsofts Update servers, NOT WSUS.

The error is followed by:
2021-11-12 15:04:21:963 880 11a8 WS WARNING: MapToSusHResult mapped Nws error 0x803d0000 to 0x80240439
2021-11-12 15:04:21:963 880 11a8 WS WARNING: Web service call failed with hr = 80240439.
2021-11-12 15:04:21:963 880 11a8 WS WARNING: Current service auth scheme='None'.
2021-11-12 15:04:21:963 880 11a8 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2021-11-12 15:04:21:963 880 11a8 WS FATAL: OnCallFailure failed with hr=0X80240439
2021-11-12 15:04:21:965 880 11a8 SLS Retrieving SLS response from server using ETAG "x+4KoqRtWL9BTdu9TOj2Nhm8T1AHalXjJpaDl/m2rO8=_1440"...
2021-11-12 15:04:21:965 880 11a8 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{7971F918-A847-4430-9279-4A52D1EFE18D}/x64/6.3.9600.0/0?CH=319&L=nl-NL&P=&PT=0x8&WUA=7.9.9600.19915
2021-11-12 15:04:22:393 880 11a8 EP Got 7971F918-A847-4430-9279-4A52D1EFE18D redir Client/Server URL: "https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx"
2021-11-12 15:04:22:394 880 11a8 PT WARNING: PTError: 0x80240439
2021-11-12 15:04:22:394 880 11a8 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80240439
2021-11-12 15:04:22:394 880 11a8 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 151) stopped; does use network; is at background priority
2021-11-12 15:04:22:394 880 11a8 PT + SyncUpdates round trips: 2
2021-11-12 15:04:22:394 880 11a8 PT WARNING: Sync of Drivers failed (Software succeeded): 0x80240439