WIndows 10 boots up to Recovery error code 0xc000000f, loading the offline installation with NTLite says it encountered corrupt registry

[Mingle]

I was shutting down my PC and it shows Repairing disk errors on Windows 10 boot screen, then restarted into this blue Recovery error screen.
I have Rollback Rx Pro installed, but no matter what snapshot I restore my system to, I can't boot.
Running sfc /scannow and DISM on a WinPE usb key and pointing it into my offline Windows 10 install results on
"Windows Resource Protection could not start the repair service" and DISM error 193 "%1 is not a valid Win32 application"
The WIndows 10 system is on build 19044 (21H1) and I have a 19045.1949 (22H2) Windows 10 ISO.

 

[Mingle]

I fixed the DISM error 193 by extracted the folders \Windows\System32\downlevel and \Windows\System32\Dism off the \sources\install.wim from the 19045.1949 ISO and overwriting the files on my Windows installation using Parted Magic v2021.11.17

DISM.log does report DEVICES, SAM, SECURITY, and SYSTEM registry hives are corrupt, so I restored known good copy from \Windows\System32\configfix directory that Rollback Rx Pro created. However configfix does not contain DEVICES, so I have to restore it from \sources\install.wim for now.

I am currently running DISM off a Windows To Go VHDX and it's currently running.

 

[Mingle]

SFC just quits with:

Beginning system scan.  This process will take some time.


Windows Resource Protection could not perform the requested operation.

And DISM just quits with:

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19044.1889

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at X:\Windows\Logs\DISM\dism.log

CBS    Cannot add wim: file source because it is not supported during offline servicing [HRESULT = 0x800f082e - CBS_E_NOT_ALLOWED_OFFLINE]

Redirecting
Oh.. so DISM is useless...

The other one is for using a mounted WIM, and it's equally as useless...

No, DISM wasn't able to contact WU even if the Windows To Go VHDX can see new updates.