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

Hello Jerry,

                      I tried your suggestion and the results were the same. I shut off system protection and rebooted. I switched system protection back on and ran a backup. Same result and error message. I wish someone in Microsoft would come up with a answer to this or have a backup feature that works properly. I guess we must wait.

(Sorry-but I gotta turn Flame On!)

OMG, the more I play around with trying to do simple sys-admin tasks on this questionable 'upgrade' to microsoft's premier O/S the more disappointed I am (I'm preaching to the MS Choir, right).  Is the Windows Server 2019 as bad? The default behavior of this new 'File History' method of a built-in system backup wants to save just your C:\Users\ file structures ??  Who just stores valuable working office and productivity file in C:\Users\ ? So MS is moving even more towards requiring paid apps (like the monetized bloody smart phone world) approach to get full functionality out of their new improved O/S.  Besides the raft of networking problems which I've struggled with for two or three days after deciding to take the plunge and make the switch from a good 'ole stable Win 7 Pro environment to installing Win 10 Enterprise on a nice fresh SSD, I find so many deprecations of previous functions and methods (e.g. MS's mandate to Drive Map all of your shared folders, don't believe they can implement a secure File Explorer -> Network category to be able view all your drives at drive root level !!!) and now I find Win 7 style System Backup and Restore replaced with Win 10 'File History' where I have to add each and every folder I want backed up?  WTF's going on in Redmond.  I don't suppose implementing an efficient filter for only flagging Delta Changes for backups would even be on the distant galaxy radar for MS, right?

So far nothing has solved this problem except for using a admin back up command,

wbAdmin start backup -backupTarget:D: -include:C: -allCritical -quiet

D is my external drive and this was run with powershell with administrative privileges. I wish MS will solve this issue.

Hi Irishman1

Thanks for your tip....

I am running your command now. It has been running for quite a long time, but for the last 10 -15 mins it seems to be in a loop, putting out the message

Compacting the virtual hard disk for volume OS(C:), completed (98%).

over and over again.

This was after the process reached

Creating a backup of volume OS(C:), copied (99%).

Do you think it will finalise properly???

If it does, is the backup created by this command able to be used to restore single, individually specified files, in the case of emergency. 

Regards.

Not sure but when I did this backup command took a long time but it worked. I have not tried to restore anything yet, I hope I do not have to.