After Windows 10 version 1809 update Build 17763.1, my Backup and Recovery now shows error 0x80070013 and will not backup as before

Thanks for the information, Michael.

This seems a bit confused, on Microsoft's side, however.  The System Image Backup feature has been working fine through build 1803 and the UI still shows it in 1809, it just happens to fail with an unexpected error.  If the error was "feature has been removed" that would be one thing, but it is not saying that ... the error claims that the drive is write-protected, which it is not.

The Wikipedia article on Windows' Backup and Restore (https://en.wikipedia.org/wiki/Backup\_and\_Restore) says that Backup was deprecated in Windows 8, removed in Windows 8.1 and then restored in Windows 10.

I also found this article -- https://support.microsoft.com/en-us/help/4034825/features-that-are-removed-or-deprecated-in-windows-10-fall-creators-up -- which states that System Image Backup is deprecated, but the UI in control panel gives no indication of this.

I may look into Macrium based on what you have said, but it seems to me that this is not a case of a feature being deprecated ... it seems to be simply a bug.

I do use File History, but that will not help me much if my primary hard drive dies.  I have used Windows Backup to do a whole drive restore in the past and it was a life-saver.  If they do remove this feature, I will miss it.

Hello,

I strongly recommend that you use File History to back up or restore your files, but if you STILL wish to create system images:

1. Right-click the Start button, and then click Command Prompt (Admin) / Windows PowerShell (Admin).
2. Type the following command and press ENTER; for example:

WBADMIN START BACKUP -backuptarget:e: -include:c: -allcritical -quiet

Note that E: may be your external hard drive.

Best regards,

Michael Higham

1: Will the Windows 10 W7 restore detect and process this output as though it had been created by Windows 10 W7 Backup?

2: It seemed to complete very quickly compared to Windows 10 W7 backup. Any comment on that?

Thankyou.

Hello,

Yes, if you use System Image Recovery on Windows Recovery Environment. Or if you use Windows 7's Back-Up and Restore Centre and click "Manage Back-ups".

File History is a quick process; it only backs up your personal files.

Windows 7's Back-Up and Restore creates a shadow copy before backing up files.

Best regards,

Michael Higham

Reviewing the log located in the folder C: \ Windows \ Logs \ WindowsBackup I was able to reach the following conclusion:

WindowsBackup consists of 2 stages depending on the configuration that each one selects, if "let Windows choose (recommended)" was selected, the program creates a system recovery image as the first option and from the second it executes a copy of the files of the user. When checking in the logs folder you can see two files per WindowsBackup execution, one indicates the result of the creation of the recovery image and the second indicates the result of the copy of the user's files. By reviewing each file you can verify that the creation of the recovery image ends correctly, and the failure is presented in the backup of the user's files, it is important to highlight that the user's files are also contained in the recovery image, only that the frequency with which this image is created is less than the copy of the user's files.

After finding this information I proceeded to change the configuration of my WindowsBackup, where I select "let me choose" and there I just select "include an image of the system of units" and uncheck everything else, the program ran without errors.

Finally to confirm that everything went correctly, make a total restoration of the computer with the last image of recovery just created and everything was correctly.

Although the copy of user files is a very important option, I have it covered by also activating the file history that keeps a copy of each file every time they are modified.

I hope this discovery can help you all

I would prefer Microsoft to fix the bug, rather than this techno babble gobbledegook excuse workaround.