Windows 11: Repeated System backup image failure

Question

Hi there

I have created probably over 100 system backup images on diverse Win 10 & 11 computers, with 99.5% running with no problem. Same on this Win 11 Dell notebook, with a back every 2 or 3 weeks. The last 4, including one just a few minutes ago however seem to run normally until the backup is about to finish, then I get errors, shown in the screenshots. I ALWAYS use the computer for my normal work during the process in all these cases and so do not know what volume or process is being referred to, which is very frustrating. The first error is what I unexpectedly got the other day and earlier on yesterday. The last successful backup was about 2, 3 weeks ago, leaving about 80GB free space on the drive.The notebook has 2 partitions, other than the ones Windows created itself.

After the first backup failing yesterday as shown in the first screenshot, I looked around online what could be leading to those errors. I implemented some recommendations like running sfc /scannow (corrected some minor errors) and then DISM Restorehealth (successful).I run Chkdisk, which found no errors on all the partitions on external HDD, then in fact decided unconnected to this to reduce files on the to be backed-up SSD by about 10GB, making the possible system image smaller. This means a fresh backup would leave about 90GB free space.

So I was shocked after running the backup image creation again to get this time a different error, shown in the lower screenshot. The last successful backup left about 80GB. How can the new find the possible 80 + 10 GB cushion on a 400GB partition too small?
I first left it at that.

On the 3rd day, today, I decided to look into the space issue again. The WindowsImageBackup folder happened to also have a backup of another notebook, about 76 GB and both have peacefully co-existed. I decided to move this OTHER system image to a different partition, which would theoretically leave the 400GB partition empty IF I happened to delete the one failing to be fully created.
I noted even though it showed no visible files, it was not empty all with about 130GB occupied!! I decided to format it, defragmented & carried out a chkdisk ALL showing it was healthy, then started another backup. There was no way lack of space or other error could play a role on a "healthy" disk. Windows Disk Managent & Nuibi Partition Editor Professional both show this partition to be HEALTHY.
It run well, but shocked me at the end with yet another failure message, a different one you can see in last screenshot. At this point, I have no words for this!

What could be going on, as I have said, up to this, the last backup error was not even with this machine and years back and all the last or so 20 backups of the current set-up on the specific HDD have all run with no issue?

The Dell 15 5570 notebook has ALL available Windows & Dell drivers installed. Latest 2025-06 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5063060) on 13th June.

Is there any chance it has to do with the state of Windows itself?

Thank you in advance

Answer 1

Hi

So I moved files from the system partition to another leaving 35.7 GB before I tried again.

It appeared to go well, until the second phase with the black screen reached about 30%. This time after restart, it did not go to 48% like previous times, but just shut itself down.

The error message this time was different as you can see. I have also included screenshots from Nuibi partition editor & Windows **** management.

For the about 224 GB SSD, I do not have the feeling there are any hidden partitions.
As you can see all partitions are considered to be healthy.

During different phases of back-up I have used the 2 commands several times and the 1 or 2 times Scannow has found anything wrong, it has repaired it, though that is the exception as they have both found nothing wrong.

Actually even before all this, I habitually now & then use the 2 commands and they hardly ever find a problem. It is quite mysterious why they cannot repair whatever corrupted files there might be, which I have not had before.

I cannot imagine what could have gone so wrong, unless it is Windows Updates, before the last 2025-05 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5058499) on Juni 01. I do not remember whether the backup was before or after it.

Do the partition images reveal any possible issue? I guess I will try again tomorrow, with Scannow, then ALL DISM commands, not sure what else ...

I have up to now not only just avoided 3 party programs, primarily because the Windows backup has always never failed.

Really strange!

Thank you for your patience ... :)

Answer 2

Since your backups and i place upgrades keep failing even after freeing space and running SFC/DISM it is likely due to deeper system or partition corruption. Try to use Macrium Reflect Free macrium.com/reflectfree to create a system image safely.

Mount the Windows 11 ISO and run setup.exe as admin with logging: setup.exe /auto upgrade /dynamicupdate disable then check logs in C:$WINDOWS.~BT\Sources\Panther\setupact.log for exact failure reason.

Run: chkdsk C: /f /r and check for hidden partitions with diskpart and temporarily disable Fast Startup in Power Options. If upgrade still fails a clean install may be the only fix but back up with Macrium first to recover apps/files later.

Best regards,

Harry

Answer 3

Hi

I thought I could implement your suggestions in phases and today, decided to first look at cloning as one of the many giveaway programs I already have, but never used, is Hasleo Disk Clone Pro. The cloning onto an old HDD run fast and I even tested it, by inserting it into the notebook, though the difference an SSD makes was apparent.

That done, I installed Macrium Reflect Free, though the options before installing were a bit overwhelming and I left out one of automatic booting of the created image (something like that). I hope in case needed, no issues with booting, though I have yet to look into the manual of how to restore.

I hoped to ask you to clarify the last sentence "If upgrade still fails a clean install may be the only fix but back up with Macrium first to recover apps/files later.".

I had also planned, after doing all this to try another Windowsimagebackup today.

Before that, I had wanted to uninstall the latest Windows updates, of 13th and 1st June, but put it off.

The only thing I did was run sfc /scannow, (I think it found nothing) ... expected the backup to fail ... wanted to do the other suggestions in the last 2 paragraphs another day.

Just before I posted this, I watched nervously as the backup of the second partition approached the end, where it had suddenly made a habit of aborting and throwing an error message.

Instead, there was the familiar pop-up asking whether I want to create a system repair disc!

So this time, it worked, not sure why, but I will do more backups in the coming days to see if whatever was causing this is gone.

I also hope in the near future to try out an in-place upgrade, as I expect my Windows, in spite of the many installed programs to be healthy. Will report back.

Thank you & best regards

Answer 4

It’s great to hear your backup finally succeeded. If in place upgrade keeps failing despite all steps then a clean install of Windows might be your only option. Try an in place upgrade again using setup.exe /auto upgrade /dynamicupdate disable

If it still fails a clean install may be needed so you may use your Macrium Reflect image to restore or recover files after reinstalling Windows. Check logs at

C:$WINDOWS.~BT\Sources\Panther\setupact.log to find the exact cause if it fails again. You are making solid progress

Best regards,

Harry

Answer 5

Hi

So after taking a rest, I decided to carry out first another Windowsimagebackup and it run smoothly. Then, I decided to try an in-place upgrade again. I debated using this command "setup.exe /auto upgrade /dynamicupdate disable" right away, but since I was not too sure, whether you just type it in the Terminal and run it, just under the line "PS C:\Users\PCUser>" or one has to give the path of the mounted image where setup.exe is [which is the case if I may ask?] ... I decided to FIRST just run setup without it.

I waited with bated breath as installation reached 30% and rebooted or 48% as the failures where at those points, but fortunately it run smoothly right up to the end. Not quite sure why it went through this time, as the sfc /scannow & DISM run before without errors were also run at least in 2 or 3 cases which failed.

Anyway, since the last 2 image backups and now the in-place upgrade run smoothly, I have no problem and hope this will stay that way.

Thank you for your assistance!