Windows 10: Laptop will not boot up after running fixing C drive

I have a external monitor because the screen on the laptop only displayed a white screen on one side and a blue screen on the other today there was a message that the C drive needed repair so I hit the okay button the computer shut off and when it booted backup nothing was displayed on either the laptop or external monitor so I change the screen on the laptop when I fired it up it went into repair C drive mode and that all displayed fine on the new screen then I got the message that it had not started properly and needed to be restarted so I did and since then has basically done nothing

:)

 

GPT disk conversion for both data drives and C drive


Macrium Rescue disk can be used to convert from MBR to GPT and vice versa without doing a fresh install of Windows.

1. Download Rescue6.1.1081X64.iso - Google Drive and use Rufus to create a bootable USB disk. Skip this step if you've already created the Macrium Rescue disk.
2. Download: BootEFI_Only-00-00.zip - Google Drive . Unzip to an external or an internal HD
   NOTE: This is a copy of the first 3 partitions of my current Windows 10 x64 (450MB Recovery, 100MB EFI and 16MB MSR)
3. Boot up Macrium Rescue disk and create a backup of your current Windows to another internal/external HD. It serves 2 purposes: you'd have a backup of your current Windows in case things go wrong and then use it to restore the C drive on the next steps.
4. Next, switch the BIOS to UEFI and use Macrium to restore the first 3 partitions downloaded in step 2 to your current MBR Windows. No need to convert or Format, Macrium will do it.
5. Again with Macrium, select the backup image from step 3, and copy back the C drive after the 3 partitions.
   After this step, you should have: 450MB, 100MB, 16MB and C drive (GPT partition scheme)
6. From Macrium, click on Fix the Windows Boot Problems
7. Reboot. Your Windows should be in UEFI mode.

 

How does Windows boot to advanced recovery option e.g. command prompt?

- that gives me a 454 'Unexpected error' This tells me that the BCD is partially corrupted.

The commands: shutdown.exe /r /o /f /t 00
or: %SystemRoot%\System32\Cmd.exe /c reagentc /boottore&shutdown /r /f /t 00
should boot into Recovery if everything is configured correctly.
FYI, If Windows is configured correctly:

1. If Reagentc is disabled, you still can get into Recovery but with limited options.
2. If Reagentc is enabled, you'll get all options.
3. If you boot Windows using Recovery USB stick, You'll get into Recovery with couple of options missing.

Here's my suggestion if you want to try:
OPTION 1: Will save the trouble of re-install Windows.

1. Download the image of my first 3 partitions (450MB Recovery, 100 MB EFI partition, and 16MB unformatted primary)
   EFI_Boot-00-00.7z - Google Drive
2. Run Macrium and restore the image from step 1, overwriting your existing 1st three partitions, leaving C alone.
3. Delete the 490MB Recovery partition.
4. From Macrium, run fix boot problems.
5. Reboot. Open Admin command prompt then run Reagentc /info to make sure that it is enabled. If not, enable it.
   if failed to enable, reboot and try again.

OPTION 2: Assuming you've already had Windows backup with Macrium.

1. Wipe out the first 5 parttiions. (450MB, 100MB, 16MB, C Drive, 480MB)
2. Fresh install Windows 10
3. Restore C drive from backup image, run fix boot problems
4. repeat step 5 from OPTION 1 above.

 

laptop doesnt boot automatically

This is what happened.

1. Did a repair install and later disabled hibertnate in CMD.
2. Enabled legacy option ROM in BIOS.
3. After a few times startup ( i used the system in such mode for 5 days), changed boot option back to default.
4. Vola!! It boots automatically to win10 without any keypress. Tested it with many starts to confirm the same.
5. Re-enabled hibernate option using CMD and later selected Fast Startup.
6. System booted normally, without the need for any keypress.

I do not know exactly whether such steps resolved the problem or what else happened, hence cannot suggest above steps.

Many thanks to all members who helped to troubleshoot problems.