Wsus and Windows 11 25H2 Asus clients sync successfully but never report status

Question

Wsus and Windows 11 25H2 Asus clients sync successfully but never report status

Marco 41

Hello,

I'm troubleshooting a WSUS reporting issue that started immediately after installing the July 2026 cumulative updates on a Windows Server 2022 WSUS server and Asus Client

Environment

WSUS on Windows Server 2022
IIS 10
HTTPS (8531)
Clients: Windows 11 build 26200.65792
WSUS version: 10.0.20348.1

Symptoms

Affected clients:

Continue to contact WSUS successfully
Appear in the WSUS console
Can scan for updates
Can download updates
Show an updated Last Contact
Remain stuck on "Not Yet Reported"
Last Status Report stopped updating on 16 July 2026Hello, I'm troubleshooting a WSUS reporting issue that started immediately after installing the July 2026 cumulative updates on a Windows Server 2022 WSUS server.
Environment
- WSUS on Windows Server 2022
- IIS 10
- HTTPS (8531)
- Clients: Windows 11 build 26200.65792
- WSUS version: 10.0.20348.1
Symptoms
Affected clients:
- Continue to contact WSUS successfully
- Appear in the WSUS console
- Can scan for updates
- Can download updates
- Show an updated Last Contact
- Remain stuck on "Not Yet Reported"
- Last Status Report stopped updating on 16 July 2026

Exemple:

Last Contact: 21/07/2026
Last Status Report: 16/07/2026

The issue started immediately after installing the July 2026 cumulative updates on the WSUS server.

Server log: C:\Program Files\Update Services\LogFiles\SoftwareDistribution.log

ReportingEvent.ValidateMiscData
ValidateMiscData: Rejecting MiscData entry with empty or whitespace-only value: t=
WebService.ValidateEventBatch
Event in batch failed to validate.
Exception: MiscData entry has empty or whitespace-only value: t=
ComputerBrand=[ASUSTeK COMPUTER INC.]
ComputerModel=[ASUS EXPERTBOOK B1502CVA_B1502CV]

OSVersion=[10.0.26200.65792.0.0.0.0.0]

miscData=[
t=
...
]

What has been checked

GPO configuration OK
WUServer/WUStatusServer OK
SSL certificate OK
IIS OK
Clients reach WSUS correctly
Resetting SusClientId does not help
Removing/recreating client objects in WSUS does not help
Other vendors (HP, Dell, etc.) continue reporting normally

João Vieira 0 Reputation points

2026-07-21T19:22:17.49+00:00

Try disable telemetry, adding this to the registry:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v "AllowTelemetry" /t REG_DWORD /d 0 /f

Followed by:
gpupdate
wuauclt /reportnow
Marco 41 Reputation points

2026-07-22T06:24:41.34+00:00

I try, but not work this method.

Workaround: remove the kb5099540 from wsus server
William Fourqurean 0 Reputation points

2026-08-03T21:17:47.38+00:00

Has anyone at Microsoft acknowledged this issue? If so, I have not seen it. This is not related to the metadata sync issues that were reported in KB5121986. This issue is directly related to a change introduced in the July LCU for Windows Server. I had to uninstall the July update for WS2022, KB5099540, just as Marco did. This immediately fixed the issue. Only certain clients are affected, as they seem to be reporting blank or null values for some data fields such as model identification.
Marco 41 Reputation points

2026-08-06T08:22:39.6133333+00:00

Any news?
shamu 15 Reputation points

2026-08-06T09:00:27.0133333+00:00

Same problem here, some clients don't report back to wsus console. Didn't find a solution except uninstalling the cum update from July on the wsus server. But I don't want do that.
William Fourqurean 0 Reputation points

2026-08-06T12:15:21.64+00:00

If anyone installs the expected August LCU next week and finds that it either fixes this problem or reintroduces it, please post a comment to let us know. I will probably update my WSUS server last, after everything else has been updated. Thanks for the comments.

Answer accepted by question author

Domic Vo 28,365 Independent Advisor

Hello,

The behavior you’re seeing is tied directly to the July 2026 cumulative update on Windows Server 2022. The WSUS server is still handling synchronization, downloads, and client contact correctly, but the reporting pipeline is breaking at the validation stage. The log entries you shared (ValidateMiscData: Rejecting MiscData entry with empty or whitespace-only value: t=) confirm that the WSUS reporting web service is rejecting status reports from affected ASUS clients because of malformed MiscData fields. This explains why “Last Contact” updates but “Last Status Report” remains frozen.

The fact that HP and Dell clients continue reporting normally points to a vendor‑specific issue in how ASUS systems populate the MiscData block during status reporting. The July update likely tightened validation logic in WSUS/IIS, so previously tolerated empty fields are now rejected. That matches the WebService.ValidateEventBatch failure you’re seeing.

At this point, the recommended path is to confirm whether Microsoft has acknowledged this regression in the July 2026 CU. If not, the workaround is to temporarily disable strict validation by rolling back the cumulative update or applying the latest servicing stack/hotfix once released. Another option is to monitor for a vendor BIOS/driver update, since MiscData often includes hardware descriptors that WSUS parses.

For immediate troubleshooting, you can capture the full client report payload with bitsadmin /list /verbose or by enabling WSUS client logging (%windir%\WindowsUpdate.log on Windows 11 via Get-WindowsUpdateLog). This will show exactly which MiscData field is malformed. If it’s consistently t=, then the ASUS WU client is sending an empty telemetry tag that WSUS now rejects.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.

Marco 41 Reputation points

2026-07-21T19:21:31.9266667+00:00

Thanks, i have remove the update and the Asus Client reporting to wsus.
William Fourqurean 0 Reputation points

2026-07-26T11:49:05.15+00:00

I am having this same issue. I uninstalled the July update from the WSUS server, and it resolved the issue. The affected client systems are reporting blanks for ComputerBrand and ComputerModel.

1 additional answer

Your answer

João Vieira 0 Reputation points

2026-07-21T19:22:17.49+00:00

Try disable telemetry, adding this to the registry:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v "AllowTelemetry" /t REG_DWORD /d 0 /f

Followed by:
gpupdate
wuauclt /reportnow
Marco 41 Reputation points

2026-07-22T06:24:41.34+00:00

I try, but not work this method.

Workaround: remove the kb5099540 from wsus server
William Fourqurean 0 Reputation points

2026-08-03T21:17:47.38+00:00

Has anyone at Microsoft acknowledged this issue? If so, I have not seen it. This is not related to the metadata sync issues that were reported in KB5121986. This issue is directly related to a change introduced in the July LCU for Windows Server. I had to uninstall the July update for WS2022, KB5099540, just as Marco did. This immediately fixed the issue. Only certain clients are affected, as they seem to be reporting blank or null values for some data fields such as model identification.
Marco 41 Reputation points

2026-08-06T08:22:39.6133333+00:00

Any news?
shamu 15 Reputation points

2026-08-06T09:00:27.0133333+00:00

Same problem here, some clients don't report back to wsus console. Didn't find a solution except uninstalling the cum update from July on the wsus server. But I don't want do that.
William Fourqurean 0 Reputation points

2026-08-06T12:15:21.64+00:00

If anyone installs the expected August LCU next week and finds that it either fixes this problem or reintroduces it, please post a comment to let us know. I will probably update my WSUS server last, after everything else has been updated. Thanks for the comments.
Marco 41 Reputation points

2026-07-21T19:21:31.9266667+00:00

Thanks, i have remove the update and the Asus Client reporting to wsus.
William Fourqurean 0 Reputation points

2026-07-26T11:49:05.15+00:00

I am having this same issue. I uninstalled the July update from the WSUS server, and it resolved the issue. The affected client systems are reporting blanks for ComputerBrand and ComputerModel.

Answer 1

Jackson, Brandon 0

This issue affects Server 2025 as well, removing KB5099536 (the July Cumulative) is also the fix.

0 comments