Windows 10: Windows 11 Boot EFI partition replacement / recreation

Discus and support Windows 11 Boot EFI partition replacement / recreation in Windows 10 Software and Apps to solve the problem; TLDR; I want to recreate the EFI partition on a different disk.SATA-SSD Disk 0 -- Which is supposed to be a dedicated LINUX and Games windows.NVME Disk... Discussion in 'Windows 10 Software and Apps' started by Ashamaan Rajaram, Sep 2, 2024.

  1. Windows 11 Boot EFI partition replacement / recreation


    TLDR; I want to recreate the EFI partition on a different disk.SATA-SSD Disk 0 -- Which is supposed to be a dedicated LINUX and Games windows.NVME Disk 2 -- Supposed to be Windows and Data.I had Linux already running off Disk 0. I re-formatted and deleted the NVME Disk 2 where the original setup of Windows partitions EFI, MSR, Recovery, Windows etc were to create 91.5 gb of unallocated space. And usually when I install Windows I just select "unallocated space" and let Windows setup do the partitioning.But this time it only created the actual Windows partiton and used the linux EFI for bo

    :)
     
    Ashamaan Rajaram, Sep 2, 2024
    #1

  2. Non-destructively Moving / recreating EFI partition

    Hello - this is similar to Moving / recreating EFI partition but it was suggested I post the specifics of my question so that the responses can be relevant and clear. I have a few internal SSDs, 2 are relevant. - my system drive is a 1TB drive that I upgraded some time ago and it turns out that I did it wrong - the EFI partition resides on the old 250gb SSD which I repurposed as a storage drive. So the system won't boot without that 250GB drive present, and I'm wanting to upsize that with a new drive. - So I need to create an EFI partition on my existing 1TB drive without destroying anything. The instructions re fairly clear in the post mentioned above, but I want to be absolutely sure what I'm doing as I'd really like to avoid restoring from backup (I do have an image created by Macrium reflect and a Backblaze backup so I'm safe) I get to the step where I'm listing partition in order to select the Windows partition (4th/5th steps in Kyhi's post) and I get the following Size Offset Partition 1 Reserved 16MB 1024KB Partition 2 Primary 930GB 17MB Partition 3 Recovery 612MB 930GB And this confuses me because I assume I'm selecting Partition 2 here but in the next step we're shrinking that partition to 100MB, and this is most likely because I don't understand fully how Windows partitioning works but I just wanted to be sure at this stage that this is the correct thing to do ("select partition 2" then "shrink desired=100") If anyone can help here to clarify / allay my fears I would be grateful! Thanks in advance, David
     
    dkaplowitz, Sep 2, 2024
    #2
  3. Non-destructively Moving / recreating EFI partition

    hello - I'm getting to the last step here and when I do the command bcdboot E:\windows /s S: it just returns a list of diskpart commands. E is the 930GB NTFS volume that's the main partition on the 1TB drive. The BOOT partition doesn't have a letter assigned to it. The new EFI 100MB partiton is volume 12 / letter S. I can't see how to post a pic on my phone here but will try on my laptop so you can see the full volume list thanks! - - - Updated - - -
    Windows 11 Boot EFI partition replacement / recreation 397902d1695375687t-non-destructively-moving-recreating-efi-partition-img20230922101603-2.jpg
     
    dkaplowitz, Sep 2, 2024
    #3
  4. Windows 11 Boot EFI partition replacement / recreation

    Cloning System Partition, Recreating EFI & Recovery partitions......

    This guide is intended for educational purposes only.

    A fresh and clean installation is always the best thing to do, because in addition to a bug-free Windows experience, everything outside the Windows environment like the EFI partition, Recovery partition, and overall system integrity remains intact and well maintained.

    However, there are times when simply cloning the current system is preferred. This is not just to save time, but also because the existing system may contain drivers (e.g. BootCamp drivers) and other factors that setting up everything fresh becomes too much time consuming, and sometimes not possible too.

    Under these circumstances, the following guide will ensure that you can quickly clone your current system to an external SSD (or an internal one) that can be used on both Windows PC as well as a Mac (assuming the existing system already has the required BootCamp drivers).

    BASICS

    Before explaining the steps, just know some basics of how the computer functions.

    Every time you power on your computer, your system firmware first loads a hidden partition on the boot device called the EFI partition. This partition contains information about the installed operating systems as well as their paths (on the disk). In my experience, simply cloning an existing system partition to another device will often not be enough to make it bootable. This is probably because it breaks the OS paths in the new EFI partition that is automatically created in the cloning process. When that happens, you cannot boot from the target device unless the EFI partition is fixed with the correct path to the OS installed in the target disk.

    LESSONS IN THIS TUTORIAL

    So in this tutorial, we will see 3 things:

    1. How to clone the system partition.
    2. How to fix the EFI partition.
    3. How to restore the native Windows Recovery Environment (if that gets broken too in the cloning process).


    CLONING THE SYSTEM PARTITION

    Things Required

    1. Backup/ Cloning software: Most cloning software allow system cloning only in their paid version, so keep that in mind.

    2. External SSD/ HDD/ Flash Drive.

    3. External keyboard and mouse (only if you want to boot from the target disk on a Mac and your existing system doesn't have BootCamp drivers).

    Process

    This is a very straight-forward process.

    1. Ensure that the target disk is partitioned as GPT. This is best for Windows 10 and newer. If it is not partitioned as GPT, you can use a partition assistant software that will allow you to convert the partition from MBR to GPT without losing data. Most free versions of well known partition softwares will allow you to do this.
    2. Clone the system to the target disk (or a partition in the target disk) using the cloning software. If you are cloning the system that you have booted into, use the System Clone feature. If you are cloning the system partition on another disk/ partition, use the Clone Disk/ Partition feature.
    3. When using the System Clone feature, you will see that the hidden EFI partition is automatically included. This EFI partition is often broken in the target disk, and we will see how to fix this in the next section.
    4. Once cloning is complete, try booting from the target device. If it boots fine, great. If it doesn't boot, then here are the steps to make it boot.

    RECREATING THE EFI PARTITION


    Things Required

    1. Windows Recovery Disk (if you can't boot into Recovery or if the native Recovery doesn't have command prompt feature)

    Process

    1. Boot to Recovery. If you don't have one or if it is broken, then connect your Windows Recovery Disk (you have to create one if you don't already have it).
    2. Go to Command Prompt while in Recovery:

    diskpart
    list vol
    sel vol x (here 'x' is the volume number of the EFI partition of the target disk; check the result from the previous command)
    format quick fs=fat32 label="EFI T5Win10" (you can give any name that helps you to identify the partition easily; in my case, I was installing Windows 10 on my Samsung T5 SSD, hence I named it as EFI T5Win10; you can replace the text within the quotes with one of your choice)
    set id=C12A7328-F81F-11D2-BA4B-00A0C93EC93B
    assign letter=a (you can replace 'a' with any alphabet that is not currently in use)
    list vol (make sure that all the windows partitions in the target disk have a letter assigned to them; if any does not have a letter assigned, then assign a letter to each one of them as in the previous steps: select the correct volume number of the OS partition first and then assign a letter)

    exit

    Now we have to copy the boot files (which contain the OS paths) from each of the installed Windows OS to the EFI partition.

    Pass the following command(s):

    bcdboot c:\windows /s a: (here, I'm assuming that the letter for the OS partition is 'c'; check the letter in your case as it need not be 'c'; use the correct letter for the OS partition that you see in your case; repeat this command for all the operating systems installed in the target disk, replacing 'c' with the corresponding letter of the OS; also remember that 'a' is the letter I used for the EFI partition; if you have assigned a different letter, then replace 'a' with the letter you have assigned for the EFI partition)

    exit

    Reboot.

    If the disk has multiple OS installations, the OS Boot Manager should now show all of them, so you can choose which one to boot from.

    If your target disk has multiple OS installed, you will see that there is an EFI partition for each of them. You can safely format all those except the first one. The system prefers the EFI partition to be installed at the beginning of the disk, so keep the 1st one and format the rest. In our case, it is the one that we assigned the letter 'a'.

    To format the additional EFI partitions in the target disk, use DISKPART in command prompt:

    diskpart

    lis vol

    sel vol x (where 'x' is the volume number of the additional EFI partitions in the target disk; repeat this for all the additional EFI partitions)

    format quick fs=fat32

    Remember, that you must only delete the extra EFI partitions on the target disk, not the ones on other disks that are attached to your system.

    Every bootable disk must have atleast one EFI partition (preferably at the beginning of the disk because that is where the firmware first looks for one) and one Recovery partition. If you are using a multi-boot disk (assuming they are all Windows), a single EFI partition is enough that should contain the paths of all the OSes in the disk. The process above will accomplish this.

    Also, each disk needs to have just one Recovery partition. You don't need a separate EFI or separate Recovery partition for each of the OSes installed. Having one EFI and one Recovery on the disk itself would suffice.

    RECREATING THE RECOVERY PARTITION

    Things Required

    1. Windows ISO

    2. 7zip or any archiver installed

    Sometimes, the recovery partition can become corrupt. If that is the case, you won't be able to boot into Recovery or create a recovery drive. Troubleshooting Windows from recovery won't be possible in such cases. But we can restore it as follows:

    ____________________________________________________________________________________________________________________________

    If the recovery partition does not exist, create it as follows:

    Open command prompt with administrative privileges:

    diskpart
    list vol (note the volume number for Windows partition)
    sel vol x (where x is the volume number of the Windows partition from above result)
    shrink desired=630 (the Recovery partition for Win10_21H1_English_x64; you can assign a higher number if you want; e.g. 1024 to create a 1 GB partition for recovery)
    create par pri
    format quick fs=NTFS label=Recovery
    set id=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC (this is the id for Recovery partition)
    gpt attributes=0x8000000000000001
    exit

    ____________________________________________________________________________________________________________________________

    If the recovery partition already exists but is corrupt, then format the recovery partition using command prompt:

    diskpart

    list vol
    sel vol x (where 'x' is the volume number of the recovery partition from the result above)
    format fs=NTFS quick label=Recovery
    set id=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC (this is the id for Recovery partition)
    gpt attributes=0x8000000000000001
    exit

    ____________________________________________________________________________________________________________________________



    reagentc /disable

    Go to C:\Windows\System32\Recovery

    Delete all files there.

    NOTE: Recovery folder may be hidden, so you may have to set the option to show hidden files.

    Now, you have to copy the appropriate files from the Windows ISO.

    Copy WinRE.wim and the uninitialized ReAgent.xml files from the installation Media (ISO file) to C:\Windows\System32\Recovery

    Here are the steps:

    1. Right click the Windows ISO file
    2. Use 7zip to open archive (just open; don't have to extract it)
    3. Sources
    4. Locate the install.wim (or install.esd) file
    5. Right click and open
    6. Choose the correct folder for your edition of Windows:

    1 - Windows 10 Home
    2 - Windows 10 Home N
    3 - Windows 10 Home Single Language
    4 - Windows 10 Education
    5 - Windows 10 Education N
    6 - Windows 10 Pro
    7 - Windows 10 Pro N
    8 - Windows 10 Pro Education
    9 - Windows 10 Pro Education N
    10 - Windows 10 Pro for Workstations
    11 - Windows 10 Pro N for Workstations

    In case of Windows Home, choose the folder '1'; for Windows Pro, choose folder '6', etc.

    7. Go to Windows\ System32\ Recovery
    8. Copy the two files (ReAgent.xml and Winre.wim) to your system (C:\Windows\System32\Recovery)

    Back to command prompt with admin privileges:

    reagentc /enable (this will move WinRe.wim to the Recovery partition and set the GUID and location in ReAgent.xml)

    After restoring the recovery partition, you'll be able to create a recovery disk on an external USB device.

    IN ALL OF THE DISKPART COMMANDS, BE EXTREMELY CAREFUL IN SELECTING THE CORRECT VOLUMES/ PARTITIONS/ DISKS. YOU MUST ONLY SELECT THE VOLUMES IN YOUR TARGET DISK. DOUBLE CHECK THIS BEFORE PASSING THE COMMANDS.

    DISCLAIMER

    With the process above, you will have a bootable system with its own recovery environment. I am not sure if this breaks anything. Everything works fine as it should as far as I have tested. Your mileage may vary depending on the hardware you use and the way you use your system.
     
    TheMysticSA, Sep 2, 2024
    #4
Thema:

Windows 11 Boot EFI partition replacement / recreation

Loading...
  1. Windows 11 Boot EFI partition replacement / recreation - Similar Threads - Boot EFI partition

  2. Windows 11 Boot EFI partition replacement / recreation

    in Windows 10 Gaming
    Windows 11 Boot EFI partition replacement / recreation: TLDR; I want to recreate the EFI partition on a different disk.SATA-SSD Disk 0 -- Which is supposed to be a dedicated LINUX and Games windows.NVME Disk 2 -- Supposed to be Windows and Data.I had Linux already running off Disk 0. I re-formatted and deleted the NVME Disk 2...
  3. Windows 11 EFI Partition

    in Windows 10 Gaming
    Windows 11 EFI Partition: I recently upgraded from Windows 10 to 11. In that process the efi partition was deleted from my boot drive. What?? I have a bootable system as another partition on another drive is bootable. I have created a new efi on my c boot drive with diskpart and next I need to format...
  4. Windows 11 EFI Partition

    in Windows 10 Software and Apps
    Windows 11 EFI Partition: I recently upgraded from Windows 10 to 11. In that process the efi partition was deleted from my boot drive. What?? I have a bootable system as another partition on another drive is bootable. I have created a new efi on my c boot drive with diskpart and next I need to format...
  5. EFI Partition

    in Windows 10 Network and Sharing
    EFI Partition: Attached below is a screenshot of my disk managerI would like to make my C drive adjacent to the unallocated space so that I can expand the C drive into the 97 free gb. Is there a way I can move the EFI partition so that the C drive is adjacent to the unallocated space.Also...
  6. Cloning System Partition, Recreating EFI & Recovery partitions......

    in Windows 10 Gaming
    Cloning System Partition, Recreating EFI & Recovery partitions......: This guide is intended for educational purposes only.A fresh and clean installation is always the best thing to do, because in addition to a bug-free Windows experience, everything outside the Windows environment like the EFI partition, Recovery partition, and overall system...
  7. Cloning System Partition, Recreating EFI & Recovery partitions......

    in Windows 10 Software and Apps
    Cloning System Partition, Recreating EFI & Recovery partitions......: This guide is intended for educational purposes only.A fresh and clean installation is always the best thing to do, because in addition to a bug-free Windows experience, everything outside the Windows environment like the EFI partition, Recovery partition, and overall system...
  8. what is the best way to recreate a missing efi partition on a small ssd with windows 10?

    in Windows 10 Installation and Upgrade
    what is the best way to recreate a missing efi partition on a small ssd with windows 10?: After several failed attempts to download 10/18 Windows 10 to a new Intel Nuc..I somehow lost my EFI partition, so, I can only boot up with an external boot drive. I'venow installed current windows but, I see that I have no efi partition. How can I safely recreate one?...
  9. Moving / recreating EFI partition

    in Windows 10 Installation and Upgrade
    Moving / recreating EFI partition: I recently upgraded my laptop with an SSD, moving my older HDD into the optical drive bay. I then installed Windows 10 from a UEFI USB (using the Windows 10 media creation tool), on my SSD (with the HDD also installed). But the problem is the EFI partition is still on my HDD,...
  10. How to make an EFI Win10 boot instruction in EFI partition?

    in Windows 10 Support
    How to make an EFI Win10 boot instruction in EFI partition?: Hi all. There are hundreds of posts in these forums and on the internet about EFI and Windows 10 booting, but I can't seem to find a single one that describes how to boot Windows from an EFI partition. Short Background ------------------------ I have a 512GB SSD...