You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/windows/windows-update-errors-requiring-in-place-upgrade.md
+48-51Lines changed: 48 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,51 +11,51 @@ ms.custom:
11
11
- pcy:WinComm Devices Deploy
12
12
---
13
13
14
-
# Troubleshoot Windows update error that require in-place upgrades for Azure Virtual Machines
14
+
# Troubleshoot Windows upgrade error that require in-place upgrades for Azure VMs
15
15
16
16
> [!IMPORTANT]
17
-
> This article covers the Windows Server upgrade process for Azure servers and virtual machines (VMs) only. To do an upgrade of Windows Server not running in an Azure VM, see [In-place upgrade for VMs not running Windows Server in Azure](/windows-server/get-started/perform-in-place-upgrade).
17
+
> This article covers the Windows Server upgrade process for Microsoft Azure servers and virtual machines (VMs) only. To upgrade an instance of Windows Server that isn't running on an Azure VM, see [In-place upgrade for VMs not running Windows Server in Azure](/windows-server/get-started/perform-in-place-upgrade).
18
18
> [!IMPORTANT]
19
-
> This article does not cover Windows Client scenarios at this time.
19
+
> This article doesn't cover Windows Client scenarios.
20
20
21
-
For Virtual Machines running in Azure, certain Windows Update errors will require an in-place upgrade of the OS to restore the servicing stack to a healthy condition so that updates can then be installed. While other options like WinRE are available to possibly mitigate this issue, this isn'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](/troubleshoot/azure/virtual-machines/windows/troubleshoot-vm-by-use-nested-virtualization). While the document instructs you to do an in-place upgrade, you will be using the media installation of the current OS and reinstalling the OS. This article provides steps to identify those specific errors requiring this action and resolve this issue.
21
+
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 on 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](/troubleshoot/azure/virtual-machines/windows/troubleshoot-vm-by-use-nested-virtualization). Although you'll be doing an in-place upgrade, you'll be using 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.
22
22
23
23
## Prerequisites
24
24
25
-
Ensure that you have administrative access to perform in-place upgrades.
25
+
Make sure that you have administrative access to perform in-place upgrades.
26
26
27
27
## How to identify the errors
28
28
29
-
To identify the errors, check under the `C:\Windows\Logs\CBS` file path for **CBS.log**, **CbsPersist_XXXXXXXXXXXXXX.log**, or the **CbsPersist_XXXXXXXXXXXXXX.cab** file for one of the following errors:
29
+
To identify upgrade 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.
| 8007371B | ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE | Servicing operation is incomplete or aborted. |
56
+
| 80242016 | WU_E_UH_POSTREBOOTUNEXPECTEDSTATE | The state of the update after its post-reboot operation was completed is unexpected. |
57
+
| 800F0911 | CBS_E_SOURCE_MODIFIED | The package sources have been modified or moved in a previous session and must be redownloaded.|
58
+
| 80071AB1 | ERROR_LOG_GROWTH_FAILED | An attempt to create space in the transactional resource manager's log failed. |
59
59
60
60
```output
61
61
Example of error 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT
@@ -75,42 +75,39 @@ Example of error 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT
75
75
2025-02-27 08:58:35, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
76
76
```
77
77
78
-
### Root Cause
78
+
### Cause
79
79
80
-
Your Azure virtual machine (VM) is experiencing internal corruption in the Windows servicing stack. This stack is responsible for managing updates and system components. When it becomes damaged due to missing files, invalid configurations, or corrupted metadata, Windows can no longer apply updates or service the OS properly.
80
+
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.
81
81
82
82
## Resolution for Azure VMs
83
83
84
-
To resolve this issue, Microsoft recommends performing an **in-place upgrade** of the Windows Server OS within the Azure VM. This process reinstalls the OS while preserving your data, apps, and settings.
84
+
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.
85
85
86
-
### Instructions for how to troubleshoot
86
+
### Instructions for troubleshooting
87
87
88
-
1.**Review the prerequisites**
89
-
1.Ensure you have **Administrative Access** to the VM.
90
-
1.Confirm the VM is running in Azure.
88
+
1. Review the prerequisites:
89
+
1.Make sure that you have administrative access to the VM.
90
+
1.Verify that the VM is running on Azure.
91
91
92
-
2.**Back up your VM**
93
-
1. Use **Azure Backup** or take a **snapshot** to ensure you can restore the VM if needed.
92
+
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.
94
93
95
-
3.**Check for Errors**
96
-
1. Review the following logs for known error codes:
97
-
1.`CBS.log`
98
-
1.`CbsPersist_*.log`
99
-
1.`CbsPersist_*.cab`
94
+
3. Review the following logs for known error codes:
95
+
-`CBS.log`
96
+
-`CbsPersist_*.log`
97
+
-`CbsPersist_*.cab`
100
98
101
-
4.**Perform an OS upgrade**
102
-
1. Follow the [In-place upgrade for VMs running Windows Server in Azure](/azure/virtual-machines/windows-in-place-upgrade) guidance.
99
+
4. Follow the guidance in [In-place upgrade for VMs running Windows Server in Azure](/azure/virtual-machines/windows-in-place-upgrade).
103
100
104
-
5.**Run the Upgrade**
105
-
1.From the elevated command prompt, change to **drive with ISO**.
106
-
1.Type setup.exe /auto upgrade /dynamicupdate disable without quotes
107
-
Choose **Keep personal files and apps** when prompted.
108
-
Follow the on-screen instructions to complete the upgrade.
101
+
5. Run the upgrade:
102
+
1.At an elevated command prompt, change to **drive with ISO**.
0 commit comments