You are not logged in.
Hi I am having a problem I did y grub all good in linux and i tryed in windows to do <bcdedit> in windows like i was suppose to and i think there is a lock out thats not recognizing grub. i was wondering if anybody else encountered this problem. so what i need to know is how can i stop windows from overiding the uefi even when i did everything i had to do to recognize grub. sorry i couldn't post programming details at this time if i am prompted to do so in this response i will momentartily thanks.
Last edited by useraddition (2026-01-20 02:07:47)
Offline
first: https://deepl.com - it's hard to comprehent
second:
how can i stop windows
only one way: don't use it - but seriously: you can't! although microsoft is one of the big ones who came up with and agreed upon uefi spec they violate it quite a lot:
- no matter what is in place at <esp>/efi/boot/boot<arch>.efi - windows overrides it anyway
- if a boot entry for bootmgfw.efi is missing windows will add it - even if it was chain loaded by another loader
- your only chance is to leave <esp>/efi/boot/boot<arch>.efi and an entry to bootmgfw.efi to windows and only add an entry to grub - and hope that when you change the boot order in your uefi booting windows doesn't mess with it - but that highly depends on the systems uefi implementation
Last edited by cryptearth (2026-01-20 07:14:22)
Offline
This is my layout in efibootmgr i am trying to access the boot from a boot disk, my windows 11 installation is strait from the store when i bought this computer.
#efibootmgr -u
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0000,2001,2002,2003
Boot0000* Windows Boot Manager HD(1,GPT,f7bfc510-1b13-425f-bcd5-3507dcdd59b0,0x800,0xfa000)/\EFI\Microsoft\Boot\bootmgfw.efi䍒
Boot0001* EFI PXE 0 for IPv4 (C8-53-09-FE-65-77) PciRoot(0x0)/Pci(0x1b,0x5)/Pci(0x0,0x0)/MAC(c85309fe6577,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)䍒
Boot0002* EFI PXE 0 for IPv6 (C8-53-09-FE-65-77) PciRoot(0x0)/Pci(0x1b,0x5)/Pci(0x0,0x0)/MAC(c85309fe6577,0)/IPv6([::],0,Static,[::],[::],64)䍒
Boot0003* EFI USB Device (SanDisk) UsbWwid(781,5575,0,0401991801232515232)/HD(1,MBR,0x1685dd8,0x800,0x72987c0)䍒
Boot0004* Windows Boot Manager HD(1,GPT,f7bfc510-1b13-425f-bcd5-3507dcdd59b0,0x800,0xfa000)/\esp\EFI\GRUB\grubx64.efi䥗䑎坏S
Boot2001* EFI USB Device 䍒
Boot2002* EFI DVD/CDROM 䍒
Boot2003* EFI Network 䍒
[root@sysrescue /]# cd /boot
[root@sysrescue boot]# ls
'$RECYCLE.BIN' EFI initramfs-linux-lts.img vmlinuz-linux-lts
BackupSbb.bin esp intel-ucode.img
BOOT grub 'System Volume Information'
[root@sysrescue boot]# So I'm kind of stuck what I'm suppose to do do I access the boot manager from windows to fix it or is there something i can do in my linux boot disk?
Offline
This is the partition layout i made with gparted i shrank the windows partition to use just a few things and once i get my linux working better i plan on doing most stuff with it.
#lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 1021.4M 1 loop
sda 8:0 1 57.3G 0 disk
└─sda1 8:1 1 57.3G 0 part
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 500M 0 part /boot
├─nvme0n1p2 259:2 0 741.2G 0 part /
├─nvme0n1p3 259:3 0 9.8G 0 part
├─nvme0n1p4 259:4 0 16M 0 part
├─nvme0n1p5 259:5 0 200.5G 0 part
└─nvme0n1p6 259:6 0 2G 0 part
[root@sysrescue boot]# Offline
the grub entry is called "Windows Boot Manager" for some reason and lives in /boot/esp?? that makes no sense, what is your exact issue? maybe a naming conflict? reinstall with a different name, the default is just "arch":
grub-install --efi-directory=/boot
grub-mkconfig -o /boot/grub/grub.cfgSo I'm kind of stuck what I'm suppose to do do I access the boot manager from windows to fix it or is there something i can do in my linux boot disk?
well you should boot into an arch installation medium and make the repairs inside of a chroot
windows nuking your nvram entries really is not windows, but a bad uefi implementation
Last edited by system72 (2026-01-20 00:08:14)
Offline
Actually what you said is in accurate and has nothing to do with my issue. The built in Windows system is overiding a command i used in Windows known as 'bcdedit' i could only change the default boot loader from windows. However when i booted into a linux boot disk i did 'efibootmgr -u' and i showed my linux call on 'boot 0004' NOT 'boot0001' so what i need to do is most likely tinker with windows command prompt and boot order again until the process is fine. Like I said, I need to know the exact method for why boot is being overiden by Windows boot manager, and how to get the 'boot0004' order upto 'boot0001' And for your reply, yes i did install my grub correctly and i did a system call to 'esp' folder. Thank you very much.
Offline
yeah seriously, nobody can understand what you're saying, if you want the windows boot manager entry that is grub to be first in the boot order then you can do it with efibootmgr:
efibootmgr -o 4,0sure, if you think what i said is inaccurate, then believe that fantasy..
Last edited by system72 (2026-01-20 00:58:08)
Offline
'efibootmgr -o 4,0' solved my problem, mark as solved.
Offline
a command i used in Windows known as 'bcdedit' i could only change the default boot loader from windows
yes, because bcdedit is for manipulating the windows boit configuration data storage (bcd) only
if at all there's bcdboot - but that's merely to setup a new entry rather than manipulating them
"Sys Vol Info" hints the esp was mounted to a regular windows - whoch is neither recommended and according to my last test not possible without tricks
as for the "esp": you seem to git confused with "esp" being a designator to where tge ESP is mounted to, not a folder name
overall several light ussues likely caused by language barrier and lack of experience - nothin i would call you out for to seek professional help - but should be improved on in the future if you want to continue dual-boot
and please: next time have a look at DeepL - it was quite hard to understand you
Offline