Hello Adari,
Thank you for posting question on Microsoft Windows Forum!
Based on the issue description as well as the provided error code 0x8078001F which might indicate that Windows Server Backup failed at the underlying Volume Shadow Copy Service (VSS) or Shared Protection Point (SPP) layer. Before Windows Server Backup can write data to your destination, it calls VSS to freeze system state and create a point-in-time snapshot (the "protection point"). When this snapshot fails or times out, the job aborts immediately.
The suggestion here is to check VSS writer health by opening an elevated Command Prompt or PowerShell and check for failed shadow copy writers by running this command vssadmin list writers then looking through the output for any writer showing a state other than [1] Stable or displaying an error (such as Timed out or Failed). If any writer is in a failed state, restart the corresponding service. You can do this via the Services console (services.msc). Right-click and restart the Volume Shadow Copy and COM+ Event System services. Alternatively try to reboot the server. A full server reboot can resolve transient issues that cause VSS writers to fail, especially those tied to critical system services that cannot be restarted easily . After the reboot, run vssadmin list writers again to confirm they are stable.
Another suggestion is to verify Shadow Storage & Volume Free Space. Since VSS requires sufficient unallocated space on every volume being backed up (including hidden partitions like the System Reserved or EFI partition) to build the differential shadow snapshot. Making sure that source drives have at least 10–15% free space. If backing up "Bare Metal Recovery" or "System State", the System Reserved Partition needs at least 32–50 MB of free space for shadow copies.
Another point worth checking the underlying event logs to pinpoint the component raising 0x8078001F by opening Event Viewer (eventvwr.msc). Then go to Windows Logs > Application. Filter by Event Sources: Backup, VSS, and SPP. Locate the error entry matching 2026-05-18T05:56:51Z. The event description right before or after this timestamp will state the precise volume or service that blocked snapshot creation.
You can refer the following article for more information.
Hope the above information is helpful!