After installation of F30 Grub dont show Windows anymore

Hello folks,

I’ve just installed f30 over F25. But now, my former dualboot System has become a single OS system.
Windows 10 is still “there” but it seems that something has messed with the UEFI Boot.

I tried to fix it myself with several “how to” tutorials on the net. Most lead to
"Just type in “sudo update-grub” and dont work.
Also those who try to use a windows boot device and use the repair terminal also fail at a certain point (cant switch to any drive but x:\ wich is the only one i dont need)

So you guys my last chance. I hope someone have a clue for me.
I had seen that there is often asked for some outputs. If they are important, here they are:

[VoidByte@localhost /]$ sudo parted --list
Modell: ATA Samsung SSD 850 (scsi)
Festplatte  /dev/sda:  500GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: gpt
Disk-Flags: 

Nummer  Anfang  Ende   Größe   Dateisystem  Name                  Flags
 1      1049kB  340GB  340GB   ntfs                               msftdata
 2      340GB   341GB  1074MB  ext4
 5      341GB   499GB  158GB                                      lvm
 3      499GB   500GB  732MB   fat32        EFI System Partition  boot, esp
 4      500GB   500GB  315MB   ntfs                               msftdata


Modell: ATA Hitachi HDP72505 (scsi)
Festplatte  /dev/sdb:  500GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos
Disk-Flags: 

Nummer  Anfang  Ende   Größe  Typ      Dateisystem  Flags
 1      1049kB  500GB  500GB  primary  ntfs         boot


Modell: ATA Hitachi HDT72505 (scsi)
Festplatte  /dev/sdc:  500GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos
Disk-Flags: 

Nummer  Anfang  Ende   Größe  Typ      Dateisystem  Flags
 1      1049kB  500GB  500GB  primary  ntfs


Modell: SMI USB DISK (scsi)
Festplatte  /dev/sdd:  8103MB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos
Disk-Flags: 

Nummer  Anfang  Ende    Größe   Typ      Dateisystem  Flags
 1      1049kB  8103MB  8102MB  primary  fat32        boot, lba


[VoidByte@localhost /]$ sudo efibootmgr -v
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0004,0007,0001
Boot0000* Windows Boot Manager	HD(3,GPT,03deea0c-9724-4aa7-b795-0573cb4017fe,0x3a193000,0x15d000)/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.}...3................
Boot0001  kali	HD(3,GPT,03deea0c-9724-4aa7-b795-0573cb4017fe,0x3a193000,0x15d000)/File(\EFI\KALI\GRUBX64.EFI)
Boot0002* Fedora	HD(3,GPT,03deea0c-9724-4aa7-b795-0573cb4017fe,0x3a193000,0x15d000)/File(\EFI\FEDORA\SHIMX64.EFI)
Boot0004* UEFI OS	HD(3,GPT,03deea0c-9724-4aa7-b795-0573cb4017fe,0x3a193000,0x15d000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0007* UEFI: SMI USB DISK 1100	PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)/HD(1,MBR,0x463f462c,0x800,0xf17800)AMBO
[VoidByte@localhost /]$ 


[VoidByte@localhost /]$ sudo efibootmgr
[sudo] Passwort für VoidByte: 
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0004,0007,0001
Boot0000* Windows Boot Manager
Boot0001  kali
Boot0002* Fedora
Boot0004* UEFI OS
Boot0007* UEFI: SMI USB DISK 1100

If i boot up the system, no matter what disk or partition, it always end up in a failsafe and bring me to GRUB2 Menu. But there are just 4 entries:

  1. Fedora 30 some version text
  2. Fedora 30 some older version text
  3. Fedora 30 some kind of emergency boot
  4. UEFI System Settings (wich brings me to my usual UEFI (BIOS) settings.)

any ideas what i can do?

Hi, @voidbyte! Welcome to the community! Please do take a few minutes to go over the introductory posts in #start-here when you have the time. They contain lots of useful information.

If you’ve already tried some things and haven’t succeed, I suggest we verify your Windows efi bootloader are still there for it to boot.

Please post here output of these two commands:

sudo tree -Dah /boot/efi
sudo cat /etc/fstab