Skip to Content
Last modified by Sebastian Marsching on 2025/10/22 21:45
From version 6.1
edited by Sebastian Marsching
on 2025/10/22 21:45
Change comment: There is no comment for this version
To version 5.3
edited by Sebastian Marsching
on 2025/10/22 21:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -116,12 +116,8 @@
116 116  
117 117  # Fixing HTTP 413 request entity too large error
118 118  
119 -I experienced this problem when running an update scan on Windows Server 2022 clients, while Windows 11 clients still worked fine, but I believe that this can essentially happen with any operating system release. On the affected clients, the update scan would fail with error code 0x80240439. After deleting `C:\Windows\SoftwareDistribution`, the next scan would succeed, but all subsequent scans would fail again. This behavior was reproducible on all Windows Server 2022 clients.
119 +I experienced this problem when running an update scan on Windows Server 2022 clients, while Windows 11 clients still worked fine, but I believe that this can essentially happen with any
120 120  
121 -When generating the Windows Update log file on the client with the PowerShell `Get-WindowsUpdateLog` cmdlet, the log file would show entries like the following ones:
122 -
123 -I found various hints that mostly pointed to the limits in `C:\Program Files\Update Services\WebServices\ClientWebService/Web.config`, but increasing those limits did not help at all. In the end, I found the [relevant piece of information](https://batchpatch.com/forums/x/topic/windows-update-error-1611-106-failure/): The `uploadReadAheadSize` in the IIS configuration had to be increased. This can be done by opening the _Internet Information Services (IIS) Manager_, choosing the _WSUS Administration_ site, under _Management_ choosing the _Configuration Editor_, selecting the `system.webServer/serverRuntime` section, and finally increasing the `uploadReadAheadSize` from its default value of 49152 bytes. I chose to increase it by a factor fo ten, which proved to be sufficient in my case. After this, one has to click _Apply_ on the right and restart IIS by running the `IISReset` command.
124 -
125 125  # Resources
126 126  
127 127  * WSUS Best Practices: <https://docs.microsoft.com/en-US/troubleshoot/mem/configmgr/windows-server-update-services-best-practices>