Hello forum, during the installation of this new ISO, a mirror failed and somehow the installation stopped.
I tried to run the installation again but it wouldn’t work, so I rebooted and noticed that my UEFI entry for Windows disappeared…
Windows is in another SSD drive than the one that I tried to install EnOS.
I usually press F8 during boot process to switch OS, but now the UEFI entry is missing.
Checked BIOS and it’s not there too…
Any idea how to recover the Windows UEFI entry ?
Strange because it said that is prober was installed by default and activated in grub again in this iso. What I recommend, go back to your installation, refresh the mirrors via welcome app then install eos.
Then add the os prober thingy to make your windows appear on grub. It should not be gone…
You could try this AFTER a successful install?
Edit: sorry you mention some part with bios and others. It’s difficult to judge what is going on, we need more infos!
You would need to post your partitioning scheme. It would be easier if you can install eos, else you out would have to chroot and post here some more hardware infos in case your windows partition is really gone.
That is quite the odd one. I’ve never seen an installation remove something in firmware, only add to it. . . I’ll be watching answers to this,I wouldn’t even know where to begin.
Thanks Zircon34 and gbodymechanic
I stopped using this a long time ago, I have been pressing F8 during boot to select the OS to boot…
So it’s pretty strange that this happened, WIndows UEFI disappeared, I just downloaded the Windows ISO from Microsoft, and I’m about to burn it to a pendrive to see if I can use the recover option
you should be able to add entries in UEFI by selecting hard drives, and entries should not get removed from calamares only added.
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,000A,0008,0009,0002,0003,0004
Boot0001* endeavouros-7347
Boot0002* UEFI:CD/DVD Drive
Boot0003* UEFI:Removable Device
Boot0004* UEFI:Network Device
Boot0008* UEFI: SanDisk
Boot0009* UEFI: SanDisk, Partition 2
Boot000A* UEFI OS
Don’t know why you would do that. It’s cleaner using grub and linx plus windows entries. The os prober are basically 2-3 commands, but as I said, we don’t know anything about how you partitioned your drive, difficult to know what is going on without that info.
In live session, can you mount Windows’ ESP and check its content?
If Windows’ bootloader is somehow gone I guess you would need a recovery disk or an installation medium to restore it.
If the bootloader is still there, then perhaps use efibootmgr to manually create an UEFI boot entry for it.
Windows is in this drive: nvme1n1
$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 NO_LABEL 19F9-D3FA 298,8M 0% /boot/efi
├─sda2 btrfs 70dc7d41-46da-4c17-b92a-51c98f0d731f 178,3G 5% /var/log
│ /home
│ /var/cache
│ /.snapshots
│ /
└─sda3 swap 1 swap 8c8234f7-cba8-41c2-9274-8d50701e8171 [SWAP]
sdb
├─sdb1 ntfs Data 1836134E36132BEE
└─sdb2 ext4 1.0 aa3e2e7b-8de9-4ff0-8e88-2824dcc86059 86,6G 7% /mnt/ext4
nvme0n1
├─nvme0n1p1
└─nvme0n1p2 ntfs wdblack 080E4AED0E4AD37C
nvme1n1
├─nvme1n1p1
└─nvme1n1p2 ntfs E674A86E74A842E3
What is this one?
and as endeavors is on 1 I would bet you choose formatting the windows ESP
Probably, but I didn’t change that option, maybe it was the default?
Unfortunately, I don’t know
$ efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,000A,0008,0009,0002,0003,0004
Boot0001* endeavouros-7347 HD(1,GPT,36d588c4-a11a-6243-8d18-00802ffc3e5e,0x1000,0x96000)/File(\EFI\ENDEAVOUROS-7347\GRUBX64.EFI)
Boot0002* UEFI:CD/DVD Drive BBS(129,,0x0)
Boot0003* UEFI:Removable Device BBS(130,,0x0)
Boot0004* UEFI:Network Device BBS(131,,0x0)
Boot0008* UEFI: SanDisk PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(3,0)/CDROM(1,0x390d00,0x33298)..BO
Boot0009* UEFI: SanDisk, Partition 2 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(3,0)/HD(2,MBR,0x1f2a498d,0x390d00,0x33000)..BO
Boot000A* UEFI OS HD(1,GPT,36d588c4-a11a-6243-8d18-00802ffc3e5e,0x1000,0x96000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
default is keep and no mountpoint set:
Definitely a complicated setup with mix of ntfs, ext4 and btrfs partitions. That is out of my league how to fix that, especially on a Friday evening…
Edit: thanks god @joekamprad is answering the call! Ghostbusters…hahaha
I chose to install in the entire hard drive, selected swap for hibernate, then selected btrfs
Thanks zircon34, any help is much appreciated 
ehhehe, I agree on that
you check your firmware if you have option to add boot entries?
You mean inside the BIOS?
the strange thing is that i do not see any ESP aside from that you created with the installer… and this is on /dev/sda where you do not have any ntfs volumes so the good question is where is your windows installation? and could it be it is installed in legacy mode? CSM BIOS / MBR ??
sudo fdisk -l would show better info
sudo LANG=C fdisk -l
Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDS100T1X0E-00AFY0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1825F755-8606-4DAB-B464-DB407139DC85
Device Start End Sectors Size Type
/dev/nvme0n1p1 34 32767 32734 16M Microsoft reserved
/dev/nvme0n1p2 32768 1953521663 1953488896 931,5G Microsoft basic data
Disk /dev/nvme1n1: 465,76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WDS500G2B0C-00PXH0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: AF20D7D3-DD03-4904-8539-1CB7E813B3CB
Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 34815 32768 16M Microsoft reserved
/dev/nvme1n1p2 34816 976773119 976738304 465,7G Microsoft basic data
Disk /dev/sda: 223,57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: Corsair Neutron
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1EFBBAE0-5CF1-D746-BE89-6B4AF0E5E99C
Device Start End Sectors Size Type
/dev/sda1 4096 618495 614400 300M EFI System
/dev/sda2 618496 396593490 395974995 188,8G Linux filesystem
/dev/sda3 396593491 468857024 72263534 34,5G Linux swap
Disk /dev/sdb: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM010-2EP1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: C82B77C7-486C-4B8D-995D-E1952A631F8E
Device Start End Sectors Size Type
/dev/sdb1 2048 1743808511 1743806464 831,5G Microsoft basic data
/dev/sdb2 1743808512 1953523711 209715200 100G Linux filesystem
Windows is here /dev/nvme1n1
CSM is disabled
GPT is in use. nothing is in MBR
If Windows is installed in UEFI mode, where is its ESP?
You did have separate ESPs, one on each drive for each OS?