Windows 10: Add Recovery Partition to Windows 10 Boot Menu?

Page 1 of 3 123 LastLast
  1.    17 Feb 2017 #1

    Add Recovery Partition to Windows 10 Boot Menu?

    If I assign a drive letter to my recovery partition, can I then also create a boot menu entry for that partition? Macrium is perfectly happy to create and assign space for its recovery partition, and create a BCD entry for same so it shows up on the boot menu. That's got me wondering if the same thing is possible for the recovery partition that the Windows installer creates by default when Windows 10 is clean installed. Happy to hear instructions, suggestions, or disadvantages to this approach. Thanks!
    Last edited by EdTittel; 17 Feb 2017 at 10:27. Reason: correct typo/error
      My ComputersSystem Spec

  2.    17 Feb 2017 #2

    Yes, you can. I just tried it. I used MiniTool Partition Wizard and EasyBCD.

    In MiniTool Partition Wizard, assign a drive letter to your recovery partition. I used X:. Also use the explore feature to find the .wim file in the recovery partition. My path was \Recovery\WinodwsRE\Winre.wim.

    Then I used EasyBCD to a new WinPE entry. I manually entered the path to the .wim file: X:\Recovery\WinodwsRE\Winre.wim

    Then I removed the drive letter again from the recovery partition in MiniTool Partition Wizard.

    I don't know if there is any advantage to this or not, but that's one way you can do it.

    From EasyBCD:

    There are a total of 3 entries listed in the bootloader.

    Default: Windows 10 Pro
    Timeout: 3 seconds
    EasyBCD Boot Device: R:\

    Entry #1
    Name: Windows 10 Pro
    BCD ID: {current}
    Drive: C:\
    Bootloader Path: \WINDOWS\system32\winload.efi

    Entry #2
    Name: Windows 10 Home
    BCD ID: {fcaab809-8717-11e6-843d-aa73efa5da58}
    Drive: E:\
    Bootloader Path: \Windows\system32\winload.efi

    Entry #3
    Name: Recovery
    BCD ID: {fcaab814-8717-11e6-843d-aa73efa5da58}
    Device: [\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim
    Bootloader Path: \Windows\System32\Boot\winload.efi
      My ComputerSystem Spec

  3.    17 Feb 2017 #3

    Thanks, NavyLCDR! I was planning to try it out this weekend but you beat me to the punch. You realize this also means you can create a partition, mark it active, and put Kyhi's recovery environment on it, and so forth. Doesn't help if the drive goes kablooey, but most of my Windows booting problems are self-inflicted and if I have ready (and fast) access to a good recovery environment it will speed up triage! PLUS: it's the best argument I've thought of so far for buying a BIGGER boot SSD ("But Honey! I have to be able to recover when I shoot myself in the foot...).
    Thanks again,
      My ComputersSystem Spec

  4.    17 Feb 2017 #4

    EdTittel said: View Post
    Thanks, NavyLCDR! I was planning to try it out this weekend but you beat me to the punch. You realize this also means you can create a partition, mark it active, and put Kyhi's recovery environment on it, and so forth.
    I did that a long time ago, except I have UEFI computers so there is no active partition. I created a 5GB partition at the end of my hard drive. I extracted a standard Windows 10 installation ISO file to it. I replaced boot.wim in the \Sources folder with the boot.wim file from Kyhi's recovery tools. Then added that boot.wim file to the boot menu.

    As you stated, that way when I screw up my Windows installation to the point it won't boot, I can boot into Kyhi's recovery tools and either restore a Macrium Reflect backup image, or re-install Windows with a clean install. I can also run setup.exe from that partition from inside my running Windows 10 to do an "in place upgrade" repair install.

    Finally, when the new Creator's Edition upgrade comes out in April, the way I will install that is to extract the ISO file to my custom recovery partition (have to replace Kyhi's boot.wim file again), and run setup.exe from there for that.

    One more thing too, this also puts Kyhi's Recovery Tools as an option in my UEFI firmware boot menu, so even if I manage to wipe out my system partition, I think and hope I would still be able to boot into recovery stored on the hard drive. I'm going to get adventurous and try that next. Delete my EFI system partition and see if I can still boot into Kyhi's recovery stored on my hard drive to restore it from a backup image.
      My ComputerSystem Spec

  5.    17 Feb 2017 #5

    Awesome: I think I need to try that, too. Thanks one more time.
      My ComputersSystem Spec

  6.    17 Feb 2017 #6

    So I just tried it.

    Deleted the EFI System Partition. Computer booted into Kyhi's recovery tools automatically on next boot.
    Used Macrium Reflect Free to restore the EFI system partition. Computer rebooted into Kyhi's recovery tools again.
    Rebooted the computer into UEFI setup and I had to move Windows Boot Manager back to the top of the boot list.
    Computer rebooted back into my normal Windows boot menu!
      My ComputerSystem Spec

  7.    17 Feb 2017 #7

    I just run a 60gb mSata (same speed as Samsung Evo but under half the price ) as my OS & all my files are up in one drive & backed up to usb dongle every month then every year I make a cd copy of my yearly backups for archive then delete last years saves of my memory stick myself, if I have any big projects to do I use my 240gb ssd which is on a power switch so stays off most of the time.

    The switching allows me to have multiple OS systems on the same PC without spreading viruses ect als I can seperate my game drives.

    Click image for larger version. 

Name:	switches pc.jpg 
Views:	2 
Size:	255.8 KB 
ID:	121507

    I only have the OS switched on as in picture right now.
      My ComputerSystem Spec

  8.    17 Feb 2017 #8

    Hey @NavyLCDR: when you set up the WinPE entry in EasyBCD, did you pick the default WIM Image (Ramdisk) option or did you go for the Extracted filesystem layout option. I could see this going either way, depending on how it's loaded. Just curious to know what you chose, because yours is already working. I can always try the experimental method, I know, but I figured I'd ask you first.
    Also did you check the "EMS Enabled" checkbox or not for that one?

    [Note: tried the experimental method. Works fine using the WIM Image (Ramdisk) approach. I didn't check the EMS checkbox, either. Thanks for the great guidance. You should do a tutorial on it. Lots of people could benefit from this.]
    Last edited by EdTittel; 17 Feb 2017 at 13:55. Reason: Add more info
      My ComputersSystem Spec

  9.    17 Feb 2017 #9

    Default ramdisk without EMS checked.
      My ComputerSystem Spec

  10. Ztruker's Avatar
    Posts : 6,275
    Windows 10 Pro X64 17134.191
       17 Feb 2017 #10

    The recovery partition can be on another drive, right? That would eliminate the possibility of the boot drive leaving you bootless (so to speak).
      My ComputersSystem Spec

Page 1 of 3 123 LastLast

Related Threads
After I did a clean install of Win10 about a year ago, I created a USB Recovery Drive. I also have a Norton Security Recovery Drive and Iíve created USB Bootable PE Rescue Disk by Kyhi. I also use Acronis to create regular full disk images and I...
Hello. I have been dualbooting OS X and Windows 8 (then 10) using Clover bootloader for over 2,5 years now. It's not ideal, but it works, or worked, up until today. After restarting from OS X to boot into W10 I got the "infinite spinner", which...
Hi, My Vaio laptop came with a built-in recovery partition (it's 'bout 32GB and hidden). Sometimes I use it to reset my PC back to factory conditions due to unexpected errors. But yesterday I was shocked 'cuz Windows Disk Management showed that...
Solved F8 Boot Menu Partition Questions in Performance & Maintenance
Okay, I have decided to get ready to remove my pesky 4.88GB Windows 8.1 Partition (partition 5) from my PC because now I have Windows 10 and no longer have the option to go back. I have used a Command in the Elevated Command Prompt to enable the F8...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:14.
Find Us