Ubuntu/Windows Boot Manager Issue





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















Okay....Ubuntu 18.4/Windows 10 (latest)



Today I decided to use my extra HDD to run Ubuntu. I have a 1TB 970 EVO NVMe for Windows 10 and a spare 1TB HDD.



I format the spare 1TB HDD



I used an already setup thumb drive using rufus to load up Ubuntu.



I choose the install along side Windows, but I choose the HDD and in no way partitioned space on my NVMe for Ubuntu.



Everything loads up fine, updates, restarts, etc.



Then I got to get back into Windows and on the grub menu it shows that I have TWO Windows Boot Manager options. One on my NVMe drive and the other on the HDD, and selecting either Windows Boot option throws me in a recovery/diagnostic mode where it tells me it can do neither.



In order to get back into Windows I have to change the boot order in BIOS of the NVMe Windows over Ubuntu or Override boot up, but then I don't get to choose Ubuntu.



Why can I override boot my Windows Boot Manager on the NVMe in BIOS and Windows 10 loads fine, but the same done in grub throws and Windows 10 throws a fit. Do I need the Windows Boot Manager on the HDD? How do I get rid of the Boot Manager on the HDD and put the Ubuntu one there instead?










share|improve this question























  • Try installing rEFInd on whatever OS and see if it can detect all your bootloaders. Make sure your HDD is plugged in while you install it.

    – avisitoritseems
    Feb 20 at 5:20











  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30


















0















Okay....Ubuntu 18.4/Windows 10 (latest)



Today I decided to use my extra HDD to run Ubuntu. I have a 1TB 970 EVO NVMe for Windows 10 and a spare 1TB HDD.



I format the spare 1TB HDD



I used an already setup thumb drive using rufus to load up Ubuntu.



I choose the install along side Windows, but I choose the HDD and in no way partitioned space on my NVMe for Ubuntu.



Everything loads up fine, updates, restarts, etc.



Then I got to get back into Windows and on the grub menu it shows that I have TWO Windows Boot Manager options. One on my NVMe drive and the other on the HDD, and selecting either Windows Boot option throws me in a recovery/diagnostic mode where it tells me it can do neither.



In order to get back into Windows I have to change the boot order in BIOS of the NVMe Windows over Ubuntu or Override boot up, but then I don't get to choose Ubuntu.



Why can I override boot my Windows Boot Manager on the NVMe in BIOS and Windows 10 loads fine, but the same done in grub throws and Windows 10 throws a fit. Do I need the Windows Boot Manager on the HDD? How do I get rid of the Boot Manager on the HDD and put the Ubuntu one there instead?










share|improve this question























  • Try installing rEFInd on whatever OS and see if it can detect all your bootloaders. Make sure your HDD is plugged in while you install it.

    – avisitoritseems
    Feb 20 at 5:20











  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30














0












0








0








Okay....Ubuntu 18.4/Windows 10 (latest)



Today I decided to use my extra HDD to run Ubuntu. I have a 1TB 970 EVO NVMe for Windows 10 and a spare 1TB HDD.



I format the spare 1TB HDD



I used an already setup thumb drive using rufus to load up Ubuntu.



I choose the install along side Windows, but I choose the HDD and in no way partitioned space on my NVMe for Ubuntu.



Everything loads up fine, updates, restarts, etc.



Then I got to get back into Windows and on the grub menu it shows that I have TWO Windows Boot Manager options. One on my NVMe drive and the other on the HDD, and selecting either Windows Boot option throws me in a recovery/diagnostic mode where it tells me it can do neither.



In order to get back into Windows I have to change the boot order in BIOS of the NVMe Windows over Ubuntu or Override boot up, but then I don't get to choose Ubuntu.



Why can I override boot my Windows Boot Manager on the NVMe in BIOS and Windows 10 loads fine, but the same done in grub throws and Windows 10 throws a fit. Do I need the Windows Boot Manager on the HDD? How do I get rid of the Boot Manager on the HDD and put the Ubuntu one there instead?










share|improve this question














Okay....Ubuntu 18.4/Windows 10 (latest)



Today I decided to use my extra HDD to run Ubuntu. I have a 1TB 970 EVO NVMe for Windows 10 and a spare 1TB HDD.



I format the spare 1TB HDD



I used an already setup thumb drive using rufus to load up Ubuntu.



I choose the install along side Windows, but I choose the HDD and in no way partitioned space on my NVMe for Ubuntu.



Everything loads up fine, updates, restarts, etc.



Then I got to get back into Windows and on the grub menu it shows that I have TWO Windows Boot Manager options. One on my NVMe drive and the other on the HDD, and selecting either Windows Boot option throws me in a recovery/diagnostic mode where it tells me it can do neither.



In order to get back into Windows I have to change the boot order in BIOS of the NVMe Windows over Ubuntu or Override boot up, but then I don't get to choose Ubuntu.



Why can I override boot my Windows Boot Manager on the NVMe in BIOS and Windows 10 loads fine, but the same done in grub throws and Windows 10 throws a fit. Do I need the Windows Boot Manager on the HDD? How do I get rid of the Boot Manager on the HDD and put the Ubuntu one there instead?







18.04 windows






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 20 at 4:51









joseph.millsjoseph.mills

1




1













  • Try installing rEFInd on whatever OS and see if it can detect all your bootloaders. Make sure your HDD is plugged in while you install it.

    – avisitoritseems
    Feb 20 at 5:20











  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30



















  • Try installing rEFInd on whatever OS and see if it can detect all your bootloaders. Make sure your HDD is plugged in while you install it.

    – avisitoritseems
    Feb 20 at 5:20











  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30

















Try installing rEFInd on whatever OS and see if it can detect all your bootloaders. Make sure your HDD is plugged in while you install it.

– avisitoritseems
Feb 20 at 5:20





Try installing rEFInd on whatever OS and see if it can detect all your bootloaders. Make sure your HDD is plugged in while you install it.

– avisitoritseems
Feb 20 at 5:20













I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

– joseph.mills
Feb 21 at 3:30





I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

– joseph.mills
Feb 21 at 3:30










1 Answer
1






active

oldest

votes


















0














Also maybe try update-grub and then grub install onto the main HDD. The Ubuntu installer might have found the recovery partition only. sudo update-grub and sudo grub-install. Report back if it helped.






share|improve this answer
























  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30











  • I found the boot loaders without rEFInd. I did update-grub. I disabled all but Ubuntu and windows 10 boot on the NVMe. I disabled fast boot and Hyberbootenabled=0 in registry. When trying to launch windows from grub2 it still triggers Windows Automatic Repair. Thoughts?

    – joseph.mills
    Feb 22 at 4:24












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%2f1119717%2fubuntu-windows-boot-manager-issue%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Also maybe try update-grub and then grub install onto the main HDD. The Ubuntu installer might have found the recovery partition only. sudo update-grub and sudo grub-install. Report back if it helped.






share|improve this answer
























  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30











  • I found the boot loaders without rEFInd. I did update-grub. I disabled all but Ubuntu and windows 10 boot on the NVMe. I disabled fast boot and Hyberbootenabled=0 in registry. When trying to launch windows from grub2 it still triggers Windows Automatic Repair. Thoughts?

    – joseph.mills
    Feb 22 at 4:24
















0














Also maybe try update-grub and then grub install onto the main HDD. The Ubuntu installer might have found the recovery partition only. sudo update-grub and sudo grub-install. Report back if it helped.






share|improve this answer
























  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30











  • I found the boot loaders without rEFInd. I did update-grub. I disabled all but Ubuntu and windows 10 boot on the NVMe. I disabled fast boot and Hyberbootenabled=0 in registry. When trying to launch windows from grub2 it still triggers Windows Automatic Repair. Thoughts?

    – joseph.mills
    Feb 22 at 4:24














0












0








0







Also maybe try update-grub and then grub install onto the main HDD. The Ubuntu installer might have found the recovery partition only. sudo update-grub and sudo grub-install. Report back if it helped.






share|improve this answer













Also maybe try update-grub and then grub install onto the main HDD. The Ubuntu installer might have found the recovery partition only. sudo update-grub and sudo grub-install. Report back if it helped.







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 20 at 5:38









Uwe PfeiferUwe Pfeifer

4511




4511













  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30











  • I found the boot loaders without rEFInd. I did update-grub. I disabled all but Ubuntu and windows 10 boot on the NVMe. I disabled fast boot and Hyberbootenabled=0 in registry. When trying to launch windows from grub2 it still triggers Windows Automatic Repair. Thoughts?

    – joseph.mills
    Feb 22 at 4:24



















  • I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

    – joseph.mills
    Feb 21 at 3:30











  • I found the boot loaders without rEFInd. I did update-grub. I disabled all but Ubuntu and windows 10 boot on the NVMe. I disabled fast boot and Hyberbootenabled=0 in registry. When trying to launch windows from grub2 it still triggers Windows Automatic Repair. Thoughts?

    – joseph.mills
    Feb 22 at 4:24

















I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

– joseph.mills
Feb 21 at 3:30





I will be working on it this weekend. I have never used anything like rEFInd before and it isn't exactly a click-and-drag thing.

– joseph.mills
Feb 21 at 3:30













I found the boot loaders without rEFInd. I did update-grub. I disabled all but Ubuntu and windows 10 boot on the NVMe. I disabled fast boot and Hyberbootenabled=0 in registry. When trying to launch windows from grub2 it still triggers Windows Automatic Repair. Thoughts?

– joseph.mills
Feb 22 at 4:24





I found the boot loaders without rEFInd. I did update-grub. I disabled all but Ubuntu and windows 10 boot on the NVMe. I disabled fast boot and Hyberbootenabled=0 in registry. When trying to launch windows from grub2 it still triggers Windows Automatic Repair. Thoughts?

– joseph.mills
Feb 22 at 4:24


















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%2f1119717%2fubuntu-windows-boot-manager-issue%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 change which sound is reproduced for terminal bell?

Can I use Tabulator js library in my java Spring + Thymeleaf project?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents