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

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.

(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?

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.

File History does not work.  I found a fix which involved turning OFF System protection and turning it back on.  WARNING:  This will delete all your restore points..   After turning Systerm Protection back on, create a restore point and you will have File History back.  The problem for this fix is if you create another restore point, it breaks file history again!!   Why would Microsoft remove this feature?  And another thing is DISM runs every day and it seems to be trying to fix The File History, but it can't find a system image to fix it.   This issue started after the October Windows Update.  

Oh what I mean about file history, is the the files that used to be kept on the C: disk in the Recovery Partition, like windows 7 used.   Please, stop changing versions and put out a  SP1 (Service Pack)

I've never used File History, not wanting to have an external HDD plugged in all the time (but I know it will wait for it to be plugged) or to give Windows extra stuff to do. Also, I don't need a history of the changes. Does it only backup the user folders (Documents, Downloads, etc.) or does it make a system image too?

A system image also contains those folders & the files, unless they are on OneDrive with On-Demand turned ON & individual files are online only (right-click a file, & select "free up space" for that). I mounted my latest .vhdx that had files online only & could not access them in the image. Only names & properties were there, but not the files. Then I mounted an image that had them available offline when the image was made (access one in File Explorer & it downloads) & they were there in the image.