Failed win 10 update from win 7. errors 80200053 & 800700c1

Hi Adottrill, Please follow the methods below and post back with your results.

Method1:
To resolve this issue, follow these steps:
Click Start, and then click Run.
Type cmd in the Open box, and then click OK.
At the command prompt, type net stop wuauserv, and then press ENTER.
Type rmdir /s %windir%\softwaredistribution\wuredir, and then press ENTER.
Type net start wuauserv, and then press ENTER.
Try to install updates again.

Method2:

Please visit the below mentioned MS link for the resolution.
http://support.microsoft.com/default...b;en-us;928228

1) Perform sfc/scannow
2) Check for CBS.LOG file.
3) Search for dll files that cannot be replaced/delete or has found error
4) Using Google.com, search for the site that provides dll files. Download the ones you need and replace them.
5) In order to replace the dll files, you need to give urself --> Authorization properties--> Security(tab)--> Advance, full rights.

Method 3:
Restart your computer and log in "Safe Mode" to install updates and then reboot to log in normal mode.
Windows Vista or Windows Server 2008
To start your computer in safe mode in Windows Vista or in Windows Server 2008, follow these steps:
Click Start and then type msconfig in the Start Search box.
In the Programs section, click Msconfig.exe.
In the System Configuration dialog box, click the Boot tab.
Click to select the Safe boot check box, click Network, and then click OK.

Note The Safe mode with networking option does not work for computers that have dial-up connections to the Internet. You cannot use safe mode with networking support because modem drivers and PC Card drivers do not load in safe mode with networking support.
In the System Configuration dialog box, click Restart. The computer restarts in "Safe mode with networking" mode.
Install the updates.
After the updates are installed, restart your computer in safe mode, and then click to clear the Safe boot check box.
In the System Configuration dialog box, click Restart. This option starts Windows in its normal mode.

Hope this helps.

I'd be very hesitant messing with system files, which are protected, with ownership is to TrustedInstaller. Almost all of the time, trying to restore ownership manually fails and you can still alter, copy, delete them, exactly what malware does. XCOPY will replace the file, but I haven't found a viable solution to the restoration of ownership to TrustedInstaller. Tried Brinks post several times, after performing the steps, it indicates TrustedInstaller has ownership, but file/folder still can be altered, copied, or deleted. Don't know if XCOPY command from Repair Environment would be preserve TrustedInstaller ownership. NoelDP certainly would have the answer.

Have your tried running SFCfix.exe by Niemiro, It recognizes win8, 8.1 & 10, then starts DISM utility. Worth a try, worst that could happen is nothing, best case scenario, it resolves your issues.

I'd try that first before messing with system files.