New error message when selecting Windows Boot Loader from the GRUB menu

[Scott Beamer]

Greetings,

After a recent Fedora 36 update, I'm getting an error message when 
selecting "Windows Boot Manager" from the GRUB menu.  Instead of booting 
like it had previously, it gives me an almost blank screen with the 
following text in the upper left:

     /EndEntire

And all I can do at that point is shut down and restart my computer, go 
to it's boot menu, and sekect
Windows Boot Manager, in order to boot into Windows.

I've been dual-booting Fedora 36 and Windows for weeks prior to this one 
without issue.

Google hasn't been of much help.

Any suggestions?

TIA

Scott

[Samuel Sieb]

On 8/4/22 15:39, Scott Beamer wrote:
>  After a recent Fedora 36 update, I'm getting an error message
> when 
>  selecting "Windows Boot Manager" from the GRUB menu.  Instead of booting 
>  like it had previously, it gives me an almost blank screen with the 
>  following text in the upper left:
>  
>       /EndEntire 
Highlight the Windows menu entry and press the "e" key to see what it's 
going to run.  You can also find that in one of the files in 
/boot/loader/entries.

[Chris Murphy]

On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote:
>  Greetings,
>
>  After a recent Fedora 36 update, I'm getting an error message when 
>  selecting "Windows Boot Manager" from the GRUB menu.  Instead of booting 
>  like it had previously, it gives me an almost blank screen with the 
>  following text in the upper left:
>
>       /EndEntire
>
>  And all I can do at that point is shut down and restart my computer, go 
>  to it's boot menu, and sekect
>  Windows Boot Manager, in order to boot into Windows.
>
>  I've been dual-booting Fedora 36 and Windows for weeks prior to this one 
>  without issue. 
What version? Current is 2.06-45.fc36 and there are a few complaints.

https://bodhi.fedoraproject.org/updates/FEDORA-2022-8ffd58c713#comment-26...
https://bugzilla.redhat.com/show_bug.cgi?id=2115202

dnf downgrade will get you the -29 version which is a ways back, but also easy and will
get you working. But to avoid it getting updated and breaking again in the near future
you'll need to add an exclude in the dnf.conf (man dnf.conf) for "grub2-*"

Set a reminder though, you'll eventually want to update it and it might even prevent a
system upgrade from getting a new version (or even failing, I'm not really sure).

An alternative is to:
rpm -qa | grep grub2

That'll get you a list of all the grub2 packages you'lll need to download from
here:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1977609

That's the -42 version which should work. Then you have the packages locally and you
can just put them in a directory and if you do an update that steps on this version again,
you can just cd to that dir and do "dnf downgrade *rpm" and it'll use the
local rpm files.

If you have a Fedora account or RGBZ account you can add yourself to the bug.



-- 
Chris Murphy

[Scott Beamer]

On 8/4/22 7:28 PM, Chris Murphy wrote:
>  On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote:
> > Greetings,
> >
> > After a recent Fedora 36 update, I'm getting an error message when
> > selecting "Windows Boot Manager" from the GRUB menu.  Instead of booting
> > like it had previously, it gives me an almost blank screen with the
> > following text in the upper left:
> >
> >       /EndEntire
> >
> > And all I can do at that point is shut down and restart my computer, go
> > to it's boot menu, and sekect
> > Windows Boot Manager, in order to boot into Windows.
> >
> > I've been dual-booting Fedora 36 and Windows for weeks prior to this one
> > without issue.
>  What version? Current is 2.06-45.fc36 and there are a few complaints. 
That version.

>  https://bodhi.fedoraproject.org/updates/FEDORA-2022-8ffd58c713#comment-26...
>  https://bugzilla.redhat.com/show_bug.cgi?id=2115202 
I commented on the bug.  Thanks
for the link.
>  dnf downgrade will get you the -29 version which is a ways back, but also easy and will
> get you working. But to avoid it getting updated and breaking again in the near future
> you'll need to add an exclude in the dnf.conf (man dnf.conf) for "grub2-*"
>
>  Set a reminder though, you'll eventually want to update it and it might even prevent
> a system upgrade from getting a new version (or even failing, I'm not really sure).
Thanks.  I went with that and added the exclude ti dnf.conf
>  An alternative is to:
>  rpm -qa | grep grub2
>
>  That'll get you a list of all the grub2 packages you'lll need to download from
> here:
>
>  https://koji.fedoraproject.org/koji/buildinfo?buildID=1977609
>
>  That's the -42 version which should work. Then you have the packages locally and you
> can just put them in a directory and if you do an update that steps on this version again,
> you can just cd to that dir and do "dnf downgrade *rpm" and it'll use the
> local rpm files. 
I'm too lazy for that ish.  I'll just hold on to the -29 version for a while and
follow up in a week.

>  If you have a Fedora account or RGBZ account you can add yourself to
> the bug.
>  I'm too lazy for that ish.  I'll just hold on to the -29 version for a while and
> follow up in a week.
>  
I do and I did.

Thanks for your help.  Much appreciated! :)

Scott

[Robert McBroom]

On 8/5/22 02:15, Scott Beamer wrote:
>  On 8/4/22 7:28 PM, Chris Murphy wrote:
> >
> > On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote:
> >> Greetings,
> >>
> >> After a recent Fedora 36 update, I'm getting an error message when
> >> selecting "Windows Boot Manager" from the GRUB menu.  Instead of 
> >> booting
> >> like it had previously, it gives me an almost blank screen with the
> >> following text in the upper left:
> >>
> >>       /EndEntire
> >>
> >> And all I can do at that point is shut down and restart my computer, go
> >> to it's boot menu, and sekect
> >> Windows Boot Manager, in order to boot into Windows.
> >>
> >> I've been dual-booting Fedora 36 and Windows for weeks prior to this 
> >> one
> >> without issue.
> > What version? Current is 2.06-45.fc36 and there are a few complaints.
>
>  That version.
>
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-8ffd58c713#comment-26... 
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2115202
>  I commented on the bug.  Thanks for the link.
> >
> > dnf downgrade will get you the -29 version which is a ways back, but 
> > also easy and will get you working. But to avoid it getting updated 
> > and breaking again in the near future you'll need to add an exclude 
> > in the dnf.conf (man dnf.conf) for "grub2-*"
> >
> > Set a reminder though, you'll eventually want to update it and it 
> > might even prevent a system upgrade from getting a new version (or 
> > even failing, I'm not really sure).
>  Thanks.  I went with that and added the exclude ti dnf.conf
> >
> > An alternative is to:
> > rpm -qa | grep grub2
> >
> > That'll get you a list of all the grub2 packages you'lll need to 
> > download from here:
> >
> > https://koji.fedoraproject.org/koji/buildinfo?buildID=1977609
> >
> > That's the -42 version which should work. Then you have the packages 
> > locally and you can just put them in a directory and if you do an 
> > update that steps on this version again, you can just cd to that dir 
> > and do "dnf downgrade *rpm" and it'll use the local rpm files.
>
>  I'm too lazy for that ish.  I'll just hold on to the -29 version for a 
>  while and follow up in a week.
>
> > If you have a Fedora account or RGBZ account you can add yourself to 
> > the bug.
> > I'm too lazy for that ish.  I'll just hold on to the -29 version for 
> > a while and follow up in a week.
> >
>
>  I do and I did.
>
>  Thanks for your help.  Much appreciated! :)
>
>  Scott  
For me the enter key makes the process continue to the windows boot

[Stephen Morris]

On 5/8/22 16:15, Scott Beamer wrote:
>  On 8/4/22 7:28 PM, Chris Murphy wrote:
> >
> > On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote:
> >> Greetings,
> >>
> >> After a recent Fedora 36 update, I'm getting an error message when
> >> selecting "Windows Boot Manager" from the GRUB menu.  Instead of 
> >> booting
> >> like it had previously, it gives me an almost blank screen with the
> >> following text in the upper left:
> >>
> >>       /EndEntire
> >>
> >> And all I can do at that point is shut down and restart my computer, go
> >> to it's boot menu, and sekect
> >> Windows Boot Manager, in order to boot into Windows.
> >>
> >> I've been dual-booting Fedora 36 and Windows for weeks prior to this 
> >> one
> >> without issue.
> > What version? Current is 2.06-45.fc36 and there are a few complaints.
>
>  That version.
>
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-8ffd58c713#comment-26... 
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2115202
>  I commented on the bug.  Thanks for the link.
> >
> > dnf downgrade will get you the -29 version which is a ways back, but 
> > also easy and will get you working. But to avoid it getting updated 
> > and breaking again in the near future you'll need to add an exclude 
> > in the dnf.conf (man dnf.conf) for "grub2-*"
> >
> > Set a reminder though, you'll eventually want to update it and it 
> > might even prevent a system upgrade from getting a new version (or 
> > even failing, I'm not really sure).
>  Thanks.  I went with that and added the exclude ti dnf.conf
> >
> > An alternative is to:
> > rpm -qa | grep grub2
> >
> > That'll get you a list of all the grub2 packages you'lll need to 
> > download from here:
> >
> > https://koji.fedoraproject.org/koji/buildinfo?buildID=1977609
> >
> > That's the -42 version which should work. Then you have the packages 
> > locally and you can just put them in a directory and if you do an 
> > update that steps on this version again, you can just cd to that dir 
> > and do "dnf downgrade *rpm" and it'll use the local rpm files.
>
>  I'm too lazy for that ish.  I'll just hold on to the -29 version for a 
>  while and follow up in a week.
>
> > If you have a Fedora account or RGBZ account you can add yourself to 
> > the bug.
> > I'm too lazy for that ish.  I'll just hold on to the -29 version for 
> > a while and follow up in a week.
> >
>
>  I do and I did.
>
>  Thanks for your help.  Much appreciated! :) 
I use grub to boot between Fedora 36,
now Windows 11 and Ubuntu, where 
Fedora 36 was a fresh install after installing the other 2 OS's first, 
and I have always received the message you have list right from the 
first boot of Fedora, but it has not stopped me from booting into Windows.

regards,
Steve

>  Scott
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam, report it: 
>  https://pagure.io/fedora-infrastructure/new_issue