Skip to content

Commit 4ccc59b

Browse files
v-tappelgatev-tappelgate
committed
Merge remote-tracking branch 'upstream/main' into AB#9354-Top-articles--Add-Summary-section
2 parents e765c9d + b6c0329 commit 4ccc59b

6 files changed

Lines changed: 261 additions & 20 deletions

File tree

‎support/azure/virtual-machines/linux/troubleshoot-linux-rhui-certificate-issues.md‎

Lines changed: 159 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ ms.custom: sap:VM Admin - Linux (Guest OS), linux-related-content
1414

1515
**Applies to:** :heavy_check_mark: Linux VMs
1616

17+
## Summary
18+
1719
This article discusses common issues in the Red Hat Update Infrastructure (RHUI) that are caused by expired or missing Transport Layer Security (TLS) or Secure Sockets Layer (SSL) certificates.
1820

1921
## Prerequisites
@@ -154,12 +156,12 @@ Use the following table to determine the correct RHUI package type based on your
154156
| Image type | Support model | Applicable version | RHUI package prefix | Using `releasever`? |
155157
|--------------------|---------------------------|----------------------------------------------|------------------------------------|-------------------------|
156158
| Generic RHEL | Non-EUS | 7.9, 8.10, 9.8, 10.0 | `rhui-azure-rhelX` | No |
157-
| Generic RHEL | EUS | 8.6, 8.8, 9.2, 9.4, 9.6 | `rhui-azure-rhelX-eus` | Yes |
158-
| RHEL-SAP-APPS | EUS | 8.6, 8.8, 9.2, 9.4, 9.6 | `rhui-azure-rhelX-sapapps` | Yes |
159+
| Generic RHEL | EUS | 9.4, 9.6, 10.0 | `rhui-azure-rhelX-eus` | Yes |
160+
| RHEL-SAP-APPS | EUS | 8.6, 8.8, 9.2, 9.4, 9.6, 10.0 | `rhui-azure-rhelX-sapapps` | Yes |
159161
| RHEL-SAP-APPS | Base (no EUS available) | 7.9, 8.10 | `rhui-azure-rhelX-base-sap-apps` | No |
160-
| RHEL-SAP-HA | E4S | 8.6, 8.8, 9.2, 9.4, 9.6 | `rhui-azure-rhelX-sap-ha` | Yes |
162+
| RHEL-SAP-HA | E4S | 8.6, 8.8, 9.2, 9.4, 9.6, 10.0 | `rhui-azure-rhelX-sap-ha` | Yes |
161163
| RHEL-SAP-HA | Base (no E4S available) | 7.9, 8.10 | `rhui-azure-rhelX-base-sap-ha` | No |
162-
| RHEL-HA | EUS | 8.6, 8.8, 9.4, 9.6 | `rhui-azure-rhelX-ha` | Yes |
164+
| RHEL-HA | EUS | 8.6, 8.8, 9.4, 9.6, 10.0 | `rhui-azure-rhelX-ha` | Yes |
163165
| RHEL-HA | Base (no EUS available) | 7.9, 8.10 | `rhui-azure-rhelX-base-ha` | No |
164166

165167
> [!NOTE]
@@ -177,6 +179,7 @@ Use the following index to navigate directly to the corresponding section:
177179
- [RHEL 7 SAP RHUI package installation](#rhel79sap)
178180
- [RHEL 8 SAP/E4S/HA RHUI package installation](#rhel8sap)
179181
- [RHEL 9 SAP/E4S/HA RHUI package installation](#rhel9sap)
182+
- [RHEL 10 SAP/E4S/HA RHUI package installation](#rhel10sap)
180183

181184

182185
##### <a id="eus"></a> EUS RHUI package installation
@@ -252,6 +255,41 @@ Select the tab of an EUS image type to see the corresponding instructions.
252255
sudo rhel9-eus.config
253256
```
254257
258+
###### [RHEL 10.x - EUS](#tab/rhel10-eus)
259+
260+
261+
262+
1. Create a config file by using this command:
263+
264+
```bash
265+
sudo tee rhel10-eus.config > /dev/null <<< $'[rhui-microsoft-azure-rhel10-eus]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 10 (rhel10-eus)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel10-eus\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft-2025.asc\nsslverify=1'
266+
267+
```
268+
269+
2. Install the `rhui-azure-rhel10-eus` package by running.
270+
271+
```bash
272+
sudo dnf --config rhel10-eus.config install rhui-azure-rhel10-eus
273+
```
274+
275+
3. Lock the `releasever` variable:
276+
277+
```bash
278+
sudo echo $(. /etc/os-release && echo $VERSION_ID) > /etc/dnf/vars/releasever
279+
```
280+
281+
4. Verify that the corresponding repositories are available and show no errors. To do this, run the `dnf repolist` command:
282+
283+
```bash
284+
sudo dnf repolist all
285+
```
286+
287+
5. Remove the temp file created on step 1.
288+
289+
```bash
290+
sudo rhel10-eus.config
291+
```
292+
255293
---
256294
257295
@@ -818,6 +856,123 @@ The following steps apply if the OS version is *earlier than the latest version
818856
---
819857
820858
859+
> [!NOTE]
860+
> If you're using a proxy in */etc/yum.conf* or */etc/dnf.conf*, the `yum --config rhelX-XX-XX.config` command won't work because it doesn't include your proxy settings. In this case, move the temp file `rhelX-XX-XX.config` directly in `/etc/yum.repos.d/` as `.repo`
861+
>
862+
> ```bash
863+
> sudo mv rhelX-XX-XX.config /etc/yum.repos.d/ms.repo
864+
> sudo yum install rhui-azure-rhel-X-X-X
865+
> sudo rm rhelX-XX-XX.config
866+
> ```
867+
> Replace `rhelX-XX-XX.config` and `rhui-azure-rhel-X-X-X` with the actual values, as appropriate.
868+
869+
##### <a id="rhel10sap"></a> RHEL 10 SAP/E4S/HA RHUI package installation
870+
871+
Select the tab of an SAP image type to see the corresponding instructions.
872+
873+
###### [RHEL 10.x - RHEL-SAP-APPS](#tab/rhel10-rhel-sap-apps)
874+
875+
The following steps apply if the OS version is *earlier than the latest version that's available* that's supported by SAP for `RHEL 10.0`, and if the VM was created by using the `RHEL-SAP-APPS` offer image.
876+
877+
1. Create a config file by using this command:
878+
879+
```bash
880+
sudo tee rhel10-sapapps.config > /dev/null <<< $'[rhui-microsoft-azure-rhel10-sapapps]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 10 (rhel10-sapapps)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel10-sapapps\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft-2025.asc\nsslverify=1'
881+
```
882+
883+
2. Install the `rhui-azure-rhel10-sapapps` package by running the `dnf install` command:
884+
885+
```bash
886+
sudo dnf --config rhel10-sapapps.config install rhui-azure-rhel10-sapapps
887+
```
888+
889+
3. Lock the `releasever` level. Currently, the version must be 10.0.
890+
891+
```bash
892+
sudo sh -c 'echo 10.0 > /etc/dnf/vars/releasever'
893+
```
894+
895+
4. Verify that the corresponding repositories are available and show no errors. To do this, run the `yum repolist` command:
896+
897+
```bash
898+
sudo dnf repolist all
899+
```
900+
901+
5. Remove the temp file created on step 1.
902+
903+
```bash
904+
sudo rm rhel10-sapapps.config
905+
```
906+
907+
###### [RHEL 10.x - RHEL-SAP-HA (E4S)](#tab/rhel10-rhel-sap-ha-e4s)
908+
909+
The following steps apply if the OS version is *earlier than the latest version available* that's supported by SAP for `RHEL 10.0`, and if the VM was created by using the `RHEL-SAP-HA` offer image.
910+
911+
1. Create a config file by using this command:
912+
913+
```bash
914+
sudo tee rhel10-sap-ha.config > /dev/null <<< $'[rhui-microsoft-azure-rhel10-sap-ha]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 10 (rhel10-sap-ha)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel10-sap-ha\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft-2025.asc\nsslverify=1'
915+
```
916+
917+
2. Install the `rhui-azure-rhel10-sap-ha` package by running the `dnf install` command:
918+
919+
```bash
920+
sudo dnf --config rhel10-sap-ha.config install rhui-azure-rhel10-sap-ha
921+
```
922+
923+
3. Lock the `releasever` level. Currently, the version must be 10.0.
924+
925+
```bash
926+
sudo sh -c 'echo 10.0 > /etc/dnf/vars/releasever'
927+
```
928+
929+
4. Verify that the corresponding repositories are available and show no errors. To do this, run the `dnf repolist` command:
930+
931+
```bash
932+
sudo dnf repolist all
933+
```
934+
935+
5. Remove the temp file created on step 1.
936+
937+
```bash
938+
sudo rm rhel10-sap-ha.config
939+
```
940+
941+
###### [RHEL 10.x - RHEL-HA](#tab/rhel10-rhel-ha-eus)
942+
943+
1. Create a config file by using this command:
944+
945+
```bash
946+
sudo tee rhel10-ha.config > /dev/null <<< $'[rhui-microsoft-azure-rhel10-ha]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 10 (rhel10-ha)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel10-ha\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft-2025.asc\nsslverify=1'
947+
```
948+
949+
2. Install the `rhui-azure-rhel10-ha` package by running the [dnf](https://dnf.readthedocs.io/en/latest/command_ref.html) installation command:
950+
951+
```bash
952+
sudo dnf --config rhel10-ha.config install rhui-azure-rhel10-ha
953+
```
954+
955+
3. Lock the `releasever` level. Currently, the version must be 10.0.
956+
957+
```bash
958+
sudo sh -c 'echo 10.0 > /etc/dnf/vars/releasever'
959+
```
960+
961+
4. Verify that the corresponding repositories are available and show no errors. To do this, run the `dnf repolist` command:
962+
963+
```bash
964+
sudo dnf repolist
965+
```
966+
967+
5. Remove the temp file created on step 1.
968+
969+
```bash
970+
sudo rm rhel10-ha.config
971+
```
972+
973+
---
974+
975+
821976
> [!NOTE]
822977
> If you're using a proxy in */etc/yum.conf* or */etc/dnf.conf*, the `yum --config rhelX-XX-XX.config` command won't work because it doesn't include your proxy settings. In this case, move the temp file `rhelX-XX-XX.config` directly in `/etc/yum.repos.d/` as `.repo`
823978
>
@@ -929,5 +1084,3 @@ Revert the cryptography to the `DEFAULT` system policy setting by following thes
9291084
For more information about cryptographic policy, see [Strong crypto defaults in RHEL 8 and deprecation of weak crypto algorithms](https://access.redhat.com/articles/3642912).
9301085
9311086
[!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]
932-
933-

‎support/azure/virtual-machines/linux/yum-dnf-common-issues.md‎

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ ms.date: 07/10/2025
1818

1919
**Applies to:** :heavy_check_mark: Linux VMs
2020

21+
## Summary
22+
2123
This article discusses and resolves common issues that you might experience when you use `yum` and `dnf` package management tools to install or update applications on Microsoft Azure virtual machines (VMs).
2224

2325
> [!CAUTION]
@@ -410,34 +412,36 @@ If the error typically occurs because an incorrect value is used for */etc/yum/v
410412

411413
2. Determine the current value for the release version by running the following `cat` command.
412414

413-
| RHEL version | Command |
414-
|--------------|-------------------------------------|
415-
| RHEL 7 | `sudo cat /etc/yum/vars/releasever` |
416-
| RHEL 8 and 9 | `sudo cat /etc/dnf/vars/releasever` |
415+
| RHEL version | Command |
416+
|----------------|-------------------------------------|
417+
| RHEL 7 | `sudo cat /etc/yum/vars/releasever` |
418+
| RHEL 8, and 10 | `sudo cat /etc/dnf/vars/releasever` |
417419

418420
3. Modify and use the correct value for the release version:
419421

420422
- If your system is using EUS repositories, make sure that the appropriate version lock is applied. In the following example, the version lock is added for RHEL 9.2 because `RHUI EUS` repositories are used:
421423

422424
```bash
423425
sudo sh -c 'echo 9.2 > /etc/dnf/vars/releasever'
426+
sudo sh -c 'echo 9.6 > /etc/dnf/vars/releasever'
424427
```
425428

426429
> [!NOTE]
427-
> Support for RHEL7 EUS ended on August 30, 2021. We recommend that you no longer use EUS repositories in RHEL7.
430+
> Support for RHEL 7 EUS ended on August 30, 2021. We recommend that you no longer use EUS repositories in RHEL 7.
428431
>
429-
> RHEL 8._x_ versions for EUS are available. These versions include RHEL 8.8, 8.6, 8.4, 8.2, and 8.1.
432+
> Support for RHEL 8 EUS ended on May 31, 2025. RHEL 8.10 is the last planned minor release of RHEL 8 and is still supported, but isn't an EUS release. We recommend that you no longer use EUS repositories in RHEL 8 and instead switch to the non-EUS repos.
430433
>
431-
> RHEL 9._x_ versions for EUS are available. Currently, these versions include RHEL 9.2 and 9.0.
434+
> RHEL 9._x_ versions for EUS are available. Currently, these versions include RHEL 9.6 and 9.4.
432435
>
436+
> RHEL 10._x_ versions for EUS are available. Currently, these versions include only RHEL 10.0.
433437
> For more information about version availability, see [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata).
434438

435439
- If your system is using non-EUS repositories, make sure that you remove the version lock for the */etc/yum/vars/releasever* or */etc/dnf/vars/releasever* file by running the following command.
436440

437-
| RHEL version | Command |
438-
|--------------|-------------------------------------------|
439-
| RHEL 7 | `sudo echo "" > /etc/yum/vars/releasever` |
440-
| RHEL 8 and 9 | `sudo echo "" > /etc/dnf/vars/releasever` |
441+
| RHEL version | Command |
442+
|-----------------|-------------------------------------------|
443+
| RHEL 7 | `sudo echo "" > /etc/yum/vars/releasever` |
444+
| RHEL 8,9 and 10 | `sudo echo "" > /etc/dnf/vars/releasever` |
441445

442446
##### [Oracle Linux](#tab/ol)
443447

‎support/azure/virtual-machines/windows/toc.yml‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -454,15 +454,15 @@ items:
454454
items:
455455
- name: Understanding VM lifecycle and states
456456
href: /azure/virtual-machines/states-billing?context=/troubleshoot/azure/virtual-machines/windows/context/context
457-
- name: Troubleshoot Start/Stop VMs during off-hours (Azure Automation)
457+
- name: Azure Automation VM Start/Stop Issues
458458
href: /azure/automation/troubleshoot/start-stop-vm?context=/troubleshoot/azure/virtual-machines/windows/context/context
459459
- name: Start VM with last known good configuration
460460
href: start-vm-last-known-good.md
461461
- name: Restarting or resizing a VM
462462
href: restart-resize-error-troubleshooting.md
463463
- name: Restarting, shutting down, or stopping services
464464
href: boot-error-troubleshoot-windows.md
465-
- name: Slow VM start caused by extensions troubleshooting
465+
- name: Slow VM start caused by extensions
466466
href: slow-vm-start-extensions-troubleshooting.md
467467

468468
- name: VM restarts or stops unexpectedly
@@ -535,6 +535,8 @@ items:
535535
href: support-agent-extensions.md
536536
- name: Troubleshoot extension issues
537537
href: /azure/virtual-machines/extensions/troubleshoot?context=/troubleshoot/azure/virtual-machines/windows/context/context
538+
- name: Slow VM start caused by extensions
539+
href: slow-vm-start-extensions-troubleshooting.md
538540

539541
- name: Cannot activate Windows
540542
items:

‎support/windows-365/provisioning-errors.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Troubleshoot provisioning errors
33
description: Troubleshoot provisioning errors in Windows 365.
44
manager: dcscontentpm
5-
ms.date: 01/7/2026
5+
ms.date: 01/23/2026
66
ms.topic: troubleshooting
77
ms.reviewer: mattsha, erikje, mmoyaaceves
88
ms.custom:
@@ -173,6 +173,8 @@ If you receive this error, some factors to consider are:
173173

174174
If you encounter other provisioning errors not covered previously, make sure all the [required endpoints](/windows-365/enterprise/requirements-network?tabs=enterprise%2Cent#allow-network-connectivity) are allowed on the virtual network used for your ANC and any gateway device.
175175

176+
For more information about provisioning statuses, see [Device management overview for Cloud PCs](/windows-365/enterprise/device-management-overview).
177+
176178
## Next steps
177179

178180
[Troubleshooting Windows 365 issues](/windows-365/enterprise/troubleshooting).

‎support/windows-server/backup-and-storage/stop-error-from-drive-repair-restart.md‎

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
title: Stop error when Windows tries to repair a drive while restarting
3+
description: This article describes an issue in which a Windows device displays a drive repair prompt when it restarts, and the system experiences a stop error.
4+
ms.date: 01/22/2026
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, simonw, v-appelgatet
9+
ai.usage: ai-assisted
10+
ms.custom:
11+
- sap:backup, recovery, disk, and storage\data corruption and disk errors
12+
- pcy:WinComm Storage High Avail
13+
appliesto:
14+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
15+
---
16+
17+
# Stop error when Windows tries to repair a drive while restarting
18+
19+
## Summary
20+
21+
When you restart a Windows device, you see a prompt to repair a drive. If you choose to repair the drive, the system displays a stop error (blue screen) that indicates that disk initialization failed. If you cancel the repair, Windows starts, but the device experiences drive errors.
22+
23+
This article describes the symptoms that characterize this issue, explains the cause, and provides step-by-step guidance to fix the issue.
24+
25+
## Symptoms
26+
27+
When Windows restarts, you see a pop-up message that prompts you to repair a drive. You perform one of the following actions:
28+
29+
- You select **Repair**. The device restarts, and then starts repairing the disk. The device experiences a stop error, and reports that the disk initialization failed.
30+
- You select **Cancel**. The device starts. Then, if you run the Check Disk tool (`chkdsk`), the tool reports errors and unmounts the drive.
31+
32+
After either action, the system might become stuck in a cycle of repair attempts followed by blue screen errors.
33+
34+
## Cause
35+
36+
Typically, this issue indicates file system corruption or disk integrity problems. The corruption prevents the disk repair process from finishing successfully. In turn, the failed repair process causes system instability and repeated blue screen errors.
37+
38+
## Resolution
39+
40+
To resolve this issue, follow these steps:
41+
42+
1. Back up all data on the affected drive.
43+
1. To check the health of the affected drive, open a Windows Command Prompt window on the device, and then run the following command:
44+
45+
```console
46+
chkdsk <X>: /scan
47+
```
48+
49+
> [!NOTE]
50+
>
51+
> - In this command. \<X> represents the letter of the affected drive.
52+
> - If `chkdsk` doesn't find any issues but the symptoms persist, contact Microsoft Support for further assistance.
53+
54+
1. To fix the drive errors, run the following command at the command prompt:
55+
56+
```console
57+
chkdsk <X>: /F
58+
```
59+
60+
1. If `chkdsk` can't repair the drive because the drive is mounted, unmount the drive, and then attach it to another Windows device. Run `chkdsk` at a command prompt on the new device.
61+
1. If the issue persists after the repairs finish, see [Data corruption and disk errors troubleshooting guidance](troubleshoot-data-corruption-and-disk-errors.md), or contact Microsoft Support.
62+
63+
## Data collection
64+
65+
Before you contact Microsoft Support, you can gather the following information about your issue. Include this information in your support request.
66+
67+
- Windows version and edition (for example, Windows 11 Pro, version 23H2)
68+
- Device model and hardware specifications
69+
- Exact error message that you receive during the blue screen
70+
- Steps that you took before the issue occurred
71+
- Output from running chkdsk on the affected drive
72+
- Any recent changes to hardware or software, including updates and installations
73+
74+
## References
75+
76+
- [Check Disk (chkdsk) - Microsoft Docs](/windows-server/administration/windows-commands/chkdsk)

0 commit comments

Comments
 (0)