Startup repair cannot repair your pc , the cause is System OS booted successfully

jraju said:

Interesting that discussion is on minute technical details. But When I entered , the command in x: bootrec /fixboot and it completed, does it not show that the command is executed correctly or only shows as executed . When I used this bootsect /nt60 sys. Does it not complete, the command by rightly doing the command to be accessible by fat32 system. Why microsoft is blocking the command of this type. fixmbr and fixboot are the essential commands to be used by users in any case of boot failures. Please say, if the command worked correctly or not. Moreover, what about system repair cannot repair my computer messages. If it shows, boot of OS successful as reason , it seems the log is not correct then

Click to expand...

Why are you still using bootrec /fixboot command you already executed also why are you not creating EFI system partition?

This command has been blocked by Microsoft: "Access is denied" - Windows 10 version 1709 (October 17, 2017) and newer installation media. And Windows 11 installation media.
Please see this link, the command is still valid and it updates the boot sector

why are you not creating EFI system partition?
I think the ESP partition is the EFI . This is also marked yellow by a fellow member in his reply.

jraju said:

my system OS booted successfully.

Click to expand...

Can the computer boot to the desktop?

jraju said:

why are you not creating EFI system partition?
I think the ESP partition is the EFI . This is also marked yellow by a fellow member in his reply.

Click to expand...

Did you change the EFI System Partition name to ESP is this why you believe this ESP partition is EFI System partition?

Hi, Freebooter, I have not made that partition . It is already in existence when I bought the pc, from Dell.
Please also see the disk management . It lists that but not showing as ESP. When you use list volume command, it shows as ESP.

jraju said:

Hi, Freebooter, I have not made that partition . It is already in existence when I bought the pc, from Dell.
Please also see the disk management . It lists that but not showing as ESP. When you use list volume command, it shows as ESP.

Click to expand...

Have you repaired EFI system partition like i showed at video at Post #2?

FreeBooter said:

Did you change the EFI System Partition name to ESP is this why you believe this ESP partition is EFI System partition?

Click to expand...

ESP actually IS an EFI partition. Another way to put it: Disk management simply uses the EFI acronym.

jraju said:

fixmbr and fixboot are the essential commands to be used by users in any case of boot failures.

Click to expand...

jraju said:

Please see this link, the command is still valid and it updates the boot sector

Bootsect Command-Line Options

Bootsect Command-Line Options

learn.microsoft.com

Click to expand...

A GPT disk works significantly differently than an MBR disk.

You don't need to care about the boot sector (LBA 0) of an MBR disk because you have a GPT disk.

Below is the best guide I found.


MBR

MBR stands for Master Boot Record. This partitioning scheme is closely tied to the BIOS, and as such, also traces its history back to the IBM Personal Computer. The MBR saves all meta-data about the disk in a single data structure stored at the start of the disk. The name MBR is used exchangeable to refer to both this data structure and to the partitioning scheme as a whole.

GPT

GPT stands for GUID Partitioning Table. It was developed by Intel in the late 1990s, and ended up becoming part of the UEFI specification. GUID stands for Global Unique IDentifier, and refers to the unique strings that are used in this scheme in order to uniquely refer to the different partitions included in a disk.

The Protective MBR (LBA 0): This area is used to prevent disk utilities from mistaking the GPT disk for a MBR one. This sector is a fully pledged MBR on its own. However, it contains a single partition entry of type GPT (0xEE) which encompasses the whole disk (or 2 TiB, whichever is smaller). Legacy disk utilities which cannot read GPT tables and expect a MBR table, will read this protective MBR and realize the whole disk is used up by a partition of ‘unknown type’, thus avoiding an erroneous data overwrite. On the other hand, disk utilities that are only aware of GPT, can check this protective MBR and stop any further disk manipulation if the MBR does not contains the single entry of type GPT.