Automatic Repair Loop, Your PC did not start correctly

Blblr · 08 Aug 2019

Hello! I've ran into a bit of an issue, I can't seem to boot into windows.

My system is uefi, windows x64 1903 build and I am stuck in automatic repair loop and can't even boot into safe mode, automatic repair starts immediately after trying to boot into safe mode.

I followed the steps from this thread: Unable to boot; 0xc000000f error on start, chkdsk found no errors, sfc /scannow reported no issues as well. However, I can't seem to use bootrec /fixboot, I get "access is denied" no matter what I do, /rebuildbcd and /scanos doesn't work, it detects 0 windows intalls, but when I rename v:\efi\microsoft\boot\bcd to bcd.old and use /rebuildbcd, it detects my windows as D:\windows (even though my windows was installed using the c: letter), but after rebooting I am still getting preparing automatic repair message and /rebuildbcd no longer works.

Following further instructions on the previously mentioned thread, trying to backup registry, I noticed that my d:\windows\system32\config\regback folder is completely empty (however, files bbi, bcd-template, components, default, drivers, elam, sam, security, software, and system, are in the d:\windows\system32\config\ folder) missing default, sam, security, software, etc.

I am lost here, I have no idea what to try next, I even tried using "Reset this PC" via troubleshoot, but that too gave me an error: "There was a problem resetting your PC. No changes were made."

What could be my next steps? I don't want to lose all my files. Any help is appreciated!

dalchina · 08 Aug 2019

Did this start immediately after upgrading to 1903 or at an arbitrary point after upgrading?

Following further instructions on the previously mentioned thread, trying to backup registry, I noticed that my d:\windows\system32\config\regback folder is completely empty

That is to be expected- I discovered this problem back when 1803 came out I think- MS disabled the reg backup function. There's a recent long thread about enabling it, but that's irrelvant to your situation.

can't even boot into safe mode

Conventionally you have to be able to log in to boot to Safe Mode.

However you can force a PC to boot to safe mode using
bcdedit /set {default} safeboot minimal
from a command prompt with Windows not running.
E.g. boot to command prompt using a Windows 10 bootable medium to boot your PC

You can try:
- booting your PC from a Win 10 bootable disk and running Startup Repair
- booting your PC from either
a Macrium Reflect boot disk
or
Kyhi's boot disk with MR on it
Toolkit Item: Kyhi’s Rescue Disk – Win10.Guru

and having started MR, run its Fix Boot utility

You can check your disk by booting your PC using Kyhi's disk and running HD Tune (Health and Error Scan tabs).

Blblr · 08 Aug 2019

@dalchina, thank you for taking your time to reply. The problem occured at a later point, way after the 1903 update was installed. However, I noticed that I still kept getting this update even after it was installed (for a few weeks now I believe).

I tried to boot to safe mode using the command you provided, but it still jumps to automatic repair, so no luck there.

I did not mention, but I did try running Startup Repair from win 10 bootable disk that I created using Media Creation Tool, but that too didn't work. I also tried Kyhi's Win 10 recovery tools, it asks me if I want to restart my pc, I select yes and nothing happens, it also doesn't detect my windows installation, even when adding one manually using the MR tool, and rebooting does not help.

I will try running HD Tune and report back asap.

dalchina · 08 Aug 2019

I also tried Kyhi's Win 10 recovery tools, it asks me if I want to restart my pc, I select yes and nothing happens,

Did you actually succeed in booting from that disk to its unique desktop with shortcuts to some of the tools provided on it?
You can see a picture in the link I provided.

You have to create a bootable disk from the iso file you have downloaded, either using a sequence of command prompt commands or a free tool such as Rufus.

Using that you can also view your disk using a partition manager- if indeed your disk is accessible- and of course using file explorer as the disk provides a version of Win 10.

FreeBooter · 09 Aug 2019

If you open the log file, you’ll be shown details of all the tests performed by Startup Repair, with any errors discovered detailed. We can use this information to help diagnose and get to the root cause of the problem.

To open log file from the Windows Recovery Environment, click and open the Command Prompt. When the Command Prompt is open, type Notepad and press Enter key to open the Notepad application. The Startup Repair log file is located at:

Code:

C:\Windows\System32\Logfiles\Srt\SrtTrail.txt

You will need to navigate to the drive on which you have Windows installed (usually the C: drive) to see the SrtTrail.txt log file.

Blblr · 09 Aug 2019

@dalchina, yes, I am able to fully boot to its desktop environment. There I can see my windows partition recognized (mounted) as C: drive, not as D: (when I am in windows recovery mode), and I can browse all my files, they seem to be fine.

HD Tune showed no damaged blocks, the drive is healthy.

I added a new entry using easyBCD to see what happens: after rebooting I can now choose two OS to boot from, if I choose to boot from the newly created entry I get an error: File: \windows\system32\config\system; Status: 0xc0000225; Info: The operating system couldn't be loaded because the system registry is missing or contains errors. I remembered I changed components, default, drivers, etc to components.old, default.old, etc. So I restored them and now I am getting a different message: Status: 0xc000000f; Info: An unexpected error has occurred. But booting from the old entry I get straight to automatic repair.

@FreeBooter, hello, I have attatched the SrtTrail.txt file.

dalchina · 09 Aug 2019

Good.. now using Kyhi's boot disk, run Macrium reflect, and then run its Fix boot utility, as the Startup Repair log tells us nothing useful.

However, what you say about changes you have made and
The operating system couldn't be loaded because the system registry is missing or contains errors.

suggests this will fail similarly.

Do you routinely use disk imaging as is so often recommended here, and do you have a recent disk image?

You have an outside possibilty of running System Restore having booted your PC from your Win 10 boot disk via Repair your computer and following the prompts.

Blblr · 09 Aug 2019

When I run "Fix Windows boot problems" task it displays: EFI partition found on disk 1; Removing old BCD; Creating BCD for C:\WINDOWS; and then asks me if I want to restart my PC, clicking yes only closes MR, after rebooting manually I am prompted to "Choose your keyboard layout" and then I get the options to troubleshoot or turn my pc off.

I do not use disk imaging.

zbook · 09 Aug 2019

What are the status of the important computer files?

Had you used Kyhi boot rescue to backup files?

Have you considered a reset save files equivalent (reinstall drivers and applications)?

Which chkdsk switches were used?
Which scannow command was used?

Had you consider formating the EFI boot partition and reinstalling the boot sector?

Often bootrec /fixboot access denied troubleshooting steps fail as regback is no longer automatic.

dalchina · 09 Aug 2019

Leaves System restore having booted from Win 10 installation disk as I suggested - if youhave any restore points.

I do not use disk imaging.

So hopefully you will have now realised this is a good idea, as it means you can recover quickly yourself without a lot of time and tech support, assuming you have a relevant recent image.

Further, the image is a full backup from which you can copy files. Thus you can recover even from catastrophic disk failure.