Fresh-Installed 37 over 33: GRUB lacks Windows entry?

Ask Fedora
,
22

Thanks Jeff.

(I’ve discovered by accident there’s a way mark in-line text as computer text as well: surround by backticks as on stackoverflow. I’m not seeing an icon for that but I have cataract issues and can’t see well.)

Indeed, /sys/firmware/efi/efivars is a directory on my laptop.

So, that means my Fedora was installed as uefi.

And we’ve determined before that the entire disk is uefi, so no surprise the Windows is uefi.

I have the Windows 10 recovery ISO and will install into a USB memory.

But just to be perfectly clear, I need to:

  1. Boot laptop with the Windows ISO and “repair Windows” or something to that effect, after which the box would become Windows-boot-only, right?

  2. I can test by booting the laptop, and I should just get Windows, right?

  3. I then boot with the previously-made Fedora 37 ISO, right?

  4. then run grub2-mkconfig -o /boot/grub2/grub.cfg and I should at that point be good, right?

So what is not clear is how the Windows partition got corrupted. I assume operator error, but what specific operator error, I wonder? Or, if it’s not operator error, why would installing grub have broken the Windows bootability when doing the regular install, but step (4) (above) not do so now?

23

Thanks Vladislav. I have followed your link, downloaded the software, made a bootable USB, and booted it.

I pick my language and so on.

Then I can choose “Troubleshoot” or “Turn off your PC.”

For Troubleshoot, I can choose “Startup Repair,” and I tried this. It works for a minute “Diagnosing your PC” and “Attempting Repairs.” and finally, “Startup Repair couldn’t repair your PC.” My only option is to go back to the Troubleshoot menu.

The other choices don’t seem appropriate: “Command Prompt,” “Uninstall Updates,” “UEFI Firmware Settings,” “System Restore” to a restore point (I have none), or “System Image Recovery.”

What do you recommend I try?