Hmm, what we could try is to repair those registry keys from the Recovery Environment when the SOFTWARE hive is load with a different name to make the changes.
See this guide for example:
Utilizing Offline Registry Editor to Repair the Registry
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32
REG_EXPAND_SZ must be:
%SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.3646_none_e932fa0242ee80d9\TiWorker.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32
REG_EXPAND_SZ must be:
%SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.3646_none_8d145e7e8a910fa3\TiWorker.exe
If you're not familiar with such fixes, please let me know? Then I will write some instructions.