I seem to have this exact issue:
"Initial install 19.04, dual boot with Win10, everything fine;
Upgrade to 19.10, Ubuntu boots fine, Win10 does not"
On a fully up to date 19.10 install, however, I seem to have one
difference:
When I select in the grub menu to boot windows it throws an error
This bug was fixed in the package grub2 - 2.04-1ubuntu12.1
---
grub2 (2.04-1ubuntu12.1) eoan; urgency=medium
* debian/patches/ubuntu-tpm-unknown-error-non-fatal.patch: treat "unknown"
TPM errors as non-fatal, but still write up the details as debug messages
so we can
There are multiple reports of chainload working again with the fix
uploaded to eoan-proposed; marking as verification-done for Eoan with
2.04-1ubuntu12.1
** Tags removed: id-5d978799ba24715c5ddcabc5 verification-needed
verification-needed-eoan
** Tags added: id-5d978799ba24715c5ddcabc
#40 works, would be nice if you release this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
Title:
Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
To manage notifications
I can confirm grub2 from eoan-proposed fixes the issue and I'm able to
boot both Windows and Linux on a system without SB and without shim.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
I have enabled the eoan-proposed apt repo, and installed the latest
grub2 packages from there.
After a reboot, booting windows works nicely! :D
Thanks heaps, @adconrad and all the others who have helped diagnose and
fix this issue.
Let me know if you want me to run any further testing or get
Hello Adam,
My test machine has been migrated to Focal. I don't know if this can
help, however, the bug has disappeared with the Focal versions of
grub/shim.
Ask me for command outputs if necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello Joseph, or anyone else affected,
Accepted grub2 into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu12.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Update: after some reboots (PC on/off, etc) and win 10 update (insider
preview last update), now bootmgfw.efi boots from grub(2.04-1ubuntu12)
successfully. Shim is currently installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is there any way to test 2.04-1ubuntu13 from focal on 19.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
Title:
Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
To manage
This bug was fixed in the package grub2 - 2.04-1ubuntu13
---
grub2 (2.04-1ubuntu13) focal; urgency=medium
* debian/patches/ubuntu-tpm-unknown-error-non-fatal.patch: treat "unknown"
TPM errors as non-fatal, but still write up the details as debug messages
so we can further
For me installing shim fixed nothing: still the same issue - return to
grub menu when trying to boot(chain load) windows. Maybe I also have to
re-install grub after shim is installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ Dual-boot users who have somehow had shim uninstalled from their system /
Secure Boot disabled.
+
+ [Test case]
+ (system with dual-boot setup for Ubuntu and Windows)
+ 1) uninstall shim/shim-signed from the system
+ 2) Run 'sudo grub-install -v'; ensure
It has nothing to do with whether the file handle is closed or not; this
is just confusing code because of how it's built.
Shim is supposed to be installed by the installer when you set up the
system in UEFI mode; this is done for you by the installer, and isn't a
dependency of grub because grub
Given that my patch fixes the issue for me means:
This works:
grub_load_and_start_image(boot_image);
grub_file_close (file);
grub_loader_set (grub_chainloader_boot, grub_chainloader_unload, 0);
return 0;
This doesn't:
grub_file_close (file);
grub_loader_set
This patch may be wrong but it fixes the issue for me. I already tested
it on my actual system (not just VirtualBox).
Now to your comments:
1. shim is not dependency of grub2. My 18.04, 18.10 and 19.04 installations had
only these packages and no shim:
grub-common, grub2-common,
No; this patch is wrong.
For starters, you really ought to have shim installed, and that is the
primary cause for such failures -- somehow your install is incomplete,
and shim was removed either because the package was removed, or through
the use of boot-repair (IIRC it replaces shim with using
For anyone trying to reproduce:
VirtualBox with EFI enabled with Win 10 Pro x86_64 installed first and
Ubuntu 19.10 installed after Windows to the latest additional partition
of /dev/sda. On fresh install with all updates:
1. Make sure you can boot both Windows and Ubuntu
2. Purge all shim* and
PPA with this patch – https://launchpad.net/~xeron-
oskom/+archive/ubuntu/grub2
Reproduced this big in VirtualBox and tested this PPA and it fixes the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attachment "Patch to keep shim protocol for chainload but fix boot
when SB disabled" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated
Possible patch. Untested, just an idea.
** Patch added: "Patch to keep shim protocol for chainload but fix boot when SB
disabled"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+attachment/5301074/+files/xeron-fix-no-sb-chainload-2.patch
--
You received this bug notification
Possible fix is to change chainloader to check `grub_efi_secure_boot()`
and not `grub_linuxefi_secure_validate()`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
Title:
Grub EFI amd64 no
Well may be grub_linuxefi_secure_validate() should still return 1 as
intended by this code to skip validation in some cases but then
chainloader should not depend on this value.
I hope grub2 package maintainers will find some time to take a look at
this.
--
You received this bug notification
Take a look at this diff between disco and eoan:
--- grub2-2.02+dfsg1/grub-core/loader/efi/linux.c 2019-10-29
00:23:53.0 +
+++ grub2-2.04/grub-core/loader/efi/linux.c 2019-10-29 00:10:44.0
+
@@ -23,6 +23,7 @@
#include
#include
#include
+#include
For some this problem is answered by: [Windows option just reloads grub
bootloader after updating to Ubuntu
19.10](https://askubuntu.com/questions/1183528/windows-option-just-
reloads-grub-bootloader-after-updating-to-ubuntu-19-10/1183623#1183623).
Before following steps in answer use
I was also experiencing this problem and fixed it by using the shim
bootloader instead of Grub. I'm not sure if using Grub directly _should_
work, maybe there's still a bug here, and I'm also not sure what changed
during the Ubuntu upgrade (I assume it was using Grub directly before as
well, but
I noticed in the attached document of comment #18 that some files were missing:
grub-install: info: cannot open `/usr/lib/shim/shim/fbx64.efi': No such file or
directory.
grub-install: info: cannot open `/usr/lib/shim/mmx64.efi': No such file or
directory.
Because these files come from the
@cyphermox
I have executed the commands as indicated. I reinstalled grub-efi-amd64
and grub-efi-amd64-signed and ran grub-install -v. You will find the
results of the commands in the attached file.
Windows still refuses to boot from Grub.
** Attachment added: "Commands output"
Downgraded to 2.02 and everything works again.
Major difference in debug output on 2.02 is the line which says:
2.02:
shim bla bla not available
shim_lock bla bla
linuxefi_secure_validate: 0
2.04:
SecureBoot: 0
SetupMode: 1
secure boot not enabled, not validating bla bla
For the sake of testing I've updated to the latest grub from 19.10
(2.04-1ubuntu12) and I can't boot Windows anymore. My exact steps were:
0. Ubuntu 19.10 with grub from 19.04. Everything works
1. Move /etc/grub.d/07_os-prober back to /etc/grub.d/30_os-prober to rule this
change out
2. sudo apt
Bug 1839317 looks too similar to ignore the possibility of the same
underlying issue. There's other person there besides me who reports the
same behavior on amd64.
My Windows bootloader is fine.
I can boot Windows using my motherboard's EFI boot menu selector.
I can boot Windows if I downgrade
Hi there
Same problem after update from 19.04 to 19.10.
I can't load Windows 10 from Grub: Grub EFI amd64 no longer start
EFI/Microsoft/Boot/bootmgfw.efi
Please fix it as soon as possible.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug is *not* a duplicate of 1839317; since we're not looking at
ARM-based systems here.
Could you please update your grub-efi-amd64 and grub-efi-amd64-signed
packages (well, make sure your system is fully up to date), then run:
sudo grub-install -v
And include the output here.
Not all the
Same issue here. GRUB is my only way of accessing Windows which is what
I use as a secondary for games and Windows-only software.
Hoping for a fix soon!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is probably duplicate of
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317.
I have the same issue.
I can boot Windows 10 from BIOS/EFI boot menu, but can't boot it from
grub.
Setting debug=chain shows that grub tries to use SecureBoot, but it's
disabled.
--
You received this
Hi @cyphermox, I have tested with F12 on my Alienware Alpha:
* F12
* Select Windows Boot Manager
* Goes straight to grub
So no difference regardless of which boot option I select.
How was the installation done?
I installed Ubuntu 19.04 the upgraded to 19.10.
Here's my disk layout:
~> sudo
Is that a duplicate of
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317 ?
** Changed in: grub2 (Ubuntu Eoan)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here the details of /boot file (with EFI partition mounted)
** Attachment added: "find /boot output (with EFI partition mounted)"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+attachment/5297817/+files/find_in_boot_dir.output
--
You received this bug notification because you
Yes, by using the F12 key, I can display the EFI start menu and start
Windows with the "Windows Boot Manager" line.
This is a test machine that follows the development of "Ubuntu next".
Initially installed with Ubuntu 17.10 beta, it has followed the updates
of all Ubuntu development versions
If you use F8 or F12 (or whatever hotkey to get the firmware's boot
menu); can you then run "Windows Boot Manager" and successfully start
Windows?
How was the installation done? Could you please describe how the disk
was partitioned for dual-booting, and the steps taked in the installer?
At this
** Tags added: id-5d978799ba24715c5ddcabc5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
Title:
Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
To manage notifications about
@brian-murray I have 2.04-1ubuntu9 installed, as well as these extras:
~> sudo apt list --installed '*grub*'
Listing... Done
grub-common/eoan,now 2.04-1ubuntu9 amd64 [installed]
grub-efi-amd64-bin/eoan,now 2.04-1ubuntu9 amd64 [installed,automatic]
grub-efi-amd64-signed/eoan,now
** Tags removed: rls-ee-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
Title:
Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
To manage notifications about this bug
** Also affects: grub2 (Ubuntu Eoan)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
Title:
Grub EFI amd64 no longer start
@Jay - What version of grub2 do you have installed?
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Tags added: rls-ee-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289
Title:
I upgraded to the eoan beta yesterday, and I have the same issue.
Running update-grub gives me:
~> sudo update-grub
[sudo] password for jtuckey:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image:
47 matches
Mail list logo
