## TL;DR
Failed to create snapshot means the job stopped before data transfer because the hypervisor or VSS snapshot never materialised. Check for leftover snapshots, stuck VSS writers, and datastore or volume free space first, in that order. Clear the blocker, restart the relevant writer services if a writer is in a failed state, and retry the job.

```text
veeam "failed to create snapshot" error
```

## Use this when
- Veeam job log shows failed to create snapshot for a VM or agent volume.
- Hyper-V or VMware snapshot creation also fails when tried manually.
- VSS writers list one or more writers in a failed or waiting state.

## Not for this skill when
- Snapshots are created but consolidation fails afterwards. That is a consolidation problem.
- The snapshot exists but data reading fails with unable to retrieve next block.

## Steps
1. Open the job log and note whether the failure is at the hypervisor snapshot call or the guest VSS freeze step. Verify: the failing layer is identified
2. Check the VM for existing snapshots and remove stale or orphaned ones through the hypervisor manager, watching for a snapshot left by a previous failed job. Verify: the VM snapshot tree is clean or consolidation is running normally
3. On the guest or agent machine run vssadmin list writers and note any writer not in a stable state. Verify: every writer reports stable with no error, or the faulty writer is named
4. Restart the Volume Shadow Copy service and the faulty writer service, then confirm datastore or volume free space is above 10 percent. Verify: writers are stable and space is sufficient
5. Retry the Veeam job and watch it pass the snapshot step into data transfer. Verify: the job progresses past snapshot creation

## Variant phrasings
### veeam unable to create snapshot hyper-v
The Hyper-V specific phrasing.
### veeam snapshot creation failed vss
The VSS-worded variant.
### veeam cannot create snapshot datastore space
The space-cause phrasing.

Compatibility: Veeam Backup and Replication 11 and 12 for VMware vSphere 7 and 8 and Hyper-V 2019 and 2022, plus Veeam Agent for Windows 6 with VSS-based jobs.

## Why it happens
Snapshot creation depends on three layers agreeing at once: the hypervisor must have room and no conflicting snapshot task, the guest VSS framework must freeze writers cleanly, and no previous orphaned snapshot can block the new one. A failure in any layer aborts the job before a single block is read, and the Veeam message rarely names the layer directly.

## Edge cases / pitfalls
- A writer stuck in waiting for completion after a reboot usually needs its owning service restarted, not a server reboot.
- Antivirus real-time scanning on VSS temporary areas can time out freezes on busy servers.
- Never delete snapshot files directly from the datastore. Always consolidate through the hypervisor manager.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_topJmOyWvtEPVnCSlHoBuQ