Windows 10 update disrupting Ubuntu dual boot once again












0















I am typing this on my phone now as my laptop has been put out of use by what had just occurred.



After a recent windows 10 update, I was once again faced with problems relating to my Ubuntu dual boot. This time however the situation seems different as my laptop did not boot directly into Windows, rather booted into a very stripped down version of grub 2, and upon exiting I was greeted with a system menu showing 2 'windows' options and an 'unknown device'. Windows was the only option that worked so I used Windows for the past few days. Recently windows has become very slow and sluggish hence I was trying to get my Ubuntu back.



As this is a problem I had not faced before, I tried to use a boot-repair USB drive this time, however I ran into many errors with this software. First it tells me:



$GPT detected. Please create a BIOS-Boot partition...$



Which I attempted by setting my UEFI partition to unformatted, however not only did that not work it seemed have resulted in my being unable to access even the stripped down grub menu to boot into Windows, instead displaying the error 'no boot able device'.



Next I tried to alter the settings of boot repair by changing in the settings, under >GRUB location, and ticking 'Separare /boot/efi partition:' as suggested by the error message. This still didn't seem to work and I was given the following pastebin:



http://paste.ubuntu.com/p/hTz4vjdpSD



At this point I'm quite afraid of doing much else now for fears of making my predicament even worse. That is why I have turned to the experts at SU wondering if anyone here could shed some insight into the issue at hand here.



Here is a boot repair summary generated by the app:



http://paste.ubuntu.com/p/PdNBXrX4mF/



Thank you very much!










share|improve this question

























  • Messing with the EFI partition has that obvious result. You need to learn how to work with UEFI if you want to dual-boot. Once you do that you will also understand that Windows feature updates do not disrupt the dual-boot; worse case scenario it change the boot order back to Windows - convenient because it takes several reboots to install those updates - but it can be easily changed back to "Ubuntu" (Grub) once done, at UEFI settings.

    – GabrielaGarcia
    Jan 18 at 21:59











  • @GabrielaGarcia haha I figured that was probably the cause of the problem. For my current situation, what would you recommend me doing?

    – CowNorris
    Jan 18 at 22:11











  • Booting Windows installation media in the recovery environment may be able to recover the Windows boot EFI files (and the partition itself). Then Boot-Repair may do the same for Ubuntu.

    – GabrielaGarcia
    Jan 18 at 22:18
















0















I am typing this on my phone now as my laptop has been put out of use by what had just occurred.



After a recent windows 10 update, I was once again faced with problems relating to my Ubuntu dual boot. This time however the situation seems different as my laptop did not boot directly into Windows, rather booted into a very stripped down version of grub 2, and upon exiting I was greeted with a system menu showing 2 'windows' options and an 'unknown device'. Windows was the only option that worked so I used Windows for the past few days. Recently windows has become very slow and sluggish hence I was trying to get my Ubuntu back.



As this is a problem I had not faced before, I tried to use a boot-repair USB drive this time, however I ran into many errors with this software. First it tells me:



$GPT detected. Please create a BIOS-Boot partition...$



Which I attempted by setting my UEFI partition to unformatted, however not only did that not work it seemed have resulted in my being unable to access even the stripped down grub menu to boot into Windows, instead displaying the error 'no boot able device'.



Next I tried to alter the settings of boot repair by changing in the settings, under >GRUB location, and ticking 'Separare /boot/efi partition:' as suggested by the error message. This still didn't seem to work and I was given the following pastebin:



http://paste.ubuntu.com/p/hTz4vjdpSD



At this point I'm quite afraid of doing much else now for fears of making my predicament even worse. That is why I have turned to the experts at SU wondering if anyone here could shed some insight into the issue at hand here.



Here is a boot repair summary generated by the app:



http://paste.ubuntu.com/p/PdNBXrX4mF/



Thank you very much!










share|improve this question

























  • Messing with the EFI partition has that obvious result. You need to learn how to work with UEFI if you want to dual-boot. Once you do that you will also understand that Windows feature updates do not disrupt the dual-boot; worse case scenario it change the boot order back to Windows - convenient because it takes several reboots to install those updates - but it can be easily changed back to "Ubuntu" (Grub) once done, at UEFI settings.

    – GabrielaGarcia
    Jan 18 at 21:59











  • @GabrielaGarcia haha I figured that was probably the cause of the problem. For my current situation, what would you recommend me doing?

    – CowNorris
    Jan 18 at 22:11











  • Booting Windows installation media in the recovery environment may be able to recover the Windows boot EFI files (and the partition itself). Then Boot-Repair may do the same for Ubuntu.

    – GabrielaGarcia
    Jan 18 at 22:18














0












0








0








I am typing this on my phone now as my laptop has been put out of use by what had just occurred.



After a recent windows 10 update, I was once again faced with problems relating to my Ubuntu dual boot. This time however the situation seems different as my laptop did not boot directly into Windows, rather booted into a very stripped down version of grub 2, and upon exiting I was greeted with a system menu showing 2 'windows' options and an 'unknown device'. Windows was the only option that worked so I used Windows for the past few days. Recently windows has become very slow and sluggish hence I was trying to get my Ubuntu back.



As this is a problem I had not faced before, I tried to use a boot-repair USB drive this time, however I ran into many errors with this software. First it tells me:



$GPT detected. Please create a BIOS-Boot partition...$



Which I attempted by setting my UEFI partition to unformatted, however not only did that not work it seemed have resulted in my being unable to access even the stripped down grub menu to boot into Windows, instead displaying the error 'no boot able device'.



Next I tried to alter the settings of boot repair by changing in the settings, under >GRUB location, and ticking 'Separare /boot/efi partition:' as suggested by the error message. This still didn't seem to work and I was given the following pastebin:



http://paste.ubuntu.com/p/hTz4vjdpSD



At this point I'm quite afraid of doing much else now for fears of making my predicament even worse. That is why I have turned to the experts at SU wondering if anyone here could shed some insight into the issue at hand here.



Here is a boot repair summary generated by the app:



http://paste.ubuntu.com/p/PdNBXrX4mF/



Thank you very much!










share|improve this question
















I am typing this on my phone now as my laptop has been put out of use by what had just occurred.



After a recent windows 10 update, I was once again faced with problems relating to my Ubuntu dual boot. This time however the situation seems different as my laptop did not boot directly into Windows, rather booted into a very stripped down version of grub 2, and upon exiting I was greeted with a system menu showing 2 'windows' options and an 'unknown device'. Windows was the only option that worked so I used Windows for the past few days. Recently windows has become very slow and sluggish hence I was trying to get my Ubuntu back.



As this is a problem I had not faced before, I tried to use a boot-repair USB drive this time, however I ran into many errors with this software. First it tells me:



$GPT detected. Please create a BIOS-Boot partition...$



Which I attempted by setting my UEFI partition to unformatted, however not only did that not work it seemed have resulted in my being unable to access even the stripped down grub menu to boot into Windows, instead displaying the error 'no boot able device'.



Next I tried to alter the settings of boot repair by changing in the settings, under >GRUB location, and ticking 'Separare /boot/efi partition:' as suggested by the error message. This still didn't seem to work and I was given the following pastebin:



http://paste.ubuntu.com/p/hTz4vjdpSD



At this point I'm quite afraid of doing much else now for fears of making my predicament even worse. That is why I have turned to the experts at SU wondering if anyone here could shed some insight into the issue at hand here.



Here is a boot repair summary generated by the app:



http://paste.ubuntu.com/p/PdNBXrX4mF/



Thank you very much!







windows-10 boot multi-boot uefi






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 18 at 20:33







CowNorris

















asked Jan 18 at 19:57









CowNorrisCowNorris

43




43













  • Messing with the EFI partition has that obvious result. You need to learn how to work with UEFI if you want to dual-boot. Once you do that you will also understand that Windows feature updates do not disrupt the dual-boot; worse case scenario it change the boot order back to Windows - convenient because it takes several reboots to install those updates - but it can be easily changed back to "Ubuntu" (Grub) once done, at UEFI settings.

    – GabrielaGarcia
    Jan 18 at 21:59











  • @GabrielaGarcia haha I figured that was probably the cause of the problem. For my current situation, what would you recommend me doing?

    – CowNorris
    Jan 18 at 22:11











  • Booting Windows installation media in the recovery environment may be able to recover the Windows boot EFI files (and the partition itself). Then Boot-Repair may do the same for Ubuntu.

    – GabrielaGarcia
    Jan 18 at 22:18



















  • Messing with the EFI partition has that obvious result. You need to learn how to work with UEFI if you want to dual-boot. Once you do that you will also understand that Windows feature updates do not disrupt the dual-boot; worse case scenario it change the boot order back to Windows - convenient because it takes several reboots to install those updates - but it can be easily changed back to "Ubuntu" (Grub) once done, at UEFI settings.

    – GabrielaGarcia
    Jan 18 at 21:59











  • @GabrielaGarcia haha I figured that was probably the cause of the problem. For my current situation, what would you recommend me doing?

    – CowNorris
    Jan 18 at 22:11











  • Booting Windows installation media in the recovery environment may be able to recover the Windows boot EFI files (and the partition itself). Then Boot-Repair may do the same for Ubuntu.

    – GabrielaGarcia
    Jan 18 at 22:18

















Messing with the EFI partition has that obvious result. You need to learn how to work with UEFI if you want to dual-boot. Once you do that you will also understand that Windows feature updates do not disrupt the dual-boot; worse case scenario it change the boot order back to Windows - convenient because it takes several reboots to install those updates - but it can be easily changed back to "Ubuntu" (Grub) once done, at UEFI settings.

– GabrielaGarcia
Jan 18 at 21:59





Messing with the EFI partition has that obvious result. You need to learn how to work with UEFI if you want to dual-boot. Once you do that you will also understand that Windows feature updates do not disrupt the dual-boot; worse case scenario it change the boot order back to Windows - convenient because it takes several reboots to install those updates - but it can be easily changed back to "Ubuntu" (Grub) once done, at UEFI settings.

– GabrielaGarcia
Jan 18 at 21:59













@GabrielaGarcia haha I figured that was probably the cause of the problem. For my current situation, what would you recommend me doing?

– CowNorris
Jan 18 at 22:11





@GabrielaGarcia haha I figured that was probably the cause of the problem. For my current situation, what would you recommend me doing?

– CowNorris
Jan 18 at 22:11













Booting Windows installation media in the recovery environment may be able to recover the Windows boot EFI files (and the partition itself). Then Boot-Repair may do the same for Ubuntu.

– GabrielaGarcia
Jan 18 at 22:18





Booting Windows installation media in the recovery environment may be able to recover the Windows boot EFI files (and the partition itself). Then Boot-Repair may do the same for Ubuntu.

– GabrielaGarcia
Jan 18 at 22:18










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1395902%2fwindows-10-update-disrupting-ubuntu-dual-boot-once-again%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • 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%2fsuperuser.com%2fquestions%2f1395902%2fwindows-10-update-disrupting-ubuntu-dual-boot-once-again%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

Plaza Victoria

Puebla de Zaragoza

Musa