Windows Update broke systemd-boot - now can't chroot in like in wiki

Dear Community,

I’m using Windows 11 on the same SSD with my endeavourOS and it worked just fine for almost a year.

EDIT: I forgot I’m using systemd-boot. :mending_heart:

Now suddenly the option to select EOS in the GRUB screen disappeared. I assume it could be due to a windows update.

So I startet to follow the Repair a non-booting GRUB EOS Guide but i get an error at this point in the linked Arch-chroot guide.

When it says sudo mount /dev/sda2 /mnt I execute sudo mount /dev/mvme0n1p6 /nmt because of nvme.

But i get this error:

[liveuser@eos-2024.09.22 ~]$ sudo mount /dev/mvme0n1p6 /nmt
mount: /nmt: fsconfig system call failed: /dev/mvme0n1p6: Can't lookup blockdev.
       dmesg(1) may have more information after failed mount system call.

My lsblk looks like this:

[liveuser@eos-2024.09.22 ~]$ lsblk -f
NAME        FSTYPE      FSVER            LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs    4.0                                                                    0   100% /run/archiso/airootfs
sda                                                                                                     
├─sda1      exfat       1.0              Ventoy     4E21-0000                                           
│ └─ventoy  iso9660     Joliet Extension EOS_202409 2024-09-22-10-45-49-00                     0   100% /run/archiso/bootmnt
└─sda2      vfat        FAT16            VTOYEFI    223C-F3F8                                           
nvme0n1                                                                                                 
├─nvme0n1p1 vfat        FAT32                       2A44-8E75                                           
├─nvme0n1p2                                                                                             
├─nvme0n1p3 ntfs                                    C48446F98446EE0C                                    
├─nvme0n1p4 ntfs                                    0E06B0FA06B0E3BD                                    
├─nvme0n1p5 vfat        FAT32                       98FA-3E23                                           
└─nvme0n1p6 crypto_LUKS 2                           082ebd56-3798-43ff-ba04-ef9bcd32cac4

What can I do and how to prevent this problem at all in the future?

Thank you very much! <3

You have a typo here. Should be nvme0n1p6

Also, since your disk is luks encrypted, you need to unlock it first with cryptsetup.

Use this guide for the chroot:
https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

There are instructions down the page for encrypted devices.

1 Like

Thank you very much Dalto, I managed to chroot into my installation.

Now I get this error when following the guide:

[root@EndeavourOS ~]# grub-install
bash: grub-install: command not found

Are you sure you are using grub and not systemd-boot?

Also, can you describe exactly what you are seeing on boot so we can be sure what the issue is here.

Oh shit you are right, I think im on systemd-boot. :smiling_face_with_tear:
Sorry for that. So easy to forget when using GRUB for years and not dealing with these things on a regular basis.

Normally I see a small list in the middle of the screen, where I have entries like

  • EOS
  • EOS Fallback
  • Windows 11

Now its just Windows 11.

I’m just reading the arch wiki article on troubleshooting systemd-boot.
This does not look right to me or is it because of the chroot?

[root@EndeavourOS ~]# bootctl
systemd-boot not installed in ESP.
System:
Not booted with EFI

Available Boot Loaders on ESP:
          ESP: /efi
         File: └─/EFI/BOOT/bootx64.efi

Boot Loader Entries:
        $BOOT: /efi
        token: endeavouros

0 entries, no entry could be determined as default.

OK, can you run reinstall-kernels from within the chroot and share the full output from that command?

You need to boot the ISO in EFI mode. Make sure you didn’t boot the ISO in legacy/csm mode.

[root@EndeavourOS ~]# reinstall-kernels
Installing kernel 6.12.7-arch1-1
dracut[I]: Executing: /usr/bin/dracut --no-hostonly --force /efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd-fallback 6.12.7-arch1-1
dracut[I]: *** Including module: bash ***
dracut[I]: *** Including module: shell-interpreter ***
dracut[I]: *** Including module: systemd ***
dracut[I]: *** Including module: systemd-ask-password ***
dracut[I]: *** Including module: systemd-cryptsetup ***
dracut[I]: *** Including module: systemd-initrd ***
dracut[I]: *** Including module: systemd-journald ***
dracut[I]: *** Including module: systemd-modules-load ***
dracut[I]: *** Including module: systemd-pcrphase ***
dracut[I]: *** Including module: systemd-sysctl ***
dracut[I]: *** Including module: systemd-sysusers ***
dracut[I]: *** Including module: systemd-tmpfiles ***
dracut[I]: *** Including module: systemd-udevd ***
dracut[I]: *** Including module: modsign ***
dracut[I]: *** Including module: i18n ***
dracut[I]: *** Including module: drm ***
dracut[I]: *** Including module: plymouth ***
dracut[I]: *** Including module: btrfs ***
dracut[I]: *** Including module: crypt ***
dracut[I]: *** Including module: dm ***
dracut[I]: *** Including module: kernel-modules ***
dracut[I]: *** Including module: kernel-modules-extra ***
dracut[I]: *** Including module: lvm ***
dracut[I]: *** Including module: mdraid ***
dracut[I]: *** Including module: nvdimm ***
dracut[I]: *** Including module: qemu ***
dracut[I]: *** Including module: qemu-net ***
dracut[I]: *** Including module: fido2 ***
dracut[I]: *** Including module: pkcs11 ***
dracut[I]: *** Including module: hwdb ***
dracut[I]: *** Including module: lunmask ***
dracut[I]: *** Including module: resume ***
dracut[I]: *** Including module: rootfs-block ***
dracut[I]: *** Including module: terminfo ***
dracut[I]: *** Including module: udev-rules ***
dracut[I]: *** Including module: virtiofs ***
dracut[I]: *** Including module: dracut-systemd ***
dracut[I]: *** Including module: usrmount ***
dracut[I]: *** Including module: base ***
dracut[I]: *** Including module: fs-lib ***
dracut[I]: *** Including module: shutdown ***
dracut[I]: *** Including modules done ***
dracut[I]: *** Installing kernel module dependencies ***
dracut[I]: *** Installing kernel module dependencies done ***
dracut[I]: *** Resolving executable dependencies ***
dracut[I]: *** Resolving executable dependencies done ***
dracut[I]: *** Hardlinking files ***
dracut[I]: *** Hardlinking files done ***
dracut[I]: *** Generating early-microcode cpio image ***
dracut[I]: *** Constructing GenuineIntel.bin ***
dracut[I]: *** Store current command line parameters ***
dracut[I]: *** Stripping files ***
dracut[I]: *** Stripping files done ***
dracut[I]: *** Creating image file '/efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd-fallback' ***
cp: error writing '/efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd-fallback': No space left on device
dracut[F]: Creation of /efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd-fallback failed
/usr/lib/kernel/install.d/50-dracut-fallback.install failed with exit status 1.

It is a GPT USB Stick with ventoy I booted from the BIOS boot menu. I thought it should be EFI Boot then?

In the meantime I followed the archwiki and did this:

[root@EndeavourOS ~]# bootctl install
Created "/efi/EFI/systemd".
Created "/efi/loader".
Created "/efi/loader/keys".
Created "/efi/loader/entries".
Created "/efi/EFI/Linux".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/BOOT/BOOTX64.EFI".
⚠ Mount point '/efi' which backs the random seed file is world accessible, which is a security hole! ⚠
⚠ Random seed file '/efi/loader/.#bootctlrandom-seed4fe9417b4b5f39e2' is world accessible, which is a security hole! ⚠
Random seed file /efi/loader/random-seed successfully written (32 bytes).
[root@EndeavourOS ~]# bootctl
System:
Not booted with EFI

Available Boot Loaders on ESP:
          ESP: /efi
         File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 257.1-1-arch)
               └─/EFI/BOOT/bootx64.efi (systemd-boot 257.1-1-arch)

Boot Loader Entries:
        $BOOT: /efi
        token: endeavouros

0 entries, no entry could be determined as default.

I think maybe I mounted the windows boot partittion instead of the EOS one?

[liveuser@eos-2024.09.22 ~]$ lsblk -f
NAME        FSTYPE      FSVER            LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs    4.0                                                                    0   100% /run/archiso/airootfs
sda                                                                                                     
├─sda1      exfat       1.0              Ventoy     4E21-0000                                           
│ └─ventoy  iso9660     Joliet Extension EOS_202409 2024-09-22-10-45-49-00                     0   100% /run/archiso/bootmnt
└─sda2      vfat        FAT16            VTOYEFI    223C-F3F8                                           
nvme0n1                                                                                                 
├─nvme0n1p1 vfat        FAT32                       2A44-8E75                                           
├─nvme0n1p2                                                                                             
├─nvme0n1p3 ntfs                                    C48446F98446EE0C                                    
├─nvme0n1p4 ntfs                                    0E06B0FA06B0E3BD                                    
├─nvme0n1p5 vfat        FAT32                       98FA-3E23                                           
└─nvme0n1p6 crypto_LUKS 2                           082ebd56-3798-43ff-ba04-ef9bcd32cac4

I chose nvme0n1p1 but I think its the boot from windows. So nvme0n1p5 could be the correct one?

You shouldn’t have done that. That is the wrong thing. We need to see what the impact to your EFI variables is here.

Can you share the output of efibootmgr

Yes. p5 is what should be mounted.

You probably have a created a bit of a mess on your Windows EFI partition. I would get Linux working for now though and see.

I did bootctl remove and restartet the laptop. Nothing has changed with the bootscreen showing just Windows 11; and it boots normally.

Now I’ll be getting back into chroot with the right boot partition.

This is the much better looking output of reinstall-kernels now:

[root@EndeavourOS /]# reinstall-kernels
Installing kernel 6.12.7-arch1-1
dracut[I]: Executing: /usr/bin/dracut --no-hostonly --force /efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd-fallback 6.12.7-arch1-1
dracut[I]: *** Including module: bash ***
dracut[I]: *** Including module: shell-interpreter ***
dracut[I]: *** Including module: systemd ***
dracut[I]: *** Including module: systemd-ask-password ***
dracut[I]: *** Including module: systemd-cryptsetup ***
dracut[I]: *** Including module: systemd-initrd ***
dracut[I]: *** Including module: systemd-journald ***
dracut[I]: *** Including module: systemd-modules-load ***
dracut[I]: *** Including module: systemd-pcrphase ***
dracut[I]: *** Including module: systemd-sysctl ***
dracut[I]: *** Including module: systemd-sysusers ***
dracut[I]: *** Including module: systemd-tmpfiles ***
dracut[I]: *** Including module: systemd-udevd ***
dracut[I]: *** Including module: modsign ***
dracut[I]: *** Including module: i18n ***
dracut[I]: *** Including module: drm ***
dracut[I]: *** Including module: plymouth ***
dracut[I]: *** Including module: btrfs ***
dracut[I]: *** Including module: crypt ***
dracut[I]: *** Including module: dm ***
dracut[I]: *** Including module: kernel-modules ***
dracut[I]: *** Including module: kernel-modules-extra ***
dracut[I]: *** Including module: lvm ***
dracut[I]: *** Including module: mdraid ***
dracut[I]: *** Including module: nvdimm ***
dracut[I]: *** Including module: qemu ***
dracut[I]: *** Including module: qemu-net ***
dracut[I]: *** Including module: fido2 ***
dracut[I]: *** Including module: pkcs11 ***
dracut[I]: *** Including module: hwdb ***
dracut[I]: *** Including module: lunmask ***
dracut[I]: *** Including module: resume ***
dracut[I]: *** Including module: rootfs-block ***
dracut[I]: *** Including module: terminfo ***
dracut[I]: *** Including module: udev-rules ***
dracut[I]: *** Including module: virtiofs ***
dracut[I]: *** Including module: dracut-systemd ***
dracut[I]: *** Including module: usrmount ***
dracut[I]: *** Including module: base ***
dracut[I]: *** Including module: fs-lib ***
dracut[I]: *** Including module: shutdown ***
dracut[I]: *** Including modules done ***
dracut[I]: *** Installing kernel module dependencies ***
dracut[I]: *** Installing kernel module dependencies done ***
dracut[I]: *** Resolving executable dependencies ***
dracut[I]: *** Resolving executable dependencies done ***
dracut[I]: *** Hardlinking files ***
dracut[I]: *** Hardlinking files done ***
dracut[I]: *** Generating early-microcode cpio image ***
dracut[I]: *** Constructing GenuineIntel.bin ***
dracut[I]: *** Store current command line parameters ***
dracut[I]: *** Stripping files ***
dracut[I]: *** Stripping files done ***
dracut[I]: *** Creating image file '/efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd-fallback' ***
dracut[I]: *** Creating initramfs image file '/efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd-fallback' done ***
dracut[W]: Running in hostonly mode in a container!
dracut[I]: Executing: /usr/bin/dracut --hostonly --no-hostonly-cmdline -f /efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd 6.12.7-arch1-1
dracut[I]: *** Including module: bash ***
dracut[I]: *** Including module: shell-interpreter ***
dracut[I]: *** Including module: systemd ***
dracut[I]: *** Including module: systemd-ask-password ***
dracut[I]: *** Including module: systemd-cryptsetup ***
dracut[I]: *** Including module: systemd-initrd ***
dracut[I]: *** Including module: systemd-journald ***
dracut[I]: *** Including module: systemd-modules-load ***
dracut[I]: *** Including module: systemd-sysctl ***
dracut[I]: *** Including module: systemd-sysusers ***
dracut[I]: *** Including module: systemd-tmpfiles ***
dracut[I]: *** Including module: systemd-udevd ***
dracut[I]: *** Including module: i18n ***
dracut[I]: *** Including module: drm ***
dracut[I]: *** Including module: plymouth ***
dracut[I]: *** Including module: crypt ***
dracut[I]: *** Including module: dm ***
dracut[I]: *** Including module: kernel-modules ***
dracut[I]: *** Including module: kernel-modules-extra ***
dracut[I]: *** Including module: hwdb ***
dracut[I]: *** Including module: rootfs-block ***
dracut[I]: *** Including module: terminfo ***
dracut[I]: *** Including module: udev-rules ***
dracut[I]: *** Including module: dracut-systemd ***
dracut[I]: *** Including module: usrmount ***
dracut[I]: *** Including module: base ***
dracut[I]: *** Including module: fs-lib ***
dracut[I]: *** Including module: shutdown ***
dracut[I]: *** Including modules done ***
dracut[I]: *** Installing kernel module dependencies ***
dracut[I]: *** Installing kernel module dependencies done ***
dracut[I]: *** Resolving executable dependencies ***
dracut[I]: *** Resolving executable dependencies done ***
dracut[I]: *** Hardlinking files ***
dracut[I]: *** Hardlinking files done ***
dracut[I]: *** Generating early-microcode cpio image ***
dracut[I]: *** Constructing GenuineIntel.bin ***
dracut[I]: *** Store current command line parameters ***
dracut[I]: *** Stripping files ***
dracut[I]: *** Stripping files done ***
dracut[I]: *** Creating image file '/efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd' ***
dracut[I]: *** Creating initramfs image file '/efi/43ebc200993e4786bda378ce7bf781f3/6.12.7-arch1-1/initrd' done ***

Output of efibootmgr:

[root@EndeavourOS /]# efibootmgr
BootCurrent: 001F
Timeout: 2 seconds
BootOrder: 0002,0000,0001,0010,0011,0012,0013,0014,0015,0016,0017,0018,0019,001E,001C,001D,001F,0020,0021,0022,0023,0024
Boot0000* Windows Boot Manager  HD(1,GPT,36e72123-f6be-43f1-ad78-05153575b944,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000043000100000010000000040000007fff0400
Boot0001* Linux Boot Manager    HD(1,GPT,e4f77ec7-9aa2-4d4c-8472-f2590b113aa1,0x1000,0x1f4000)/\EFI\systemd\systemd-bootx64.efi
Boot0002* Linux Boot Manager    HD(5,GPT,441932fe-52d0-4866-a22f-b0c6f3aa0778,0x12544c12,0x1f4000)/\EFI\systemd\systemd-bootx64.efi
Boot0010  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu     FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen      FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics    FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  Asset Information     FvFile(da465b87-a26f-4c12-b78a-0361428fa026)
Boot0015  Regulatory Information        FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot0016  ThinkShield secure wipe       FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0017  ThinkShield Passwordless Power-On Device Manager      FvFile(08448b41-7f83-49be-82a7-0e84790ab133)
Boot0018  Wi-Fi Configuration   FvFile(d3aaff0f-cb22-4792-896c-802c2e9383ba)2d004100700070000000
Boot0019  Intel(R) MEBx FvFile(29a70110-7762-4211-ae88-fab19b7665be)
Boot001A  Startup Interrupt Menu        FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot001B  Rescue and Recovery   FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot001C* USB CD        VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot001D* USB FDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot001E* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001F* USB HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0020* PXE BOOT      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0021* LENOVO CLOUD  VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
Boot0022* ON-PREMISE    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri()
Boot0023  Other CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35400)
Boot0024  Other HDD     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ca88c2349e7ae947beeb43038a5aeae700)
Boot0025* IDER BOOT CDROM       PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
Boot0026* IDER BOOT Floppy      PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
Boot0027* ATA HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0028* ATAPI CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)

Thank you very much so far.

This probably needs to be removed.

1 Like

Ok. Looks like this now:

[root@EndeavourOS /]# sudo efibootmgr -b 0001 --delete-bootnum
BootCurrent: 001F
Timeout: 2 seconds
BootOrder: 0002,0000,0010,0011,0012,0013,0014,0015,0016,0017,0018,0019,001E,001C,001D,001F,0020,0021,0022,0023,0024
Boot0000* Windows Boot Manager  HD(1,GPT,36e72123-f6be-43f1-ad78-05153575b944,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000043000100000010000000040000007fff0400
Boot0002* Linux Boot Manager    HD(5,GPT,441932fe-52d0-4866-a22f-b0c6f3aa0778,0x12544c12,0x1f4000)/\EFI\systemd\systemd-bootx64.efi
Boot0010  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu     FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen      FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics    FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  Asset Information     FvFile(da465b87-a26f-4c12-b78a-0361428fa026)
Boot0015  Regulatory Information        FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot0016  ThinkShield secure wipe       FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0017  ThinkShield Passwordless Power-On Device Manager      FvFile(08448b41-7f83-49be-82a7-0e84790ab133)
Boot0018  Wi-Fi Configuration   FvFile(d3aaff0f-cb22-4792-896c-802c2e9383ba)2d004100700070000000
Boot0019  Intel(R) MEBx FvFile(29a70110-7762-4211-ae88-fab19b7665be)
Boot001A  Startup Interrupt Menu        FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot001B  Rescue and Recovery   FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot001C* USB CD        VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot001D* USB FDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot001E* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001F* USB HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0020* PXE BOOT      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0021* LENOVO CLOUD  VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
Boot0022* ON-PREMISE    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri()
Boot0023  Other CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35400)
Boot0024  Other HDD     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ca88c2349e7ae947beeb43038a5aeae700)
Boot0025* IDER BOOT CDROM       PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
Boot0026* IDER BOOT Floppy      PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
Boot0027* ATA HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0028* ATAPI CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)

I’ll try a reboot.

Works. You are the best! :heart:

Thank you very much for your help and time.

Out of interest: Any idea how all that happened?

1 Like

The old entries are removed at the beginning of the update process and the new entries are created at the end of the update process. The most common reason for them being missing is that the update was interrupted in the middle.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.