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
When you try to install any patch using the standalone installer (.msu) or Windows Update and the update was not installed:
29
35
30
36
## Root cause
@@ -49,11 +55,11 @@ In order to see exactly what is happening, we need to open and check the CBS.log
49
55
> This issue may vary depending on each case but the baseline of the issue is the same.
50
56
51
57
> [!NOTE]
52
-
> To get the CBS.log or logs, you can use the TSSv2 to collect all the logs you need for such cases. The information about how to do it is in https://aka.ms/dndlogs.
58
+
> To get the CBS.log or logs, you can use the TSSv2 to collect all the logs you need for such cases. For more information see, [CBS logs](https://aka.ms/dndlogs).
53
59
54
60
## Mitigation
55
61
56
-
### Backup
62
+
Backup
57
63
Before proceeding with the mitigation of this document, follow the process to backup the OS disk: Back up OS Disk
58
64
59
65
## Online Mitigation
@@ -71,7 +77,7 @@ We need to move to the plan, to either add or remove the culprit KB manually fro
71
77
72
78
1. Reproduce the issue by trying to install the patch or the feature with issues. We need to do this step to ensure that the latest data is logged into the latest CBS.log.
73
79
1. Identify the package that the CBS process is complaining about, ensure you verify the KB as well.
74
-
1. In any web browser, go the Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Home.aspx
80
+
1. In any web browser, go to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx).
75
81
1. Search for the identified KB number.
76
82
1. Select and download the proper KB depending on the OS version and architecture
77
83
1. When you download the KB, paste it into a temp folder in the C drive C:\temp
**Awareness: If the mitigations given did not fix the issue, this specific Windows Update (WU) error code is identified that may require an In-Place Upgrade (IPU) to recover the virtual machine (VM). For Windows on Azure (WOA) scenarios—especially in alignment with efforts to reduce days to closure—these WU errors are reviewed and approved as eligible for IPU as a simplified recovery path. Customers encountering these specific issues can be confidently offered the in-place upgrade option as an effective resolution."**
141
+
> [!NOTE]
142
+
> Awareness: If the mitigations given did not fix the issue, this specific Windows Update (WU) error code is identified that may require an In-Place Upgrade (IPU) to recover the virtual machine (VM). For Windows on Azure (WOA) scenarios—especially in alignment with efforts to reduce days to closure—these WU errors are reviewed and approved as eligible for IPU as a simplified recovery path. Customers encountering these specific issues can be confidently offered the in-place upgrade option as an effective resolution.
0 commit comments