GRUB problems after Windows 10 update [duplicate]












0















This question already has an answer here:




  • Windows 10 upgrade kills grub and boot-repair doesn't help

    13 answers




After a Windows 10 update, I'm experiencing a problem with GRUB: the system boots directly into Windows and i don't have the chance to select Ubuntu. I tried to use a live USB of Boot-Repair (first the recommended option and then with the "purge the grub" option flagged). I also tried to use these commands in an administrator command prompt (Windows):



bcdedit /set {bootmgr} path efiubuntushimx64.efi
bcdedit /set {bootmgr} path efiubuntugrubx64.efi


Here is the Boot-info summary



Any tips?










share|improve this question















marked as duplicate by Eric Carvalho, Thomas, Zanna, Kulfy, WinEunuuchs2Unix Dec 30 '18 at 13:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.




















    0















    This question already has an answer here:




    • Windows 10 upgrade kills grub and boot-repair doesn't help

      13 answers




    After a Windows 10 update, I'm experiencing a problem with GRUB: the system boots directly into Windows and i don't have the chance to select Ubuntu. I tried to use a live USB of Boot-Repair (first the recommended option and then with the "purge the grub" option flagged). I also tried to use these commands in an administrator command prompt (Windows):



    bcdedit /set {bootmgr} path efiubuntushimx64.efi
    bcdedit /set {bootmgr} path efiubuntugrubx64.efi


    Here is the Boot-info summary



    Any tips?










    share|improve this question















    marked as duplicate by Eric Carvalho, Thomas, Zanna, Kulfy, WinEunuuchs2Unix Dec 30 '18 at 13:42


    This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.


















      0












      0








      0








      This question already has an answer here:




      • Windows 10 upgrade kills grub and boot-repair doesn't help

        13 answers




      After a Windows 10 update, I'm experiencing a problem with GRUB: the system boots directly into Windows and i don't have the chance to select Ubuntu. I tried to use a live USB of Boot-Repair (first the recommended option and then with the "purge the grub" option flagged). I also tried to use these commands in an administrator command prompt (Windows):



      bcdedit /set {bootmgr} path efiubuntushimx64.efi
      bcdedit /set {bootmgr} path efiubuntugrubx64.efi


      Here is the Boot-info summary



      Any tips?










      share|improve this question
















      This question already has an answer here:




      • Windows 10 upgrade kills grub and boot-repair doesn't help

        13 answers




      After a Windows 10 update, I'm experiencing a problem with GRUB: the system boots directly into Windows and i don't have the chance to select Ubuntu. I tried to use a live USB of Boot-Repair (first the recommended option and then with the "purge the grub" option flagged). I also tried to use these commands in an administrator command prompt (Windows):



      bcdedit /set {bootmgr} path efiubuntushimx64.efi
      bcdedit /set {bootmgr} path efiubuntugrubx64.efi


      Here is the Boot-info summary



      Any tips?





      This question already has an answer here:




      • Windows 10 upgrade kills grub and boot-repair doesn't help

        13 answers








      boot dual-boot grub2 uefi windows-10






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 29 '18 at 19:50









      Zanna

      50.2k13132241




      50.2k13132241










      asked Nov 11 '17 at 13:37









      Axel Naike Zamatei

      111




      111




      marked as duplicate by Eric Carvalho, Thomas, Zanna, Kulfy, WinEunuuchs2Unix Dec 30 '18 at 13:42


      This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






      marked as duplicate by Eric Carvalho, Thomas, Zanna, Kulfy, WinEunuuchs2Unix Dec 30 '18 at 13:42


      This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
























          2 Answers
          2






          active

          oldest

          votes


















          -1














          If your firmware supports Boot file selection then go as per stated by #ravery's answer.
          Open boot settings of your computer then start seeking if there is an option provided somewhere to select boot file.
          If not then you have two options as per my knowledge. Either search for commands from google that will change your OS Boot file-if you not wish to loose your data in /root partition and if you can afford the overhead of reinstalling /root and updating your system again then go through the method described by me below.
          If you have not installed any specific software and if you could afford installing /root partition again then do it best way.
          It will simply install grub again. None of the the other partition will be affected and none of the data other than /root will be affected.Boot through live medium & Open G-parted. Choose /root partition then select (-) from the bottom. Select un-allocated space & press (+). Then again make /root partition . Look for column named FORMAT in the top if it is not checked in front of /root, then make it checked otherwise it's OK. DEVICE FOR Boot loader installation select whole disk /dva/sda it will automatically overwrite the Windows boot file.
          Only those partition that are checked in the format partition are going to be formatted. Feel free to select INSTALL NOW option. None of the data other than the /root partition will be lost.



          Then select done.






          share|improve this answer





















          • EFI does not use the MBR. installing to /dev/sda is for Legacy boot only
            – ravery
            Nov 12 '17 at 12:26



















          -1














          I see that /efi/boot/bootx64.efi is present. Some EFI systems will ignore OS boot options if the device boot path is present.



          If the systems firmware allows OS boot selection, rename /efi/boot to test booting via OS.



          If the firmware only allows Device boot selection, then /efi/boot/bootx64.efi needs to be replaced with /efi/ubuntu/shimx64.efi. Relocate the original file in case you want to restore it later. Then copy shimx64.efi to the /efi/boot/ directory and rename it bootx64.efi.






          share|improve this answer






























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            -1














            If your firmware supports Boot file selection then go as per stated by #ravery's answer.
            Open boot settings of your computer then start seeking if there is an option provided somewhere to select boot file.
            If not then you have two options as per my knowledge. Either search for commands from google that will change your OS Boot file-if you not wish to loose your data in /root partition and if you can afford the overhead of reinstalling /root and updating your system again then go through the method described by me below.
            If you have not installed any specific software and if you could afford installing /root partition again then do it best way.
            It will simply install grub again. None of the the other partition will be affected and none of the data other than /root will be affected.Boot through live medium & Open G-parted. Choose /root partition then select (-) from the bottom. Select un-allocated space & press (+). Then again make /root partition . Look for column named FORMAT in the top if it is not checked in front of /root, then make it checked otherwise it's OK. DEVICE FOR Boot loader installation select whole disk /dva/sda it will automatically overwrite the Windows boot file.
            Only those partition that are checked in the format partition are going to be formatted. Feel free to select INSTALL NOW option. None of the data other than the /root partition will be lost.



            Then select done.






            share|improve this answer





















            • EFI does not use the MBR. installing to /dev/sda is for Legacy boot only
              – ravery
              Nov 12 '17 at 12:26
















            -1














            If your firmware supports Boot file selection then go as per stated by #ravery's answer.
            Open boot settings of your computer then start seeking if there is an option provided somewhere to select boot file.
            If not then you have two options as per my knowledge. Either search for commands from google that will change your OS Boot file-if you not wish to loose your data in /root partition and if you can afford the overhead of reinstalling /root and updating your system again then go through the method described by me below.
            If you have not installed any specific software and if you could afford installing /root partition again then do it best way.
            It will simply install grub again. None of the the other partition will be affected and none of the data other than /root will be affected.Boot through live medium & Open G-parted. Choose /root partition then select (-) from the bottom. Select un-allocated space & press (+). Then again make /root partition . Look for column named FORMAT in the top if it is not checked in front of /root, then make it checked otherwise it's OK. DEVICE FOR Boot loader installation select whole disk /dva/sda it will automatically overwrite the Windows boot file.
            Only those partition that are checked in the format partition are going to be formatted. Feel free to select INSTALL NOW option. None of the data other than the /root partition will be lost.



            Then select done.






            share|improve this answer





















            • EFI does not use the MBR. installing to /dev/sda is for Legacy boot only
              – ravery
              Nov 12 '17 at 12:26














            -1












            -1








            -1






            If your firmware supports Boot file selection then go as per stated by #ravery's answer.
            Open boot settings of your computer then start seeking if there is an option provided somewhere to select boot file.
            If not then you have two options as per my knowledge. Either search for commands from google that will change your OS Boot file-if you not wish to loose your data in /root partition and if you can afford the overhead of reinstalling /root and updating your system again then go through the method described by me below.
            If you have not installed any specific software and if you could afford installing /root partition again then do it best way.
            It will simply install grub again. None of the the other partition will be affected and none of the data other than /root will be affected.Boot through live medium & Open G-parted. Choose /root partition then select (-) from the bottom. Select un-allocated space & press (+). Then again make /root partition . Look for column named FORMAT in the top if it is not checked in front of /root, then make it checked otherwise it's OK. DEVICE FOR Boot loader installation select whole disk /dva/sda it will automatically overwrite the Windows boot file.
            Only those partition that are checked in the format partition are going to be formatted. Feel free to select INSTALL NOW option. None of the data other than the /root partition will be lost.



            Then select done.






            share|improve this answer












            If your firmware supports Boot file selection then go as per stated by #ravery's answer.
            Open boot settings of your computer then start seeking if there is an option provided somewhere to select boot file.
            If not then you have two options as per my knowledge. Either search for commands from google that will change your OS Boot file-if you not wish to loose your data in /root partition and if you can afford the overhead of reinstalling /root and updating your system again then go through the method described by me below.
            If you have not installed any specific software and if you could afford installing /root partition again then do it best way.
            It will simply install grub again. None of the the other partition will be affected and none of the data other than /root will be affected.Boot through live medium & Open G-parted. Choose /root partition then select (-) from the bottom. Select un-allocated space & press (+). Then again make /root partition . Look for column named FORMAT in the top if it is not checked in front of /root, then make it checked otherwise it's OK. DEVICE FOR Boot loader installation select whole disk /dva/sda it will automatically overwrite the Windows boot file.
            Only those partition that are checked in the format partition are going to be formatted. Feel free to select INSTALL NOW option. None of the data other than the /root partition will be lost.



            Then select done.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 12 '17 at 6:23









            diwakar

            11




            11












            • EFI does not use the MBR. installing to /dev/sda is for Legacy boot only
              – ravery
              Nov 12 '17 at 12:26


















            • EFI does not use the MBR. installing to /dev/sda is for Legacy boot only
              – ravery
              Nov 12 '17 at 12:26
















            EFI does not use the MBR. installing to /dev/sda is for Legacy boot only
            – ravery
            Nov 12 '17 at 12:26




            EFI does not use the MBR. installing to /dev/sda is for Legacy boot only
            – ravery
            Nov 12 '17 at 12:26













            -1














            I see that /efi/boot/bootx64.efi is present. Some EFI systems will ignore OS boot options if the device boot path is present.



            If the systems firmware allows OS boot selection, rename /efi/boot to test booting via OS.



            If the firmware only allows Device boot selection, then /efi/boot/bootx64.efi needs to be replaced with /efi/ubuntu/shimx64.efi. Relocate the original file in case you want to restore it later. Then copy shimx64.efi to the /efi/boot/ directory and rename it bootx64.efi.






            share|improve this answer




























              -1














              I see that /efi/boot/bootx64.efi is present. Some EFI systems will ignore OS boot options if the device boot path is present.



              If the systems firmware allows OS boot selection, rename /efi/boot to test booting via OS.



              If the firmware only allows Device boot selection, then /efi/boot/bootx64.efi needs to be replaced with /efi/ubuntu/shimx64.efi. Relocate the original file in case you want to restore it later. Then copy shimx64.efi to the /efi/boot/ directory and rename it bootx64.efi.






              share|improve this answer


























                -1












                -1








                -1






                I see that /efi/boot/bootx64.efi is present. Some EFI systems will ignore OS boot options if the device boot path is present.



                If the systems firmware allows OS boot selection, rename /efi/boot to test booting via OS.



                If the firmware only allows Device boot selection, then /efi/boot/bootx64.efi needs to be replaced with /efi/ubuntu/shimx64.efi. Relocate the original file in case you want to restore it later. Then copy shimx64.efi to the /efi/boot/ directory and rename it bootx64.efi.






                share|improve this answer














                I see that /efi/boot/bootx64.efi is present. Some EFI systems will ignore OS boot options if the device boot path is present.



                If the systems firmware allows OS boot selection, rename /efi/boot to test booting via OS.



                If the firmware only allows Device boot selection, then /efi/boot/bootx64.efi needs to be replaced with /efi/ubuntu/shimx64.efi. Relocate the original file in case you want to restore it later. Then copy shimx64.efi to the /efi/boot/ directory and rename it bootx64.efi.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 12 '17 at 11:04









                vidarlo

                9,29442445




                9,29442445










                answered Nov 11 '17 at 14:12









                ravery

                5,43351132




                5,43351132















                    Popular posts from this blog

                    Human spaceflight

                    Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

                    File:DeusFollowingSea.jpg