Springnuts: So if I understand you correctly, the ubuntu boot entry works for you. I think what happens is that Windows changes the boot order during boot, or the firmware forgets it, which is a bit outside our ability to fix.
Unfortunately, I don't think I'm able to help you here. I don't see a boot entry containing S outside WINDOWS in your boot entry. IIRC, Boot-Repair is known to break boot, and we can't really provide any support for it or Windows boot loader editing tools. In either case, the next shim should boot for you in those situations, albeit with a 2s delay if it's booting via shimx64.efi (0s if it's booting via bootx64.efi). I believe the bcdedit command causes the Window's equivalent of shim (the bootx64.efi) to install to then run shim as the second stage, and hence it might pass windows specific arguments to it that shim does not understand, but I can't say for sure, it's a Windows question -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937115 Title: Unable to boot/install Impish daily in UEFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-amd64/+bug/1937115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
