About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The two codes are related but not the same. 0x80780119 is the "not enough disk space for the volume shadow copy" failure: Windows could not create a shadow copy of a volume in the backup because there was too little free space. 0x807800C5 is worded by Windows as "There was a failure in preparing the backup image of one of the volumes in the backup set", which is a general failure message, not one specific cause. For 0x807800C5 the real reason is in the event details, so find that before you change anything.
What the error means
Windows Server Backup takes its snapshot with the Volume Shadow Copy Service (VSS) and writes the result to the target. Two documented behaviours matter here.
Backups are stored using shadow copies and virtual disks. A Microsoft Storage team post, Backup Version and Space Management in Windows Server Backup (page date 10 April 2019, written for Windows Server 2008 and 2008 R2), says each backup writes a .vhd file per source volume and that "Windows Server Backup stores backup versions in volume shadow copies". It also says "Windows Server Backup can store only one backup version on a network share (remote shared folder)".
A shadow copy needs working space. Microsoft's article The "last backup did not complete successfully" error when you back up a Windows 8 system (KB 2851998, no date shown) reports error 0x80780119 with the text that there is not enough disk space for the volume shadow copy, and lists the free space needed: "For volumes less than 500 megabytes, the minimum is 50 megabytes of free space" and "For volumes more than 500 megabytes, the minimum is 320 megabytes of free space". It recommends at least 1 gigabyte of free space on each volume larger than 1 gigabyte. The article says the free-space minimum "applies to both the backup storage destination and volumes included in the backup", so check the destination as well as the source volumes. It applies to Windows 8 and Windows Server 2012.
The VSS event that goes with the same fault is Event ID 4001, source VSS, symbolic name VSS_ERROR_NO_DIFF_AREAS_CANDIDATES, documented in Event ID 4001 — VSS Shadow Copy Creation and Storage Space Availability (archived, dated 2011-01-27, Windows Server 2008 R2). Its message says VSS "Cannot find diff areas for creating shadow copies" and needs free space on each volume to be shadow copied. The message quotes a figure of 300 MB, but the page notes that "the correct minimum size is 320 MB".
For 0x807800C5, the only Microsoft-hosted page that discusses it is a Microsoft Q&A question, Windows Server 2012 r2 Backup Error 0x807800C5 (asked 27 May 2021). It shows the full text and a related log line, "Backup of volume \\?\GLOBALROOT\Device\HarddiskVolume2\ has failed. The semaphore timeout period has expired." The answers are from community members, none is marked accepted, and the page does not identify any of them as Microsoft staff. They are useful as leads, not as authority.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Not enough free space on a volume in the backup (including small system or OEM partitions), or on the backup destination, for the shadow copy | 0x80780119; VSS Event ID 4001 | Free space on every volume in the job and on the destination against the minimums above; vssadmin list shadowstorage |
| Shadow copy storage area too small, on the wrong volume, or limited by a maximum size | 0x80780119 or shadow copies vanishing | vssadmin list shadowstorage shows used, allocated and maximum space |
Existing backup in the same location conflicts with the new one (same computer, same WindowsImageBackup folder); community-reported, not Microsoft-documented |
0x807800C5 on a target that already holds a backup | Look at the target for an existing WindowsImageBackup\<ComputerName> folder; wbadmin get versions -backupTarget:<target> |
| Backup target or source disk problems (read timeouts); community-reported, not Microsoft-documented | 0x807800C5 with "The semaphore timeout period has expired" on one volume | The backup event details name the volume; the same volume fails each time |
| An unhealthy VSS writer | Backup fails at the snapshot step | vssadmin list writers; Application log, source VSS |
| Unpatched Windows Server 2012 / Windows 8 volsnap driver | 0x80780119 although free space looks adequate | Check Volsnap.sys version against KB 2851998 (6.2.9200.16613 and 6.2.9200.20718 are the versions named there) |
Prove the cause before changing anything
All of these read only. They come from Microsoft documentation and have not been run. Use an elevated command prompt.
Read the backup's own event. In Event Viewer open Windows Logs, then Application, and look at the events from source Backup; filter for source VSS around the same time. The Microsoft post Diagnosing Failures in Windows Server Backup, Part 1 (updated 10 April 2019, first published 16 September 2009) describes this approach. It does not list 0x807800C5 or 0x80780119 and gives no event IDs, so treat it as a method, not a lookup table.
Check the shadow copy storage. Per the vssadmin list shadowstorage reference:
vssadmin list shadowstorageIt shows where shadow copy storage is and how much it uses. You can restrict it with
/for=<volume>or/on=<volume>.Check the writers. The vssadmin list writers reference gives
vssadmin list writers.See what is already on the target. Per the wbadmin get versions reference:
wbadmin get versions -backupTarget:<target> -machine:<ComputerName>Check whether VSS can make a shadow copy at all. The Event 4001 page suggests
diskshadow, thenadd volume <volume>, thencreate. Run this only on a server where creating a shadow copy during the test is acceptable.
Example (illustrative). APP01 backs up C:, E: and the system reserved partition to \\NAS01\backups. The job fails with 0x80780119. The Application log shows VSS Event 4001. vssadmin list shadowstorage shows C: shadow storage on C:, with its maximum nearly reached. The system partition is 350 MB, so the 50 MB minimum for volumes under 500 MB applies, and it has only 30 MB free. The cause is space on that partition, not the network share.
Fix
Not enough free space (0x80780119, Event 4001). Free space on each volume in the job, and on the backup destination, until it meets the minimums above. KB 2851998 names this workaround: "increase the size of the OEM partition on the backup drive". If the shadow copy storage area is nearly full, the Event 4001 page suggests moving it to a different volume.
- Caution: the same page states that when you change the location of the shadow copy storage area "all previous shadow copies are deleted". The vssadmin resize shadowstorage reference also warns that "Resizing the storage association may cause shadow copies to disappear." If users rely on Previous Versions, tell them first.
- The resize syntax from that page is
vssadmin resize shadowstorage /for=<volume> /on=<volume> /maxsize=<size>; without/maxsizethere is no limit.
Existing backup conflicts (0x807800C5 on a target that already has a backup). The community answer in the Q&A thread suggests the error "suggests a conflict of the identical folders named WindowsImageBackup" and asks whether the old backup folder was renamed. Microsoft's wbadmin start backup reference is clear about the risk: a second backup from the same computer to the same remote shared folder overwrites the previous one, so if it fails "you can end up without a backup". Before you rename or move any backup folder, copy it somewhere safe and make sure you are not removing your only good backup. The same page recommends sub-folders per backup on a share, which needs twice the space.
Read timeouts on one volume. The "semaphore timeout" text points at the disk or path that serves that volume, not at VSS. One community answer suggests replacing an external disk and running a new full backup; another suggests checking source files for corruption. Microsoft does not document either as a cause. Check the health of the source and target disks and the path to them before trying anything destructive.
Unpatched Windows 8 or Windows Server 2012. KB 2851998 offers an update that replaces Volsnap.sys (listed versions 6.2.9200.16613 and 6.2.9200.20718). It applies to those releases only and requires no restart or registry change per the page. Newer releases are not in its scope.
Do not add -vssFull to the job as a fix. Microsoft's wbadmin page cautions that it can break the incremental or differential backups of another backup product that tracks the same applications.
Confirm the fix
- Run the job again and check Application log events from source Backup show success, with no VSS Event 4001 or error entries around the run time.
wbadmin get versions -backupTarget:<target>should now list the new version with a current date.vssadmin list shadowstorageshould show used space well under the maximum.- A successful job is not proof of recovery. Restore a few files, and for a system backup test recovery on a spare machine or an isolated virtual machine, before you rely on it.
What to watch afterwards
- Free space on every volume in the job, especially system and recovery partitions; alert before they drop towards the documented minimums.
- Event 4001 from VSS and failed Windows Server Backup events in the Application log.
- Backups to a network share that keep only one version: if a run fails, the previous version may be the one that was lost, so keep a second copy somewhere else.
Read next
Related articles you may want next.
- Backup & RecoveryWindows Server Backup and wbadmin: the limits to know before you rely on themUnderstand Windows Server Backup retention, VSS modes, system-state exclusions and bare-metal recovery limits before relying on a backup.Read article
- Backup & Recovery'The shadow copies of volume were deleted': volsnap events 25, 33 and 36 and shadow copy storage that cannot growVolsnap event 25, 33, 35 or 36 and shadow copies deleted: what each event means, vssadmin checks, and how to resize or move shadow copy storage safely.Read article
- Backup & RecoveryBare-metal recovery for Windows Server: VSS, system state and dissimilar hardwareWhat a Windows bare-metal backup captures through VSS, why system state and bare-metal recovery differ, and recovery planning for dissimilar hardware.Read article
Risks and limits
- These commands have not been run or lab-tested. They come from the Microsoft pages listed below.
- KB 2851998 applies to Windows 8 and Windows Server 2012, and the Event 4001 page to Windows Server 2008 R2. Neither states that it covers current Windows Server releases, and Microsoft documents no cause for 0x807800C5 beyond its message text.
- The Windows Server Backup storage description is from a 2019-dated post written for Windows Server 2008 and 2008 R2. The 2040 GB virtual disk limit it quotes is for that era; later releases were not checked here.
- Other suggested causes of 0x807800C5, such as a target sector size or a share that keeps only one version, are not documented by Microsoft and are left out.
- Community answers in Microsoft Q&A are not Microsoft guidance.
Sources
- The "last backup did not complete successfully" error message when you back up a Windows 8 system (KB 2851998) — Microsoft Support, date not shown, accessed 16 November 2026
- Event ID 4001 — VSS Shadow Copy Creation and Storage Space Availability — Microsoft Learn (archived), 27 January 2011, accessed 16 November 2026
- Windows Server 2012 r2 Backup Error 0x807800C5 — Microsoft Q&A, question dated 27 May 2021, accessed 16 November 2026
- Backup Version and Space Management in Windows Server Backup — Microsoft Tech Community (Jose Barreto), 10 April 2019 (last updated 10 November 2023 per page), accessed 16 November 2026
- Diagnosing Failures in Windows Server Backup, Part 1: VSS/SPP Errors — Microsoft Tech Community (Jose Barreto), 10 April 2019, accessed 16 November 2026
- wbadmin start backup — Microsoft Learn, page dated 2017-10-16, updated 2025-09-22, accessed 16 November 2026
- wbadmin get versions — Microsoft Learn, page dated 2017-10-16, updated 2025-09-22, accessed 16 November 2026
- vssadmin list shadowstorage — Microsoft Learn, page dated 2026-09-07, accessed 16 November 2026
- vssadmin resize shadowstorage — Microsoft Learn, page dated 2020-03-05, updated 2026-02-16, accessed 16 November 2026
- vssadmin list writers — Microsoft Learn, page dated 2018-05-18, updated 2026-02-16, accessed 16 November 2026
This article was originally published on .