Failing installing Fedora 42 Gnome

[tonyemilly]

Hi I’m not new to installing linux but currently I am having issue with installing fedora 42 when it gets to part with bootloader it crashes with this:

or similar window where is something about utf-8… i don’t know what is happening because when i tried to install it for the first time it worked fine…

Does anyone had the same issue and/or know how to fix it… I’m trying to install my fedora for two days straight and it’s driving me crazy…

Thank you

[pg-tips (P G)]

Toshiba laptop by any chance?

It sounds like it might be a similar issue to these two:

Fedora 41 Bootloader Fails to Install with Anaconda Error 41.35

Just need some help running. I’m trying to install Fedora 41 on my old laptop Model: Toshiba Satellite Dynabook B65/Y RAM/ROM: 8GB RAM, 1TB SSD Processor: Intel i5200u Graphics: Intel HD 5500 Already tried the following basic troubleshooting. Using the Fedora Media Writer, used Ventoy at some point Manual Partitioning Using the same bootable USB and successfully install Fedora 41 on my other laptop. Tweaking w…

Installing bootloader failed on installing Fedora KDE Plasma 42

Hi everyone. My name is Sajed. I’ve a problem with installing the bootloader when I am trying to install Fedora KDE Plasma on my laptop as primary OS. Previously I had Windows 10 installed on my one disk drive (ssd SATA), partitioned into two drive (C as sys files l, and D for data). I downloaded the .iso from the official site and used Fedora media writer to put the system into the USB flash disk. Then I booted normally, with checking that my BIOS is on UEFI mode and the secure boot is enab…

[tonyemilly]

It’s not Toshiba laptop it’s HP ProBook 6560b

[pg-tips (P G)]

Can you boot into the live Fedora 42 USB, open a terminal and run the command efibootmgr ?

If you paste the results here, we might be able to see if a problematic entry there is causing those UTF-8 errors.

[tonyemilly]

i have this here:

[pg-tips (P G)]

Thanks. So it’s a bit odd that no boot entries exist, even though 0000, 0001 and 0005 “should” exist according to the BootCurrent and BootOrder.

However, it’s not clear why that would cause the error you get in the installer.

When you have time to run the installer again, it would be useful to see the actual UTF-8 error message you mention.

[gnwiii (George N. White III)]

Issues like this often affect multiple Linux distros, so, if you can avoid AI nonsense clickbait, you may find useful information from users of other distros. It is also worth checking “probes” for your system in the LHDB. Some LHDB probes include helpful user comments.

When reporting problems it helps if you can provide enough detail to allow others with similar hardware reproduce the issue. This is more likely to generate results of the information is provided in text form so it is easily discovered with web searches. System details are often provided by running inxi -Fzxx in a terminal. In the live installer you will have to install inxi (and it will be lost with a reboot). You should also mention whether you are dual booting. It is best to make sure system UEFI/BIOS firmware is fully updated, as others won’t generally be able to test with matching older firmware versions.

Edit: from the LHDB, I gather the system is quite old. Even “high quality” systems suffer from deterioration of components (particularly capacitors) over time. Investing time in older systems is often a losing battle. At present many large companies are dumping high quality (enterprise grade) systems as they reduce staff, so refurbished used systems that don’t support enterprise Windows 11 with a warranty are selling for bargain prices so it is a good time to upgrade.