Multiple C: drive partitions related to windows boot

NavyLCDR said:

Even easier run:
reagentc /disable

Delete both recovery partitions, then run:
reagentc /enable

You will still have the mess of all the EFI system partitions to deal with though.

I deleted one and it works, but now i have 2 that is legit, but i think i just need one of them, but i dont know which one is safe to delete. they both have the exact size free. The other one did not match the MB size i deleted that one, so im left with 2 and one of them is the one that i use and one is some kind of remnant from old install it seems. What does this command do in CMD? If you look at my picture you will see 3 EFI drives dont show anything in computer management, i wonder if i can delete those because they have no information vs the other ones?

- - - Updated - - -

Megahertz said:

Do you have a drive image software like Macrium or Aomei?

To find out what is the active recovery partition, open a CMD window as administrator and type:
reagentc /info

So what do i do with this information? I have aomei partition assistant

Here you can see in diskpart i selected disk 1 and then you can see partition 4 i guess its the same as the reagentc shows?

- - - Updated - - -

Ok i deleted 3 of the EFI, no issues. But i have 1 extra EFI, but maybe i need that one? And i have 2, 6.88 mb ones, i know 1 is needed, but i dont know which one i can delete of the 6.88 mb

In summary of @Megahertz post, what I would do is:
Run Reagentc /disable command.
Delete all partitions other than the Windows OS partition and any data partition you wanted to keep.
Create a new 100 MB EFI system partition (and a 16 MB MSR partition if you didn't feel safe without it).
Populated the new 100 MB EFI system partition with boot files using the bcdboot command.
Resize the Windows OS partition to fill all the free space.

It is not complicated.

The two commands you have been given tell you which two partitions are in use as system and recovery. You dont need the others.

reg query HKLM\SYSTEM\CurrentControlSet\Control /v FirmwareBootDevice

reagentc /info

If you want you could run this getbootdevice_x64.zip

which will show something like this

SIW2 said:

It is not complicated.

The two commands you have been given tell you which two partitions are in use as system and recovery. You dont need the others.

reg query HKLM\SYSTEM\CurrentControlSet\Control /v FirmwareBootDevice

reagentc /info

If you want you could run this getbootdevice_x64.zip

which will show something like this

It doesn't really matter which ones are active, though. "reagentc /disable" moves the recovery partition files into Windows\System32\Recovery so that the recovery environment can be re-enabled later. After that, all Recovery Partitions can be deleted.

The EFI System Partition is easy to recreate:

Code:

diskpart
select disk 1  <- or whichever disk the EFI system partition is wanted on
create part ESP size=100
format fs=FAT32 quick
assign letter=s
exit
bcdboot C:\Windows /s S: /f UEFI
exit

Therefore deleting all of the EFI System Partitions is not a big deal. That's why if it was mine, I would just delete all the partitions not containing the Windows OS or data I wanted to keep and recreate the EFI system partition from scratch.

SIW2 said:

It is not complicated.

The two commands you have been given tell you which two partitions are in use as system and recovery. You dont need the others.

reg query HKLM\SYSTEM\CurrentControlSet\Control /v FirmwareBootDevice

reagentc /info

If you want you could run this getbootdevice_x64.zip

which will show something like this

This was great, as you see in the picture i found "c4" so i can safely delete the other one but i did not have "04"
04 is the C: drive. Can you please tell me from the pictures which one i can delete? Just realized how unnecessary me painting in the pictures was, but whatever.

That is interesting. Check the arc paths with winobj https://learn.microsoft.com/en-us/sy...wnloads/winobj

SIW2 said:

That is interesting. Check the arc paths with winobj https://learn.microsoft.com/en-us/sy...wnloads/winobj

Thanks. Here is the picture, hope it helps you help me