● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows 11 Hyper-V Manager window showing a virtual machine in Starting state with system task manager displaying resource usage in background
Fix It Yourself · Troubleshooting

Hyper-V VM stuck starting

Updated 26 July 202613 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Your Hyper-V VM sits there spinning, frozen at Starting state. No error message. No progress. Just waiting. You've got work to do, and this isn't helping. Before you ring a support line or spend a morning rebuilding the whole thing, try this. Most Hyper-V VM stuck starting issues clear up in 45 minutes with the right approach.

TL;DR

Hyper-V VM stuck starting usually means the VMMS service is hung, storage is inaccessible, or saved state is corrupted. Restart VMMS service first, delete saved state if present, check host resources aren't maxed out, and verify VHDX file paths exist. If those don't work, check Secure Boot settings and virtual switch configuration. Last resort: force-kill vmwp.exe or verify hypervisor launch type is enabled.

⏱️ 14 min read ✅ 85% success rate 📅 Updated May 2026

Key Takeaways

  • Restart the VMMS service first, it solves this for most people
  • Delete saved state files if your VM has them
  • Check your host isn't out of disk space or RAM
  • Verify your VHDX files are on local SSD, not network storage
  • Disable Secure Boot temporarily if quick fixes don't work
  • Force-killing vmwp.exe is a nuclear option but works when nothing else does

At a Glance

  • Difficulty: Medium
  • Time Required: 15 mins (quick fix) to 45 mins (full troubleshooting)
  • Success Rate: 85% of users fix this without professional help

What Causes Hyper-V VM Stuck Starting?

The VM stuck in Starting state issue happens when Hyper-V can't transition the machine from its idle state into a fully running state. This is different from a VM that crashes after starting or won't boot the guest OS. The VM never actually launches. The hypervisor is trying, but something blocks the process.

Here's what's happening behind the scenes. When you click Start in Hyper-V Manager, the management service (VMMS) spawns a worker process (vmwp.exe) for your specific VM. That worker process talks to the hypervisor, loads the VHDX disk files, attaches the virtual network adapter, and boots the guest OS. If any step in that chain fails, the VM hangs in Starting state and just sits there waiting for something that never comes.

The most common culprits are a hung VMMS service that isn't responding to state-change requests, corrupted saved state files that confuse the hypervisor about what state the VM should be in, inaccessible storage (slow network drives, permission issues, missing files), resource exhaustion on the host (no free memory or disk space), or virtual switch problems that stop the network adapter from initialising. Sometimes it's also a BIOS setting or third-party antivirus locking files.

Quick Fix: Restart VMMS and Check Host Resources

1

Restart the Hyper-V Virtual Machine Management Service Easy

  1. Open Services Manager
    Press Win+R, type services.msc, press Enter.
  2. Find VMMS
    Scroll down and locate Hyper-V Virtual Machine Management Service (it's alphabetically under H).
  3. Restart the Service
    Right-click it and select Restart. If Restart is greyed out, click Stop first, wait 5 seconds, then click Start.
  4. Wait for Full Restart
    The service usually takes 10-15 seconds to restart. You'll see it briefly say Stopping, then Starting, then Running.
  5. Return to Hyper-V Manager
    Close Services Manager. Open Hyper-V Manager and attempt to start your stuck VM.
If the VM starts after this, you're done. The VMMS service was hung and needed a fresh start.
2

Check Host Resources Aren't Exhausted Easy

  1. Open Task Manager
    Press Ctrl+Shift+Esc to open Task Manager directly.
  2. Check Performance Tab
    Click the Performance tab. Look at CPU, Memory, and Disk panels.
  3. Verify Free Resources
    Your CPU usage should be below 90%. Memory should have at least 10% free (if you have 16GB, at least 1.6GB should be free). Disk should not show 100% usage.
  4. Close Unnecessary Applications
    If any of these are maxed out, close unnecessary programs. Pause other running VMs to free up RAM.
  5. Check Again and Retry
    Once resources look reasonable, return to Hyper-V Manager and try starting the VM again.
Resource exhaustion is often overlooked. Sometimes just closing Chrome or pausing another VM is enough.
3

Delete Saved State and Adjust VM Settings Easy

  1. Open Hyper-V Manager
    Press Win+X and select Hyper-V Manager (or search for it).
  2. Find Your Stuck VM
    In the left panel, highlight your stuck VM.
  3. Check for Saved State Option
    Right-click the VM. If you see a Delete Saved State option, click it. Wait for it to complete.
  4. Open VM Settings
    Right-click the VM again and select Settings.
  5. Disable Secure Boot
    Click Firmware in the left menu. Uncheck Enable Secure Boot. Click Apply.
  6. Check Hard Drive Path
    Click SCSI Controller, then Hard Drive. Verify the path shown actually exists and is accessible. If the path shows something like D:\VMs\broken.vhdx, make sure that drive and file are still there.
  7. Disconnect Network Temporarily
    Click Network Adapter. Change Virtual switch to Not connected. Click Apply and OK.
  8. Try Starting the VM
    Right-click the VM and select Start. If it starts, you can reconnect the network and re-enable Secure Boot one at a time to find the culprit.
Corrupted saved state and Secure Boot issues account for roughly 30% of stuck starting VMs. This step catches most of them.

Intermediate Fixes: Storage, Features, and System Health

4

Verify Hyper-V Features Are Fully Enabled Easy

  1. Open Optional Features
    Press Win+R, type optionalfeatures.exe, press Enter.
  2. Check Hyper-V is Ticked
    Scroll down and look for Hyper-V. It should be checked, and you should see sub-options for Hyper-V Management Tools and Hyper-V Platform also checked.
  3. Verify Additional Features
    Also check that Virtual Machine Platform and Windows Hypervisor Platform are checked.
  4. Apply Changes
    If you unchecked anything or made changes, click OK. Windows will apply them. You may be prompted to reboot.
  5. Reboot If Prompted
    If prompted, reboot your system. Wait for it to fully boot.
  6. Test the VM
    Open Hyper-V Manager and try starting your VM again.
Sometimes Windows updates disable these features or they get partially unchecked. This step ensures Hyper-V is fully enabled at the OS level.
5

Verify VHDX Storage Paths and NTFS Permissions Medium

  1. Get the Storage Location
    In Hyper-V Manager, right-click your stuck VM and select Settings. Note the Configuration location shown at the top. Also check SCSI Controller > Hard Drive to note the VHDX file path.
  2. Open File Explorer
    Press Win+E to open File Explorer.
  3. Navigate to the VHDX File
    Paste the path from step 1 into the File Explorer address bar. Verify the VHDX file actually exists and isn't corrupted (file size should be at least a few hundred MB, not 0 bytes).
  4. Check Storage is Local SSD
    If the path is on a network drive (like \\server\share) or external USB drive, that's your problem. VMs need local SSD storage. Move the files to C: or another local fast disk.
  5. Check NTFS Permissions
    Right-click the VM folder (the parent of the VHDX file) and select Properties. Go to Security tab. Check that SYSTEM and Administrators both have Full Control. If they don't, click Edit, select Administrators, check Full Control, and click Apply.
  6. Verify Disk Space
    In File Explorer, right-click the drive where VHDX is stored and select Properties. Ensure at least 10GB is free on that drive.
  7. Retry VM Start
    Return to Hyper-V Manager and try starting the VM.
Network storage and permission issues are silent killers. VMs on slow network drives often hang indefinitely in Starting state.
6

Repair System Files and Check Disk Health Medium

  1. Open PowerShell as Administrator
    Right-click PowerShell and select Run as administrator.
  2. Run System File Checker
    Type sfc /scannow and press Enter. This will scan and repair any corrupted Windows system files. It takes 10-15 minutes.
  3. Wait for Completion
    Once done, you'll see a summary. If repairs were made, note them.
  4. Run DISM Cleanup
    After sfc finishes, run DISM /Online /Cleanup-Image /RestoreHealth and press Enter. Wait for completion (another 5-10 minutes).
  5. Reboot the Host
    Close PowerShell and restart your Windows 11 machine. Let it fully boot.
  6. Test VM Again
    Open Hyper-V Manager and attempt to start your VM.
Corrupted system files can subtly break Hyper-V functionality. This step catches OS-level issues that simple restarts miss.
7

Check and Reconfigure Virtual Switch Medium

  1. Open Virtual Switch Manager
    In Hyper-V Manager, right-click your host (top left) and select Virtual Switch Manager.
  2. List Your Switches
    You'll see a list of virtual switches. For each one, check the Connection type. If it says External, verify the associated physical NIC is listed and enabled.
  3. Check Physical NIC Health
    Open Settings > Network & internet > Advanced network settings and verify your physical network adapters are all enabled and connected. Disabled NICs will break external switches.
  4. Temporarily Disconnect Network
    Go back to your stuck VM settings, click Network Adapter, and change Virtual switch to Not connected. Apply and try starting the VM.
  5. If VM Starts, Reconnect to Different Switch
    If it starts, the virtual switch was the issue. Try connecting it to a different switch (Internal or Private if available, not External). Or check the physical NIC connection status.
  6. Repair or Recreate Switch If Needed
    If the switch is truly broken, delete it in Virtual Switch Manager and create a new one with the same physical NIC assigned.
Virtual switch issues are sneaky. A disabled physical NIC can leave a switch orphaned, causing all attached VMs to hang in Starting state.

Advanced Fixes: Process Termination and Hypervisor Configuration

8

Force-Kill the VM Worker Process (vmwp.exe) Hard

  1. Open PowerShell as Administrator
    Right-click PowerShell and select Run as administrator.
  2. Get Your VM Name and GUID
    Run these commands one at a time:
    $VMName = "Your VM Name" (replace with your actual VM name)
    $VM = Get-VM -Name $VMName
    $VMGUID = $VM.Id
    $VMGUID (this will display your VM's GUID)
  3. Find the Worker Process
    Run:
    $VMWMProc = Get-WmiObject Win32_Process | Where-Object { $_.Name -match 'vmwp' -and $_.CommandLine -match $VMGUID }
    $VMWMProc (this shows the process details)
  4. Kill the Process
    If a process is returned, run:
    Stop-Process -Id $VMWMProc.ProcessId -Force
  5. Wait and Restart VM
    Wait 5 seconds, then run:
    Start-VM -Name $VMName
WARNING: Killing vmwp.exe is equivalent to pulling the power plug on a physical machine. Any unsaved data inside the guest OS will be lost. Use this only when the VM is completely unresponsive and nothing else has worked.
9

Force-Restart VMMS and Verify Hypervisor Launch Type Hard

  1. Open PowerShell as Administrator
    Right-click PowerShell and select Run as administrator.
  2. Stop VMMS Forcefully
    Run:
    Stop-Service vmms -Force
    Then run:
    Get-Process | Where-Object { $_.ProcessName -eq 'vmms' } | Stop-Process -Force
  3. Restart the Service
    Run:
    Start-Service vmms
    Wait 10 seconds for the service to fully start.
  4. Check Hypervisor Launch Type
    Run:
    bcdedit (without parameters, this just displays boot config)
    Look for the line that says hypervisorlaunchtype. It should say auto.
  5. Fix Hypervisor Launch Type if Needed
    If it says off, run:
    bcdedit /set hypervisorlaunchtype auto
  6. Reboot If You Changed Hypervisor Launch Type
    If you ran the bcdedit /set command, reboot your host. If you only restarted VMMS, you don't need to reboot.
  7. Test VM Start
    Run:
    Start-VM -Name "Your VM Name"
What's hypervisorlaunchtype? This setting controls whether Hyper-V loads at boot. If it's Off, the hypervisor never starts and VMs cannot run. This often gets disabled by firmware updates or BIOS resets.
10

Check Event Logs for Specific Errors Hard

  1. Open Event Viewer
    Press Win+R, type eventvwr.msc, press Enter.
  2. Navigate to Hyper-V Logs
    Go to Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS (or Hyper-V-Worker).
  3. Check for Errors
    Click the Admin tab, then sort by Level to show errors first. Look for any red entries with timestamps matching when your VM tried to start.
  4. Note Error Codes
    Common errors include IO errors (storage problem), file not found (VHDX path is wrong), permission denied (NTFS permissions issue), or hypervisor not available (hypervisor launch type is off).
  5. Google the Error Code
    If you see a specific error code or message, search Microsoft support docs or your VM vendor's troubleshooting guide for that code.
  6. Document and Escalate
    If logs show something exotic (like hardware incompatibility), document the error and consider contacting Microsoft support or your system vendor.
Event logs often tell you exactly what went wrong. Most people skip this step and miss the root cause.
11

Disable Third-Party Antivirus Temporarily Medium

  1. Open Your Antivirus Application
    Click its icon in the system tray or open it from the Start menu (Windows Defender, Norton, McAfee, Kaspersky, etc.).
  2. Disable Real-Time Protection
    Most antivirus apps have a toggle for real-time or active protection. Click it to temporarily disable it. You may be asked to confirm.
  3. Set Exclusions (Optional)
    If you want to be safer than just disabling, add exclusions for:
    C:\ProgramData\Microsoft\Windows\Hyper-V\
    and your VM storage folder (e.g., C:\VirtualMachines\).
    Consult your antivirus docs for how to add exclusions.
  4. Test VM Start
    Return to Hyper-V Manager and try starting your VM.
  5. Re-Enable Antivirus
    If the VM starts successfully, re-enable real-time protection and keep the exclusions in place permanently. This prevents the issue from recurring.
  6. If Still Stuck
    If the VM still won't start even with antivirus disabled, the issue is not antivirus-related. Move on to the next fix.
Antivirus software often locks VHDX files or system DLLs that Hyper-V needs to read. This is a common culprit, especially with Norton and McAfee.
12

Export and Rebuild the VM Configuration Hard

  1. Export the VM if Possible
    In Hyper-V Manager, right-click your stuck VM and select Export. Choose a safe location (like your Documents folder). If export fails, skip to step 3.
  2. Note VM Settings
    Before deleting, write down:
    - VM name
    - Generation (1 or 2)
    - CPU count (how many vCPUs)
    - Memory (RAM allocated)
    - VHDX file paths
    - Virtual switch assigned
  3. Delete VM Configuration
    Right-click the VM and select Delete. When prompted, choose to delete the VM configuration only, NOT the VHDX files. Your disk files stay safe.
  4. Create New VM with Same Settings
    Right-click your host and select New > Virtual Machine. Use the wizard to create a new VM with the exact same name, generation, CPU, and memory as before.
  5. Attach Existing VHDX Files
    In the wizard, when prompted for hard drive, do not create a new one. Instead, attach the existing VHDX files from the original VM.
  6. Complete Wizard and Test
    Finish the wizard, then try starting the new VM. If it starts, the old configuration was corrupted.
This is a nuclear option. Use it only if all other fixes have failed and you have the time to rebuild. Your data is safe because you're reusing the original VHDX files.
Need expert help? If you've tried 8+ of these fixes and the VM is still stuck, remote support can often pinpoint the exact issue faster than trial and error.

Preventing Hyper-V VM Stuck Starting in Future

Once you've fixed this, don't let it happen again. Here's what matters most.

Keep your Hyper-V host updated. Run Windows Update regularly. Also grab the latest chipset drivers and firmware from your motherboard or system vendor. These updates often fix virtualisation bugs that cause stuck VMs.

Always store VHDX files on local SSD. Network drives, USB sticks, and external drives are too slow and unreliable. Hyper-V works best with fast local storage. If you run out of space on your C: drive, buy a second SSD. Don't move VMs to slower storage.

Avoid saved states. Instead of putting a VM to sleep with Save State, shut it down cleanly from inside the guest OS or use Shut Down from Hyper-V Manager. Saved state files corrupt easily, especially after updates. Clean shutdowns are safer.

Monitor your host resources. Use Resource Monitor (Win+R, resmon) once a week to check CPU, memory, and disk usage. If any regularly hit 90%+ capacity, something needs to change. Add RAM, upgrade your SSD, or reduce the number of running VMs.

Configure antivirus exclusions now. Open your antivirus and add permanent exclusions for C:\ProgramData\Microsoft\Windows\Hyper-V\ and your VM storage folder. This prevents file locking issues down the line.

Keep your virtual switch stable. Don't constantly rename or remove physical NICs. Don't switch external switches between different physical adapters. Stability in your network configuration means stability for your VMs.

Backup your VMs. Export critical VMs or back up their configuration and VHDX files to external storage. If corruption happens again, you can restore from a known-good backup in minutes instead of spending hours troubleshooting.

Hyper-V VM Stuck Starting Summary

A Hyper-V VM stuck in Starting state is fixable 85% of the time without professional help. Start by restarting the VMMS service and checking your host resources. Delete any saved state files. Verify your VHDX files are on local SSD, not network storage. Disable Secure Boot temporarily. If those don't work, restart VMMS again forcefully, check your system files, and verify hypervisor launch type is enabled. Last resort: force-kill vmwp.exe or rebuild your VM configuration.

Most importantly, once it's fixed, move your VHDX files to local SSD, keep your host updated, and add antivirus exclusions. Those three things prevent this problem from coming back.

Frequently Asked Questions

Yes, it will. Killing the VM worker process is equivalent to pulling the power plug on a physical machine. Any unsaved data inside the guest OS will be lost. Use this only as a last resort when the VM is completely frozen and won't respond to any other method.

Restarting the Hyper-V Virtual Machine Management Service affects the management layer, not the hypervisor itself. Running VMs typically continue executing, but management operations like start, stop, and checkpoints become temporarily unavailable during the restart. It usually takes 10-15 seconds.

Yes, you can move VHDX and configuration files, but you must update the VM settings in Hyper-V Manager to point to the new paths. Make sure the destination is a fast, reliable, always-online local SSD. Network shares or external USB drives are too slow and unreliable for production VMs.

This BIOS/UEFI setting controls whether the Hyper-V hypervisor loads at system boot. If set to Off, Hyper-V cannot function at all and VMs won't start. It should be set to Auto for normal operation. You can check and fix this via bcdedit in PowerShell.

If a VM is stuck in Starting state and has a saved state file, deleting the saved state is often the quickest fix. The saved state file may be corrupted or incompatible with the current Hyper-V version. Deleting it does not affect the VHDX data disk, so your VM data is safe.