[SOLVED] Unable to install cumulative updates since September (Windows 10), error 0x800f0922

[yonic_soseki]

Since September I've been unable to install any cumulative updates.

Things I've done:

• DISM.exe /Online /Cleanup-image /Restorehealth (completed succesfully)
• sfc /scannow (ran after DISM.exe command), it apparently fixed something, but according to the CBS log it was just a simple shortcut to OneDrive.
• Ran the following script to restart Windows Update services (BITS, appidsvc, etc), although I also tried doing this with the Windows Update troubleshooter.

In the attached zip file, the CBS logs pertaining to the updates are in the CBSPersist logs, while the regular CBS.log file is from SFC.

The situation seems very similar to this previous issue, so I suspect that it's got something to do with the System Reserved partition size, but the Disk Manager tool doesn't display it. diskpart does seem to display it, but it's only 16MB in size. Maybe it's too small? Also, my system partition is located on drive 2 instead of drive 0, so I'm not sure if the layout may be causing something strange.

I've been having other issues regarding Quick Boot, but it seems to have nothing to do with this.
The following screenshots are in Spanish:

 

[yonic_soseki]

I think I was on the wrong track about expanding the System Reserved partition, in that I should expand the EFI system partition instead.
So I expanded it to roughly 650MB in size, but the update process keeps failing after reaching 97%.

I do have some drives with leftover installs of Windows (Disk 0 and Disk 1) listed prior to this one (Disk 2), but only the one on Disk 1 has another EFI partition, but I don't think that's the cause of it.
As for the one I'm using right now, it's a single boot to Windows 10.

Also, I ran ComponentsScanner, but it found nothing wrong.

I'm attaching the new CBS logs here. The forums are complaining about the filesize so I'm sending it in two parts. I'm also attaching the ComponentsScanner log just in case.
Hope that helps!

 

[yonic_soseki]

I'm not sure whether if there's anyone who has checked my issue yet, but I assume it got under the radar (probably replying to the post instead of editing my first post might have partly caused it). I appreciate your effort on fixing everyone else's, though!
At any rate, hopefully this time I'm not catching everyone too busy.