Problems upgrading dual boot system

After having upgraded my desktop pc from FC31 to FC33 without any problem I attempted the upgrade of my laptop HP Pavilion G7 from FC32 to FC33, had a conflict in kde/plasma that seems to be solved by now, but as it was not then, I tried a fresh install and discovered that it was required to reformat the sda2 /boot/efi to enable to proceed as I got the explanation that the partition is on ntfs format. I tried the same on my desktop pc and there there was no such constraint. I did not want to reformat the EFI partition knowing that it were to destroy the windows boot. So I ended up in installing, without any complication, FC28, of which I still got a live-dvd and from there upgraded without any problem to fc33.
There are other discussions that show that after FC29 there was a change in the installer that make it very difficult to do a fresh install with personal partitioning to older pc’s that do not have the right level of UEFI bios, it seems that at HP the level should be at least be 30 while my laptop is at 25, and there is no upgrade. The consequence is that I can only boot into Fedora by pressing ESC and/or F9 at the right moment at power-on.

You should have waited a few days or enabled the updates-testing repository when updating/upgrading

the efi partition should be FAT32, not NTFS. At this early stage of boot, I think Linux/Grub don’t even understand NTFS filesystem

that sounds hard to believe, could you link additional information?

Can you show us the outputs of

lsblk

fdisk -l

efibootmgr -v

My reply by email, though using the appropriate address, did not work, so here in the alternative way:
You should have waited a few days or enabled the updates-testing repository when updating/upgrading

I found the bug report describing the problem and giving a dnf command adding a specific updates/testing >repository but it did not solve the issue

that sounds hard to believe, could you link additional information?

As releases before fc30 don’t complain, and Windows 10 neither, I don’t see why sda2 could be ntfs

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 698,6G 0 disk
├─sda1 8:1 0 400M 0 part
├─sda2 8:2 0 260M 0 part /boot/efi
├─sda3 8:3 0 128M 0 part
├─sda4 8:4 0 89,8G 0 part
├─sda5 8:5 0 1002M 0 part /swap
├─sda6 8:6 0 7,8G 0 part [SWAP]
├─sda7 8:7 0 109,4G 0 part /
├─sda8 8:8 0 20,7G 0 part
├─sda9 8:9 0 59G 0 part
├─sda10 8:10 0 97,7G 0 part
├─sda11 8:11 0 119,5G 0 part
└─sda12 8:12 0 97,3G 0 part
sr0 11:0 1 1024M 0 rom
zram0 252:0 0 1,9G 0 disk [SWAP]
[root@localhost gerard]# fdisk -l
Disque /dev/sda : 698,64 GiB, 750156374016 octets, 1465149168 secteurs
Modèle de disque : ST750LM022 HN-M7
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : gpt
Identifiant de disque : 1683D89B-A998-4963-B0C0-8941D5A8686C

Périphérique Début Fin Secteurs Taille Type
/dev/sda1 2048 821247 819200 400M Environnement de récupération Windows
/dev/sda2 821248 1353727 532480 260M Système EFI
/dev/sda3 1353728 1615871 262144 128M Réservé Microsoft
/dev/sda4 1615872 189867710 188251839 89,8G Données de base Microsoft
/dev/sda5 189868032 191920127 2052096 1002M Environnement de récupération Windows
/dev/sda6 191922176 208306175 16384000 7,8G Partition d'échange Linux
/dev/sda7 208306176 437682175 229376000 109,4G Système de fichiers Linux
/dev/sda8 1421643776 1465147391 43503616 20,7G Données de base Microsoft
/dev/sda9 437682176 561483775 123801600 59G Système de fichiers Linux
/dev/sda10 561483776 766283775 204800000 97,7G Données de base Microsoft
/dev/sda11 766283776 1016893439 250609664 119,5G Système de fichiers Linux
/dev/sda12 1016893440 1220939775 204046336 97,3G Système de fichiers Linux

Les entrées de la table de partitions ne sont pas dans l’ordre du disque.

Disque /dev/zram0 : 1,86 GiB, 2000683008 octets, 488448 secteurs
Unités : secteur de 1 × 4096 = 4096 octets
Taille de secteur (logique / physique) : 4096 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
[root@localhost gerard]# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 3000,3002,2001,2002,2003
Boot0000* Windows Boot Manager HD(2,GPT,ae85b5a3-03c9-4bde-bf78-f67163c45c97,0xc8800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...-................
Boot0002* Fedora HD(2,GPT,ae85b5a3-03c9-4bde-bf78-f67163c45c97,0xc8800,0x82000)/File(\EFI\fedora\shimx64.efi)
Boot2001* USB Drive (UEFI) RC
Boot2002* Internal CD/DVD ROM Drive (UEFI) RC
Boot3000* Internal Hard Disk RC
Boot3002* Internal Hard Disk RC

Not asked for but additional proof that sda2 is not ntfs I made a screenprint of yhe partitionmanager output.
That the early implementation of UEFI on a range of HP laptops gives dual boot problems is also seen in discussions of other linux distributions, I found several at Ubuntu.