acedude1234
(Eric Andrade-Strohm)
August 10, 2022, 2:31am
1
GRUB isn’t loading Windows 10 anymore after the recent update.
I saw there was the recent grub update to fix this issue, but that didn’t seem to work for me. (Maybe I’m installing it wrong?) I am on Windows 10, and all the posts I see talk about Windows 11.
The posts I saw were:
I was using a “maintenance” app in Windows to clean up my computer and that app changed something to the boot process.
Now when I select the “Windows Boot Manager” entry in GRUB, the Dell logo appears and it stays there indefinitely:
[ce654c843b8c30d4385b91fd23cdc8a80e92fd3d.jpeg]
[e4bf93684cb51babee88cc95aca27cca7bcde636.jpeg]
It looks like GRUB is pointing to a wrong path of the bootmgfw.efi file which is located in the /EFI/Microsoft/Boot/ path of the EFI partition but I don’t know how …
and
https://discussion.fedoraproject.org/t/grub-dual-boot-issue-win-logo-and-then-freeze/25126/7
Seems to be the same issue on my end, where I can boot to Windows through the Boot Menu, but not through GRUB. It hangs on the boot and gets stuck.
Any advice is appreciated.
Thank you.
acedude1234
(Eric Andrade-Strohm)
August 10, 2022, 2:42am
2
I think I figured out my issue. Documenting in case anybody else comes across this.
In the update documentation, the update to fix the issue was given the command:
sudo dnf upgrade --refresh --advisory=FEDORA-2022-d0c322d15a
I read through the original bug report again:
https://bugzilla.redhat.com/show_bug.cgi?id=2115202#c27
And after scrolling down, it seems that the command that worked for me was listed in there:
sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d0c322d15a
That command worked for me but not the other.
2 Likes
The first command seems to have missed the need to enable updates-testing in order to work.
If you already have that repo enabled then it would work, but if not then the extra option is needed.
acedude1234
(Eric Andrade-Strohm)
August 10, 2022, 3:53pm
4
Yeah, I didn’t think it needed to be enabled because in the documentation it seemed that the update was marked as stable and was pushed out already.