VMM 2025 and Windows Server 2025 24H2 Baseline Compliance Issue

I think I've found a reproducible VMM 2025 / Windows Server 2025 (24H2) compliance issue and I'm curious if anyone else is seeing it.

If I remediate a Windows Server 2025 (24H2) host through SCVMM 2025 and choose not to reboot after remediation, the update is actually staged by Windows servicing, but VMM doesn't recognize the machine as being in the expected Pending Machine Reboot state.

Instead, compliance stays non-compliant. Reboot the server manually, run another compliance scan, and suddenly everything is compliant.

Server 2022 behaves differently, I reproduced the same workflow on Windows Server 2022 with the same SCVMM 2025: Remediate (without reboot) --> Object becomes compliant, Operational status changes to "Peding Machine Reboot" --> (later) Reboot --> Officially Compliant.

On Server 2025: Remediate (without reboot) --> Object DOES NOT become compliant (the Job task is successful tho), Operational status DOES NOT change to anything --> (later) Manual Reboot --> Secondary compliance Scan --> Officially Compliant.

I enabled VMM debugging and followed what VMM is doing.

VMM uses WSMan against the managed host and queries the VMM WMI provider under root/scvmm.

It queries the SoftwareUpdate resources to determine whether the updates are installed. During the pre-reboot state, the provider reports the update as still required/not installed rather than giving VMM a clean "installed, pending reboot" state.

That makes sense from the servicing-stack perspective: the update isn't fully active until reboot.

But VMM apparently doesn't translate that intermediate state into the expected Pending Machine Reboot compliance state.

Instead, VMM ends up with something like:

OverallComplianceState = Unknown

PendingReboot = False

The VMM compliance task itself completes successfully, which makes this even more confusing.

DISM confirms the update is actually being staged. I checked the servicing state with DISM before rebooting. The new LCU/SSU is being deployed and the previous components are pending uninstall while the new ones are pending install.

So this doesn't look like: "Windows Update failed and VMM correctly says the update is missing."

It's more like: "Windows has staged the update and knows a reboot is required, but VMM doesn't recognize the intermediate state correctly."

After reboot, the servicing transaction completes and VMM sees the update as installed.

On Server 2022, VMM can represent that intermediate state properly. On Server 2025, VMM can continue to consider the machine non-compliant/unknown until the reboot actually happens. So dashboards can report the host incorrectly during the maintenance window.

Has anyone else seen this?

I am specifically interested in people running:

-> Microsoft Server OS 24H2 with SCVMM 2025

-> WSUS-backed VMM update management

-> Remediation with reboot suppressed

++ I am running the latest Update Rollup 1, 10.25.1439.0, KB5068308, issue still present.

I'm particularly interested in whether anyone has found a VMM hotfix/workaround that makes Server 2025 report Pending Machine Reboot correctly without actually rebooting the host.