System always boots to grub prompt18.04 dual boot showing grub2 manualServer 12.04 boots to Grub CLIRecovering GRUB after installing Windows 7 with boot repairXen vm stuck at grub prompt14.04 on Macbook Pro always boots to GRUB promptUbuntu 14.04 doesn't boot grub promptGrub Rescue afterinstall Ubuntu 14.04Clean Install of 18.04 Boots to Grub Prompt18.04 dual boot showing grub2 manualBoot stops at grub prompt, can't find ubuntu partitionFresh install of Ubuntu 18.04 boots straight to Grub menu

The Digit Triangles

Why does the Sun have different day lengths, but not the gas giants?

What is the English pronunciation of "pain au chocolat"?

What's the name of the logical fallacy where a debater extends a statement far beyond the original statement to make it true?

A variation to the phrase "hanging over my shoulders"

When were female captains banned from Starfleet?

Is this part of the description of the Archfey warlock's Misty Escape feature redundant?

What to do when eye contact makes your coworker uncomfortable?

PTIJ: Why is Haman obsessed with Bose?

What is the highest possible scrabble score for placing a single tile

How to get directions in deep space?

Quoting Keynes in a lecture

Which was the first story featuring espers?

Doesn't the system of the Supreme Court oppose justice?

Giving feedback to someone without sounding prejudiced

Why does AES have exactly 10 rounds for a 128-bit key, 12 for 192 bits and 14 for a 256-bit key size?

Mimic lecturing on blackboard, facing audience

How do you make your own symbol when Detexify fails?

Biological Blimps: Propulsion

How to draw a matrix with arrows in limited space

awk assign to multiple variables at once

Is there a nicer/politer/more positive alternative for "negates"?

I found an audio circuit and I built it just fine, but I find it a bit too quiet. How do I amplify the output so that it is a bit louder?

Why does this expression simplify as such?



System always boots to grub prompt


18.04 dual boot showing grub2 manualServer 12.04 boots to Grub CLIRecovering GRUB after installing Windows 7 with boot repairXen vm stuck at grub prompt14.04 on Macbook Pro always boots to GRUB promptUbuntu 14.04 doesn't boot grub promptGrub Rescue afterinstall Ubuntu 14.04Clean Install of 18.04 Boots to Grub Prompt18.04 dual boot showing grub2 manualBoot stops at grub prompt, can't find ubuntu partitionFresh install of Ubuntu 18.04 boots straight to Grub menu













3















After installing a fresh copy of Ubuntu 18.04 Desktop, I am shown the grub prompt at boot.



I've tried:



  • boot-repair tool within liveUSB: https://paste.ubuntu.com/p/6Q3ndws93b/

  • Re-install grub from liveUSB: https://paste.ubuntu.com/p/GrCKTgbjRm/

  • manually booting ( https://paste.ubuntu.com/p/j89ZK9Jgdx/ ) and using boot-repair ( https://paste.ubuntu.com/p/knYGTtwkWz/ )

But I am still shown the grub prompt at each boot.



How can I fix grub so that it automatically starts the installed system?










share|improve this question






















  • I fixed it by setting BIOS parameter "UEFI/Legacy Boot" to "UEFI Only" and "CSM Support" to Yes.

    – Jos
    Jul 10 '18 at 14:36











  • @Jos Doesn't seem to work for me

    – DanielB
    Jul 10 '18 at 14:42






  • 1





    What brand/model system. Some require work arounds. But you are showing grub entry, not typical Ubuntu entry. If not from another install like Debian, grub is not correct. I installed 18.10 and got a similar grub entry, but it used my default /EFI/ubuntu/grub.cfg file, not the /EFI/grub/grub.cfg file for 18.10. You do not have /EFI/ubuntu folder in ESP? If not copy all of /EFI/grub to /EFI/ubuntu. You may only need grub.cfg for it to work. Please post this bug, if grub UEFI entry is from Ubuntu, not another install: bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743

    – oldfred
    Jul 10 '18 at 15:02












  • @oldfred - custom build, had no /EFI/ubuntu/grub.cfg ( paste.ubuntu.com/p/82bFbST6xw ). That ticket mentioned grub-efi-amd64 was missing and sure enough installing it fixes my issue! Thanks.

    – DanielB
    Jul 10 '18 at 15:20















3















After installing a fresh copy of Ubuntu 18.04 Desktop, I am shown the grub prompt at boot.



I've tried:



  • boot-repair tool within liveUSB: https://paste.ubuntu.com/p/6Q3ndws93b/

  • Re-install grub from liveUSB: https://paste.ubuntu.com/p/GrCKTgbjRm/

  • manually booting ( https://paste.ubuntu.com/p/j89ZK9Jgdx/ ) and using boot-repair ( https://paste.ubuntu.com/p/knYGTtwkWz/ )

But I am still shown the grub prompt at each boot.



How can I fix grub so that it automatically starts the installed system?










share|improve this question






















  • I fixed it by setting BIOS parameter "UEFI/Legacy Boot" to "UEFI Only" and "CSM Support" to Yes.

    – Jos
    Jul 10 '18 at 14:36











  • @Jos Doesn't seem to work for me

    – DanielB
    Jul 10 '18 at 14:42






  • 1





    What brand/model system. Some require work arounds. But you are showing grub entry, not typical Ubuntu entry. If not from another install like Debian, grub is not correct. I installed 18.10 and got a similar grub entry, but it used my default /EFI/ubuntu/grub.cfg file, not the /EFI/grub/grub.cfg file for 18.10. You do not have /EFI/ubuntu folder in ESP? If not copy all of /EFI/grub to /EFI/ubuntu. You may only need grub.cfg for it to work. Please post this bug, if grub UEFI entry is from Ubuntu, not another install: bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743

    – oldfred
    Jul 10 '18 at 15:02












  • @oldfred - custom build, had no /EFI/ubuntu/grub.cfg ( paste.ubuntu.com/p/82bFbST6xw ). That ticket mentioned grub-efi-amd64 was missing and sure enough installing it fixes my issue! Thanks.

    – DanielB
    Jul 10 '18 at 15:20













3












3








3


2






After installing a fresh copy of Ubuntu 18.04 Desktop, I am shown the grub prompt at boot.



I've tried:



  • boot-repair tool within liveUSB: https://paste.ubuntu.com/p/6Q3ndws93b/

  • Re-install grub from liveUSB: https://paste.ubuntu.com/p/GrCKTgbjRm/

  • manually booting ( https://paste.ubuntu.com/p/j89ZK9Jgdx/ ) and using boot-repair ( https://paste.ubuntu.com/p/knYGTtwkWz/ )

But I am still shown the grub prompt at each boot.



How can I fix grub so that it automatically starts the installed system?










share|improve this question














After installing a fresh copy of Ubuntu 18.04 Desktop, I am shown the grub prompt at boot.



I've tried:



  • boot-repair tool within liveUSB: https://paste.ubuntu.com/p/6Q3ndws93b/

  • Re-install grub from liveUSB: https://paste.ubuntu.com/p/GrCKTgbjRm/

  • manually booting ( https://paste.ubuntu.com/p/j89ZK9Jgdx/ ) and using boot-repair ( https://paste.ubuntu.com/p/knYGTtwkWz/ )

But I am still shown the grub prompt at each boot.



How can I fix grub so that it automatically starts the installed system?







boot grub2 uefi 18.04






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jul 10 '18 at 14:27









DanielBDanielB

1265




1265












  • I fixed it by setting BIOS parameter "UEFI/Legacy Boot" to "UEFI Only" and "CSM Support" to Yes.

    – Jos
    Jul 10 '18 at 14:36











  • @Jos Doesn't seem to work for me

    – DanielB
    Jul 10 '18 at 14:42






  • 1





    What brand/model system. Some require work arounds. But you are showing grub entry, not typical Ubuntu entry. If not from another install like Debian, grub is not correct. I installed 18.10 and got a similar grub entry, but it used my default /EFI/ubuntu/grub.cfg file, not the /EFI/grub/grub.cfg file for 18.10. You do not have /EFI/ubuntu folder in ESP? If not copy all of /EFI/grub to /EFI/ubuntu. You may only need grub.cfg for it to work. Please post this bug, if grub UEFI entry is from Ubuntu, not another install: bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743

    – oldfred
    Jul 10 '18 at 15:02












  • @oldfred - custom build, had no /EFI/ubuntu/grub.cfg ( paste.ubuntu.com/p/82bFbST6xw ). That ticket mentioned grub-efi-amd64 was missing and sure enough installing it fixes my issue! Thanks.

    – DanielB
    Jul 10 '18 at 15:20

















  • I fixed it by setting BIOS parameter "UEFI/Legacy Boot" to "UEFI Only" and "CSM Support" to Yes.

    – Jos
    Jul 10 '18 at 14:36











  • @Jos Doesn't seem to work for me

    – DanielB
    Jul 10 '18 at 14:42






  • 1





    What brand/model system. Some require work arounds. But you are showing grub entry, not typical Ubuntu entry. If not from another install like Debian, grub is not correct. I installed 18.10 and got a similar grub entry, but it used my default /EFI/ubuntu/grub.cfg file, not the /EFI/grub/grub.cfg file for 18.10. You do not have /EFI/ubuntu folder in ESP? If not copy all of /EFI/grub to /EFI/ubuntu. You may only need grub.cfg for it to work. Please post this bug, if grub UEFI entry is from Ubuntu, not another install: bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743

    – oldfred
    Jul 10 '18 at 15:02












  • @oldfred - custom build, had no /EFI/ubuntu/grub.cfg ( paste.ubuntu.com/p/82bFbST6xw ). That ticket mentioned grub-efi-amd64 was missing and sure enough installing it fixes my issue! Thanks.

    – DanielB
    Jul 10 '18 at 15:20
















I fixed it by setting BIOS parameter "UEFI/Legacy Boot" to "UEFI Only" and "CSM Support" to Yes.

– Jos
Jul 10 '18 at 14:36





I fixed it by setting BIOS parameter "UEFI/Legacy Boot" to "UEFI Only" and "CSM Support" to Yes.

– Jos
Jul 10 '18 at 14:36













@Jos Doesn't seem to work for me

– DanielB
Jul 10 '18 at 14:42





@Jos Doesn't seem to work for me

– DanielB
Jul 10 '18 at 14:42




1




1





What brand/model system. Some require work arounds. But you are showing grub entry, not typical Ubuntu entry. If not from another install like Debian, grub is not correct. I installed 18.10 and got a similar grub entry, but it used my default /EFI/ubuntu/grub.cfg file, not the /EFI/grub/grub.cfg file for 18.10. You do not have /EFI/ubuntu folder in ESP? If not copy all of /EFI/grub to /EFI/ubuntu. You may only need grub.cfg for it to work. Please post this bug, if grub UEFI entry is from Ubuntu, not another install: bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743

– oldfred
Jul 10 '18 at 15:02






What brand/model system. Some require work arounds. But you are showing grub entry, not typical Ubuntu entry. If not from another install like Debian, grub is not correct. I installed 18.10 and got a similar grub entry, but it used my default /EFI/ubuntu/grub.cfg file, not the /EFI/grub/grub.cfg file for 18.10. You do not have /EFI/ubuntu folder in ESP? If not copy all of /EFI/grub to /EFI/ubuntu. You may only need grub.cfg for it to work. Please post this bug, if grub UEFI entry is from Ubuntu, not another install: bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743

– oldfred
Jul 10 '18 at 15:02














@oldfred - custom build, had no /EFI/ubuntu/grub.cfg ( paste.ubuntu.com/p/82bFbST6xw ). That ticket mentioned grub-efi-amd64 was missing and sure enough installing it fixes my issue! Thanks.

– DanielB
Jul 10 '18 at 15:20





@oldfred - custom build, had no /EFI/ubuntu/grub.cfg ( paste.ubuntu.com/p/82bFbST6xw ). That ticket mentioned grub-efi-amd64 was missing and sure enough installing it fixes my issue! Thanks.

– DanielB
Jul 10 '18 at 15:20










4 Answers
4






active

oldest

votes


















1














I needed to install grub-efi-amd64, system then booted as expected.



See https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743#yui_3_10_3_1_1531236190615_547 and comment #21 by Jean-Baptiste Lallement (jibel)






share|improve this answer























  • There is now a separate bug for 18.04. bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1781042 Please add to it, to get it prioritized. Seems strange that installer updates install a "bad" version of grub that installs to /EFI/grub, but manually booting and updating grub works as /EFI/ubuntu?

    – oldfred
    Jul 10 '18 at 21:44



















0














Set your boot mode to UEFI, if it doesn't work, try install again with UEFI and be sure to set the partition to GPT rather than MBR to avoid these kind of things!






share|improve this answer























  • Did a fresh install, confirmed GPT ( paste.ubuntu.com/p/7q5qB7PPhd ), still no good

    – DanielB
    Jul 10 '18 at 15:09











  • Did it work after installing grub-efi-amd64 ??

    – Lucifer
    Jul 10 '18 at 16:22


















0














I had same issue. Solved by manual partitioning of hard disk within installer.
I chose partition1 /dev/sda1 type efi size 1023 type boot. Partition 2 type swap size 2xRAM e.g 16384. Partition 3 ext4 / remaining. But i believe wher it all ends in tears is that one needs to select at bottom of screen boot=/dev/sda1 NOT boot=/dev/sda






share|improve this answer






























    0














    I'm having a similar problem: after installing Ubuntu I was left with an empty grub prompt.
    I'm dual booting with Windows 10. Both the ssd on which I have the Windows and the EFI partition, and the harddisk on which I have Ubuntu are partitioned with GPT. Bios is set to boot in UEFI mode, with secure boot and fast boot both turned off.
    I've installed grub-efi-amd64, but it changed nothing.
    After installing Ubuntu, I could boot either operating system only by pressing F12 to access the boot menu, from where I could choose either Windows or Ubuntu, both of which continue booting normally from here, the Ubuntu menu entry leading to a working grub.
    At the end, I've had to edit my EFI entries so that Windows would be the first one, so that at least now Windows loads directly, without any further intervention during the boot process. If I want to enter Ubuntu, I have to go through the bios boot menu.






    share|improve this answer
























      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%2f1053895%2fsystem-always-boots-to-grub-prompt%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      I needed to install grub-efi-amd64, system then booted as expected.



      See https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743#yui_3_10_3_1_1531236190615_547 and comment #21 by Jean-Baptiste Lallement (jibel)






      share|improve this answer























      • There is now a separate bug for 18.04. bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1781042 Please add to it, to get it prioritized. Seems strange that installer updates install a "bad" version of grub that installs to /EFI/grub, but manually booting and updating grub works as /EFI/ubuntu?

        – oldfred
        Jul 10 '18 at 21:44
















      1














      I needed to install grub-efi-amd64, system then booted as expected.



      See https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743#yui_3_10_3_1_1531236190615_547 and comment #21 by Jean-Baptiste Lallement (jibel)






      share|improve this answer























      • There is now a separate bug for 18.04. bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1781042 Please add to it, to get it prioritized. Seems strange that installer updates install a "bad" version of grub that installs to /EFI/grub, but manually booting and updating grub works as /EFI/ubuntu?

        – oldfred
        Jul 10 '18 at 21:44














      1












      1








      1







      I needed to install grub-efi-amd64, system then booted as expected.



      See https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743#yui_3_10_3_1_1531236190615_547 and comment #21 by Jean-Baptiste Lallement (jibel)






      share|improve this answer













      I needed to install grub-efi-amd64, system then booted as expected.



      See https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743#yui_3_10_3_1_1531236190615_547 and comment #21 by Jean-Baptiste Lallement (jibel)







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jul 10 '18 at 15:22









      DanielBDanielB

      1265




      1265












      • There is now a separate bug for 18.04. bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1781042 Please add to it, to get it prioritized. Seems strange that installer updates install a "bad" version of grub that installs to /EFI/grub, but manually booting and updating grub works as /EFI/ubuntu?

        – oldfred
        Jul 10 '18 at 21:44


















      • There is now a separate bug for 18.04. bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1781042 Please add to it, to get it prioritized. Seems strange that installer updates install a "bad" version of grub that installs to /EFI/grub, but manually booting and updating grub works as /EFI/ubuntu?

        – oldfred
        Jul 10 '18 at 21:44

















      There is now a separate bug for 18.04. bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1781042 Please add to it, to get it prioritized. Seems strange that installer updates install a "bad" version of grub that installs to /EFI/grub, but manually booting and updating grub works as /EFI/ubuntu?

      – oldfred
      Jul 10 '18 at 21:44






      There is now a separate bug for 18.04. bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1781042 Please add to it, to get it prioritized. Seems strange that installer updates install a "bad" version of grub that installs to /EFI/grub, but manually booting and updating grub works as /EFI/ubuntu?

      – oldfred
      Jul 10 '18 at 21:44














      0














      Set your boot mode to UEFI, if it doesn't work, try install again with UEFI and be sure to set the partition to GPT rather than MBR to avoid these kind of things!






      share|improve this answer























      • Did a fresh install, confirmed GPT ( paste.ubuntu.com/p/7q5qB7PPhd ), still no good

        – DanielB
        Jul 10 '18 at 15:09











      • Did it work after installing grub-efi-amd64 ??

        – Lucifer
        Jul 10 '18 at 16:22















      0














      Set your boot mode to UEFI, if it doesn't work, try install again with UEFI and be sure to set the partition to GPT rather than MBR to avoid these kind of things!






      share|improve this answer























      • Did a fresh install, confirmed GPT ( paste.ubuntu.com/p/7q5qB7PPhd ), still no good

        – DanielB
        Jul 10 '18 at 15:09











      • Did it work after installing grub-efi-amd64 ??

        – Lucifer
        Jul 10 '18 at 16:22













      0












      0








      0







      Set your boot mode to UEFI, if it doesn't work, try install again with UEFI and be sure to set the partition to GPT rather than MBR to avoid these kind of things!






      share|improve this answer













      Set your boot mode to UEFI, if it doesn't work, try install again with UEFI and be sure to set the partition to GPT rather than MBR to avoid these kind of things!







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jul 10 '18 at 14:44









      LuciferLucifer

      1011




      1011












      • Did a fresh install, confirmed GPT ( paste.ubuntu.com/p/7q5qB7PPhd ), still no good

        – DanielB
        Jul 10 '18 at 15:09











      • Did it work after installing grub-efi-amd64 ??

        – Lucifer
        Jul 10 '18 at 16:22

















      • Did a fresh install, confirmed GPT ( paste.ubuntu.com/p/7q5qB7PPhd ), still no good

        – DanielB
        Jul 10 '18 at 15:09











      • Did it work after installing grub-efi-amd64 ??

        – Lucifer
        Jul 10 '18 at 16:22
















      Did a fresh install, confirmed GPT ( paste.ubuntu.com/p/7q5qB7PPhd ), still no good

      – DanielB
      Jul 10 '18 at 15:09





      Did a fresh install, confirmed GPT ( paste.ubuntu.com/p/7q5qB7PPhd ), still no good

      – DanielB
      Jul 10 '18 at 15:09













      Did it work after installing grub-efi-amd64 ??

      – Lucifer
      Jul 10 '18 at 16:22





      Did it work after installing grub-efi-amd64 ??

      – Lucifer
      Jul 10 '18 at 16:22











      0














      I had same issue. Solved by manual partitioning of hard disk within installer.
      I chose partition1 /dev/sda1 type efi size 1023 type boot. Partition 2 type swap size 2xRAM e.g 16384. Partition 3 ext4 / remaining. But i believe wher it all ends in tears is that one needs to select at bottom of screen boot=/dev/sda1 NOT boot=/dev/sda






      share|improve this answer



























        0














        I had same issue. Solved by manual partitioning of hard disk within installer.
        I chose partition1 /dev/sda1 type efi size 1023 type boot. Partition 2 type swap size 2xRAM e.g 16384. Partition 3 ext4 / remaining. But i believe wher it all ends in tears is that one needs to select at bottom of screen boot=/dev/sda1 NOT boot=/dev/sda






        share|improve this answer

























          0












          0








          0







          I had same issue. Solved by manual partitioning of hard disk within installer.
          I chose partition1 /dev/sda1 type efi size 1023 type boot. Partition 2 type swap size 2xRAM e.g 16384. Partition 3 ext4 / remaining. But i believe wher it all ends in tears is that one needs to select at bottom of screen boot=/dev/sda1 NOT boot=/dev/sda






          share|improve this answer













          I had same issue. Solved by manual partitioning of hard disk within installer.
          I chose partition1 /dev/sda1 type efi size 1023 type boot. Partition 2 type swap size 2xRAM e.g 16384. Partition 3 ext4 / remaining. But i believe wher it all ends in tears is that one needs to select at bottom of screen boot=/dev/sda1 NOT boot=/dev/sda







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 11 '18 at 7:41









          DaveBDaveB

          1




          1





















              0














              I'm having a similar problem: after installing Ubuntu I was left with an empty grub prompt.
              I'm dual booting with Windows 10. Both the ssd on which I have the Windows and the EFI partition, and the harddisk on which I have Ubuntu are partitioned with GPT. Bios is set to boot in UEFI mode, with secure boot and fast boot both turned off.
              I've installed grub-efi-amd64, but it changed nothing.
              After installing Ubuntu, I could boot either operating system only by pressing F12 to access the boot menu, from where I could choose either Windows or Ubuntu, both of which continue booting normally from here, the Ubuntu menu entry leading to a working grub.
              At the end, I've had to edit my EFI entries so that Windows would be the first one, so that at least now Windows loads directly, without any further intervention during the boot process. If I want to enter Ubuntu, I have to go through the bios boot menu.






              share|improve this answer





























                0














                I'm having a similar problem: after installing Ubuntu I was left with an empty grub prompt.
                I'm dual booting with Windows 10. Both the ssd on which I have the Windows and the EFI partition, and the harddisk on which I have Ubuntu are partitioned with GPT. Bios is set to boot in UEFI mode, with secure boot and fast boot both turned off.
                I've installed grub-efi-amd64, but it changed nothing.
                After installing Ubuntu, I could boot either operating system only by pressing F12 to access the boot menu, from where I could choose either Windows or Ubuntu, both of which continue booting normally from here, the Ubuntu menu entry leading to a working grub.
                At the end, I've had to edit my EFI entries so that Windows would be the first one, so that at least now Windows loads directly, without any further intervention during the boot process. If I want to enter Ubuntu, I have to go through the bios boot menu.






                share|improve this answer



























                  0












                  0








                  0







                  I'm having a similar problem: after installing Ubuntu I was left with an empty grub prompt.
                  I'm dual booting with Windows 10. Both the ssd on which I have the Windows and the EFI partition, and the harddisk on which I have Ubuntu are partitioned with GPT. Bios is set to boot in UEFI mode, with secure boot and fast boot both turned off.
                  I've installed grub-efi-amd64, but it changed nothing.
                  After installing Ubuntu, I could boot either operating system only by pressing F12 to access the boot menu, from where I could choose either Windows or Ubuntu, both of which continue booting normally from here, the Ubuntu menu entry leading to a working grub.
                  At the end, I've had to edit my EFI entries so that Windows would be the first one, so that at least now Windows loads directly, without any further intervention during the boot process. If I want to enter Ubuntu, I have to go through the bios boot menu.






                  share|improve this answer















                  I'm having a similar problem: after installing Ubuntu I was left with an empty grub prompt.
                  I'm dual booting with Windows 10. Both the ssd on which I have the Windows and the EFI partition, and the harddisk on which I have Ubuntu are partitioned with GPT. Bios is set to boot in UEFI mode, with secure boot and fast boot both turned off.
                  I've installed grub-efi-amd64, but it changed nothing.
                  After installing Ubuntu, I could boot either operating system only by pressing F12 to access the boot menu, from where I could choose either Windows or Ubuntu, both of which continue booting normally from here, the Ubuntu menu entry leading to a working grub.
                  At the end, I've had to edit my EFI entries so that Windows would be the first one, so that at least now Windows loads directly, without any further intervention during the boot process. If I want to enter Ubuntu, I have to go through the bios boot menu.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 1 hour ago

























                  answered 1 hour ago









                  ciprianlciprianl

                  7113




                  7113



























                      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%2f1053895%2fsystem-always-boots-to-grub-prompt%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

                      Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

                      Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

                      Antonio De Lisio Carrera Referencias Menú de navegación«Caracas: evolución relacional multipleja»«Cuando los gobiernos subestiman a las localidades: L a Iniciativa para la Integración de la Infraestructura Regional Suramericana (IIRSA) en la frontera Colombo-Venezolana»«Maestría en Planificación Integral del Ambiente»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»«Conózcanos»«Caracas: evolución relacional multipleja»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»