Skip to content

Commit 8981aea

Browse files
authored
Revise section titles in troubleshooting document
1 parent 1728233 commit 8981aea

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/azure/virtual-machines/windows/slow-vm-start-extensions-troubleshooting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ VM extensions are software components that run inside the VM to enable configura
2323

2424
If a VM has one or more extensions in a **Failed** state, delays can occur in other VM operations, such as **Start** or **Redeploy**. This issue occurs because the Azure platform tries to provision the failed extensions again before it completes the operation. Therefore, the VMs show a **Starting** status for an extended period.
2525

26-
## Workaround
26+
## More information
2727

2828
To mitigate this issue, follow these steps:
2929

@@ -44,7 +44,7 @@ To mitigate this issue, follow these steps:
4444

4545
1. Stop and then restart the VM to verify that the extension provisioning succeeds and the VM Start operation finishes faster. You can use the Azure portal, PowerShell, CLI, or REST API to do these operations.
4646

47-
## More information
47+
## References
4848

4949
For more guidance to troubleshoot the Azure VM Guest Agent and extension issues, see:
5050

0 commit comments

Comments
 (0)