Cannot permanently remove boot entry using efibootmgr












0















My notebook is Lenovo G50-45. I have two dual boot systems Windows 10 and Ubuntu 16.04. I also had Phoenix OS with separate dual boot with Windows 10 (I suppose there is second Grub). I deleted unused system Phoenix via Gparted. Though I cannot delete the efi boot entry. Precisely, I can delete it, but it shows up again after reboot.
I used efibootmgr in Linux:



sudo efibootmgr -b 6 -B


In Windows I tried EasyUefi, there it shows even after refresh I do not have to reboot.
I do not understand much what is happening by EFI booting. Can someone suggest solution?
Here are my current settings:



honza@lenovoG50:~$ sudo efibootmgr -v
BootCurrent: 0004
Timeout: 15 seconds
BootOrder: 0004,0003,2003,0005,0006,0000,2001,2002
Boot0000* Lenovo Recovery System HD(3,GPT,b11a59bf-42d6-4548-b244-1858af8a20e4,0x276800,0x1f4000)/File(EFIMicrosoftBootLrsBootMgr.efi)RC
Boot0001* EFI Network 0 for IPv4 (68-F7-28-92-3E-35) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/MAC(68f728923e35,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
Boot0002* EFI Network 0 for IPv6 (68-F7-28-92-3E-35) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/MAC(68f728923e35,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0003* Windows Boot Manager HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0004* ubuntu HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIubuntushimx64.efi)
Boot0005* ubuntu HD(3,GPT,b11a59bf-42d6-4548-b244-1858af8a20e4,0x276800,0x1f4000)/File(EFIubuntushimx64.efi)RC
Boot0006* Phoenix OS HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIPhoenixOSBootbootx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.1.e.a.a.d.8.9.3.-.d.e.d.e.-.1.1.e.7.-.b.f.a.7.-.b.5.e.0.8.c.6.0.2.4.d.f.}....................
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC


EDIT



I followed advice and after reboot to Windows this is output of EasyUEFI:
EasyUEFI list of boot entries.










share|improve this question

























  • This answer may help you.

    – user68186
    Jan 23 at 17:11
















0















My notebook is Lenovo G50-45. I have two dual boot systems Windows 10 and Ubuntu 16.04. I also had Phoenix OS with separate dual boot with Windows 10 (I suppose there is second Grub). I deleted unused system Phoenix via Gparted. Though I cannot delete the efi boot entry. Precisely, I can delete it, but it shows up again after reboot.
I used efibootmgr in Linux:



sudo efibootmgr -b 6 -B


In Windows I tried EasyUefi, there it shows even after refresh I do not have to reboot.
I do not understand much what is happening by EFI booting. Can someone suggest solution?
Here are my current settings:



honza@lenovoG50:~$ sudo efibootmgr -v
BootCurrent: 0004
Timeout: 15 seconds
BootOrder: 0004,0003,2003,0005,0006,0000,2001,2002
Boot0000* Lenovo Recovery System HD(3,GPT,b11a59bf-42d6-4548-b244-1858af8a20e4,0x276800,0x1f4000)/File(EFIMicrosoftBootLrsBootMgr.efi)RC
Boot0001* EFI Network 0 for IPv4 (68-F7-28-92-3E-35) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/MAC(68f728923e35,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
Boot0002* EFI Network 0 for IPv6 (68-F7-28-92-3E-35) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/MAC(68f728923e35,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0003* Windows Boot Manager HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0004* ubuntu HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIubuntushimx64.efi)
Boot0005* ubuntu HD(3,GPT,b11a59bf-42d6-4548-b244-1858af8a20e4,0x276800,0x1f4000)/File(EFIubuntushimx64.efi)RC
Boot0006* Phoenix OS HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIPhoenixOSBootbootx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.1.e.a.a.d.8.9.3.-.d.e.d.e.-.1.1.e.7.-.b.f.a.7.-.b.5.e.0.8.c.6.0.2.4.d.f.}....................
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC


EDIT



I followed advice and after reboot to Windows this is output of EasyUEFI:
EasyUEFI list of boot entries.










share|improve this question

























  • This answer may help you.

    – user68186
    Jan 23 at 17:11














0












0








0








My notebook is Lenovo G50-45. I have two dual boot systems Windows 10 and Ubuntu 16.04. I also had Phoenix OS with separate dual boot with Windows 10 (I suppose there is second Grub). I deleted unused system Phoenix via Gparted. Though I cannot delete the efi boot entry. Precisely, I can delete it, but it shows up again after reboot.
I used efibootmgr in Linux:



sudo efibootmgr -b 6 -B


In Windows I tried EasyUefi, there it shows even after refresh I do not have to reboot.
I do not understand much what is happening by EFI booting. Can someone suggest solution?
Here are my current settings:



honza@lenovoG50:~$ sudo efibootmgr -v
BootCurrent: 0004
Timeout: 15 seconds
BootOrder: 0004,0003,2003,0005,0006,0000,2001,2002
Boot0000* Lenovo Recovery System HD(3,GPT,b11a59bf-42d6-4548-b244-1858af8a20e4,0x276800,0x1f4000)/File(EFIMicrosoftBootLrsBootMgr.efi)RC
Boot0001* EFI Network 0 for IPv4 (68-F7-28-92-3E-35) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/MAC(68f728923e35,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
Boot0002* EFI Network 0 for IPv6 (68-F7-28-92-3E-35) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/MAC(68f728923e35,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0003* Windows Boot Manager HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0004* ubuntu HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIubuntushimx64.efi)
Boot0005* ubuntu HD(3,GPT,b11a59bf-42d6-4548-b244-1858af8a20e4,0x276800,0x1f4000)/File(EFIubuntushimx64.efi)RC
Boot0006* Phoenix OS HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIPhoenixOSBootbootx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.1.e.a.a.d.8.9.3.-.d.e.d.e.-.1.1.e.7.-.b.f.a.7.-.b.5.e.0.8.c.6.0.2.4.d.f.}....................
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC


EDIT



I followed advice and after reboot to Windows this is output of EasyUEFI:
EasyUEFI list of boot entries.










share|improve this question
















My notebook is Lenovo G50-45. I have two dual boot systems Windows 10 and Ubuntu 16.04. I also had Phoenix OS with separate dual boot with Windows 10 (I suppose there is second Grub). I deleted unused system Phoenix via Gparted. Though I cannot delete the efi boot entry. Precisely, I can delete it, but it shows up again after reboot.
I used efibootmgr in Linux:



sudo efibootmgr -b 6 -B


In Windows I tried EasyUefi, there it shows even after refresh I do not have to reboot.
I do not understand much what is happening by EFI booting. Can someone suggest solution?
Here are my current settings:



honza@lenovoG50:~$ sudo efibootmgr -v
BootCurrent: 0004
Timeout: 15 seconds
BootOrder: 0004,0003,2003,0005,0006,0000,2001,2002
Boot0000* Lenovo Recovery System HD(3,GPT,b11a59bf-42d6-4548-b244-1858af8a20e4,0x276800,0x1f4000)/File(EFIMicrosoftBootLrsBootMgr.efi)RC
Boot0001* EFI Network 0 for IPv4 (68-F7-28-92-3E-35) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/MAC(68f728923e35,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
Boot0002* EFI Network 0 for IPv6 (68-F7-28-92-3E-35) PciRoot(0x0)/Pci(0x2,0x4)/Pci(0x0,0x0)/MAC(68f728923e35,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0003* Windows Boot Manager HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0004* ubuntu HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIubuntushimx64.efi)
Boot0005* ubuntu HD(3,GPT,b11a59bf-42d6-4548-b244-1858af8a20e4,0x276800,0x1f4000)/File(EFIubuntushimx64.efi)RC
Boot0006* Phoenix OS HD(2,GPT,c3623e25-a72c-492b-8ff5-9ea449e37436,0x1f4800,0x82000)/File(EFIPhoenixOSBootbootx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.1.e.a.a.d.8.9.3.-.d.e.d.e.-.1.1.e.7.-.b.f.a.7.-.b.5.e.0.8.c.6.0.2.4.d.f.}....................
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC


EDIT



I followed advice and after reboot to Windows this is output of EasyUEFI:
EasyUEFI list of boot entries.







dual-boot grub2 uefi






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 23 at 17:06







weatherman

















asked Jan 23 at 13:37









weathermanweatherman

499




499













  • This answer may help you.

    – user68186
    Jan 23 at 17:11



















  • This answer may help you.

    – user68186
    Jan 23 at 17:11

















This answer may help you.

– user68186
Jan 23 at 17:11





This answer may help you.

– user68186
Jan 23 at 17:11










3 Answers
3






active

oldest

votes


















0














When logged into the installed Ubuntu, type the following command, as root, to delete a specific entry:



efibootmgr -b 0006 -B


The number (0006) is the hexadecimal number representing the entry you want to delete.



and type in the terminal:



sudo update-grub





share|improve this answer


























  • Vijay: It removed entry in linux. I did not see it in BIOS, after I booted to Windows and started EasyUEFI it was here. Could be there some backup process?

    – weatherman
    Jan 23 at 16:55











  • What happens when you do sudo update-grub.

    – Vijay
    Jan 23 at 17:05











  • I re-do the process, when Phoenix appears in Ubuntu: honza@lenovoG50:~$ sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-141-generic Found initrd image: /boot/initrd.img-4.4.0-141-generic Found linux image: /boot/vmlinuz-4.4.0-140-generic Found initrd image: /boot/initrd.img-4.4.0-140-generic Found linux image: /boot/vmlinuz-4.4.0-130-generic Found initrd image: /boot/initrd.img-4.4.0-130-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done

    – weatherman
    Jan 23 at 17:17








  • 1





    If not solved try from Windows If still not solved it is a firmware problem. See this also

    – Vijay
    Jan 23 at 18:00











  • It seems that try from Windows with proper options worked. So delete phoenix EFI folder seems to be a solution.

    – weatherman
    Jan 23 at 19:16



















0














In my case I incorrectly formatted Phoenix OS, it did not do any visible damage, and also did many other attempts and experiment. Surprisingly, I could boot all system I have (Windows 10, ubuntu 16.04).
Therefore



1. If your plan is to uninstall Phoenix OS, find proper instructions



(see e. g. my https://superuser.com/questions/1398508/difference-between-easyuefi-boot-item-and-mounted-disk-folder/1398626#1398626
B. paragraph)



2. Removing Phoenix system boot entry, if you incorrectly uninstalled Phoenix OS



a) In ubuntu efibootmgr does not seem to do much. Only check what entries are there by:



 sudo efibootmgr -v


b) In Windows the easiest way comes from:



https://www.youtube.com/watch?v=zyOBF2ePvHY



using bcdedit in admin command prompt: to see all bootable options.



bcdedit /enum all 


There are (usually) many items. So, if you see it for the first time you may get lost. I think the best is to compare it with EasyUEFI outup. See in picture in question:



File path:EFIPhoenixOSBootbootx64.efi.


I show small part of my bcdedit /enum all output:



 Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {1eaad893-dede-11e7-bfa7-b5e08c6024df}
{933ae2d3-bf4b-11e4-8258-68f728923e35}
{19f0e09b-20f3-11e9-83f9-806e6f6e6963}
{c2d01e39-20bc-11e9-83f6-806e6f6e6963}
{203b70a1-1fd2-11e9-83f3-806e6f6e6963}
{881ea240-bf4f-11e4-8a37-806e6f6e6963}
{881ea242-bf4f-11e4-8a37-806e6f6e6963}
{881ea23e-bf4f-11e4-8a37-806e6f6e6963}
{164f529a-6ec2-11e7-8308-806e6f6e6963}
timeout 6

Windows Boot Manager
--------------------
identifier {1eaad893-dede-11e7-bfa7-b5e08c6024df}
device partition=DeviceHarddiskVolume2
path EFIPhoenixOSBootbootx64.efi
description Phoenix OS
locale en-US
inherit {globalsettings}
resumeobject {933ae2da-bf4b-11e4-8258-68f728923e35}
toolsdisplayorder {memdiag}
timeout 0


I did not care about "Windows Boot Manager" important is path for identification. Next you have to copy UUID (=identifier item) {1eaad893-dede-11e7-bfa7-b5e08c6024df}. (It should vary in your case). And delete this entry by:



bcdedit /delete {1eaad893-dede-11e7-bfa7-b5e08c6024df}


I did reboot. But I think it is not necessary. Now, you should not see Phoenix OS boot entry either in EasyUEFI nor by bcdedit /enum all nor in BIOS boot options. That is it.






share|improve this answer































    0














    'Grub Customizer' worked easily for me. I'm running ver. 5.1.1 on Ubuntu 18.04.
    http://ubuntuhandbook.org/index.php/2016/04/install-grub-customizer-ubuntu-16-04-lts/



    After using Boot repair I had multiple Win10 listings in boot two booted correctly into windows two did not. Grub Customizer easily fixed that. You can revert back also.



    https://sourceforge.net/p/boot-repair/home/Home/






    share|improve this answer



















    • 1





      Welcome to Ask Ubuntu! If possible you should explain in your answer the steps needed instead of linking to remote sources, since they are likely to change or go offline in the future. Thanks!

      – Kristopher Ives
      Jan 29 at 8:09











    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112243%2fcannot-permanently-remove-boot-entry-using-efibootmgr%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    When logged into the installed Ubuntu, type the following command, as root, to delete a specific entry:



    efibootmgr -b 0006 -B


    The number (0006) is the hexadecimal number representing the entry you want to delete.



    and type in the terminal:



    sudo update-grub





    share|improve this answer


























    • Vijay: It removed entry in linux. I did not see it in BIOS, after I booted to Windows and started EasyUEFI it was here. Could be there some backup process?

      – weatherman
      Jan 23 at 16:55











    • What happens when you do sudo update-grub.

      – Vijay
      Jan 23 at 17:05











    • I re-do the process, when Phoenix appears in Ubuntu: honza@lenovoG50:~$ sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-141-generic Found initrd image: /boot/initrd.img-4.4.0-141-generic Found linux image: /boot/vmlinuz-4.4.0-140-generic Found initrd image: /boot/initrd.img-4.4.0-140-generic Found linux image: /boot/vmlinuz-4.4.0-130-generic Found initrd image: /boot/initrd.img-4.4.0-130-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done

      – weatherman
      Jan 23 at 17:17








    • 1





      If not solved try from Windows If still not solved it is a firmware problem. See this also

      – Vijay
      Jan 23 at 18:00











    • It seems that try from Windows with proper options worked. So delete phoenix EFI folder seems to be a solution.

      – weatherman
      Jan 23 at 19:16
















    0














    When logged into the installed Ubuntu, type the following command, as root, to delete a specific entry:



    efibootmgr -b 0006 -B


    The number (0006) is the hexadecimal number representing the entry you want to delete.



    and type in the terminal:



    sudo update-grub





    share|improve this answer


























    • Vijay: It removed entry in linux. I did not see it in BIOS, after I booted to Windows and started EasyUEFI it was here. Could be there some backup process?

      – weatherman
      Jan 23 at 16:55











    • What happens when you do sudo update-grub.

      – Vijay
      Jan 23 at 17:05











    • I re-do the process, when Phoenix appears in Ubuntu: honza@lenovoG50:~$ sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-141-generic Found initrd image: /boot/initrd.img-4.4.0-141-generic Found linux image: /boot/vmlinuz-4.4.0-140-generic Found initrd image: /boot/initrd.img-4.4.0-140-generic Found linux image: /boot/vmlinuz-4.4.0-130-generic Found initrd image: /boot/initrd.img-4.4.0-130-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done

      – weatherman
      Jan 23 at 17:17








    • 1





      If not solved try from Windows If still not solved it is a firmware problem. See this also

      – Vijay
      Jan 23 at 18:00











    • It seems that try from Windows with proper options worked. So delete phoenix EFI folder seems to be a solution.

      – weatherman
      Jan 23 at 19:16














    0












    0








    0







    When logged into the installed Ubuntu, type the following command, as root, to delete a specific entry:



    efibootmgr -b 0006 -B


    The number (0006) is the hexadecimal number representing the entry you want to delete.



    and type in the terminal:



    sudo update-grub





    share|improve this answer















    When logged into the installed Ubuntu, type the following command, as root, to delete a specific entry:



    efibootmgr -b 0006 -B


    The number (0006) is the hexadecimal number representing the entry you want to delete.



    and type in the terminal:



    sudo update-grub






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jan 23 at 16:48









    weatherman

    499




    499










    answered Jan 23 at 14:16









    VijayVijay

    1,8101720




    1,8101720













    • Vijay: It removed entry in linux. I did not see it in BIOS, after I booted to Windows and started EasyUEFI it was here. Could be there some backup process?

      – weatherman
      Jan 23 at 16:55











    • What happens when you do sudo update-grub.

      – Vijay
      Jan 23 at 17:05











    • I re-do the process, when Phoenix appears in Ubuntu: honza@lenovoG50:~$ sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-141-generic Found initrd image: /boot/initrd.img-4.4.0-141-generic Found linux image: /boot/vmlinuz-4.4.0-140-generic Found initrd image: /boot/initrd.img-4.4.0-140-generic Found linux image: /boot/vmlinuz-4.4.0-130-generic Found initrd image: /boot/initrd.img-4.4.0-130-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done

      – weatherman
      Jan 23 at 17:17








    • 1





      If not solved try from Windows If still not solved it is a firmware problem. See this also

      – Vijay
      Jan 23 at 18:00











    • It seems that try from Windows with proper options worked. So delete phoenix EFI folder seems to be a solution.

      – weatherman
      Jan 23 at 19:16



















    • Vijay: It removed entry in linux. I did not see it in BIOS, after I booted to Windows and started EasyUEFI it was here. Could be there some backup process?

      – weatherman
      Jan 23 at 16:55











    • What happens when you do sudo update-grub.

      – Vijay
      Jan 23 at 17:05











    • I re-do the process, when Phoenix appears in Ubuntu: honza@lenovoG50:~$ sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-141-generic Found initrd image: /boot/initrd.img-4.4.0-141-generic Found linux image: /boot/vmlinuz-4.4.0-140-generic Found initrd image: /boot/initrd.img-4.4.0-140-generic Found linux image: /boot/vmlinuz-4.4.0-130-generic Found initrd image: /boot/initrd.img-4.4.0-130-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done

      – weatherman
      Jan 23 at 17:17








    • 1





      If not solved try from Windows If still not solved it is a firmware problem. See this also

      – Vijay
      Jan 23 at 18:00











    • It seems that try from Windows with proper options worked. So delete phoenix EFI folder seems to be a solution.

      – weatherman
      Jan 23 at 19:16

















    Vijay: It removed entry in linux. I did not see it in BIOS, after I booted to Windows and started EasyUEFI it was here. Could be there some backup process?

    – weatherman
    Jan 23 at 16:55





    Vijay: It removed entry in linux. I did not see it in BIOS, after I booted to Windows and started EasyUEFI it was here. Could be there some backup process?

    – weatherman
    Jan 23 at 16:55













    What happens when you do sudo update-grub.

    – Vijay
    Jan 23 at 17:05





    What happens when you do sudo update-grub.

    – Vijay
    Jan 23 at 17:05













    I re-do the process, when Phoenix appears in Ubuntu: honza@lenovoG50:~$ sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-141-generic Found initrd image: /boot/initrd.img-4.4.0-141-generic Found linux image: /boot/vmlinuz-4.4.0-140-generic Found initrd image: /boot/initrd.img-4.4.0-140-generic Found linux image: /boot/vmlinuz-4.4.0-130-generic Found initrd image: /boot/initrd.img-4.4.0-130-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done

    – weatherman
    Jan 23 at 17:17







    I re-do the process, when Phoenix appears in Ubuntu: honza@lenovoG50:~$ sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-141-generic Found initrd image: /boot/initrd.img-4.4.0-141-generic Found linux image: /boot/vmlinuz-4.4.0-140-generic Found initrd image: /boot/initrd.img-4.4.0-140-generic Found linux image: /boot/vmlinuz-4.4.0-130-generic Found initrd image: /boot/initrd.img-4.4.0-130-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done

    – weatherman
    Jan 23 at 17:17






    1




    1





    If not solved try from Windows If still not solved it is a firmware problem. See this also

    – Vijay
    Jan 23 at 18:00





    If not solved try from Windows If still not solved it is a firmware problem. See this also

    – Vijay
    Jan 23 at 18:00













    It seems that try from Windows with proper options worked. So delete phoenix EFI folder seems to be a solution.

    – weatherman
    Jan 23 at 19:16





    It seems that try from Windows with proper options worked. So delete phoenix EFI folder seems to be a solution.

    – weatherman
    Jan 23 at 19:16













    0














    In my case I incorrectly formatted Phoenix OS, it did not do any visible damage, and also did many other attempts and experiment. Surprisingly, I could boot all system I have (Windows 10, ubuntu 16.04).
    Therefore



    1. If your plan is to uninstall Phoenix OS, find proper instructions



    (see e. g. my https://superuser.com/questions/1398508/difference-between-easyuefi-boot-item-and-mounted-disk-folder/1398626#1398626
    B. paragraph)



    2. Removing Phoenix system boot entry, if you incorrectly uninstalled Phoenix OS



    a) In ubuntu efibootmgr does not seem to do much. Only check what entries are there by:



     sudo efibootmgr -v


    b) In Windows the easiest way comes from:



    https://www.youtube.com/watch?v=zyOBF2ePvHY



    using bcdedit in admin command prompt: to see all bootable options.



    bcdedit /enum all 


    There are (usually) many items. So, if you see it for the first time you may get lost. I think the best is to compare it with EasyUEFI outup. See in picture in question:



    File path:EFIPhoenixOSBootbootx64.efi.


    I show small part of my bcdedit /enum all output:



     Firmware Boot Manager
    ---------------------
    identifier {fwbootmgr}
    displayorder {1eaad893-dede-11e7-bfa7-b5e08c6024df}
    {933ae2d3-bf4b-11e4-8258-68f728923e35}
    {19f0e09b-20f3-11e9-83f9-806e6f6e6963}
    {c2d01e39-20bc-11e9-83f6-806e6f6e6963}
    {203b70a1-1fd2-11e9-83f3-806e6f6e6963}
    {881ea240-bf4f-11e4-8a37-806e6f6e6963}
    {881ea242-bf4f-11e4-8a37-806e6f6e6963}
    {881ea23e-bf4f-11e4-8a37-806e6f6e6963}
    {164f529a-6ec2-11e7-8308-806e6f6e6963}
    timeout 6

    Windows Boot Manager
    --------------------
    identifier {1eaad893-dede-11e7-bfa7-b5e08c6024df}
    device partition=DeviceHarddiskVolume2
    path EFIPhoenixOSBootbootx64.efi
    description Phoenix OS
    locale en-US
    inherit {globalsettings}
    resumeobject {933ae2da-bf4b-11e4-8258-68f728923e35}
    toolsdisplayorder {memdiag}
    timeout 0


    I did not care about "Windows Boot Manager" important is path for identification. Next you have to copy UUID (=identifier item) {1eaad893-dede-11e7-bfa7-b5e08c6024df}. (It should vary in your case). And delete this entry by:



    bcdedit /delete {1eaad893-dede-11e7-bfa7-b5e08c6024df}


    I did reboot. But I think it is not necessary. Now, you should not see Phoenix OS boot entry either in EasyUEFI nor by bcdedit /enum all nor in BIOS boot options. That is it.






    share|improve this answer




























      0














      In my case I incorrectly formatted Phoenix OS, it did not do any visible damage, and also did many other attempts and experiment. Surprisingly, I could boot all system I have (Windows 10, ubuntu 16.04).
      Therefore



      1. If your plan is to uninstall Phoenix OS, find proper instructions



      (see e. g. my https://superuser.com/questions/1398508/difference-between-easyuefi-boot-item-and-mounted-disk-folder/1398626#1398626
      B. paragraph)



      2. Removing Phoenix system boot entry, if you incorrectly uninstalled Phoenix OS



      a) In ubuntu efibootmgr does not seem to do much. Only check what entries are there by:



       sudo efibootmgr -v


      b) In Windows the easiest way comes from:



      https://www.youtube.com/watch?v=zyOBF2ePvHY



      using bcdedit in admin command prompt: to see all bootable options.



      bcdedit /enum all 


      There are (usually) many items. So, if you see it for the first time you may get lost. I think the best is to compare it with EasyUEFI outup. See in picture in question:



      File path:EFIPhoenixOSBootbootx64.efi.


      I show small part of my bcdedit /enum all output:



       Firmware Boot Manager
      ---------------------
      identifier {fwbootmgr}
      displayorder {1eaad893-dede-11e7-bfa7-b5e08c6024df}
      {933ae2d3-bf4b-11e4-8258-68f728923e35}
      {19f0e09b-20f3-11e9-83f9-806e6f6e6963}
      {c2d01e39-20bc-11e9-83f6-806e6f6e6963}
      {203b70a1-1fd2-11e9-83f3-806e6f6e6963}
      {881ea240-bf4f-11e4-8a37-806e6f6e6963}
      {881ea242-bf4f-11e4-8a37-806e6f6e6963}
      {881ea23e-bf4f-11e4-8a37-806e6f6e6963}
      {164f529a-6ec2-11e7-8308-806e6f6e6963}
      timeout 6

      Windows Boot Manager
      --------------------
      identifier {1eaad893-dede-11e7-bfa7-b5e08c6024df}
      device partition=DeviceHarddiskVolume2
      path EFIPhoenixOSBootbootx64.efi
      description Phoenix OS
      locale en-US
      inherit {globalsettings}
      resumeobject {933ae2da-bf4b-11e4-8258-68f728923e35}
      toolsdisplayorder {memdiag}
      timeout 0


      I did not care about "Windows Boot Manager" important is path for identification. Next you have to copy UUID (=identifier item) {1eaad893-dede-11e7-bfa7-b5e08c6024df}. (It should vary in your case). And delete this entry by:



      bcdedit /delete {1eaad893-dede-11e7-bfa7-b5e08c6024df}


      I did reboot. But I think it is not necessary. Now, you should not see Phoenix OS boot entry either in EasyUEFI nor by bcdedit /enum all nor in BIOS boot options. That is it.






      share|improve this answer


























        0












        0








        0







        In my case I incorrectly formatted Phoenix OS, it did not do any visible damage, and also did many other attempts and experiment. Surprisingly, I could boot all system I have (Windows 10, ubuntu 16.04).
        Therefore



        1. If your plan is to uninstall Phoenix OS, find proper instructions



        (see e. g. my https://superuser.com/questions/1398508/difference-between-easyuefi-boot-item-and-mounted-disk-folder/1398626#1398626
        B. paragraph)



        2. Removing Phoenix system boot entry, if you incorrectly uninstalled Phoenix OS



        a) In ubuntu efibootmgr does not seem to do much. Only check what entries are there by:



         sudo efibootmgr -v


        b) In Windows the easiest way comes from:



        https://www.youtube.com/watch?v=zyOBF2ePvHY



        using bcdedit in admin command prompt: to see all bootable options.



        bcdedit /enum all 


        There are (usually) many items. So, if you see it for the first time you may get lost. I think the best is to compare it with EasyUEFI outup. See in picture in question:



        File path:EFIPhoenixOSBootbootx64.efi.


        I show small part of my bcdedit /enum all output:



         Firmware Boot Manager
        ---------------------
        identifier {fwbootmgr}
        displayorder {1eaad893-dede-11e7-bfa7-b5e08c6024df}
        {933ae2d3-bf4b-11e4-8258-68f728923e35}
        {19f0e09b-20f3-11e9-83f9-806e6f6e6963}
        {c2d01e39-20bc-11e9-83f6-806e6f6e6963}
        {203b70a1-1fd2-11e9-83f3-806e6f6e6963}
        {881ea240-bf4f-11e4-8a37-806e6f6e6963}
        {881ea242-bf4f-11e4-8a37-806e6f6e6963}
        {881ea23e-bf4f-11e4-8a37-806e6f6e6963}
        {164f529a-6ec2-11e7-8308-806e6f6e6963}
        timeout 6

        Windows Boot Manager
        --------------------
        identifier {1eaad893-dede-11e7-bfa7-b5e08c6024df}
        device partition=DeviceHarddiskVolume2
        path EFIPhoenixOSBootbootx64.efi
        description Phoenix OS
        locale en-US
        inherit {globalsettings}
        resumeobject {933ae2da-bf4b-11e4-8258-68f728923e35}
        toolsdisplayorder {memdiag}
        timeout 0


        I did not care about "Windows Boot Manager" important is path for identification. Next you have to copy UUID (=identifier item) {1eaad893-dede-11e7-bfa7-b5e08c6024df}. (It should vary in your case). And delete this entry by:



        bcdedit /delete {1eaad893-dede-11e7-bfa7-b5e08c6024df}


        I did reboot. But I think it is not necessary. Now, you should not see Phoenix OS boot entry either in EasyUEFI nor by bcdedit /enum all nor in BIOS boot options. That is it.






        share|improve this answer













        In my case I incorrectly formatted Phoenix OS, it did not do any visible damage, and also did many other attempts and experiment. Surprisingly, I could boot all system I have (Windows 10, ubuntu 16.04).
        Therefore



        1. If your plan is to uninstall Phoenix OS, find proper instructions



        (see e. g. my https://superuser.com/questions/1398508/difference-between-easyuefi-boot-item-and-mounted-disk-folder/1398626#1398626
        B. paragraph)



        2. Removing Phoenix system boot entry, if you incorrectly uninstalled Phoenix OS



        a) In ubuntu efibootmgr does not seem to do much. Only check what entries are there by:



         sudo efibootmgr -v


        b) In Windows the easiest way comes from:



        https://www.youtube.com/watch?v=zyOBF2ePvHY



        using bcdedit in admin command prompt: to see all bootable options.



        bcdedit /enum all 


        There are (usually) many items. So, if you see it for the first time you may get lost. I think the best is to compare it with EasyUEFI outup. See in picture in question:



        File path:EFIPhoenixOSBootbootx64.efi.


        I show small part of my bcdedit /enum all output:



         Firmware Boot Manager
        ---------------------
        identifier {fwbootmgr}
        displayorder {1eaad893-dede-11e7-bfa7-b5e08c6024df}
        {933ae2d3-bf4b-11e4-8258-68f728923e35}
        {19f0e09b-20f3-11e9-83f9-806e6f6e6963}
        {c2d01e39-20bc-11e9-83f6-806e6f6e6963}
        {203b70a1-1fd2-11e9-83f3-806e6f6e6963}
        {881ea240-bf4f-11e4-8a37-806e6f6e6963}
        {881ea242-bf4f-11e4-8a37-806e6f6e6963}
        {881ea23e-bf4f-11e4-8a37-806e6f6e6963}
        {164f529a-6ec2-11e7-8308-806e6f6e6963}
        timeout 6

        Windows Boot Manager
        --------------------
        identifier {1eaad893-dede-11e7-bfa7-b5e08c6024df}
        device partition=DeviceHarddiskVolume2
        path EFIPhoenixOSBootbootx64.efi
        description Phoenix OS
        locale en-US
        inherit {globalsettings}
        resumeobject {933ae2da-bf4b-11e4-8258-68f728923e35}
        toolsdisplayorder {memdiag}
        timeout 0


        I did not care about "Windows Boot Manager" important is path for identification. Next you have to copy UUID (=identifier item) {1eaad893-dede-11e7-bfa7-b5e08c6024df}. (It should vary in your case). And delete this entry by:



        bcdedit /delete {1eaad893-dede-11e7-bfa7-b5e08c6024df}


        I did reboot. But I think it is not necessary. Now, you should not see Phoenix OS boot entry either in EasyUEFI nor by bcdedit /enum all nor in BIOS boot options. That is it.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 26 at 10:18









        weathermanweatherman

        499




        499























            0














            'Grub Customizer' worked easily for me. I'm running ver. 5.1.1 on Ubuntu 18.04.
            http://ubuntuhandbook.org/index.php/2016/04/install-grub-customizer-ubuntu-16-04-lts/



            After using Boot repair I had multiple Win10 listings in boot two booted correctly into windows two did not. Grub Customizer easily fixed that. You can revert back also.



            https://sourceforge.net/p/boot-repair/home/Home/






            share|improve this answer



















            • 1





              Welcome to Ask Ubuntu! If possible you should explain in your answer the steps needed instead of linking to remote sources, since they are likely to change or go offline in the future. Thanks!

              – Kristopher Ives
              Jan 29 at 8:09
















            0














            'Grub Customizer' worked easily for me. I'm running ver. 5.1.1 on Ubuntu 18.04.
            http://ubuntuhandbook.org/index.php/2016/04/install-grub-customizer-ubuntu-16-04-lts/



            After using Boot repair I had multiple Win10 listings in boot two booted correctly into windows two did not. Grub Customizer easily fixed that. You can revert back also.



            https://sourceforge.net/p/boot-repair/home/Home/






            share|improve this answer



















            • 1





              Welcome to Ask Ubuntu! If possible you should explain in your answer the steps needed instead of linking to remote sources, since they are likely to change or go offline in the future. Thanks!

              – Kristopher Ives
              Jan 29 at 8:09














            0












            0








            0







            'Grub Customizer' worked easily for me. I'm running ver. 5.1.1 on Ubuntu 18.04.
            http://ubuntuhandbook.org/index.php/2016/04/install-grub-customizer-ubuntu-16-04-lts/



            After using Boot repair I had multiple Win10 listings in boot two booted correctly into windows two did not. Grub Customizer easily fixed that. You can revert back also.



            https://sourceforge.net/p/boot-repair/home/Home/






            share|improve this answer













            'Grub Customizer' worked easily for me. I'm running ver. 5.1.1 on Ubuntu 18.04.
            http://ubuntuhandbook.org/index.php/2016/04/install-grub-customizer-ubuntu-16-04-lts/



            After using Boot repair I had multiple Win10 listings in boot two booted correctly into windows two did not. Grub Customizer easily fixed that. You can revert back also.



            https://sourceforge.net/p/boot-repair/home/Home/







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 29 at 6:32









            R FernandezR Fernandez

            1




            1








            • 1





              Welcome to Ask Ubuntu! If possible you should explain in your answer the steps needed instead of linking to remote sources, since they are likely to change or go offline in the future. Thanks!

              – Kristopher Ives
              Jan 29 at 8:09














            • 1





              Welcome to Ask Ubuntu! If possible you should explain in your answer the steps needed instead of linking to remote sources, since they are likely to change or go offline in the future. Thanks!

              – Kristopher Ives
              Jan 29 at 8:09








            1




            1





            Welcome to Ask Ubuntu! If possible you should explain in your answer the steps needed instead of linking to remote sources, since they are likely to change or go offline in the future. Thanks!

            – Kristopher Ives
            Jan 29 at 8:09





            Welcome to Ask Ubuntu! If possible you should explain in your answer the steps needed instead of linking to remote sources, since they are likely to change or go offline in the future. Thanks!

            – Kristopher Ives
            Jan 29 at 8:09


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112243%2fcannot-permanently-remove-boot-entry-using-efibootmgr%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to send String Array data to Server using php in android

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

            Is anime1.com a legal site for watching anime?