dual EFI entries after GPT conversion

Anonymous

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.

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

(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...

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.

0 comments

Answer accepted by question author

Anonymous

(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.

(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...?...

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

0 comments

Answer accepted by question author

Ramesh 181.8K Volunteer Moderator

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.

0 comments

56 additional answers

Anonymous

2023-03-07T01:44:30+00:00
This is SOOO painful. I remounted dis3par4 as R: and ran the dir command - confirming that winre.wim was not there. Looking back at page 4 of this thread, I noticed the Robocopy did not deposit winre.wim in that area when we attempted to copy it from c:\windows\system32\recovery initially! So I ran the dir to confirm it was still in the source and ran robocopy again and this time it appears to have work (bolded below).

C:\Windows\system32>DIR C:\Recovery\WindowsRE\WinRE.wim /a

Volume in drive C has no label.

Volume Serial Number is D791-C240

Directory of C:\Recovery\WindowsRE

05/10/2020 09:32 PM 423,565,200 Winre.wim
```
           1 File(s)    423,565,200 bytes 

           0 Dir(s)  267,128,426,496 bytes free 
```
C:\Windows\system32>C:\Windows\system32>RoboCopy c:\Recovery R:\Recovery /MIR

'C:\Windows\system32' is not recognized as an internal or external command,

operable program or batch file.

C:\Windows\system32>RoboCopy c:\Recovery R:\Recovery /MIR

ROBOCOPY :: Robust File Copy for Windows

Started : Monday, March 6, 2023 5:12:41 PM

Source : c:\Recovery\
```
 Dest : R:\Recovery\ 

Files : \*.\* 
```
Options : *.* /S /E /DCOPY:DA /COPY:DAT /PURGE /MIR /R:1000000 /W:30
```
                       1    c:\Recovery\ 

                       1    c:\Recovery\Logs\ 

                       2    c:\Recovery\OEM\ 

                       3    c:\Recovery\WindowsRE\ 
```
100% Newer 1136 ReAgent.xml

100% New File 403.9 m Winre.wim
```
           Total    Copied   Skipped  Mismatch    FAILED    Extras 

Dirs :         4         0         4         0         0         0 
```
Files : 7 2 5 0 0 0

Bytes : 406.97 m 403.94 m 3.02 m 0 0 0

Times : 0:00:00 0:00:00 0:00:00 0:00:00

Speed : 1750274115 Bytes/sec.

Speed : 100151.488 MegaBytes/min.

Ended : Monday, March 6, 2023 5:12:41 PM

=============dir r:\ a/ /s====================

Directory of r:\Recovery\WindowsRE

03/06/2023 05:12 PM <DIR> .

03/06/2023 05:12 PM <DIR> ..

12/07/2019 01:08 AM 3,170,304 boot.sdi

02/28/2023 02:05 PM 1,136 ReAgent.xml

05/10/2020 09:32 PM 423,565,200 Winre.wim
```
           3 File(s)    426,736,640 bytes
```
=================================

C:\Windows\system32>reagentc /info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:
```
Windows RE status:         Enabled 

Windows RE location:       \\?\GLOBALROOT\device\harddisk3\**partition4**\Recovery\WindowsRE 

Boot Configuration Data (BCD) identifier: e1f8ff5c-b603-11ed-850b-a8a1594c6c15 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0
```
==========================

Why oh why did I not stop here!?! In spite of not running the disable/enable cycle, Windows suddenly was pointing to the right location. However, I stupidly soldiered on.

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

C:\Windows\system32>reagentc /disable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /SetREImage /Path R:\Recovery\WindowsRE /Target C:\Windows

REAGENTC.EXE: The specified path was not found.

C:\Windows\system32>reagentc /disable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /enable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:
```
Windows RE status:         Enabled 

Windows RE location:       \\?\GLOBALROOT\device\harddisk3\**partition3**\Recovery\WindowsRE 

Boot Configuration Data (BCD) identifier: e1f8ff60-b603-11ed-850b-a8a1594c6c15 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0 
```
REAGENTC.EXE: Operation Successful.

C:\Windows\system32>ReagentC /SetREImage /Path R:\Recovery\WindowsRE

REAGENTC.EXE: Windows RE is already enabled.

C:\Windows\system32>reagentc /disable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /enable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:
```
Windows RE status:         Enabled 

Windows RE location:       \\?\GLOBALROOT\device\harddisk3\**partition3**\Recovery\WindowsRE 

Boot Configuration Data (BCD) identifier: e1f8ff62-b603-11ed-850b-a8a1594c6c15 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0 
```
REAGENTC.EXE: Operation Successful.

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

The /SetREimage command did not work, so I tried a quick disable/enable and ended back up on dis3par3! I read up on the command and tried it again with only /Path and not /Target. It completed successfully (so I'm wondering if /Target should have been c:\windows\system32\recover ?) so I tried another disable/enable and remain attached to dis3/par3. For legibility purposes, I'm going to post the log file contents separately. I'm so frazzled over this...
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-07T01:44:23+00:00
This is SOOO painful. I remounted dis3par4 as R: and ran the dir command - confirming that winre.wim was not there. Looking back at page 4 of this thread, I noticed the Robocopy did not deposit winre.wim in that area when we attempted to copy it from c:\windows\system32\recovery initially! So I ran the dir to confirm it was still in the source and ran robocopy again and this time it appears to have work (bolded below).

C:\Windows\system32>DIR C:\Recovery\WindowsRE\WinRE.wim /a

Volume in drive C has no label.

Volume Serial Number is D791-C240

Directory of C:\Recovery\WindowsRE

05/10/2020 09:32 PM 423,565,200 Winre.wim
```
           1 File(s)    423,565,200 bytes 

           0 Dir(s)  267,128,426,496 bytes free 
```
C:\Windows\system32>C:\Windows\system32>RoboCopy c:\Recovery R:\Recovery /MIR

'C:\Windows\system32' is not recognized as an internal or external command,

operable program or batch file.

C:\Windows\system32>RoboCopy c:\Recovery R:\Recovery /MIR

ROBOCOPY :: Robust File Copy for Windows

Started : Monday, March 6, 2023 5:12:41 PM

Source : c:\Recovery\
```
 Dest : R:\Recovery\ 

Files : \*.\* 
```
Options : *.* /S /E /DCOPY:DA /COPY:DAT /PURGE /MIR /R:1000000 /W:30
```
                       1    c:\Recovery\ 

                       1    c:\Recovery\Logs\ 

                       2    c:\Recovery\OEM\ 

                       3    c:\Recovery\WindowsRE\ 
```
100% Newer 1136 ReAgent.xml

100% New File 403.9 m Winre.wim
```
           Total    Copied   Skipped  Mismatch    FAILED    Extras 

Dirs :         4         0         4         0         0         0 
```
Files : 7 2 5 0 0 0

Bytes : 406.97 m 403.94 m 3.02 m 0 0 0

Times : 0:00:00 0:00:00 0:00:00 0:00:00

Speed : 1750274115 Bytes/sec.

Speed : 100151.488 MegaBytes/min.

Ended : Monday, March 6, 2023 5:12:41 PM

=============dir r:\ a/ /s====================

Directory of r:\Recovery\WindowsRE

03/06/2023 05:12 PM <DIR> .

03/06/2023 05:12 PM <DIR> ..

12/07/2019 01:08 AM 3,170,304 boot.sdi

02/28/2023 02:05 PM 1,136 ReAgent.xml

05/10/2020 09:32 PM 423,565,200 Winre.wim
```
           3 File(s)    426,736,640 bytes
```
=================================

C:\Windows\system32>reagentc /info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:
```
Windows RE status:         Enabled 

Windows RE location:       \\?\GLOBALROOT\device\harddisk3\**partition4**\Recovery\WindowsRE 

Boot Configuration Data (BCD) identifier: e1f8ff5c-b603-11ed-850b-a8a1594c6c15 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0
```
==========================

Why oh why did I not stop here!?! In spite of not running the disable/enable cycle, Windows suddenly was pointing to the right location. However, I stupidly soldiered on.

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

C:\Windows\system32>reagentc /disable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /SetREImage /Path R:\Recovery\WindowsRE /Target C:\Windows

REAGENTC.EXE: The specified path was not found.

C:\Windows\system32>reagentc /disable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /enable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:
```
Windows RE status:         Enabled 

Windows RE location:       \\?\GLOBALROOT\device\harddisk3\**partition3**\Recovery\WindowsRE 

Boot Configuration Data (BCD) identifier: e1f8ff60-b603-11ed-850b-a8a1594c6c15 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0 
```
REAGENTC.EXE: Operation Successful.

C:\Windows\system32>ReagentC /SetREImage /Path R:\Recovery\WindowsRE

REAGENTC.EXE: Windows RE is already enabled.

C:\Windows\system32>reagentc /disable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /enable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>reagentc /info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:
```
Windows RE status:         Enabled 

Windows RE location:       \\?\GLOBALROOT\device\harddisk3\**partition3**\Recovery\WindowsRE 

Boot Configuration Data (BCD) identifier: e1f8ff62-b603-11ed-850b-a8a1594c6c15 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0 
```
REAGENTC.EXE: Operation Successful.

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

The /SetREimage command did not work, so I tried a quick disable/enable and ended back up on dis3par3! I read up on the command and tried it again with only /Path and not /Target. It completed successfully (so I'm wondering if /Target should have been c:\windows\system32\recover ?) so I tried another disable/enable and remain attached to dis3/par3. For legibility purposes, I'm going to post the log file contents separately. I'm so frazzled over this...
Was this answer helpful?

0 comments No comments