grub2 gone every time I boot Windows 10
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I installed Windows 7 on an SSD and upgraded it to Windows 10. Then I installed Linux mint 17.2 Cinnamon and had the following partitions:
The boot menu was showing Linux Mint and Windows 10 and I thought everything was fine. UEFI boot configuration showed "ubuntu". However after booting Windows and then rebooting, grub was gone, and in boot configuration there was only "Windows Boot Manager" available.
When I repaired grub2 with grub-install
and grub-update
I was able boot Linux Mint again, but only as long as I don't boot into Windows 10, which seems to wipe out grub like this every time.
Secureboot and Fastboot are disabled.
/boot/efi contains folders Boot, Microsoft and ubuntu.
Did I do something wrong? How can I get grub2 working permanently?
linux-mint windows grub2 uefi
add a comment |Â
up vote
1
down vote
favorite
I installed Windows 7 on an SSD and upgraded it to Windows 10. Then I installed Linux mint 17.2 Cinnamon and had the following partitions:
The boot menu was showing Linux Mint and Windows 10 and I thought everything was fine. UEFI boot configuration showed "ubuntu". However after booting Windows and then rebooting, grub was gone, and in boot configuration there was only "Windows Boot Manager" available.
When I repaired grub2 with grub-install
and grub-update
I was able boot Linux Mint again, but only as long as I don't boot into Windows 10, which seems to wipe out grub like this every time.
Secureboot and Fastboot are disabled.
/boot/efi contains folders Boot, Microsoft and ubuntu.
Did I do something wrong? How can I get grub2 working permanently?
linux-mint windows grub2 uefi
is GRUB the best bootloading solution? is there an easier alternative?
â mikeserv
Nov 9 '15 at 9:43
Sorry, but this link does nothing for me. I can't be the only one that wants to get Windows 10 and Linux Mint working together on an UEFI system like this.
â Kana
Nov 9 '15 at 10:48
probably not. but the point is you don't need grub - just put your mint kernel and your windows loader on your esp and boot them. maybe you didn't read the link?
â mikeserv
Nov 9 '15 at 11:00
I did read that actually, and I gave it a try to copy vmlinuz and initramfs (there seems to be no such thing in mint, is this initrd.img? And also no initramfs-fallback.img). I only found some info how to do this on arch linux, not how it could be accomplished with other distributions. My UEFI boot menu didn't show any new options after that... Even so, this seems to be doing something completely else, by avoiding the problem. But I want to know what the problem is and how I can fix it.
â Kana
Nov 9 '15 at 17:01
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I installed Windows 7 on an SSD and upgraded it to Windows 10. Then I installed Linux mint 17.2 Cinnamon and had the following partitions:
The boot menu was showing Linux Mint and Windows 10 and I thought everything was fine. UEFI boot configuration showed "ubuntu". However after booting Windows and then rebooting, grub was gone, and in boot configuration there was only "Windows Boot Manager" available.
When I repaired grub2 with grub-install
and grub-update
I was able boot Linux Mint again, but only as long as I don't boot into Windows 10, which seems to wipe out grub like this every time.
Secureboot and Fastboot are disabled.
/boot/efi contains folders Boot, Microsoft and ubuntu.
Did I do something wrong? How can I get grub2 working permanently?
linux-mint windows grub2 uefi
I installed Windows 7 on an SSD and upgraded it to Windows 10. Then I installed Linux mint 17.2 Cinnamon and had the following partitions:
The boot menu was showing Linux Mint and Windows 10 and I thought everything was fine. UEFI boot configuration showed "ubuntu". However after booting Windows and then rebooting, grub was gone, and in boot configuration there was only "Windows Boot Manager" available.
When I repaired grub2 with grub-install
and grub-update
I was able boot Linux Mint again, but only as long as I don't boot into Windows 10, which seems to wipe out grub like this every time.
Secureboot and Fastboot are disabled.
/boot/efi contains folders Boot, Microsoft and ubuntu.
Did I do something wrong? How can I get grub2 working permanently?
linux-mint windows grub2 uefi
linux-mint windows grub2 uefi
edited Sep 16 at 23:11
Jeff Schaller
33.1k849111
33.1k849111
asked Nov 9 '15 at 9:39
Kana
166
166
is GRUB the best bootloading solution? is there an easier alternative?
â mikeserv
Nov 9 '15 at 9:43
Sorry, but this link does nothing for me. I can't be the only one that wants to get Windows 10 and Linux Mint working together on an UEFI system like this.
â Kana
Nov 9 '15 at 10:48
probably not. but the point is you don't need grub - just put your mint kernel and your windows loader on your esp and boot them. maybe you didn't read the link?
â mikeserv
Nov 9 '15 at 11:00
I did read that actually, and I gave it a try to copy vmlinuz and initramfs (there seems to be no such thing in mint, is this initrd.img? And also no initramfs-fallback.img). I only found some info how to do this on arch linux, not how it could be accomplished with other distributions. My UEFI boot menu didn't show any new options after that... Even so, this seems to be doing something completely else, by avoiding the problem. But I want to know what the problem is and how I can fix it.
â Kana
Nov 9 '15 at 17:01
add a comment |Â
is GRUB the best bootloading solution? is there an easier alternative?
â mikeserv
Nov 9 '15 at 9:43
Sorry, but this link does nothing for me. I can't be the only one that wants to get Windows 10 and Linux Mint working together on an UEFI system like this.
â Kana
Nov 9 '15 at 10:48
probably not. but the point is you don't need grub - just put your mint kernel and your windows loader on your esp and boot them. maybe you didn't read the link?
â mikeserv
Nov 9 '15 at 11:00
I did read that actually, and I gave it a try to copy vmlinuz and initramfs (there seems to be no such thing in mint, is this initrd.img? And also no initramfs-fallback.img). I only found some info how to do this on arch linux, not how it could be accomplished with other distributions. My UEFI boot menu didn't show any new options after that... Even so, this seems to be doing something completely else, by avoiding the problem. But I want to know what the problem is and how I can fix it.
â Kana
Nov 9 '15 at 17:01
is GRUB the best bootloading solution? is there an easier alternative?
â mikeserv
Nov 9 '15 at 9:43
is GRUB the best bootloading solution? is there an easier alternative?
â mikeserv
Nov 9 '15 at 9:43
Sorry, but this link does nothing for me. I can't be the only one that wants to get Windows 10 and Linux Mint working together on an UEFI system like this.
â Kana
Nov 9 '15 at 10:48
Sorry, but this link does nothing for me. I can't be the only one that wants to get Windows 10 and Linux Mint working together on an UEFI system like this.
â Kana
Nov 9 '15 at 10:48
probably not. but the point is you don't need grub - just put your mint kernel and your windows loader on your esp and boot them. maybe you didn't read the link?
â mikeserv
Nov 9 '15 at 11:00
probably not. but the point is you don't need grub - just put your mint kernel and your windows loader on your esp and boot them. maybe you didn't read the link?
â mikeserv
Nov 9 '15 at 11:00
I did read that actually, and I gave it a try to copy vmlinuz and initramfs (there seems to be no such thing in mint, is this initrd.img? And also no initramfs-fallback.img). I only found some info how to do this on arch linux, not how it could be accomplished with other distributions. My UEFI boot menu didn't show any new options after that... Even so, this seems to be doing something completely else, by avoiding the problem. But I want to know what the problem is and how I can fix it.
â Kana
Nov 9 '15 at 17:01
I did read that actually, and I gave it a try to copy vmlinuz and initramfs (there seems to be no such thing in mint, is this initrd.img? And also no initramfs-fallback.img). I only found some info how to do this on arch linux, not how it could be accomplished with other distributions. My UEFI boot menu didn't show any new options after that... Even so, this seems to be doing something completely else, by avoiding the problem. But I want to know what the problem is and how I can fix it.
â Kana
Nov 9 '15 at 17:01
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
1
down vote
accepted
I found the problem. Looking at the NVRAM with sudo efibootmgr
I noticed that the Windows boot loader somehow seems to have the urge to be the first entry in the boot order. When I changed it to grub2 being first, windows overwrites entry 0000 and changes the boot order, even if grub2 was 0000 before, therefore overwriting it.
The solution was setting the Windows boot manager entry inactive but leave it in first position of the boot order:
sudo efibootmgr --bootnum 0000 --inactive
sudo efibootmgr --bootorder 0000,0002,000C,000D
(with 0002 being grub2)
add a comment |Â
up vote
1
down vote
I face exactly same problem to yours.
And here is my solution.
PS. My computer is ASUS and my first os is Win10 the second is ubuntu.
First please make sure Win10 completely shutdown by turnoff the quick startup of Win10. Prevent the issue that Win10 might not completely shutdown.
https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html
I found that there is a solution use the software 'boot-repair'.
https://help.ubuntu.com/community/Boot-Repair
So I use the boot usb, by which I could access the ubuntu os environment.
Then open the terminal, and go thru the commands below.
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
After the process completed, reboot the computer.
Use special key to go into BootMenu. In my case (ASUS desktop) F8.
http://www.disk-image.com/faq-bootmenu.htm
Do not go into the BIOS/UEFI setting mode!!
(I tried many times if I get into the BIOS/UEFI mode to change the boot sequence it will not work. I can see the Ubuntu option appear again, however after i put it to the first option and restart, it directly go to the Win10. I double check from the BIOS/UEFI mode, it simply make the Ubuntu option disappear again...)
Change the boot option sequence to what U expect.(Ubuntu to first)
Then the problem solved.
add a comment |Â
up vote
0
down vote
Some BIOS/EFI will by default point to EFIMicrosoftBootbootmgfw.efi
.
Just move EFIMicrosoftBootbootmgfw.efi
and EFIMicrosoftBootBCD
to EFIMicrosoftwin10
, or just move the whole folder and toast the EFI entry using bootice or something similar and it will use the fallback efi loader EFIBootBOOTX64.EFI
.
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I found the problem. Looking at the NVRAM with sudo efibootmgr
I noticed that the Windows boot loader somehow seems to have the urge to be the first entry in the boot order. When I changed it to grub2 being first, windows overwrites entry 0000 and changes the boot order, even if grub2 was 0000 before, therefore overwriting it.
The solution was setting the Windows boot manager entry inactive but leave it in first position of the boot order:
sudo efibootmgr --bootnum 0000 --inactive
sudo efibootmgr --bootorder 0000,0002,000C,000D
(with 0002 being grub2)
add a comment |Â
up vote
1
down vote
accepted
I found the problem. Looking at the NVRAM with sudo efibootmgr
I noticed that the Windows boot loader somehow seems to have the urge to be the first entry in the boot order. When I changed it to grub2 being first, windows overwrites entry 0000 and changes the boot order, even if grub2 was 0000 before, therefore overwriting it.
The solution was setting the Windows boot manager entry inactive but leave it in first position of the boot order:
sudo efibootmgr --bootnum 0000 --inactive
sudo efibootmgr --bootorder 0000,0002,000C,000D
(with 0002 being grub2)
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I found the problem. Looking at the NVRAM with sudo efibootmgr
I noticed that the Windows boot loader somehow seems to have the urge to be the first entry in the boot order. When I changed it to grub2 being first, windows overwrites entry 0000 and changes the boot order, even if grub2 was 0000 before, therefore overwriting it.
The solution was setting the Windows boot manager entry inactive but leave it in first position of the boot order:
sudo efibootmgr --bootnum 0000 --inactive
sudo efibootmgr --bootorder 0000,0002,000C,000D
(with 0002 being grub2)
I found the problem. Looking at the NVRAM with sudo efibootmgr
I noticed that the Windows boot loader somehow seems to have the urge to be the first entry in the boot order. When I changed it to grub2 being first, windows overwrites entry 0000 and changes the boot order, even if grub2 was 0000 before, therefore overwriting it.
The solution was setting the Windows boot manager entry inactive but leave it in first position of the boot order:
sudo efibootmgr --bootnum 0000 --inactive
sudo efibootmgr --bootorder 0000,0002,000C,000D
(with 0002 being grub2)
answered Nov 10 '15 at 20:33
Kana
166
166
add a comment |Â
add a comment |Â
up vote
1
down vote
I face exactly same problem to yours.
And here is my solution.
PS. My computer is ASUS and my first os is Win10 the second is ubuntu.
First please make sure Win10 completely shutdown by turnoff the quick startup of Win10. Prevent the issue that Win10 might not completely shutdown.
https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html
I found that there is a solution use the software 'boot-repair'.
https://help.ubuntu.com/community/Boot-Repair
So I use the boot usb, by which I could access the ubuntu os environment.
Then open the terminal, and go thru the commands below.
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
After the process completed, reboot the computer.
Use special key to go into BootMenu. In my case (ASUS desktop) F8.
http://www.disk-image.com/faq-bootmenu.htm
Do not go into the BIOS/UEFI setting mode!!
(I tried many times if I get into the BIOS/UEFI mode to change the boot sequence it will not work. I can see the Ubuntu option appear again, however after i put it to the first option and restart, it directly go to the Win10. I double check from the BIOS/UEFI mode, it simply make the Ubuntu option disappear again...)
Change the boot option sequence to what U expect.(Ubuntu to first)
Then the problem solved.
add a comment |Â
up vote
1
down vote
I face exactly same problem to yours.
And here is my solution.
PS. My computer is ASUS and my first os is Win10 the second is ubuntu.
First please make sure Win10 completely shutdown by turnoff the quick startup of Win10. Prevent the issue that Win10 might not completely shutdown.
https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html
I found that there is a solution use the software 'boot-repair'.
https://help.ubuntu.com/community/Boot-Repair
So I use the boot usb, by which I could access the ubuntu os environment.
Then open the terminal, and go thru the commands below.
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
After the process completed, reboot the computer.
Use special key to go into BootMenu. In my case (ASUS desktop) F8.
http://www.disk-image.com/faq-bootmenu.htm
Do not go into the BIOS/UEFI setting mode!!
(I tried many times if I get into the BIOS/UEFI mode to change the boot sequence it will not work. I can see the Ubuntu option appear again, however after i put it to the first option and restart, it directly go to the Win10. I double check from the BIOS/UEFI mode, it simply make the Ubuntu option disappear again...)
Change the boot option sequence to what U expect.(Ubuntu to first)
Then the problem solved.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I face exactly same problem to yours.
And here is my solution.
PS. My computer is ASUS and my first os is Win10 the second is ubuntu.
First please make sure Win10 completely shutdown by turnoff the quick startup of Win10. Prevent the issue that Win10 might not completely shutdown.
https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html
I found that there is a solution use the software 'boot-repair'.
https://help.ubuntu.com/community/Boot-Repair
So I use the boot usb, by which I could access the ubuntu os environment.
Then open the terminal, and go thru the commands below.
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
After the process completed, reboot the computer.
Use special key to go into BootMenu. In my case (ASUS desktop) F8.
http://www.disk-image.com/faq-bootmenu.htm
Do not go into the BIOS/UEFI setting mode!!
(I tried many times if I get into the BIOS/UEFI mode to change the boot sequence it will not work. I can see the Ubuntu option appear again, however after i put it to the first option and restart, it directly go to the Win10. I double check from the BIOS/UEFI mode, it simply make the Ubuntu option disappear again...)
Change the boot option sequence to what U expect.(Ubuntu to first)
Then the problem solved.
I face exactly same problem to yours.
And here is my solution.
PS. My computer is ASUS and my first os is Win10 the second is ubuntu.
First please make sure Win10 completely shutdown by turnoff the quick startup of Win10. Prevent the issue that Win10 might not completely shutdown.
https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html
I found that there is a solution use the software 'boot-repair'.
https://help.ubuntu.com/community/Boot-Repair
So I use the boot usb, by which I could access the ubuntu os environment.
Then open the terminal, and go thru the commands below.
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
After the process completed, reboot the computer.
Use special key to go into BootMenu. In my case (ASUS desktop) F8.
http://www.disk-image.com/faq-bootmenu.htm
Do not go into the BIOS/UEFI setting mode!!
(I tried many times if I get into the BIOS/UEFI mode to change the boot sequence it will not work. I can see the Ubuntu option appear again, however after i put it to the first option and restart, it directly go to the Win10. I double check from the BIOS/UEFI mode, it simply make the Ubuntu option disappear again...)
Change the boot option sequence to what U expect.(Ubuntu to first)
Then the problem solved.
answered Feb 8 at 7:35
Jason Hus
111
111
add a comment |Â
add a comment |Â
up vote
0
down vote
Some BIOS/EFI will by default point to EFIMicrosoftBootbootmgfw.efi
.
Just move EFIMicrosoftBootbootmgfw.efi
and EFIMicrosoftBootBCD
to EFIMicrosoftwin10
, or just move the whole folder and toast the EFI entry using bootice or something similar and it will use the fallback efi loader EFIBootBOOTX64.EFI
.
add a comment |Â
up vote
0
down vote
Some BIOS/EFI will by default point to EFIMicrosoftBootbootmgfw.efi
.
Just move EFIMicrosoftBootbootmgfw.efi
and EFIMicrosoftBootBCD
to EFIMicrosoftwin10
, or just move the whole folder and toast the EFI entry using bootice or something similar and it will use the fallback efi loader EFIBootBOOTX64.EFI
.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Some BIOS/EFI will by default point to EFIMicrosoftBootbootmgfw.efi
.
Just move EFIMicrosoftBootbootmgfw.efi
and EFIMicrosoftBootBCD
to EFIMicrosoftwin10
, or just move the whole folder and toast the EFI entry using bootice or something similar and it will use the fallback efi loader EFIBootBOOTX64.EFI
.
Some BIOS/EFI will by default point to EFIMicrosoftBootbootmgfw.efi
.
Just move EFIMicrosoftBootbootmgfw.efi
and EFIMicrosoftBootBCD
to EFIMicrosoftwin10
, or just move the whole folder and toast the EFI entry using bootice or something similar and it will use the fallback efi loader EFIBootBOOTX64.EFI
.
edited Jul 27 '17 at 13:28
zagrimsan
674418
674418
answered Jul 27 '17 at 12:05
Az Ze
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f241809%2fgrub2-gone-every-time-i-boot-windows-10%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
is GRUB the best bootloading solution? is there an easier alternative?
â mikeserv
Nov 9 '15 at 9:43
Sorry, but this link does nothing for me. I can't be the only one that wants to get Windows 10 and Linux Mint working together on an UEFI system like this.
â Kana
Nov 9 '15 at 10:48
probably not. but the point is you don't need grub - just put your mint kernel and your windows loader on your esp and boot them. maybe you didn't read the link?
â mikeserv
Nov 9 '15 at 11:00
I did read that actually, and I gave it a try to copy vmlinuz and initramfs (there seems to be no such thing in mint, is this initrd.img? And also no initramfs-fallback.img). I only found some info how to do this on arch linux, not how it could be accomplished with other distributions. My UEFI boot menu didn't show any new options after that... Even so, this seems to be doing something completely else, by avoiding the problem. But I want to know what the problem is and how I can fix it.
â Kana
Nov 9 '15 at 17:01