I have already given a second try to install the OS on my desktop PC in case I selected something incorrectly during the first attempt but the result is the same: the installer hangs at 91% when it says it is cleaning up the system and making final adjusts.
The install log looks as it is shown in the log below:
Issue sorted. EndeavourOS is up and running at last.
I am moving away from Windows (so no dual-booting) and my recent Windows installation was on disk nvme0n1. As suggested in a guide I read, I erased all partitions using gparted launched from the welcome app before starting the installation and was relying on the installer at a later stage to re-partition my system disk. However, one of the drives (sdb) in my computer was the system disk before nvme0n1 hosted Windows and still had some boot partitions that I was not aware of as Windows could cope with that and no issues resulted while using Windows.
[daniel@daniel-desktop ~]$ lsblk -l
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 2,7T 0 disk
sda1 8:1 0 128M 0 part
sda2 8:2 0 2,7T 0 part
sdb 8:16 0 223,6G 0 disk
sdc 8:32 0 3,6T 0 disk
sdc1 8:33 0 16M 0 part
sdc2 8:34 0 100G 0 part
sdc3 8:35 0 3,5T 0 part
nvme0n1 259:0 0 232,9G 0 disk
nvme0n1p1 259:1 0 512M 0 part /boot/efi
nvme0n1p2 259:2 0 215,2G 0 part /
nvme0n1p3 259:3 0 17,2G 0 part [SWAP]
The thing that should have made me suspicious a bit earlier is that the UEFI boot menu - when loading the USB installer media - still contained an entry called Windows Boot Manager (or something like this). This was still there when I was at my 5th or 6th attempt of installing Endeavour OS with different methods and versions of installers. Another ‘weird’ thing was that when I succeeded the installation, EOS did not load but I got a blue screen of death screen with error code 0xc000000e.
Before succeeding, there was a 2-hour power outage in the middle of my struggle that prevented me from replying to you earlier but at least also made me calm down and restart my attempts with a clear head and behold…
Thank you for your attention and support, Rick. Have great rest of the weekend.
Right, there was no bootable Windows on the PC anymore but some Windows created boot partitions on one of the drives. As soon as these were deleted, I could boot into EOS.
I never thought i would see that even if it left a partition behind. Windows usually has 4 partitions efi, recovery, restore and the C: partition which holds Windows OS. Wierd!
I think some UEFI machines expect an .efi file at a specific location on the EFI partition. This location is where Windows typically puts its .efi file.
I remember that with one machine we had to overwrite that Windows .efi file in order to have Antergos boot working. No other .efi file location worked with that particular machine. Untortunately I don’t remember the machine’s brand.
So UEFI implementations may vary between machines.
