Windows Automatic Repair Loop - Win 10 and HyperV Server - 6 Possible Solutions

solution to the windows automatic repair loop caused by failed updates or power loss. Error message BAD_SYSTEM_CONFIG_INFO , no minidump created. First two solutions are fairly straight this is to either run startup repair from the automatic repair window or x:\sources ecovery\ or use the last known good configurations. Next we want to copy the contents of the regback folder under C:\windows\system32\config egback into the current registry folder C:\windows\system32\config to replace corrupt registry with a backup. We will also manually delete pending update packages from registry or rename the file to correct the issue can also be used to revert pending actions and updates and restore the health of your windows image when scandisk sfc and check disk do not work. as always leave a comment if you get stuck and I will try and help you out.