Azure VM Boot Diagnostic Won't Load – Fix Guide

Quick Fix (30 seconds) – Check the VM Status

Before you do anything complicated, look at the VM's status in the Azure portal. Go to your VM, click Overview on the left menu. Look under Status – it should say Running. If it says Stopped or Deallocated, boot diagnostics won't work. Start the VM first. Wait 2 minutes after starting, then refresh the boot diagnostics tab. If it loads now, you're done.

Also check if the VM has a Public IP address. Boot diagnostics uses that for serial console output sometimes. If there's no public IP, you might see a blank screen. Add a public IP under Networking if needed. But skip this if you're only using managed disk diagnostics (see next step).

Moderate Fix (5 minutes) – Check Storage Account Settings

Boot diagnostics saves its data to a storage account. If that storage account is misconfigured, you get nothing. Go to your VM, click Boot diagnostics from the left menu. Under Settings, you'll see two options: Managed or Storage account.

1. If you're on Managed (the default for new VMs), this usually works fine. But sometimes Azure's managed storage for boot diagnostics has a hiccup. Switch to Storage account temporarily. Click Save.
2. Choose an existing storage account in the same region as your VM. If you don't have one, create one. Go to Storage accounts in the portal, click Create. Name it something like bootdiagvm123. Pick the same region as your VM. Standard performance is fine. Click Review + create then Create.
3. After the storage account is ready, go back to your VM's Boot diagnostics settings. Select Storage account and pick the new one.
4. Click Save and wait 1 minute.
5. Go to Boot diagnostics tab again and click Refresh. You should see the screenshot or serial log now.

If it still shows blank, try the opposite – switch from Storage account back to Managed. Sometimes the managed service just needed a kick.

Advanced Fix (15+ minutes) – Reset the VM's Boot Configuration

If the simple and moderate fixes didn't work, your VM might have a corrupted boot config. This happens when a Windows update fails, or the Linux kernel panics. You'll need to redeploy the VM (but keep your data). Here's how.

Step 1: Stop the VM

In the Azure portal, go to your VM, click Stop. Wait until status shows Stopped (deallocated). This takes about 2 minutes.

Step 2: Backup the OS Disk

You'll swap the OS disk for a new one, but first save a copy. Go to your VM's Disks tab. Click on the OS disk name. On the disk's page, click + Create snapshot. Give it a name like osdisk-bootdiag-backup. Choose the same resource group. Click Review + create then Create. Wait 5 minutes for the snapshot to finish.

Step 3: Create a New VM with the OS Disk

You'll attach this disk to a new VM to fix the boot. Go back to the OS disk page, click Create VM (this option appears when the original VM is deallocated). This creates a new VM with the same OS disk attached. Give it a new name, like temp-bootfix-vm. Use the same region and size as the original. Click Review + create then Create. Wait 5 minutes.

Step 4: Repair the Boot on the New VM

Once the new VM is running, connect to it via RDP (Windows) or SSH (Linux). For Windows:

1. Open a Command Prompt as Administrator.
2. Run bcdedit /enum and look for the Windows Boot Loader section. Note the device and osdevice values. They should point to partition=C:.
3. If they're wrong (like pointing to a missing partition), run bcdedit /set {default} device partition=C: and bcdedit /set {default} osdevice partition=C:.
4. Also run sfc /scannow to fix system files. Let it finish.

For Linux:

1. SSH into the VM.
2. Run sudo grub2-mkconfig -o /boot/grub2/grub.cfg (for RHEL/CentOS) or sudo update-grub (for Ubuntu/Debian).
3. Check the boot log: journalctl -b | tail -50.

Step 5: Swap the Disk Back

Stop the new VM. Detach the OS disk from it (go to Disks on the new VM, click the disk name, then Detach). Go back to the original VM, click Disks, click Attach existing, select the repaired OS disk. Start the original VM. Boot diagnostics should work now.

If you still see blank boot diagnostics after all this, disable boot diagnostics entirely in the VM settings, wait 5 minutes, then re-enable it. This clears any cached state. Sometimes the portal just needs a reboot.