dual EFI entries after GPT conversion

Anonymous
2023-02-18T01:49:50+00:00

For reasons too lengthy to detail here, I was unable to use MBR2GPT for converting my current boot disk. Instead, I used Hasleo Disk Clone to clone the disk to another SSD while also converting it to GPT. This worked fine and the new drive correctly shows up as GPT with the shiny new MSR and EFI partitions. However, it left the protected/system EFI directory intact on the drive. My UEFI has been set to UEFI only with CSM=Disabled and yet I can still see entries for both EFI instances. Booting to the GPT partition works fine, but booting to the EFI directory fails. Is it possible (and safe) to either archive/rename or delete the EFI directory on C:\ so that it is no longer detected by the UEFI and disappears from the boot menu? I'm loathe to take any of the additional steps towards a Win11 upgrade without sorting this out first.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2023-03-07T05:38:10+00:00

(1) Even looking at the log, I'm unsure what's up with /SetREImage. But I think it is unnecessary. We'll revisit it if necessary.

(2) It looks like /Disable followed by /Enable would get the job done all by themselves. /Disable moved WinRE.wim from partition 3 into the staging area, namely C:\Windows\system32\Recovery....

"

2023-03-06 17:24:41, Info [ReAgentc.exe] winreCopyWIMBack moved WIM file from \?\GLOBALROOT\device\harddisk3\partition3\Recovery\WindowsRE\ to C:\Windows\system32\Recovery\Winre.wim successfully!

"

Then /Enable wanted to move it into partition 4, which it did recognize to be the Recovery partition. But it found that partition to be too small...

"

2023-03-06 17:24:49, Info [ReAgentc.exe] Checking partition at offset 497942528000, partition number: 4

2023-03-06 17:24:49, Info [ReAgentc.exe] MeetPartitionRequirements Partition details: {Offset: 497942528000, Free space: 467849216, Total space: 487256064}

2023-03-06 17:24:49, Info [ReAgentc.exe] MeetPartitionRequirements WinRE WIM size: 423565200

2023-03-06 17:24:49, Info [ReAgentc.exe] MeetPartitionRequirements Required free space: 478091152

2023-03-06 17:24:49, Warning [ReAgentc.exe] MeetPartitionRequirements Not enough free space req = 478091152 avail = 467849216 offset = 497942528000

2023-03-06 17:24:49, Info [ReAgentc.exe] skip partition because it does not meet WinRE requirements

"

(3) So, let's make it bigger. Mine is 848 MB. Your Disk Management (DM) shows the Recovery partition of 465 MB is followed by 1.56 GB of unallocated space...

Image

Unfortunately, DM won't let you make it larger because it is a system partition. Can you easily add 383 MB to it using AOMEI Partition Assistant? If not, we can try this...

DiskPart <<<Enter DiskPart

Select Disk 3 <<<Focus on the EVO 970

List Part <<<Show its partitions

Select Part 4 <<<Focus on its Recovery partition

Detail Part <<<Show it has the Recovery type code

SET ID=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 Override <<<Basic Data Partition

Detail Part <<<Show the new type code

Exit <<<Leave DiskPart

The 2nd Detail Part should show the new type. It is now a Basic Data Partition. Reboot to be sure the whole system knows. Then open Disk Management, right-click what was the Recovery partition, & see whether you can extend volume to 848 MB. Then make it a Recovery partition again this way...

DiskPart <<<Enter DiskPart

Select Disk 3 <<<Focus on the EVO 970

List Part <<<Show its partitions

Select Part 4 <<<Focus on what was its Recovery partition

Detail Part <<<Show it has the Basic type code

SET ID=de94bba4-06d1-4d40-a16a-bfd50179d6ac Override <<<Recovery Partition

Detail Part <<<Show the new type code

Exit <<<Leave DiskPart

I would Reboot again. Then, try...

ReagentC /Disable

ReagentC /Enable

ReagentC /Info

I hope that will do it. Good luck.

Was this answer helpful?

1 person found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2023-02-23T12:27:49+00:00

(1) This should move {bootmgr} back to the top of DisplayOrder...

BCDEdit /Set {FWBootMGR} DisplayOrder {BootMGR} /Addfirst

That is where it belongs. I don't know how it got to the bottom. Do a full reboot for it to register in BIOS. Then, show us a new BCDEdit /Enum All.

That's nasty that BIOS adds one back after you have deleted it.

(2) The order of the GUIDs in DisplayOrder does not have to be the same as they are in the body of the BCD. In the body, they are in the order the boot entry was created. Moving one to the top of DisplayOrder should also move it to the top in BIOS Setup (after a full reboot). It then becomes the one that will boot by default. That is, it's the one that boots unless you chose another by using the one-time BIOS Boot Options menu. I think in your Asrock that is invoked with F11. (And DEL or F2 goes to BIOS Setup).

(3) I'm confused about your BIOS. I don't have one that complex.

(a) I don't know why it's got 4 Boot Options.

(b) Are you sure it is Boot Option #1 that is executing? Maybe disable ...#2 to be sure.

(c) Show us the contents of ...#2 as you showed ...#1 below.

(d) What is that item that is disabled within ...#1?

Our goal is to have you boot to the EVO that has Windows on it. So, that is the drive that needs to be at the top of the Boot Order in your Boot Option #1. Is it...?...

Image

The way to know that it is the correct Windows partition that is booted is that your C: partition will be 463 GB...

Was this answer helpful?

1 person found this answer helpful.
0 comments
Answer accepted by question author
Ramesh 181.8K Reputation points Volunteer Moderator
2023-02-23T03:26:03+00:00

Rebuilding the BCD should be enough, not the entire boot files, even though rebuilding the entire boot files doesn't do any harm.

And wondering why you're trying to create a Recovery drive with system files? Is it for backup/restore purposes or only for accessing WinRE? If it's for accessing WinRE, you can uncheck "Backup system files..." and create the media.

Regarding your question about C:\EFI folder, you can simply rename it. If Windows reboots correctly, that folder can be deleted. Do this only after creating the USB setup disk or Recovery drive.

Was this answer helpful?

1 person found this answer helpful.
0 comments

56 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-02-19T19:18:32+00:00

    While I do appreciate the thoroughness of looking at all of this info, my initial question is much simpler. "Is it safe to delete the \EFI directory on the boot partition if UEFI is successfully booting from the EFI partition on that disk after the GPT conversion?" I'm happy to tackle the partition layout, rebuilding WinRE, creating a new USB Win10 recovery drive and other topics later, but right now I just want to solve this booting issue. I noticed that BCD info below looks completely wrong as diskpart identifies Volume10 as a USB drive. I used a trial version of EasyUEFI to take a look at the boot manager entries and remain confident that I'm booting from the GPT EFI partition rather than the EFI directory (though I can't explain why the 3 disabled entries show up in my UEFI F11 menu).

    FYI, I did run those other commands from your original request, but piped them into text files before realizing that I couldn't attach them. They're now pasted below as well as the Sel Dis 2 commands omitted in the initial request (keep in mind that Disk2 eventually will get wiped and become a data drive). I'm not getting the classic BSOD of a Windows crash - I'm getting the version where it fails to detect the boot media. The ONLY crash type message in the Windows Event Log is also pasted at the end of this message. For the same reason that I can't upload text files to this forum, I'm understandably reticent about downloading and running some third-party batch files - particularly since it's unclear how they would help with my core question. Thanks for prompt and very detailed replies though!!!

    C:\Windows\system32>bcdedit

    Windows Boot Manager

    identifier {bootmgr}

    device partition=\Device\HarddiskVolume10

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    locale en_US

    inherit {globalsettings}

    flightsigning Yes

    default {current}

    resumeobject {8aa54c62-2e50-11e3-a87c-d9faf047cf21}

    displayorder {current}

    toolsdisplayorder {memdiag}

    timeout 30

    Windows Boot Loader

    identifier {current}

    device partition=C:

    path \Windows\system32\winload.efi

    description Windows 10 Home

    locale en_US

    inherit {bootloadersettings}

    recoveryenabled Yes

    isolatedcontext Yes

    flightsigning Yes

    allowedinmemorysettings 0x15000075

    osdevice partition=C:

    systemroot \Windows

    resumeobject {8aa54c62-2e50-11e3-a87c-d9faf047cf21}

    nx OptIn

    bootmenupolicy Standard

    C:\Windows\system32>

    C:\Windows\system32>reagentc /info

    Windows Recovery Environment (Windows RE) and system reset configuration

    Information: 

    Windows RE status:         Disabled 

Windows RE location: 

Boot Configuration Data (BCD) identifier: dd9a74b1-88a3-11ed-be40-d03598d64954 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0

    REAGENTC.EXE: Operation Successful.

    DISKPART> sel dis 2

    Disk 2 is now the selected disk.

    DISKPART>

    DISKPART> det dis

    Samsung SSD 850 EVO 250GB

    Disk ID: {85FD8DC1-5CB9-4138-B026-9CD7FF94B57D}

    Type : SATA

    Status : Online

    Path : 5

    Target : 0

    LUN ID : 0

    Location Path : PCIROOT(0)#PCI(0102)#PCI(0001)#ATA(C05T00L00)

    Current Read-only State : No

    Read-only : No

    Boot Disk : No

    Pagefile Disk : No

    Hibernation File Disk : No

    Crashdump Disk : No

    Clustered Disk : No

    Volume ### Ltr Label Fs Type Size Status Info

    Volume 3 System Rese NTFS Partition 35 MB Healthy

    Volume 4 F NTFS Partition 232 GB Healthy

    Volume 5 FAT32 Partition 100 MB Healthy Hidden

    Volume 6 Recovery NTFS Partition 464 MB Healthy Hidden

    DISKPART>

    DISKPART> lis par

    Partition ### Type Size Offset

    Partition 1 Reserved 128 MB 1024 KB

    Partition 2 System 100 MB 129 MB

    Partition 3 Primary 35 MB 229 MB

    Partition 4 Primary 232 GB 265 MB

    Partition 5 Recovery 464 MB 232 GB

    DISKPART>

    DISKPART> sel par 1

    Partition 1 is now the selected partition.

    DISKPART>

    DISKPART> det par

    Partition 1

    Type : e3c9e316-0b5c-4db8-817d-f92df00215ae

    Hidden : Yes

    Required: No

    Attrib : 0X8000000000000000

    Offset in Bytes: 1048576

    There is no volume associated with this partition.

    DISKPART>

    DISKPART> sel par 2

    Partition 2 is now the selected partition.

    DISKPART>

    DISKPART> det par

    Partition 2

    Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b

    Hidden : Yes

    Required: No

    Attrib : 0X8000000000000000

    Offset in Bytes: 135266304

    Volume ### Ltr Label Fs Type Size Status Info

    * Volume 5 FAT32 Partition 100 MB Healthy Hidden

    DISKPART>

    DISKPART> sel par 3

    Partition 3 is now the selected partition.

    DISKPART>

    DISKPART> det par

    Partition 3

    Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

    Hidden : No

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 240123904

    Volume ### Ltr Label Fs Type Size Status Info

    * Volume 3 System Rese NTFS Partition 35 MB Healthy

    DISKPART>

    DISKPART> sel par 4

    Partition 4 is now the selected partition.

    DISKPART>

    DISKPART> det par

    Partition 4

    Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

    Hidden : No

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 277872640

    Volume ### Ltr Label Fs Type Size Status Info

    * Volume 4 F NTFS Partition 232 GB Healthy

    DISKPART>

    DISKPART> sel par 5

    Partition 5 is now the selected partition.

    DISKPART> det par

    Partition 5

    Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

    Hidden : Yes

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 249569992704

    Volume ### Ltr Label Fs Type Size Status Info

    * Volume 6 Recovery NTFS Partition 464 MB Healthy Hidden

    ===================

    Windows failed fast startup with error status 0xC00000D4.

    • System
      • Provider
      [ Name] Microsoft-Windows-Kernel-Boot [ Guid] {15ca44ff-4d7a-4baa-bba5-0998955e531e} EventID 29 Version 1 Level 2 Task 0 Opcode 0 Keywords 0x8000080000000000
      • TimeCreated
      [ SystemTime] 2023-02-18T16:40:36.7981756Z EventRecordID 54423 Correlation
      • Execution
      [ ProcessID] 4 [ ThreadID] 8 Channel System Computer DESKTOP-QABCANO
      • Security
      [ UserID] S-1-5-18
    • EventData FailureStatus 3221225684 FailureMsg A fatal error occurred processing the restoration data.

    =================

    C:\Windows\system32>bcdedit /enum all

    Firmware Boot Manager

    identifier {fwbootmgr}

    displayorder {bootmgr} 

                        {6a0a1946-aef6-11ed-84fb-a8a1594c6c15} 

                    {6a0a1947-aef6-11ed-84fb-a8a1594c6c15} 

                    {a24b43ad-af18-11ed-84fe-806e6f6e6963}

    timeout 3

    Windows Boot Manager

    identifier {bootmgr}

    device partition=\Device\HarddiskVolume10

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    locale en_US

    inherit {globalsettings}

    flightsigning Yes

    default {current}

    resumeobject {8aa54c62-2e50-11e3-a87c-d9faf047cf21}

    displayorder {current}

    toolsdisplayorder {memdiag}

    timeout 30

    Firmware Application (101fffff)

    identifier {6a0a1946-aef6-11ed-84fb-a8a1594c6c15}

    device partition=F:

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    Firmware Application (101fffff)

    identifier {6a0a1947-aef6-11ed-84fb-a8a1594c6c15}

    device partition=C:

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    Firmware Application (101fffff)

    identifier {a24b43ad-af18-11ed-84fe-806e6f6e6963}

    device partition=\Device\HarddiskVolume5

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    Windows Boot Loader

    identifier {current}

    device partition=C:

    path \Windows\system32\winload.efi

    description Windows 10 Home

    locale en_US

    inherit {bootloadersettings}

    recoveryenabled Yes

    isolatedcontext Yes

    flightsigning Yes

    allowedinmemorysettings 0x15000075

    osdevice partition=C:

    systemroot \Windows

    resumeobject {8aa54c62-2e50-11e3-a87c-d9faf047cf21}

    nx OptIn

    bootmenupolicy Standard

    Windows Boot Loader

    identifier {a2a20109-981b-4aa1-abb7-3c015278072a}

    device ramdisk=[C:]\Aomei\AomeiBoot.wim,{68c7d26e-b6a2-4d56-9184-ef9dcb9e3ee5}

    description Aomei PE

    osdevice ramdisk=[C:]\Aomei\AomeiBoot.wim,{68c7d26e-b6a2-4d56-9184-ef9dcb9e3ee5}

    systemroot \Windows

    detecthal Yes

    winpe Yes

    Resume from Hibernate

    identifier {8aa54c62-2e50-11e3-a87c-d9faf047cf21}

    device partition=C:

    path \Windows\system32\winresume.efi

    description Windows Resume Application

    locale en_US

    inherit {resumeloadersettings}

    recoveryenabled Yes

    isolatedcontext Yes

    allowedinmemorysettings 0x15000075

    filedevice partition=C:

    filepath \hiberfil.sys

    bootmenupolicy Standard

    pae Yes

    debugoptionenabled No

    Windows Memory Tester

    identifier {memdiag}

    device partition=\Device\HarddiskVolume10

    path \EFI\Microsoft\Boot\memtest.efi

    description Windows Memory Diagnostic

    locale en_US

    inherit {globalsettings}

    badmemoryaccess Yes

    EMS Settings

    identifier {emssettings}

    bootems No

    Debugger Settings

    identifier {dbgsettings}

    debugtype Serial

    debugport 1

    baudrate 115200

    RAM Defects

    identifier {badmemory}

    Global Settings

    identifier {globalsettings}

    inherit {dbgsettings} 

                        {emssettings} 

                    {badmemory}

    Boot Loader Settings

    identifier {bootloadersettings}

    inherit {globalsettings} 

                        {hypervisorsettings}

    Hypervisor Settings

    identifier {hypervisorsettings}

    hypervisordebugtype Serial

    hypervisordebugport 1

    hypervisorbaudrate 115200

    Resume Loader Settings

    identifier {resumeloadersettings}

    inherit {globalsettings}

    Device options

    identifier {68c7d26e-b6a2-4d56-9184-ef9dcb9e3ee5}

    ramdisksdidevice partition=C:

    ramdisksdipath \Aomei\AomeiBoot.sdi

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-02-19T02:10:26+00:00

    How come selected commands were not run or were deleted?

    For example: bcdedit, reagentc /info, etc.

    Sel dis 2 was missing in the commands and is included in the the scripts below.

    1. Please run these bat scripts and post share links into this thread using one drive, drop box, or google drive:

    diskparinfo

    tuneup plus

    (bat scripts by default will prompt antivirus software and require manual overrides)

    https://www.tenforums.com/attachments/bsod-crashes-debugging/355861d1640707960-batch-files-use-bsod-debugging-diskparinfo.bat

    https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

    1. Run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    Was this answer helpful?

    0 comments