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: Most helpful
Most helpful Newest Oldest
  1. Ramesh 181.8K Reputation points Volunteer Moderator
    2023-03-04T03:12:02+00:00

    REAGENTC.EXE: Operation Successful.

    C:\Windows\system32>reagentc /enable

    REAGENTC.EXE: The Windows RE image was not found.

    Pretty much what I was trying to avoid in my previous message. Next I ran BCDedit again. I'm not quite sure what happened vs what was expected, but I'm really glad that I exported BCD first! I'm not sure whether the reverse the 2 sets of applied commands or where to go next though.

    I'd say that's progress. The last action seemed to update the BCD, which hadn't happened before. The issue will be sorted out if the "The Windows RE image was not found" is resolved. ReAgent.log might have some clues. Perhaps placing a copy of Winre.wim in "C:\Windows\System32\Recovery", and re-running the 2nd and 3rd reagentc commands will help.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-04T01:29:09+00:00

    Your BCD looks good to me. It's just like mine with regard to the recovery environment. I thought all would be well in the world after that, but apparently not. But don't worry, we'll set it right.

    (1) Let's check again that WinRE.wim is where it needs to be...?...

    DiskPart <<<Enter DiskPart

    List Vol <<<If R: is still on Recovery, just exit & do the DIR

    List Disk <<<Show the disks

    Select Disk 3 <<<Select the 970 EVO

    List Part <<<List its partitions

    Select Part 4 <<<Focus on Recovery

    Assign Letter=R <<<Give it letter R:

    Exit <<<Leave Diskpart

    DIR R:\Recovery\WindowsRE\WinRE.wim /a <<<Is WinRE.wim still there?

    (a) If it isn't there, something must have gone wrong with that RoboCopy we did earlier. Let's see what R: looks like: DIR R:\ /a /s

    (b) If it is there, then try this...

    ReagentC /Info <<<Shows partition 3 has RE

    ReagentC /Disable <<<Moves WinRE.wim into a "staging area"

    ReagentC /SetREImage /Path R:\Recovery\WindowsRE /Target C:\Windows

    ReagentC /Enable <<<Moves it to the new location (we hope)

    === Let's try a reboot here ===

    ReagentC /Info <<<Should show RE is partition 4 now

    Looking at my /Disable below, that might be necessary to move WinRE.wim into the staging area which is C:\WINDOWS\system32\Recovery (I think). Then /Enable can move it back to R: & inform the rest of Windows that it is there.

    I'm including the /SetREImage command because I think Ramesh meant for you to try that again after deleting ReAgent.xml from the staging area (with his 3 commands). If ReAgent.xml isn't there after /SetREImage, move it back this way...

    Copy C:\ReAgent.xml C:\Windows\System32\Recovery

    Then proceed to the /Enable. It needs to be there.

    (2) Copy/paste "C:\Windows\Logs\ReAgent\ReAgent.log" into Search, & show it to us...

    Here is mine...

    2023-02-26 01:00:15, Info [ReAgentc.exe] -----Executing command line: reagentc /info-----

    2023-02-26 01:00:15, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:00:15, Info [ReAgentc.exe] Enter WinReGetConfig

    2023-02-26 01:00:15, Info [ReAgentc.exe] Parameters: configWinDir: NULL

    2023-02-26 01:00:15, Info [ReAgentc.exe] WinRE config file path: C:\WINDOWS\system32\Recovery\ReAgent.xml

    2023-02-26 01:00:15, Info [ReAgentc.exe] Update enhanced config info is enabled.

    2023-02-26 01:00:16, Info [ReAgentc.exe] WinRE is installed

    2023-02-26 01:00:16, Info [ReAgentc.exe] WinRE is installed at: \?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

    2023-02-26 01:00:16, Info [ReAgentc.exe] System is WimBoot: FALSE

    2023-02-26 01:00:16, Info [ReAgentc.exe] WinRE image validated

    2023-02-26 01:00:16, Info [ReAgentc.exe] Exit WinReGetConfig return value: 1, last error: 0x0

    2023-02-26 01:00:16, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:00:16, Info [ReAgentc.exe] -----Exiting command line: reagentc /info, Error: 0-----

    2023-02-26 01:00:16, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:00:32, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:00:32, Info [ReAgentc.exe] -----Executing command line: reagentc /disable-----

    2023-02-26 01:00:32, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:00:32, Info [ReAgentc.exe] Enter WinReUnInstall

    2023-02-26 01:00:32, Info [ReAgentc.exe] Update enhanced config info is enabled.

    2023-02-26 01:00:32, Info [ReAgentc.exe] WinRE is installed

    2023-02-26 01:00:52, Info [ReAgentc.exe] winreCopyWIMBack moved WIM file from \?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\ to C:\WINDOWS\system32\Recovery\Winre.wim successfully!

    2023-02-26 01:00:52, Info [ReAgentc.exe] WinRE uninstall step 1 succeeded: copy WIM file back to its staging location

    2023-02-26 01:00:52, Info [ReAgentc.exe] WinRE uninstall step 2 succeeded: update agent config for BCD id, install state, schedule operation.

    2023-02-26 01:00:54, Info [ReAgentc.exe] The current Recovery BCD entry points to \Device\HarddiskVolume4[\Recovery\WindowsRE\Winre.wim]

    2023-02-26 01:00:54, Info [ReAgentc.exe] The WIM file being unregistered is \Device\HarddiskVolume4[\Recovery\WindowsRE\Winre.wim]

    2023-02-26 01:00:54, Info [ReAgentc.exe] Paths are the same, clearing Recovery BCD

    2023-02-26 01:00:54, Info [ReAgentc.exe] Cleared recovery BCD successfully

    2023-02-26 01:00:54, Info [ReAgentc.exe] WinRE uninstall step 3 succeeded: unregister winre.wim from recovery BCD.

    2023-02-26 01:00:54, Info [ReAgentc.exe] WinRE uninstall step 4 succeeded: remove recovery related sequence from BCD.

    2023-02-26 01:00:54, Info [ReAgentc.exe] WinRE uninstall step 5 completed with return value TRUE: remove validation task.

    2023-02-26 01:00:54, Info [ReAgentc.exe] Exit WinReUnInstall returns 1 with last error: 0x0

    2023-02-26 01:00:55, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:00:55, Info [ReAgentc.exe] -----Exiting command line: reagentc /disable, Error: 0-----

    2023-02-26 01:00:55, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:02:50, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:02:50, Info [ReAgentc.exe] -----Executing command line: reagentc /enable-----

    2023-02-26 01:02:50, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:02:50, Info [ReAgentc.exe] Enter WinRECheckGuid

    2023-02-26 01:02:50, Info [ReAgentc.exe] Parameter: TargetOsGuid: : NULL

    2023-02-26 01:02:50, Info [ReAgentc.exe] Exit WinRECheckGuid return error code: 0x0

    2023-02-26 01:02:50, Info [ReAgentc.exe] Enter WinReInstall

    2023-02-26 01:02:50, Info [ReAgentc.exe] Parameter: ReInstallBecauseOfBitlocker: 0

    2023-02-26 01:02:50, Info [ReAgentc.exe] --Install on target OS step 1: collect info like partition list, loading reagent.xml, source winre.wim and partition

    2023-02-26 01:02:50, Info [ReAgentc.exe] Enumerate and log all fixed partitions:

    2023-02-26 01:02:50, Info [ReAgentc.exe] --Partition info--

    2023-02-26 01:02:50, Info [ReAgentc.exe] VolumeName: \?\Volume{3853bb65-3d72-4bb1-9964-7f26ee7ad47e}, PartitionName: \?\GLOBALROOT\device\harddisk0\partition1

    2023-02-26 01:02:50, Info [ReAgentc.exe] Partition number: 1, offset: 32768, free space: 72656896, total space: 100662272

    2023-02-26 01:02:50, Info [ReAgentc.exe] DiskNumber:0, DiskSignature:0, NTFS:0, Mbr:0, Active:0, Boot:0, BitlockerEnabled:0

    2023-02-26 01:02:50, Info [ReAgentc.exe] GPT partition GUID:: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}

    2023-02-26 01:02:50, Info [ReAgentc.exe] DiskId: {FF69AAFC-9985-4B5C-9E34-9AA629D8F4D7}

    2023-02-26 01:02:50, Info [ReAgentc.exe] --Partition info--

    2023-02-26 01:02:50, Info [ReAgentc.exe] VolumeName: \?\Volume{457ef4fb-b253-437a-8212-e3b0b7dc0926}, PartitionName: \?\GLOBALROOT\device\harddisk0\partition4

    2023-02-26 01:02:50, Info [ReAgentc.exe] Partition number: 4, offset: 999313944576, free space: 869806080, total space: 888840192

    2023-02-26 01:02:50, Info [ReAgentc.exe] DiskNumber:0, DiskSignature:0, NTFS:1, Mbr:0, Active:0, Boot:0, BitlockerEnabled:0

    2023-02-26 01:02:50, Info [ReAgentc.exe] GPT partition GUID:: {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC}

    2023-02-26 01:02:50, Info [ReAgentc.exe] DiskId: {FF69AAFC-9985-4B5C-9E34-9AA629D8F4D7}

    2023-02-26 01:02:50, Info [ReAgentc.exe] --Partition info--

    2023-02-26 01:02:50, Info [ReAgentc.exe] VolumeName: \?\Volume{e25e0508-48be-470f-a312-9a0ea0ce543e}, PartitionName: \?\GLOBALROOT\device\harddisk0\partition3

    2023-02-26 01:02:50, Info [ReAgentc.exe] Partition number: 3, offset: 121667072, free space: 942214209536, total space: 999190286336

    2023-02-26 01:02:50, Info [ReAgentc.exe] DiskNumber:0, DiskSignature:0, NTFS:1, Mbr:0, Active:0, Boot:1, BitlockerEnabled:0

    2023-02-26 01:02:50, Info [ReAgentc.exe] GPT partition GUID:: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}

    2023-02-26 01:02:50, Info [ReAgentc.exe] DiskId: {FF69AAFC-9985-4B5C-9E34-9AA629D8F4D7}

    2023-02-26 01:02:50, Info [ReAgentc.exe] Get downlevel ReAgent config

    2023-02-26 01:02:50, Info [ReAgentc.exe] Downlevel config file path: \Recovery\ReAgentOld.xml

    2023-02-26 01:02:50, Info [ReAgentc.exe] Checking for downlevel WinRE installation.

    2023-02-26 01:02:50, Warning [ReAgentc.exe] read xml file (\Recovery\ReAgentOld.xml) failed: 0x2

    2023-02-26 01:02:50, Warning [ReAgentc.exe] ReAgentXMLParser::ParseConfigFile failed to read config xml file (0x2) in file base\diagnosis\srt\reagent2\reinfo\parser_2.0.cpp line 784

    2023-02-26 01:02:50, Warning [ReAgentc.exe] ReAgentXMLParser::ParseConfigFile (xml file: \Recovery\ReAgentOld.xml) returning 0x2

    2023-02-26 01:02:50, Info [ReAgentc.exe] ReAgentConfig::ParseConfigFile ReAgent.XML was not found or could not be parsed, creating a new config xml Err=2

    2023-02-26 01:02:51, Info [ReAgentc.exe] First round search

    2023-02-26 01:02:51, Info [ReAgentc.exe] Get ReAgent config

    2023-02-26 01:02:51, Info [ReAgentc.exe] GetReAgentConfig Config file path: C:\WINDOWS\system32\Recovery\ReAgent.xml

    2023-02-26 01:02:51, Info [ReAgentc.exe] CheckRegKey test hook (SystemSetupInProgress) present and disabled

    2023-02-26 01:02:51, Info [ReAgentc.exe] Update enhanced config info is enabled.

    2023-02-26 01:02:51, Warning [ReAgentc.exe] Failed to get recovery entries: 0xc0000225

    2023-02-26 01:02:51, Info [ReAgentc.exe] winreGetWinReGuid returning 0X490

    2023-02-26 01:02:51, Info [ReAgentc.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo WinRE disabled, WinRE Guid could not be determined (0x490)

    2023-02-26 01:02:51, Info [ReAgentc.exe] FindWinReSourceImageAndPartition No source winre.wim was specified. Checking for a staged winre.wim.

    2023-02-26 01:02:51, Info [ReAgentc.exe] FindWinReSourceImageAndPartition using winre.wim from C:\WINDOWS\system32\Recovery

    2023-02-26 01:02:51, Info [ReAgentc.exe] --Install on target OS step 2: detect and fix if there is any issue for winre settings

    2023-02-26 01:02:51, Info [ReAgentc.exe] DetectAndFixWinReIssues nothing to do because winre is not enabled.

    2023-02-26 01:02:51, Info [ReAgentc.exe] --Install on target OS step 3: check if we can keep winre.wim in the same partition if it is staged.

    2023-02-26 01:02:51, Info [ReAgentc.exe] --Install on target OS step 4: check if we can put winre.wim in other partitions or create one if needed.

    2023-02-26 01:02:51, Info [ReAgentc.exe] CanPutWinREOnOtherPartitions WinRE is not staged. Searching for a suitable partition for WinRE.

    2023-02-26 01:02:51, Info [ReAgentc.exe] Entering FindTargetPartition

    2023-02-26 01:02:51, Info [ReAgentc.exe] RegLoadKey $OFFLINE$SYSTEM failed. Error: 0x522.

    2023-02-26 01:02:51, Info [ReAgentc.exe] Not allowed to repartition the disk

    2023-02-26 01:02:51, Info [ReAgentc.exe] Start looping through each partition and initialize os partition, recovery partition and system partition for MBR

    2023-02-26 01:02:51, Info [ReAgentc.exe] Checking partition at offset 32768, partition number: 1

    2023-02-26 01:02:51, Info [ReAgentc.exe] skip GPT Partition which type is not PARTITION_MSFT_RECOVERY_GUID

    2023-02-26 01:02:51, Info [ReAgentc.exe] Checking partition at offset 999313944576, partition number: 4

    2023-02-26 01:02:51, Info [ReAgentc.exe] MeetPartitionRequirements Partition details: {Offset: 999313944576, Free space: 869806080, Total space: 888840192}

    2023-02-26 01:02:51, Info [ReAgentc.exe] MeetPartitionRequirements WinRE WIM size: 530417571

    2023-02-26 01:02:51, Info [ReAgentc.exe] MeetPartitionRequirements Required free space: 584943523

    2023-02-26 01:02:51, Info [ReAgentc.exe] partition meets requirements

    2023-02-26 01:02:51, Info [ReAgentc.exe] NOTE: select partition because it meets WinRE requirements

    2023-02-26 01:02:51, Info [ReAgentc.exe] Checking partition at offset 121667072, partition number: 3

    2023-02-26 01:02:51, Info [ReAgentc.exe] find OS partition

    2023-02-26 01:02:51, Info [ReAgentc.exe] Complete looping through each partition

    2023-02-26 01:02:51, Info [ReAgentc.exe] ----Search target partition option #1: try existing WinRE partition

    2023-02-26 01:02:51, Info [ReAgentc.exe] ----Search target partition option #2: try first recovery partition

    2023-02-26 01:02:51, Info [ReAgentc.exe] Found target partition: use the first recovery partition, offset: 999313944576

    2023-02-26 01:02:51, Info [ReAgentc.exe] Exit FindTargetPartition returns with status code: 0x0

    2023-02-26 01:02:51, Info [ReAgentc.exe] --Install on target OS step 5: set WinRE settings and restore system to a good state when hitting any errors

    2023-02-26 01:02:51, Info [ReAgentc.exe] Enter SetWinRESettings

    2023-02-26 01:02:51, Info [ReAgentc.exe] RegLoadKey $OFFLINE$SYSTEM failed. Error: 0x522.

    2023-02-26 01:02:51, Info [ReAgentc.exe] Copying WinRE from C:\WINDOWS\system32\Recovery to staging location on \?\GLOBALROOT\device\harddisk0\partition4

    2023-02-26 01:02:51, Info [ReAgentc.exe] RegLoadKey $OFFLINE$SYSTEM failed. Error: 0x522.

    2023-02-26 01:02:53, Info [ReAgentc.exe] Copied WinRE to staging location

    2023-02-26 01:02:53, Info [ReAgentc.exe] Creating BCD entry

    2023-02-26 01:02:53, Info [ReAgentc.exe] WinRE created BCD entry: : {346BB303-B59B-11ED-B293-74E6E2074932}

    2023-02-26 01:02:53, Info [ReAgentc.exe] Moving Winre and boot.sdi from staging location to target

    2023-02-26 01:02:53, Info [ReAgentc.exe] Moved Winre and boot.sdi from staging location to target

    2023-02-26 01:02:53, Info [ReAgentc.exe] Updating reagent.xml

    2023-02-26 01:02:53, Info [ReAgentc.exe] Set WinRE location path to: \Recovery\WindowsRE

    2023-02-26 01:02:53, Info [ReAgentc.exe] Set recovery guid

    2023-02-26 01:02:53, Info [ReAgentc.exe] Set scheduled operation: WinReNoOperation

    2023-02-26 01:02:53, Info [ReAgentc.exe] Set OS build version: 19041.1.amd64fre.vb_release.191206-1406

    2023-02-26 01:02:53, Info [ReAgentc.exe] Set Wimboot state: 0

    2023-02-26 01:02:53, Info [ReAgentc.exe] Set install state to: enabled

    2023-02-26 01:02:53, Info [ReAgentc.exe] Setting the recovery sequence for the target OS.

    2023-02-26 01:02:54, Info [ReAgentc.exe] Unable to get default BCD object (0xc0000225), checking display order instead

    2023-02-26 01:02:54, Info [ReAgentc.exe] Bootmgr has no default object set (0xc0000225), will use first display order entry instead

    2023-02-26 01:02:54, Info [ReAgentc.exe] Couldn't get top of display order: 0xc0000225

    2023-02-26 01:02:54, Info [ReAgentc.exe] We will report success and exit because recovery BCD is not used at all.

    2023-02-26 01:02:55, Info [ReAgentc.exe] Creating backup of reagent.xml

    2023-02-26 01:02:55, Info [ReAgentc.exe] Created backup of reagent.xml

    2023-02-26 01:02:55, Info [ReAgentc.exe] Configuring the WinRE validation task.

    2023-02-26 01:02:55, Info [ReAgentc.exe] Failed to clear WIM file trusted state: 0x2

    2023-02-26 01:02:55, Info [ReAgentc.exe] Failed to clear WIM file hash: 0x2

    2023-02-26 01:02:55, Info [ReAgentc.exe] Update enhanced config info is enabled.

    2023-02-26 01:02:56, Info [ReAgentc.exe] WinRE is installed

    2023-02-26 01:02:57, Info [ReAgentc.exe] Loading boot index 1

    2023-02-26 01:02:58, Info [ReAgentc.exe] winreValidateWimFile took 1922 ms.

    2023-02-26 01:03:02, Info [ReAgentc.exe] WinReValidateRecoveryWimInternal took 6907 ms.

    2023-02-26 01:03:02, Info [ReAgentc.exe] Completed the WinRE validation task.

    2023-02-26 01:03:02, Info [ReAgentc.exe] Creating backup of customization file

    2023-02-26 01:03:02, Warning [ReAgentc.exe] Recovery file not found at C:\WINDOWS\system32\Recovery\ReCustomization.xml

    2023-02-26 01:03:02, Warning [ReAgentc.exe] winreBackupRecoveryFile (C:\WINDOWS\system32\Recovery\ReCustomization.xml, ReCustomization.xml) failed, Err: 2

    2023-02-26 01:03:02, Info [ReAgentc.exe] Created backup of customization file

    2023-02-26 01:03:02, Info [ReAgentc.exe] Storing disk info in NVRAM

    2023-02-26 01:03:03, Info [ReAgentc.exe] NVRAM update not necessary

    2023-02-26 01:03:03, Info [ReAgentc.exe] Stored disk info in NVRAM

    2023-02-26 01:03:03, Info [ReAgentc.exe] SetWinRESettings return with error code 0x0

    2023-02-26 01:03:03, Info [ReAgentc.exe] WinReInstallOnTargetOSInternal WinRE installation completed successfully.

    2023-02-26 01:03:03, Info [ReAgentc.exe] Exit WinReInstall return value: 1, last error: 0x0

    2023-02-26 01:03:03, Info [ReAgentc.exe] Enter WinReSetConfig

    2023-02-26 01:03:03, Info [ReAgentc.exe] Parameters: configWinDir: NULL

    2023-02-26 01:03:03, Info [ReAgentc.exe] Update enhanced config info is enabled.

    2023-02-26 01:03:03, Info [ReAgentc.exe] WinRE is installed

    2023-02-26 01:03:03, Info [ReAgentc.exe] Exit WinReSetConfig return value: 1, last error: 0x0

    2023-02-26 01:03:03, Info [ReAgentc.exe] Clear non critical error when enabling auto repair

    2023-02-26 01:03:03, Info [ReAgentc.exe] ------------------------------------------------------

    2023-02-26 01:03:03, Info [ReAgentc.exe] -----Exiting command line: reagentc /enable, Error: 0-----

    2023-02-26 01:03:03, Info [ReAgentc.exe] ------------------------------------------------------

    Was this answer helpful?

    0 comments