Windows Server 2022 WSUS with WID - Windows 11 25H2 clients sync successfully but never report status

Rajendra Chandrikapure 50

Has anyone seen this behavior with Windows 11 25H2 clients and WSUS on Windows Server 2022 (WID) where:

Successfully scans against WSUS.

Finds approved updates.

Downloads updates.

Installs updates.

Windows Update Operational log shows Event ID 26 ("Windows Update successfully found updates") and Event ID 41 ("An update was downloaded").

Therefore, client-to-WSUS communication appears to be working.

synchronization succeeds,

IIS returns HTTP 200,

clients download/install updates,

but status reporting never reaches SUSDB (LastReportedStatusTime, LastInventoryTime, and tbEventInstance remain empty)?

Is there a known compatibility issue, required WSUS update, or server-side fix for Windows 11 25H2 reporting?

0 comments

Answer accepted by question author

Adam J. Marshall 11,031 MVP

If you have a licence for WAM, we added a tool to fix this. Download 2026.07.1 and install it and then you can run from the WAM Shell

Invoke-DetectoidCleanup

This will follow Microsoft's instructions and easily clean up your database from the test detectoids.

If you want to let WAM tell you if you have it or not, just wait for the next run tomorrow or execute from the WAM Shell:

.\Clean-WSUS.ps1 -ScheduledRun

And then check the report to see if the detectoids have been found in your database.

Alternatively follow https://support.microsoft.com/en-us/servicing/os/windows/docs/2026/07/kb5121986-windows-server-update-service-sync-operations-issues-and-timeouts

Rajendra Chandrikapure 50 Reputation points

2026-07-23T11:22:07.19+00:00

Thank you for sharing KB5121986. I have reviewed the article.

My WSUS server does not appear to exhibit the synchronisation issues described in the KB. Synchronisation completes successfully; clients can scan, download, and install updates; and IIS logs show successful HTTP 200 responses from ReportingWebService.asmx.

The only issue is that Windows 11 25H2 clients do not update LastReportedStatusTime and remain "Not yet reported"

Could you please confirm whether this behaviour is expected to be covered by KB5121986, or should be investigated as a separate Windows 11 25H2 reporting issue?
Adam J. Marshall 11,031 Reputation points MVP

2026-07-23T13:29:05.36+00:00

The only way to know if this applies to you or not is to modify the SQL code to select the appropriate rows and see if you have more than 0. If you have more than 0, this applies to you. If you don't, then this isn't the answer.

This is a widespread issue Microsoft created causing anyone who was syncing with MS before July 18th (when they fixed it) to be affected. This was such a problem that we chose to create an emergency detection path in WAM and create an easy tool for our customers to fix this issue causing us to re-release WAM with this updated check in our off-schedule. If this ever happens again, WAM would then detect and alert you to remove the detectoids.
William Fourqurean 5 Reputation points

2026-07-24T11:01:57.71+00:00

What is WAM?
Adam J. Marshall 11,031 Reputation points MVP

2026-07-24T13:35:37.5766667+00:00

WAM stands for WSUS Automated Maintenance (Full disclosure: our product). You will need to search for it, as my intent is not advertising.)

Answer accepted by question author

Chen Tran 12,765 Independent Advisor

Hello Rajendra,

Thank you for posting question on Microsoft Windows Forum!

Based on the issue description. Well! The plausible explanation to this behavior is that Windows 11 25H2 introduces changes to the Windows Update Agent that affect how reporting data is packaged and sent to WSUS. While the scan, download, and install workflows (which use the newer Unified Update Platform protocols) function correctly, the reporting event payload appears incompatible with the WSUS server-side processing on Windows Server 2022. The server accepts the connection (HTTP 200), but fails to parse the reporting data into the SUSDB, so tbEventInstance, LastReportedStatusTime, and LastInventoryTime are never updated.

The suggestion is to ensure your WSUS server is fully patched with the latest cumulative update from Windows Update/Microsoft Update Catalog. If you are already on a patch level later than February 2025 and the issue persists, a specific out-of-band fix may still be pending for 25H2. Checking for any latest servicing stack updates.

On the other hand, try to check the Server-Side by looking at what WSUS is doing with the data it receives. You can open the WSUS application log on your Server 2022 box. Navigate to this path C:\Program Files\Update Services\LogFiles\SoftwareDistribution.log and search the log for references to ReportingWebService.asmx or DBNull / ArgumentNullException. If you see SOAP or Parsing Exceptions which indicates that Windows 11 25H2 introduced minor changes to the Windows Update Agent (WUA) payload string. If WSUS does not know how to map a new hardware property or OS feature metric sent by 25H2, the web service throws an unhandled exception and silently discards the report. Ensure your Server 2022 host has the absolute latest Cumulative Updates installed to get the updated microsoft.updateservices binaries. In case, you see SQL Timeout Exceptions which indicates the reporting pipeline is choking on the WID back-end.

Hope the above information is helpful!

Rajendra Chandrikapure 50 Reputation points

2026-07-18T05:49:20.34+00:00

I reviewed SoftwareDistribution.log and did not find any SOAP exceptions, SQL timeout errors, or parsing/ArgumentNullException errors related to ReportingWebService.

The WSUS server is fully patched (WSUS version 10.0.20348.5386). IIS logs confirm that ReportingWebService.asmx returns HTTP 200 for Windows 11 25H2 clients, and Windows 10/earlier Windows 11 versions report successfully. Only Windows 11 25H2 clients fail to update LastReportedStatusTime and LastInventoryTime.

Could you please confirm whether this is a known compatibility issue between Windows 11 25H2 and WSUS on Windows Server 2022, and whether a hotfix or workaround is available?

4 additional answers

Rajendra Chandrikapure 50 Reputation points

2026-08-01T06:24:29.6166667+00:00

Thank you for your suggestions.

I have already completed the recommended WSUS maintenance, including the Server Cleanup Wizard, database maintenance, and verification related to the KB5121986 detectoid issue. No test detectoids were found in my SUSDB, and synchronisation is working normally.

I also checked the KB5121767 recommendation. However, I am unable to find KB5121767 in the Microsoft Update Catalog, so I cannot import it into WSUS. Could you please confirm whether this update has been withdrawn/superseded or provide the correct Microsoft Update Catalog link?

My current issue is different: affected Windows 11 (24H2/25H2) clients successfully scan, download, and install updates, and LastSyncTime updates correctly in SUSDB. However, LastReportedStatusTime remains NULL, resulting in "Not Yet Reported" and incorrect Needed/Failed status in WSUS. IIS logs confirm the clients are contacting the WSUS server, but no reporting events are recorded for the affected clients.

If there are any additional diagnostics or known fixes for this specific reporting issue, I would appreciate your guidance.
Was this answer helpful?
Adam J. Marshall 11,031 Reputation points MVP

2026-08-01T20:46:11.03+00:00

I'm not sure how you're not able to import that KB

PS C:\Users\Administrator> Import-WsusUpdate -KB KB5121767 ============================= Brought to you by: AJ Tek Corporation https://www.ajtek.ca ============================= Update files will be saved in C:\Users\ADMINI~1\AppData\Local\Temp\2\Import-WsusUpdate. Connecting to the local WSUS server... WARNING: Found multiple updates while searching for KB KB5121767. 1. 2026-07 Cumulative Update for Windows 11, version 24H2 for x64-based Systems (KB5121767) (26100.8894) Update ID: f5ee3797-8092-4dfc-8808-d7606e82a902 2. 2026-07 Cumulative Update for Windows 11, version 25H2 for x64-based Systems (KB5121767) (26200.8894) Update ID: 6188ce2c-1995-4670-89f0-c414cb600f0b 3. 2026-07 Cumulative Update for Windows 11, version 24H2 for arm64-based Systems (KB5121767) (26100.8894) Update ID: 3a0fb4db-ca3b-4a91-a565-d7f3c85e4e7b 4. 2026-07 Cumulative Update for Windows 11, version 25H2 for arm64-based Systems (KB5121767) (26200.8894) Update ID: 216a2770-7b9e-4426-a6b4-cfb11016bbb8 WARNING: Please use the -Filter parameter to narrow your search, or use the updates UpdateID with the -UpdateID parameter of the cmdlet. Import-WsusUpdate : Found several matching updates when searching for the update with KB "KB5121767" (no additional filters used). At line:1 char:1 + Import-WsusUpdate -KB KB5121767 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (System.String[]:String[]) [Write-Error], WriteErrorException + FullyQualifiedErrorId : MultipleUpdatesFound,Import-WsusUpdate PS C:\Users\Administrator> Import-WsusUpdate -KB KB5121767 -Filter "25H2" -x64 ============================= Brought to you by: AJ Tek Corporation https://www.ajtek.ca ============================= Update files will be saved in C:\Users\ADMINI~1\AppData\Local\Temp\2\Import-WsusUpdate. Connecting to the local WSUS server... Getting information about the update we are going to import from the Microsoft Update Catalog... Found 2 files to download. Checking to ensure all files are available for download... Downloading update file windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu (1/2)... Downloading update file windows11.0-kb5121767-x64_588e6404d4e909f2609486fd91a7b28f02d4be0a.msu (2/2)... Importing downloaded update with ID 6188ce2c-1995-4670-89f0-c414cb600f0b into the local WSUS server. Successfully imported update 6188ce2c-1995-4670-89f0-c414cb600f0b into the local WSUS server. Removing downloaded update files in C:\Users\ADMINI~1\AppData\Local\Temp\2\Import-WsusUpdate since they have been copied to the WSUSContent folder...

Installation instructions on how to install Import-WsusUpdate are located here: https://www.ajtek.ca/free-tools/import-wsusupdate/

William Fourqurean 5 Reputation points

2026-08-03T21:05:54.5366667+00:00

Hi Rajendra,

Your issue sounds the same as what I experienced, along with a couple of other commenters on this thread. If the issue is the same, the problem is with the Windows Server running the WSUS server, not with the Windows 11 clients. The clients are sending the data, but the WSUS server is rejecting the data. As recommended by Marco, I uninstalled the July LCU from my WSUS server, and the problem was resolved.

My bigger concern is that I have not heard anyone from Microsoft weigh in on this issue, so I have no idea if someone is doing anything about it. There were several other problems occurring around the same time (some with WSUS, some with Windows 11), however they were not related and I have not seen any way to resolve this issue so far except to uninstall the July LCU. I guess we'll see in August whether the new LCU still has the issue, or whether it was fixed.

If anyone else has any other information related to this, I'd love to hear it.

Thanks.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Windows Server 2022 WSUS with WID - Windows 11 25H2 clients sync successfully but never report status

4 additional answers

Your answer