You are not logged in.
Pages: 1
Hello, I have arch installed on my SSD. And I do use Ventoy (a bootable USB) to boot windows installed on VHD at my external HDD. So I did boot to windows and installed the monthly updates, all good till I tried to boot to arch. And I notice that the Windows Boot Manager boots instead of grub. I've tried to delete the /boot/EFI/Microsoft folder created while installing Windows updates and update the grub using grub-mkconfig -o /boot/grub/grub.cfg command. But it keeps booting to Windows Boot Manager.
https://imgur.com/RTCQOyM
even efibootmgr -v output not showing any Windows entry.
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0010,0011,0012,0013,0014,0015,0016,0017,0018,0019,001A,001B,001C
Boot0000* GRUB HD(1,GPT,22789d44-1bfd-425c-9db7-10ab89189d6a,0x2800,0xf2000)/File(\EFI\GRUB\grubx64.efi)
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012* Removable Drive VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,20699b27e1a34f488e97534d40523c1d)
Boot0013* Hard Drive VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,f5b01cc8ce8e9841b3a8fb94b6dfefee)
Boot0014* Second Hard Drive VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,293b8046e622c74ebd287431e0c56179)
Boot0015* USB Storage Device VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6895f49a99882e4bb0da03ec784d2828)
Boot0016* CD/DVD/CD-RW Drive VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,3750dce1249e1748876bee5d3f25ebfb)
Boot0017* Network VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6567de8ee595634d842b325e6a43510b)
Boot0018* Onboard NIC VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,1b7f7356e3475744a9a6ed8e91832083)
Boot0019* Onboard NIC VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,b4a054dda1fa7043abf832c5a88367a6)
Boot001A Diagnostics FvFile(be77e3c1-eb5a-4a5d-897f-536e8b3c74c0)
Boot001B Peripheral Device setting (OPROM setting) FvFile(be77e3c1-eb5a-4a5d-897f-536e8b3c74c0)
Boot001C Change boot mode setting FvFile(be77e3c1-eb5a-4a5d-897f-536e8b3c74c0)
Offline
Hello,
Could you explain what happens in the video you linked to?
It looks like you boot your computer, presenting an error that says Windows failed to start. You then reboot into the firmware interface and specify that you want to boot from GRUB (the video is too blurry to really read much else). Linux then boots successfully, but you reboot without selecting GRUB and you get the same error message as you did the first time.
I can't read the screen where you are in some kind of UEFI menu, but are you sure that you aren't selecting a temporary startup device instead of persistently changing the boot order?
Also, I'd suggest giving your post a significantly more descriptive title. The one it has right now is...sad.
If my advice above doesn't help, would you tell what kind of comptuer you are using and what keys you pressed to change the boot order? (And maybe consider uploading a higher quality video by changing the video settings on your phone or something so the text can be read more easily?)
I don't think removing Window's EFI files is going to help much. Did Windows fail before you removed the files or did it only fail afterwards?
Offline
This is just a guess but I think the motherboard firmware ("BIOS") is hard-coded to look for the Windows EFI loader and shows this message if it's not found. If you want to get rid of Windows completely then try deleting the recovery partition, it might be linked to that. Otherwise you need to restore the Windows bootloader, which was stored in the /EFI/Microsoft/ directory on the EFI system partition which you claim to have deleted. A Windows recovery disk can probably do that for you but if it doesn't then seek support from Microsoft.
To prevent Windows from hijacking the UEFI loader in future you should check the ArchWiki (which is what you should have done before randomly deleting system critical directories):
Jin, Jîyan, Azadî
Offline
As I can see on a video, Windows probably boots via MBR and not UEFI. (there is only Arch under UEFI boot but several items under Legacy). Consider disabling legacy boot all together in your BIOS, if you only use UEFI media. Also, what's your boot order? Maybe just putting Arch in the front would solve this.
Offline
Pages: 1