Skip to Content
Last modified by Sebastian Marsching on 2025/10/22 21:45
From version 5.4
edited by Sebastian Marsching
on 2025/10/22 21:39
Change comment: There is no comment for this version
To version 5.2
edited by Sebastian Marsching
on 2025/10/22 21:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -114,14 +114,8 @@
114 114  
115 115  More information on Defender updates: <https://www.microsoft.com/en-us/wdsi/defenderupdates>
116 116  
117 -# Fixing HTTP 413 request entity too large error
117 +# Fixing
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.
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 ``
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>