On the next startup, try taking system image backup and see if the error is now fixed.
When the above command is executed, you have to access the DISKPART tool in CMD.You can change the drive letter as you want. In the above command, C: is the current system drive, while F: is the new partition of an MBR disk. Now, enter the following command in CMD: bcdboot.exe /s C:\Windows /s F:.First of all, open the Command Prompt with administrator privilege.To make a system volume on a primary partition of an MBR disk, you can use the following steps: You can try creating a new system volume and then see if you are able to take a system image backup. Ensure that System Protection is enabled.Extend System Reserved Partition or Recovery Partition.
Here are the methods you can try to fix Windows Backup Image Error 0x80780113 on Windows 11/10: Let’s check out! Error 0x80780113, Not enough space to create the volume shadow copy, The backup failed Now, if you are facing the same error in any scenario, you can resolve it using the methods we have listed here. It can be caused due to bad sectors on your drive, too many junk files, faulty disk drivers, etc. While the error message indicates low space for creating the backup image, there can be several other reasons for this error. This error prevents you from successfully creating the backup image.
However, some users have experienced an error message “ Not enough space to create the volume shadow copy” along with error code 0x80780113 while creating a Windows backup image.
Windows offers a built-in Backup and Restore tool which is primarily used for creating a full system image backup so that you can restore the system to its original status if Windows gets corrupted. To resolve this problem, in the VM's settings, change from Production checkpoints to Standard on guests that are domain controllers running pre-2016 OS, when the Hyper-V host is running Windows Server 2016.Here is a full guide on how you can fix the error 0x80780113 when the backup has failed on Windows 11/10. The problem may be related to the new Hyper-V Production Checkpoint architecture.
This is a known issue for pre-2016 Domain Controllers running in VMs on 2016 / Win10 Hypervisors. Hyper-V solution 2 - Change the Production checkpoints to standard Mistakes can render the system inoperable. Warning: Changes to the registry should only be performed by an experienced Systems admin.