AB#9551-b: Modify web.config to increase update limits

Second PR for [CI 9551](https://dev.azure.com/KMOps/ContentExperience/_queries/edit/9551)

Author: v-tappelgate

support/mem/configmgr/update-management/error-80244007-when-wsus-client-scans-updates.md

@@ -1,17 +1,21 @@
 ---
 title: Error 80244007 when a Windows Server Update Services (WSUS) client scans for updates
 description: Describes an issue in which WSUS clients can't scan for updates.
-ms.date: 02/11/2025
-ms.reviewer: kaushika
+ms.date: 02/03/2026
+ms.reviewer: kaushika, viki, v-appelgate
 ms.custom: sap:Software Update Management (SUM)\Software Update Scanning
 ---
 # Error 80244007 when a WSUS client scans for updates
 
-This article helps you fix an issue where you receive the **[80244007] SyncUpdates_WithRecovery failed** error when a WSUS client scans for updates.
-
 _Original product version:_   Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012  
 _Original KB number:_   4096317
 
+## Summary
+
+When Windows Server Update Services (WSUS) clients scan for updates, they might fail with error `[80244007] SyncUpdates_WithRecovery failed`. This error occurs when the number of updates to be synchronized exceeds the default maximum number of installed prerequisites that a client can pass to the SyncUpdates method.
+
+This article describes how to identify and resolve this issue by adjusting WSUS server configuration settings.
+
 ## Symptom
 
 You use WSUS to deploy software updates to computers in your organization. When a WSUS client computer scans for updates on the WSUS server, you see the following error message in the WindowsUpdate.log file on the client computer:
@@ -36,9 +40,7 @@ This issue occurs when the number of updates to be synchronized exceeds the maxi
 
 To fix the issue, follow these steps on the WSUS server:
 
-1. Open an elevated Command Prompt window, and then go to the following location:
-
-   `%programfiles%\Update Services\WebServices\ClientWebService`
+1. Open an elevated Command Prompt window, and then go to %programfiles%\Update Services\WebServices\ClientWebService.
 
 2. Type the following commands, and press Enter after each command:
 
@@ -48,12 +50,14 @@ To fix the issue, follow these steps on the WSUS server:
     notepad.exe web.config
     ```
 
-3. Locate the following line in web.config:
+3. In **web.config**, locate the following entries, and then update their values as indicated:
 
    ```xml
-   <add key="maxInstalledPrerequisites" value="400"/>
+   <add key="maxInstalledPrerequisites" value="800"/>
+   <add key="maxCachedUpdates" value="44000"/>
    ```
 
-4. Change the value from **400** to **800**.
-5. Save the web.config file.
-6. Run `IISReset`.
+   This change increases **maxInstalledPrerequisites** from 400 to 800 and **maxCachedUpdates** from 22,000 to 44,000.
+
+4. Save the web.config file.
+5. Run `IISReset`.