Hello,
I am experiencing a WSUS reporting issue on Windows Server 2022 Standard.
Environment:
- Windows Server 2022 Standard
OS build: 20348.5386
WSUS role installed locally
WSUS clients include recent Windows 11 versions
Issue:
Multiple clients appear to have problems submitting their status reports to WSUS.
The WSUS server log (SoftwareDistribution.log) contains repeated exceptions during reporting event validation:
ReportingEvent.ValidateMiscData Exception occurred while parsing MiscData for event.
System.ArgumentException:
Error occurred while parsing MiscData for event.
Inner exception:
System.FormatException:
Guid should contain 32 digits with 4 dashes
(xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
Microsoft.UpdateServices.Internal.Reporting.WebService.ValidateEventBatch
WebService.ValidateEventBatch Event in batch failed to validate.
The affected reporting events have the following characteristics:
AppName: MoUpdateOrchestrator
SourceId: 101
NamespaceId: 1
EventId: 156
The exception appears to occur while parsing the g= element in MiscData. This element contains multiple GUID values separated by the pipe character (|).
Example of the format found in the log (illustrative values):
g=85961D5C-6C88-47E6-B6CE-07C1D8DD0CB7|8D9610D6-57F8-4913-ACBE-96E4DF67AF30
The errors are repeated across multiple clients, so this does not appear to be an isolated workstation issue.
Impact:
Some clients do not update their WSUS reporting status, and their last reported status timestamps remain outdated despite attempts to initiate a new scan and reporting cycle.
Troubleshooting already performed:
Verified that clients are configured to use the correct WSUS server URL.
Triggered Windows Update detection and reporting on affected clients.
Confirmed that clients can communicate with the WSUS server.
Verified that the WSUS content endpoint is accessible over HTTP.
Reviewed the WSUS server logs and identified the repeated GUID parsing exceptions.
Questions:
Is this a known WSUS Reporting Web Service issue on Windows Server 2022?
Can newer Windows 11 clients send reporting data in a format that the current WSUS reporting parser cannot process?
Is there an official fix, hotfix, or supported workaround?
Is it possible to update or repair the WSUS reporting components independently of a full operating system update?
What is the recommended way to restore normal client reporting without modifying the SUSDB database or manually replacing WSUS DLL files?
I would appreciate any information about a confirmed fix or a Microsoft-supported workaround.
Thank you.Hello,
I am experiencing a WSUS reporting issue on Windows Server 2022 Standard.
Environment:
Windows Server 2022 Standard
OS build: 20348.5386
WSUS role installed locally
WSUS clients include recent Windows 11 versions
Issue:
Multiple clients appear to have problems submitting their status reports to WSUS.
The WSUS server log (SoftwareDistribution.log) contains repeated exceptions during reporting event validation:
ReportingEvent.ValidateMiscData Exception occurred while parsing MiscData for event.
System.ArgumentException:
Error occurred while parsing MiscData for event.
Inner exception:
System.FormatException:
Guid should contain 32 digits with 4 dashes
(xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
Microsoft.UpdateServices.Internal.Reporting.WebService.ValidateEventBatch
WebService.ValidateEventBatch Event in batch failed to validate.
The affected reporting events have the following characteristics:
AppName: MoUpdateOrchestrator
SourceId: 101
NamespaceId: 1
EventId: 156
The exception appears to occur while parsing the g= element in MiscData. This element contains multiple GUID values separated by the pipe character (|).
Example of the format found in the log (illustrative values):
g=85961D5C-6C88-47E6-B6CE-07C1D8DD0CB7|8D9610D6-57F8-4913-ACBE-96E4DF67AF30
The errors are repeated across multiple clients, so this does not appear to be an isolated workstation issue.
Impact:
Some clients do not update their WSUS reporting status, and their last reported status timestamps remain outdated despite attempts to initiate a new scan and reporting cycle.
Troubleshooting already performed:
Verified that clients are configured to use the correct WSUS server URL.
Triggered Windows Update detection and reporting on affected clients.
Confirmed that clients can communicate with the WSUS server.
Verified that the WSUS content endpoint is accessible over HTTP.
Reviewed the WSUS server logs and identified the repeated GUID parsing exceptions.
Questions:
Is this a known WSUS Reporting Web Service issue on Windows Server 2022?
Can newer Windows 11 clients send reporting data in a format that the current WSUS reporting parser cannot process?
Is there an official fix, hotfix, or supported workaround?
Is it possible to update or repair the WSUS reporting components independently of a full operating system update?
What is the recommended way to restore normal client reporting without modifying the SUSDB database or manually replacing WSUS DLL files?
I would appreciate any information about a confirmed fix or a Microsoft-supported workaround.
Thank you.