title | description | services | author | manager | tags | ms.service | ms.collection | ms.workload | ms.tgt_pltfrm | ms.reviewer | ms.date | ms.author | ms.custom |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
VM startup is stuck on "Getting Windows ready. Don't turn off your computer" in Azure |
Introduce the steps to troubleshoot the issue in which VM startup is stuck on "Getting Windows ready. Don't turn off your computer." |
virtual-machines |
genlin |
dcscontentpm |
azure-resource-manager |
virtual-machines |
windows |
infrastructure-services |
vm-windows |
jarrettr, v-leedennis |
12/18/2023 |
genli |
sap:My VM is not booting |
This article describes the "Getting ready" and "Getting Windows ready" screens that you may encounter when you start a Windows virtual machine (VM) in Microsoft Azure. It provides steps to help you collect data for a support ticket.
[!INCLUDE Feedback]
A Windows VM doesn't start. When you use Boot diagnostics to get the screenshot of the VM, you may see that the VM displays the message "Getting ready" or "Getting Windows ready".
:::image type="content" source="media/troubleshoot-vm-boot-configure-update/getting-ready.png" alt-text="Screenshot of the Windows Server 2012 R2 V M, showing the message: Getting ready.":::
:::image type="content" source="media/troubleshoot-vm-boot-configure-update/getting-windows-ready.png" alt-text="Screenshot of the V M, showing the message: Getting Windows ready." border="false":::
Usually, this problem occurs when the server does the final restart after the configuration is changed. The configuration change might be initialized by Windows updates or by the changes on the roles or feature of the server. For Windows Update, if the updates were large, the operating system needs more time to reconfigure the changes.
If you have a recent backup of the VM, you can try restoring the VM from the backup to fix the startup problem.
If restoring the VM from backup isn't possible or doesn't resolve the problem, you have to collect a memory dump file so that the crash can be analyzed.
[!INCLUDE Collect OS Memory Dump File]
If you can't find the dump file, go to the next steps to enable the dump log and the serial console, and then trigger the memory dump process.
[!INCLUDE Registry important alert]
To enable the dump log and the serial console, run the following script:
[!INCLUDE Enable Serial Console and Memory Dump Collection]
Make sure that there's enough space on the disk to allocate as much memory as the RAM, which depends on the size that you're selecting for this VM. If there isn't enough space or this is a large size VM (G, GS or E series), you can change the location in which this file is created and refer that to any other data disk that's attached to the VM. To do this, you have to modify registry keys, as shown in the following code:
reg load HKLM\BROKENSYSTEM F:\windows\system32\config\SYSTEM
REG ADD "HKLM\BROKENSYSTEM\ControlSet001\Control\CrashControl" /v DumpFile /t REG_EXPAND_SZ /d "<DRIVE LETTER OF YOUR DATA DISK>:\MEMORY.DMP" /f
REG ADD "HKLM\BROKENSYSTEM\ControlSet002\Control\CrashControl" /v DumpFile /t REG_EXPAND_SZ /d "<DRIVE LETTER OF YOUR DATA DISK>:\MEMORY.DMP" /f
reg unload HKLM\BROKENSYSTEM
-
Detach the OS disk and then Re-attach the OS disk to the affected VM.
-
Start the VM and access the serial console.
-
Select Send Non-Maskable Interrupt(NMI) to trigger the memory dump.
:::image type="content" source="media/troubleshoot-vm-boot-configure-update/run-nmi.png" alt-text="Screenshot of the Send Non-Maskable Interrupt item.":::
-
Follow the instructions in Step 1: Collect the dump file directly again.
[!INCLUDE Azure Help Support]