SFC said it fixed some stuff, but not everything. The log file is over 3 MB with 65,000+ lines. I see messages like:
00000070 Manifest hash for component [l:93 ml:140]'amd64_117b9fa0caf6ec4b0f6cf1b24dda2fc4_31bf3856ad364e35_10.0.19041.1852_none_c279a35b0b2bfd66' does not match expected value.
000000a8 (F) Unable to load manifest for component [l:93 ml:140]'amd64_1751b9d651379d8e2380ace0b524d314_31bf3856ad364e35_10.0.19041.1852_none_1ab8694852e70f5f'
0000ea1f Hashes for file member [l:23]'PresentationHostDLL.dll' do not match.
Expected: {l:32 ml:33 b:308f9597825f518e96f40a67b9b8ef89208a43cc7ca5b6a6a9252a4f1878f19e}.
Actual: {l:32 b:b56843886ad61b22f7dbd4f7d5f9b3aa0bd919fdc7d8bdb45477e5218a6070d0}.
0000128e [SR] Cannot repair member file [l:12]'usbprint.sys' of dual_usbprint.inf, version 10.0.19041.2193, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, hash mismatch
00001928 [SR] Could not reproject corrupted file ??\C:\Windows\System32\Microsoft-Windows-AppModelExecEvents.dll; source file in store is also corrupted
There are tons of these.
Now I just get the BSOD when I try to boot.
I am using a recovery USB that I created from a different computer (same version of Windows 10); don't know if that matters.
It's almost as if it broke mid way through doing a Windows update. I didn't get any reports of any viruses before it stopped booting.