Qubes efi breaks after booting windows drive (Not dual boot)

[vingallo]

Installed Qubes 4.1.2, works fine, shut down reboot install software all good.

On same PC I physically removed Qubes hdd and replaced it with a Windows hdd. Booted into windows. After removing Windows hdd and putting back Qubes hdd it will not boot, Is asking for proper boot media.

The drives were only installed and turned on one at a time (not dual booting and physically swapped). So I really cannot understand why Qubes refuses to boot.

Reinstalled qubes and did the same physical swap again to test it…same result qubes will not boot and required propper boot media after windows is booted once.

What could be going wrong and how do I get Qubes to boot ?

[cayce]

edited

[vingallo]

secure boot disabled, same issue.

It is only when the hdd is removed, windows hdd is booted into, and then qubes is put back into the pc that I have an issue.

Otherwise Qubest works without issue.

One single boot of windows and it is game over for qubes. I cannot understand this.

[sm95]

efibootmgr may need to be corrected. Windows probably deleted your Qubes boot entry. There are quite a few EFI related posts in the forum that should cover how to check and update.

Edit to add Docs page:

UEFI troubleshooting

Edit to add another forum post:

Qubes 4.1: efibootmgr usage

If your device is /dev/sda and efi partition is 1 then : efibootmgr -v -c -u -L MichaelA -l /EFI/qubes/grubx64.efi -d /dev/sda -p 1 If you use qubes os as external device, folow this (I assume that your device is /dev/sda and efi partition is 1) : cp /boot/efi/EFI/qubes/* /boot/efi/EFI/BOOT mv /boot/efi/EFI/BOOT/grubx64.efi /boot/efi/EFI/BOOT/bootx64.efi mv /boot/efi/EFI/BOOT/grub.cfg /boot/efi/EFI/BOOT/boox64.cfg efibootmgr -v -c -u -L MichaelB -l /EFI/BOOT/bootx.64efi -d /dev/sda -p 1

[vingallo]

I physically disconnected the qubes hdd, then connected win hdd and booted.

Do you think it may be something else ? I dont see how that file could be deleted or altered if the qubes drive was physically disconnect. What do you think please let me know?

[vingallo]

The second thread linked solved problem! Thank you. Perhaps guide can be updated for 4.1.2 for any user facing a similar issue. Is there I way I can help do that ?