Hi, I hate to be a party pooper, however the method referenced in Dc3's post #9 will not work, I sure wish it did, would make life so much simpler.
There are two problems. first is the cmd asks to remove a package from c: drive, (dism.exe /image:c:\ /remove-package) this makes sense since the OS is typically on c: drive, unfortunately the RE is a virtual drive, and in this diagnostic mode, it is almost never the c: drive that is assigned the OS. So the cmd will fail.
We need to find the drive the OS has been assigned in the RE and use this drive letter in the cmd, to do this at the x:\windows\system32> prompt we first type:-
bcdedit |find "osdevice" (press enter), this returns osdevice .......... partition x (where X is a drive letter) it is this letter we need to use in the cmd:- dism.exe /image:c:\ /remove-package, typically in most win 10 this drive letter is d:
And secondly the problem can be partly written data to the manifest file in winsxs, this will cause reset failure and corrupt further downloads, so in the RE we need to load a registry hive, delete a registry entry, before we remove the package. I wrote the only fix for this, unfortunately it appears to frighten users and has not been employed, I don't really blame users... MS need to automate this, in a fix it. The full fix is here:-