Backup and Restore copies files first and builds the system image afterwards. When the job fails at that second stage with 0x8078005D, the file copy is usually fine and the image is not. The cause is normally shadow storage on the target, a drive that drops out, or a target file system that cannot hold the image.
The code is produced by the imaging stage rather than by the file copy. In the log you will see the volume snapshot succeed and then the image write fail, often within seconds of each other.
Three causes cover most cases: the destination is formatted exFAT or FAT32 and cannot hold the image file, the destination has less free space than the system volume needs, or the external drive disconnects when the write becomes sustained.
Because the failure happens after the file copy, users often assume the backup succeeded. Check the job status and the destination folder; a task that stops during imaging leaves no usable system image.
Confirm that the destination is NTFS and that it holds at least the used space of the system volume. An image is large, and a destination that only looks generous in gigabytes may still fall short.
Look at the shadow storage allocation on the destination volume. A small maximum size can stop the image writer even when free space is plentiful.
If the target is a USB drive, disable selective suspend for USB devices and stop the drive from powering down. A single disconnect during the image phase produces exactly this error.
Restart the Windows Backup service and run the job once with the destination freshly formatted as NTFS. If it fails again at the same point, the built-in tool is not the right path for this machine.
A block-level image written by a dedicated tool does not depend on the Backup and Restore imaging components, and it can be verified by mounting the result.
Keep at least one working image before you change anything else. A failed backup job is not the moment to experiment with the only copy of the system.
Qiling Disk Master writes a block-level image of the system and boot partitions and reports its own progress, so a failure is visible at the stage where it happens rather than at the end.
Open the program and select System Backup. It includes the EFI or System Reserved partition automatically, which is what the built-in job was struggling to write.
Choose an internal disk or a USB drive formatted as NTFS. Check the free space against the used space of the system volume before you continue.
Review the task summary and start the job. Keep the drive connected and the machine powered until the progress bar finishes.
Open the image afterwards and browse a folder from it. An image that cannot be browsed is not a backup, even when the job reported success.
Often yes, but the job is reported as failed. Do not rely on it; run a complete job again after fixing the imaging stage.
Not with the built-in imaging tool. Format the destination as NTFS, or use a tool that writes its own container format.
Intermittent failures usually come from the USB link or from shadow storage limits. Both produce a failure at the image stage rather than at the start.
No. The same imaging failure appears on Windows 10 and on Windows 7, where the Backup and Restore tool originated.
For the wider backup routine behind this job, see how to set up Windows Backup.