An Azure service to centrally manages updates and compliance at scale.
0x800F0982 during Azure-managed hotpatch deployment indicates the VM is likely not on a valid servicing baseline for the hotpatch being applied, or the servicing stack has underlying component-store issues that are blocking delta patch applicability.
A supported investigation and remediation path is:
- Verify hotpatch eligibility and orchestration mode
Confirm the VM is still running Windows Server 2022 Datacenter: Azure Edition or later, uses a supported Azure Marketplace image lineage, and has patch orchestration set to AutomaticByPlatform. Check on the VM:
Check orchestration mode in Azure:(Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").ProductName (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").DisplayVersion
In the portal, verify Virtual machines > VM > Updates > Update settings shows Azure-orchestrated.az vm show --resource-group <resource-group> --name <vm-name> --query "osProfile.windowsConfiguration.patchSettings" - Check whether the baseline cumulative update is stale
Hotpatches are delta patches layered on the latest cumulative baseline. If the baseline was missed, later hotpatches can fail until the latest cumulative update is installed, and that install requires a reboot. Check recent cumulative update history:
If the last cumulative update is older than 3 months, install the latest cumulative update from Azure Update Manager:$session = New-Object -ComObject Microsoft.Update.Session $searcher = $session.CreateUpdateSearcher() $history = $searcher.QueryHistory(0, 20) $history | Where-Object { $_.Title -match "Cumulative" } | Select-Object Date, Title, ResultCode -First 5- Go to the VM > Updates > One-time update
- Select Include all update classifications
- Deploy the update
- Allow the reboot
- Check the hotpatch extension health
In the portal, go to Virtual machines > VM > Extensions + applications and verify
Microsoft.CPlat.Core.WindowsHotpatchis healthy. If it is failed:- Select the extension
- Uninstall it
- Wait for uninstall to complete
- Trigger a new update assessment from Updates so the extension is reinstalled automatically
- Check for Windows Update policy conflicts
WSUS or other Windows Update Group Policy settings can interfere with Azure Update Manager hotpatch delivery. Run:
Review:gpresult /h C:\Temp\gpresult.html- Computer Configuration > Administrative Templates > Windows Components > Windows Update
-
Configure Automatic Updates -
Specify intranet Microsoft update service location -
Do not connect to any Windows Update Internet locations
- Investigate component-store evidence even if ScanHealth and SFC pass
A passing
DISM /ScanHealthandSFC /VerifyOnlydoes not rule out servicing issues affecting a specific hotpatch delta. ReviewCBS.logfor patterns that indicate whether repair is possible or whether the image is in a more severe state. Relevant log patterns include:-
STATUS_SXS_COMPONENT_STORE_CORRUPT -
HRESULT_FROM_WIN32(14098) -
CBS_E_SOURCE_MISSING(0x800F081F) -
Attempting to mark store corrupt -
CBS_E_IMAGE_UNSERVICEABLE(0x800F0830) -
PSFX_E_MATCHING_BINARY_MISSING
-
C:\Windows\Logs\CBS\CBS.log -
C:\Windows\Logs\CBS\CbsPersist_*.log -
C:\Windows\Logs\DISM\dism.log
-
- Collect logs before escalation if the VM still fails while a comparable VM succeeds
Since
Server1has reached a later build with the same orchestration settings, the failing VM likely has a VM-specific servicing or baseline problem rather than a general Azure Update Manager configuration issue. Collect before contacting Azure support:-
WindowsUpdate.loggenerated byGet-WindowsUpdateLog -
C:\Windows\Logs\CBS\CBS.log -
C:\Packages\Plugins\Microsoft.CPlat.Core.WindowsHotpatch\<version>\ -
C:\Windows\Logs\DISM\dism.log
-
- Expected supported remediation The supported remediation is to bring the VM onto the latest cumulative baseline through Azure Update Manager, allow the required reboot, confirm the hotpatch extension is healthy, and remove any WSUS-conflicting policy. If hotpatch still fails after that, use the collected logs for Azure support investigation.
If CBS.log shows severe servicing patterns such as CBS_E_IMAGE_UNSERVICEABLE or repeated delta-matching failures, the issue is no longer a normal hotpatch eligibility problem and requires deeper servicing investigation using the collected logs.