0xc0000225 registry missing error after using Rufus

Hello,

I have a problem caused by a problem. It started with the most recent Win10 update (from version 19041.685). After the update, I received a 0xc000021a code and could neither boot regularly nor in safe mode. Dism informed me that Wof.sys "encountered a corruption in the compressed file's Resource." That seemed like a fairly common thing, and someone suggested that I use Rufus to try to solve it. Ok. I used an iso from MS and rufus did the rest with a bootable USB drive. Unfortunately, within a minute of getting Rufus going on my computer (to the desktop), it crashed. I immediately rebooted and received the 0xc0000225 code--which makes me long for good 'ol 0xc000021a. The error said the registry was corrupt or missing files. I can still get in WinRE (others with the error couldn't), but I can't do much. SFC and DISM halt immediately; their brief logs providing little insight (to me, anyhow). The two system restore points I had vanished. I rebuilt the BCD, but that did nothing. So I'm lost as to what to do next. I've read that the error often results from the registry not being closed properly, but I have no idea which registry keys would be relevant. Any help would be greatly appreciated

I've attached the sfc log.


Aidyl

RJARRRPCGP said:

Looks like corruption. Possibly a drive failure or unstable RAM.
RAM instability may cause a registry error.

It may also cause a boot loader error before the NT kernel loads as well.

Looks like symptoms of a RAM malfunction or a bad drive.

Thanks for the reply. Both RAM and drive have been thoroughly tested. No problems.

RJARRRPCGP said:

OK, I dunno then!

Yeah, me too.

Hi all,

I have some additional information on the hope that any of it could spark an idea or at least help with some aspect of the problem. I noted in my initial post that after Rufus crashed on first use the computer began crashing at the start of the boot with an 0xc0000225 error. At that point the two restore points I previously had in WinRE vanished and I soon realized the "Reset" computer option was gone too. Another odd thing, WinRE no longer asked for my password to use the elevated command prompt. I'm no computer expert, so it took me a few days to realize a connection, so I ran reagentc and it said that WinRE was disabled! Thanks to an old thread on this site, I got that sorted out---I have no idea what the watered down version of it was. The problem now is that when WinRE loads up now with the restore points and reset option, it wants my password but claims no administrator account (or any other user account) can be found. So the 0xc0000255 problem seems to rear its head again as my windows installation doesn't seem to be recognized. I ran bootrec osscan, which spit out:

Successfully scanned Windows installations.
Total identified Windows installations: 0

And I've found some people claiming to fix their 0xc0000225 BSOD by resolving that. But the resolution seems to be what I did early on by rebuilding the BCD file.

So does any of this spark any ideas? Should I go through the boot configuration process again? Maybe I missed some final step?

Thanks in advance for ANY advice.