# Revision history [back]

Sounds to me like the the boot-order in NVRAM has reverted to Windows by default. This happens sometimes on my HP laptop as well. The simplest solution is to boot Fedora and then:

$efibootmgr BootCurrent: 0001 BootOrder: 0002,0001,2001,2002,2004 Boot0000* USB Hard Drive (UEFI) - Samsung Flash Drive Boot0001* Fedora Boot0002* Windows Boot Manager  You might see some extra items. On my computer, BootCurrent is 0001, which is a reference to Boot0001, which is the Fedora entry. The Boot0002 entry is for Windows. Note though that the BootOrder says Windows first, Fedora second. You probably see that too but maybe with different number assignments. To change the order, using my numbers as an example: $ sudo efibootmgr --bootorder 1,2


And confirm it.

$efibootmgr BootCurrent: 0001 BootOrder: 0001,0002 Boot0000* USB Hard Drive (UEFI) - Samsung Flash Drive Boot0001* Fedora Boot0002* Windows Boot Manager  Now the order is 0001 (Fedora) first, and 0002 (Windows) second. Note, you can either include or exclude the prefix zeros. All that normally matters is what's first in the bootorder because as long as that is a working entry, that's what boots. So what's the point of having something listed second? It's just a fallback. Now if in your case the BootOrder is already correct but it still boots Windows first, that means something else is wrong. So the first step to figure that out is for you to post what you get for efibootmgr -v but for now I'm just gonna assume this is that the BootOrder switched back to Windows being first. Sounds to me like the the boot-order in NVRAM has reverted to Windows by default. This happens sometimes on my HP laptop as well. The simplest solution is to boot Fedora and then:run efibootmgr which looks like this: $ efibootmgr
BootCurrent: 0001
BootOrder: 0002,0001,2001,2002,2004
Boot0000* USB Hard Drive (UEFI) - Samsung Flash Drive
Boot0001* Fedora
Boot0002* Windows Boot Manager


You might see some extra items. On my computer, BootCurrent is 0001, which is a reference to Boot0001, which is the Fedora entry. The Boot0002 entry is for Windows. Note though that the BootOrder says Windows first, Fedora second. You probably see that too but maybe with different number assignments. To change the order, using my numbers as an example:

$sudo efibootmgr --bootorder 1,2  And confirm it. $ efibootmgr
BootCurrent: 0001
BootOrder: 0001,0002
Boot0000* USB Hard Drive (UEFI) - Samsung Flash Drive
Boot0001* Fedora
Boot0002* Windows Boot Manager


Now the order is 0001 (Fedora) first, and 0002 (Windows) second. Note, you can either include or exclude the prefix zeros. All that normally matters is what's first in the bootorder because as long as that is a working entry, that's what boots. So what's the point of having something listed second? It's just a fallback. Now if in your case the BootOrder is already correct but it still boots Windows first, that means something else is wrong. So the first step to figure that out is for you to post what you get for efibootmgr -v but for now I'm just gonna assume this is that the BootOrder switched back to Windows being first.

Sounds to me like the the boot-order in NVRAM has reverted to Windows by default. This happens sometimes on my HP laptop as well. The simplest solution is to boot Fedora and run efibootmgr which looks like this:

$efibootmgr BootCurrent: 0001 BootOrder: 0002,0001,2001,2002,2004 Boot0000* USB Hard Drive (UEFI) - Samsung Flash Drive Boot0001* Fedora Boot0002* Windows Boot Manager  You might see some extra items. On my computer, BootCurrent is 0001, which is a reference to Boot0001, which is the Fedora entry. The Boot0002 entry is for Windows. Note though that the BootOrder says Windows first, Fedora second. You probably see that too but maybe with different number assignments. To change the order, using my numbers as an example: $ sudo efibootmgr --bootorder 1,2


And confirm it.

\$ efibootmgr
BootCurrent: 0001
BootOrder: 0001,0002
Boot0000* USB Hard Drive (UEFI) - Samsung Flash Drive
Boot0001* Fedora
Boot0002* Windows Boot Manager


Now the order is 0001 (Fedora) first, and 0002 (Windows) second. Note, you can either include or exclude the prefix zeros. And you don't even have to include each boot entry.

All that normally matters is what's first in the bootorder because as long as that is a working entry, that's what boots. So what's the point of having something listed second? second and third? It's just a fallback. Now if in your case the BootOrder is already correct but it still boots Windows first, that means something else is wrong. So the The first step to figure that out is for you to post what you get for efibootmgr -v but for now I'm just gonna going to assume this is that the BootOrder switched back to Windows being first.