Summary
After you install updates and restart your Windows Server computer, the computer doesn't start. Instead, it enters a continuous restart loop. This issue might occur if disk corruption or bad clusters on the operating system (OS) disk prevent Windows Server from completing its startup processes. Use this article to identify the cause and fix the issue.
Symptoms
After you install updates and restart your computer, you experience the following symptoms:
- The computer doesn't start. However, it tries repeatedly to restart.
- The startup process reports particular error codes that indicate disk read errors.
- A disk health check (for example, by running
chkdsk) indicates that the disk has bad clusters or other corruption. - If you run standard disk repair commands, the commands don't restore the computer to a point at which it can start.
Cause
This issue occurs if the operating system (OS) disk is corrupted or has bad clusters. The following factors contribute to the issue:
- The OS disk doesn't have enough free space to allow the system files to function.
- Windows experienced disk read errors while it installed the updates.
- The system files that the computer requires for startup are corrupted.
- The disk has health issues that affect successful logging and normal startup operations.
If the OS disk is damaged or has bad sectors, Windows Server can't start. Although the system tries to restart, it enters a continuous loop of startup attempts.
Resolution
Important:
- If the affected computer is a Windows virtual machine (VM) that can't restart correctly or that you can't access by using RDP or SSH, make sure that you can use the Azure Serial Console to access the VM.
- Before you troubleshoot this issue, back up the operating system disk. For information about this process for VMs, see About Azure Virtual Machine restore.
To resolve the issue, follow these steps:
-
If the affected computer is a VM, make sure that the OS disk has enough free space by increasing the size of the OS disk. For more information, see Expand virtual hard disks attached to a Windows virtual machine.
-
On the affected computer, open an administrative Windows Command Prompt window.
-
To fix file system errors, locate bad sectors, and recover readable information, run the following command at the command prompt:
chkdsk /r /x -
After
chkdskfinishes, check the health of the disk. To check health, use any of the following methods:- The Disk Management tool
- The PowerShell
Get-PhysicalDiskcommand - The
chkdskcommand without flags (read-only check) - Azure portal diagnostics
-
Try to start the computer.
-
If the computer still doesn't start, try the following methods:
- If the affected computer is a VM, detach the OS disk, and then attach it to a test VM. Verify that the disk mounts and functions correctly.
- Contact your storage vendor (or your storage and system administration teams) for assistance in more in-depth troubleshooting. You might have to replace the disk hardware.
Data collection
The following types of data can help you troubleshoot this issue. Additionally, if you contact Microsoft Support, you can attach this data to your support request.
- Exported data from the System and Application event logs.
- Output from the
chkdskoperation, including the details of any repairs. - Disk health reports from monitoring or troubleshooting tools (for VMs, include reports from Azure monitoring tools).
- Screenshots or logs that show startup errors and error codes.
- A description of the steps that you already used to try to fix the issue.
References
- chkdsk
- Get-PhysicalDisk
- Attach a managed data disk to a Windows VM by using the Azure portal
- Troubleshoot Azure virtual machine boot errors
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
