Troubleshoot Windows Update errors that require in-place upgrades for Azure VMs

Trying to diagnose and resolve Windows Update or Windows OS upgrade issues for your Azure VM? Try one of the following tools:

• Azure VM Windows Update Error Detection Tool to diagnose specific Windows Update errors.
• Azure VM Windows Servicing Stack Reset Tool to reset the Windows servicing stack.
• Azure Virtual Machine (VM) Windows OS Upgrade Assessment Tool to validate the OS upgrade path and any known issues.

If you're experiencing performance problems with VMs, run these tools first before contacting support.

For Virtual Machines (VMs) that are running on Azure, certain Windows Update errors require an in-place upgrade of the OS to restore the servicing stack to a healthy condition in which updates can be installed. Other options, such as WinRE, are available to possibly mitigate this issue. However, such processes aren't possible unless the VM is connected to a nested virtualization environment, as described in Troubleshoot a faulty Azure VM by using nested virtualization in Azure. Although you do an in-place upgrade, you use the installation media of the current OS to reinstall the system. This article provides the steps to identify the specific upgrade errors that require this action.

Prerequisites

Make sure that you have administrative access to perform in-place upgrades.

How to identify the errors

To identify Windows Update errors, check the C:\Windows\Logs\CBS file path for CBS.log, CbsPersist_XXXXXXXXXXXXXX.log, or the CbsPersist_XXXXXXXXXXXXXX.cab file for one of the following error entries.

Example of error 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT

2025-02-27 08:58:35, Error                 CSI    0000000a@2025/2/27:11:58:35.891 (F) Attempting to mark store corrupt with category [l:21 ml:22]'CorruptComponentValue'[gle=0x80004005]
2025-02-27 08:58:35, Error                 CSI    0000000b (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #62038# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 0[gle=0xd015001a]
2025-02-27 08:58:35, Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(14098) #61875# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddComponents(Flags = 1, a = @0x29dd79f20d0, mp = @0x29dd79f28d0, disp = 0)[gle=0x80073712]
2025-02-27 08:58:35, Info                  CBS    Failed to add one or more deployment [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2025-02-27 08:58:35, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Wrapper-DDDA51604A99B1668F4E7D804F8F81E7558D0FEB4EA0DE087D6BF2DE607411F0~31bf3856ad364e35~amd64~~10.0.20348.3081 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2025-02-27 08:58:35, Info                  CBS    CommitPackagesState: Started persisting state of packages
2025-02-27 08:58:35, Info                  CBS    CommitPackagesState: Completed persisting state of packages
2025-02-27 08:58:35, Info                  CSI    0000000d@2025/2/27:11:58:35.891 CSI Transaction @0x29dd717d150 destroyed
2025-02-27 08:58:35, Info                  CBS    Perf: Resolve chain complete.
2025-02-27 08:58:35, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2025-02-27 08:58:35, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2025-02-27 08:58:35, Info                  CBS    WER: Generating failure report for package: Package_for_ServicingStack_3081~31bf3856ad364e35~amd64~~20348.3081.1.1, status: 0x80073712, failure source: Resolve, start state: Installed, target state: Installed, client id: WindowsUpdateAgent
2025-02-27 08:58:35, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Cause

The Azure VM is experiencing internal corruption in the Windows servicing stack. This stack is responsible for managing updates and system components. When it becomes damaged because of missing files, an invalid configuration, or corrupted metadata, Windows can no longer apply updates or service the OS correctly.

Trying to diagnose and resolve Windows Update or Windows OS upgrade issues for your Azure VM? Try one of the following tools:

• Azure VM Windows Update Error Detection Tool to diagnose specific Windows Update errors.
• Azure VM Windows Servicing Stack Reset Tool to reset the Windows servicing stack.
• Azure Virtual Machine (VM) Windows OS Upgrade Assessment Tool to validate the OS upgrade path and any known issues.

If you're experiencing performance problems with VMs, run these tools first before contacting support.

Resolution for Azure VMs

To resolve this issue, we recommend that you perform an in-place upgrade of Windows Server within the Azure VM. This process reinstalls the OS while preserving your data, apps, and settings.

Instructions for troubleshooting

1. Review the prerequisites:

   1. Make sure that you have administrative access to the VM.
   2. Verify that the VM is running on Azure.

2. Back up the VM. Use Azure Backup or take a snapshot to make sure that you can restore the VM, if it's necessary.

3. Review the following logs for known error codes:

   • CBS.log
   • CbsPersist_*.log
   • CbsPersist_*.cab

4. Follow the guidance in In-place upgrade for VMs running Windows Server in Azure.

5. Run the upgrade:

   1. At an elevated command prompt, change to drive with ISO.
   2. Enter setup.exe /auto upgrade /dynamicupdate disable.
   3. When you're prompted, select Keep personal files and apps.
   4. To complete the upgrade, follow the on-screen instructions.

6. Post-upgrade checks

   1. Verify system functionality.
   2. Reapply any custom configurations or policies as necessary.
   3. Re-enable any services, such as Azure Backup or monitoring agents, if they were paused.

References

1. In-place upgrade for VMs not running Windows Server in Azure
2. Troubleshoot a faulty Azure VM by using nested virtualization in Azure
3. In-place upgrade for VMs running Windows Server in Azure