● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows 11 desktop showing Hyper-V Manager with a snapshot failed error dialog on a dark monitor
Fix It Yourself · Troubleshooting

Hyper-V checkpoints not working

Published 23 August 202613 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

You know that sinking feeling when you right-click a VM, hit 'Checkpoint', and get back a vague 'snapshot failed' error? I've seen it hundreds of times. The frustrating part is that most guides online send you down a rabbit hole of registry edits and reinstalls when the actual fix is usually one of five specific things. This article cuts straight to those five things, in order of how often they actually cause Hyper-V checkpoints not working on Windows 11.

TL;DR

Hyper-V checkpoints not working is almost always caused by VSS failures, low disk space, broken AVHDX chains, or missing permissions on the VM storage folder. Start by restarting the Volume Shadow Copy Service and switching to Standard checkpoint mode. If that doesn't sort it, check storage space, fix NTFS permissions with icacls, and inspect the AVHDX chain using PowerShell's Get-VHDChain.

⏳️ 13 min read ✅ 87% success rate 📅 Updated July 2026

Key Takeaways

  • Hyper-V checkpoints not working is most often a VSS or storage space issue, not a Hyper-V bug
  • Switching from Production to Standard checkpoint type fixes a large proportion of failures instantly
  • The NT VIRTUAL MACHINE\Virtual Machines group needs full NTFS permissions on your VM storage folder
  • Broken AVHDX chains require PowerShell inspection before any manual merge attempt
  • Always back up VHDX files before attempting advanced chain repairs

At a Glance

  • Difficulty: Intermediate to Advanced
  • Time Required: 15 to 45 mins
  • Success Rate: 87% of users fixed with Tier 1 or Tier 2 steps

What Actually Causes Hyper-V Checkpoints Not Working?

Before touching anything, it helps to know what you're dealing with. Hyper-V checkpoints not working doesn't have one single cause. It's a symptom that can come from five different directions, and the fix depends entirely on which one you're hitting.

The most common culprit by far is the Volume Shadow Copy Service. When you create a Production checkpoint, Hyper-V reaches into the guest OS and asks VSS to freeze application state before snapping the disk. If VSS is stopped, stuck, or has a writer in a failed state (which happens after dodgy backup software runs), the whole operation falls over. You'll see errors like 'checkpoint operation failed' or 'the virtual machine is not in a valid state for this operation'.

Second most common: storage space. This one catches people out because they check the host volume and it looks fine, but they forget that AVHDX differencing disks can grow to match the full size of the parent VHDX during a merge. Microsoft's own best practices guidance recommends keeping free space equal to or greater than the size of your virtual disk. If you're running tight, checkpoints will fail mid-operation and sometimes corrupt the chain in the process.

Third is permissions. The NT VIRTUAL MACHINE\Virtual Machines group needs full NTFS access to your VM storage folder. This breaks silently after a VM move, a storage migration, or when someone runs a permissions reset across a drive. Hyper-V just can't write the AVHDX file and gives you a generic error.

Fourth is Integration Services. Specifically the Backup (volume shadow copy) component inside the guest. If that's disabled or out of date, Production checkpoints won't work. And fifth is orphaned or broken AVHDX chains, usually left behind by third-party backup tools that didn't clean up properly after themselves.

Right, now let's actually fix it.

Hyper-V Checkpoints Not Working: Quick Fix (5 to 10 Minutes)

Start here. These two fixes together resolve the majority of Hyper-V snapshot failed errors without any PowerShell or file system work.

1

Restart VSS and Toggle Backup Integration Easy

  1. Restart VSS inside the guest VM
    Open an elevated Command Prompt inside the guest and run:
    net stop vss
    then
    net start vss
    Wait for both to complete before moving on.
  2. Restart VSS on the host
    Press Win + R, type services.msc, find 'Volume Shadow Copy', right-click it and select Restart. If it's not running, start it.
  3. Toggle backup integration in Hyper-V Manager
    Right-click your VM, select Settings, then Integration Services. Uncheck 'Backup (volume shadow copy / volume checkpoint)', click Apply. Now try creating a checkpoint. If it works, go back and re-enable the backup integration.
  4. Make sure the VM isn't in a transient state
    If the VM shows as 'Saving', 'Creating Checkpoint', or 'Stopping' in Hyper-V Manager, stop it cleanly and restart before retrying. A stuck transient state blocks all checkpoint operations.
Success: Checkpoint creates without error and appears in the Checkpoints pane in Hyper-V Manager.
2

Switch to Standard Checkpoint Type Easy

  1. Open VM Settings
    In Hyper-V Manager, right-click the VM and select Settings. Navigate to Checkpoints under the Management section in the left pane.
  2. Change the checkpoint type
    Change from 'Production' to 'Standard', or select 'Production checkpoints with fallback to Standard'. Click Apply.
  3. Test checkpoint creation
    Right-click the VM and select Checkpoint. Standard checkpoints bypass VSS entirely, so they succeed in most cases where Production checkpoints fail.
Standard checkpoints don't capture application-consistent state the way Production checkpoints do. They're fine for dev and test VMs, but for production workloads running SQL Server or Exchange, you'll want to fix the underlying VSS issue eventually rather than leaving it on Standard permanently.
Success: Checkpoint creates. You can now decide whether to investigate VSS further or leave the VM on Standard mode.

More Hyper-V Checkpoints Not Working Solutions (15 to 30 Minutes)

If the quick fixes didn't work, the problem is almost certainly storage space, permissions, or antivirus interference. These fixes are a bit more involved but still well within reach without specialist tools.

3

Check Storage Space and Clean Up Old Checkpoints Medium

  1. Check host volume free space
    Open File Explorer on the host and check the drive holding your VHDX and AVHDX files. You need free space equal to at least the size of your virtual disk. A 100GB VHDX needs at least 100GB free on the host volume for safe checkpoint creation and merging.
  2. Check guest OS free space
    Inside the guest VM, open Disk Management or File Explorer and verify the guest volumes aren't full. Low space inside the guest can cause VSS-based Production checkpoints to fail even when the host has plenty of room.
  3. Delete old checkpoints
    In Hyper-V Manager, select the VM. In the middle pane you'll see the Checkpoints list. Right-click any checkpoint you no longer need and select 'Delete Checkpoint'. Let the merge complete before creating a new one.
Success: After freeing space and deleting old checkpoints, retry checkpoint creation.
4

Fix NTFS Permissions for the VM Storage Folder Medium

  1. Open an elevated Command Prompt on the host
    Right-click Start, select 'Windows Terminal (Admin)' or 'Command Prompt (Admin)'.
  2. Run icacls to restore permissions
    Replace the path below with your actual VM storage folder:
    icacls "C:\VMs\VM1" /grant "NT VIRTUAL MACHINE\Virtual Machines":F /T
    The /T flag applies the change recursively to all subfolders and files. This gives the Hyper-V service account full NTFS access.
  3. Verify the change
    Run icacls "C:\VMs\VM1" and confirm 'NT VIRTUAL MACHINE\Virtual Machines' appears with (F) (full access) in the output.
  4. Retry checkpoint creation
    Go back to Hyper-V Manager and try creating a checkpoint again.
If your VM storage is on a network share or a drive that had permissions reset by Group Policy, you may need to re-apply this fix after every policy refresh. Check with your domain admin if it keeps reverting.
Success: Checkpoint creates without a permissions-related error.
5

Configure Antivirus Exclusions and Reset Checkpoint Config Medium

  1. Add antivirus exclusions for Hyper-V paths
    Real-time scanning of VHDX and AVHDX files can lock them mid-operation and cause checkpoint failures. Add exclusions in your antivirus product for the VM storage folder (e.g. C:\VMs\), the Hyper-V configuration folder (usually C:\ProgramData\Microsoft\Windows\Hyper-V\), and any checkpoint directories. Consult your antivirus documentation for the exact exclusion syntax.
  2. Reset checkpoint configuration at the VM level
    In Hyper-V Manager, open VM Settings and go to Checkpoints. Uncheck 'Enable checkpoints', click Apply. Wait a few seconds, then re-check 'Enable checkpoints' and click Apply again. This resets the checkpoint metadata at the VM level without touching any disk files.
  3. Retry checkpoint creation
    Right-click the VM and select Checkpoint to test.
Success: Checkpoint creates cleanly. If antivirus was the culprit, you'll notice the operation completes much faster than before.

If you're dealing with a more complex setup and want someone to take a look remotely, our guide on common Windows 11 virtualisation issues covers some of the broader Hyper-V configuration problems we see regularly.

Advanced Hyper-V Checkpoints Not Working Fixes (30+ Minutes)

These steps are for when the checkpoint chain itself is broken or corrupted. We're talking orphaned AVHDX files, missing parent disks, and chains that won't merge through the normal UI. Back up everything before you start here. Seriously.

6

Inspect and Repair the AVHDX Chain with PowerShell Advanced

Back up all VM files (VHDX, AVHDX, XML configuration files) to a separate location before proceeding. A failed merge on a corrupted chain can cause data loss.
  1. List all checkpoints for the VM
    Open PowerShell as Administrator on the host and run:
    Get-VMSnapshot -VMName "YourVMName"
    This shows every checkpoint, its name, creation time, and ID. Note any that look orphaned or have unusual names.
  2. Inspect the VHD chain
    Run:
    Get-VHDChain -Path "C:\Path\To\Disk.vhdx"
    This outputs the full parent-child relationship between your VHDX and any AVHDX differencing disks. Look for any entry that shows a missing or unresolvable parent. According to Microsoft's Merge-VHD documentation, the chain must be fully intact before a merge can succeed.
  3. Check for orphaned differencing disks
    Browse the VM storage folder in File Explorer and look for AVHD, AVHDX, MRT, and RCT files that don't correspond to any visible checkpoint in Hyper-V Manager. These are orphaned files left behind by failed operations or backup software. Note their names before touching them.
  4. Manually merge an AVHDX file
    If the chain is logically consistent but won't merge through the UI, power off the VM completely and run:
    Merge-VHD -Path "C:\VMs\VM1\Disk-Checkpoint.avhdx" -DestinationPath "C:\VMs\VM1\Disk.vhdx"
    Replace the paths with your actual file locations. The VM must be fully powered off, not just saved.
  5. Verify the merged disk
    After the merge completes, run:
    Get-VHD -Path "C:\VMs\VM1\Disk.vhdx"
    Check that the VhdType shows as 'Dynamic' or 'Fixed' (not 'Differencing') and that the FragmentationPercentage is reasonable. A high fragmentation percentage is normal after a merge.
Success: Get-VHDChain shows a clean single-level chain with no missing parents. The VM boots and checkpoints can be created normally.
7

Re-Create the VM When Corruption Is Severe Advanced

  1. Back up everything first
    Copy all VHDX, AVHDX, and XML files to a separate drive. Don't skip this.
  2. Merge what you can
    Use Merge-VHD to consolidate the AVHDX chain into a single healthy VHDX as described in Solution 6. If Get-VHDChain shows a missing base disk, you'll need to restore it from backup before merging.
  3. Create a new VM
    In Hyper-V Manager, select New, then Virtual Machine. Match the original VM's settings (generation, RAM, network adapters, etc.).
  4. Attach the merged VHDX
    In the new VM's Settings, under SCSI Controller or IDE Controller (depending on generation), attach the merged healthy VHDX as the primary disk. Do not create a new virtual disk.
  5. Boot and test
    Start the new VM, verify it boots correctly, then create a test checkpoint to confirm the issue is resolved.
This approach is a last resort for heavily corrupted checkpoint chains. The good news is that as long as the base VHDX data is intact, you won't lose any VM data. If you're dealing with a VM that also has driver or activation issues after the recreation, our article on fixing Hyper-V VMs that won't boot covers the common post-migration problems.
Success: New VM boots from the merged VHDX and checkpoint creation works without errors.

Preventing Hyper-V Checkpoints Not Working

Most of the time, Hyper-V checkpoints not working is preventable. The number one thing you can do is keep storage headroom. Seriously, don't let your VM storage volume drop below the size of your largest VHDX. Set a disk alert if you need to. Running out of space mid-merge is one of the fastest ways to end up with a corrupted chain.

Second, clean up old checkpoints regularly. Long AVHDX chains are fragile. Every additional checkpoint in the chain is another link that can break. Use Get-VMSnapshot -VMName "YourVMName" in PowerShell to review what's there, and delete anything you don't actively need. Microsoft's checkpoint management documentation recommends merging checkpoints before any major OS or application upgrade for exactly this reason.

Third, sort your antivirus exclusions properly. Every Hyper-V storage path, every VHDX folder, every checkpoint directory. Real-time scanning of these files causes intermittent checkpoint failures that are genuinely hard to diagnose because they don't happen every time.

Fourth, keep an eye on VSS health inside your guest VMs. Run vssadmin list writers inside the guest occasionally and check that all writers show 'Stable' state. A writer stuck in 'Failed' or 'Waiting for completion' will cause Production checkpoints to fail every time until it's fixed. And finally, after any VM move or storage migration, always re-check NTFS permissions on the new storage path using icacls. It takes two minutes and saves a lot of head-scratching later.

If you're running third-party backup software alongside Hyper-V, make sure it's configured to clean up its own checkpoints after each job. Some older backup products leave residual AVHDX files behind after each run, which gradually builds up a broken chain over weeks. Our article on Windows 11 backup not working covers how to audit and fix backup software conflicts that affect Hyper-V.

Hyper-V Checkpoints Not Working: Summary

Hyper-V checkpoints not working on Windows 11 comes down to five things: VSS failures, low storage space, bad NTFS permissions, misconfigured Integration Services, and broken AVHDX chains. Start with the quick fixes (restart VSS, toggle backup integration, switch to Standard checkpoint type) because they fix the majority of cases in under ten minutes. If those don't work, check storage space, fix permissions with icacls, and sort your antivirus exclusions. For broken chains, use Get-VHDChain and Merge-VHD in PowerShell to inspect and repair before considering a VM recreation. And going forward, keep storage headroom, clean up old checkpoints regularly, and check VSS writer health inside your guests. Do those things and you'll rarely see Hyper-V checkpoints not working again.

Frequently Asked Questions

Production checkpoints use the Volume Shadow Copy Service inside the guest to create application-consistent snapshots. Standard checkpoints create a simple differencing disk without VSS involvement. Standard checkpoints are faster and more reliable, but they do not capture application state. If Hyper-V checkpoints not working errors appear with Production mode, switching to Standard often fixes it immediately.

VSS writer errors happen when the Volume Shadow Copy Service inside the guest OS fails to prepare for snapshot creation. This can occur if VSS is stopped, a writer is in a failed state, or backup software has left VSS in an inconsistent state. Restart VSS on both the guest and the host, then run vssadmin list writers inside the guest to identify any failed writers.

Yes, if you still have a healthy base VHDX file. Use Get-VHDChain in PowerShell to identify which files in the chain are valid, manually merge any intact AVHDX files using Merge-VHD, then create a new VM and attach the merged VHDX. If the base VHDX itself is corrupted, you will need to restore from a backup.

Microsoft recommends that the volume storing your VHDX and AVHDX files has free space equal to at least the full size of the virtual disk. This gives checkpoint creation and merge operations enough room to complete without running out of space mid-operation, which can cause corruption.

Yes. Deleting old checkpoints can help when the chain has become too long or complex, and it frees up storage space that may be causing the failure. Use Hyper-V Manager to delete unused checkpoints. Just make sure you no longer need to restore to those points before you delete them.