Where is the UEFI boot order stored?
I know the UEFI boot loaders are stored on a FAT32 partition on my (usually GPT) drive, but where is the boot order stored?
My reasoning:
- It can't be stored as part of the firmware settings, since it's specific to the storage drive, not the computer.
- It can't be in a boot-loader-specific database, because then the firmware wouldn't know how to change the order since it wouldn't know the format (but mine can).
- It doesn't seem to be in a text file or something.
So where is it?
boot uefi bootloader
asked Aug 11 '15 at 18:41
Mehrdad
14.1k36114187
|
show 5 more comments
I know the UEFI boot loaders are stored on a FAT32 partition on my (usually GPT) drive, but where is the boot order stored?
My reasoning:
- It can't be stored as part of the firmware settings, since it's specific to the storage drive, not the computer.
- It can't be in a boot-loader-specific database, because then the firmware wouldn't know how to change the order since it wouldn't know the format (but mine can).
- It doesn't seem to be in a text file or something.
So where is it?
boot uefi bootloader
asked Aug 11 '15 at 18:41
Mehrdad
14.1k36114187
4
In the firmaware of the system board Time for some reading also over here
– Moab
Aug 11 '15 at 21:56
1
@Moab: Oh what the heck. So if I move the drive to another instance of the same computer model it won't boot?
– Mehrdad
Aug 11 '15 at 22:07
It should, the firmware is a mini OS that enumerates all attached hardware before the actual boot process.
– Moab
Aug 11 '15 at 23:09
Also when you move a windows installation to different hardware, even if it is the same model exactly, widows activation may be inactivated.
– Moab
Aug 11 '15 at 23:12
1
@Moab: That doesn't make sense. If the boot entries are stored in the system board's NVRAM then that means the second computer can't find the boot entries on the drive, since they're not there. Hence I don't see how it could possibly be able to boot from the drive. And yes, I know perfectly well about Windows activation but that's irrelevant to my question here.
– Mehrdad
Aug 11 '15 at 23:13
|
show 5 more comments
I know the UEFI boot loaders are stored on a FAT32 partition on my (usually GPT) drive, but where is the boot order stored?
My reasoning:
- It can't be stored as part of the firmware settings, since it's specific to the storage drive, not the computer.
- It can't be in a boot-loader-specific database, because then the firmware wouldn't know how to change the order since it wouldn't know the format (but mine can).
- It doesn't seem to be in a text file or something.
So where is it?
boot uefi bootloader
asked Aug 11 '15 at 18:41
Mehrdad
14.1k36114187
I know the UEFI boot loaders are stored on a FAT32 partition on my (usually GPT) drive, but where is the boot order stored?
My reasoning:
- It can't be stored as part of the firmware settings, since it's specific to the storage drive, not the computer.
- It can't be in a boot-loader-specific database, because then the firmware wouldn't know how to change the order since it wouldn't know the format (but mine can).
- It doesn't seem to be in a text file or something.
So where is it?
boot uefi bootloader
boot uefi bootloader
asked Aug 11 '15 at 18:41
Mehrdad
14.1k36114187
asked Aug 11 '15 at 18:41
Mehrdad
14.1k36114187
asked Aug 11 '15 at 18:41
Mehrdad
14.1k36114187
asked Aug 11 '15 at 18:41
Mehrdad
14.1k36114187
asked Aug 11 '15 at 18:41
Mehrdad
14.1k36114187
14.1k36114187
4
In the firmaware of the system board Time for some reading also over here
– Moab
Aug 11 '15 at 21:56
1
@Moab: Oh what the heck. So if I move the drive to another instance of the same computer model it won't boot?
– Mehrdad
Aug 11 '15 at 22:07
It should, the firmware is a mini OS that enumerates all attached hardware before the actual boot process.
– Moab
Aug 11 '15 at 23:09
Also when you move a windows installation to different hardware, even if it is the same model exactly, widows activation may be inactivated.
– Moab
Aug 11 '15 at 23:12
1
@Moab: That doesn't make sense. If the boot entries are stored in the system board's NVRAM then that means the second computer can't find the boot entries on the drive, since they're not there. Hence I don't see how it could possibly be able to boot from the drive. And yes, I know perfectly well about Windows activation but that's irrelevant to my question here.
– Mehrdad
Aug 11 '15 at 23:13
|
show 5 more comments
4
In the firmaware of the system board Time for some reading also over here
– Moab
Aug 11 '15 at 21:56
1
@Moab: Oh what the heck. So if I move the drive to another instance of the same computer model it won't boot?
– Mehrdad
Aug 11 '15 at 22:07
It should, the firmware is a mini OS that enumerates all attached hardware before the actual boot process.
– Moab
Aug 11 '15 at 23:09
Also when you move a windows installation to different hardware, even if it is the same model exactly, widows activation may be inactivated.
– Moab
Aug 11 '15 at 23:12
1
@Moab: That doesn't make sense. If the boot entries are stored in the system board's NVRAM then that means the second computer can't find the boot entries on the drive, since they're not there. Hence I don't see how it could possibly be able to boot from the drive. And yes, I know perfectly well about Windows activation but that's irrelevant to my question here.
– Mehrdad
Aug 11 '15 at 23:13
4
4
In the firmaware of the system board Time for some reading also over here
– Moab
Aug 11 '15 at 21:56
In the firmaware of the system board Time for some reading also over here
– Moab
Aug 11 '15 at 21:56
1
1
@Moab: Oh what the heck. So if I move the drive to another instance of the same computer model it won't boot?
– Mehrdad
Aug 11 '15 at 22:07
@Moab: Oh what the heck. So if I move the drive to another instance of the same computer model it won't boot?
– Mehrdad
Aug 11 '15 at 22:07
It should, the firmware is a mini OS that enumerates all attached hardware before the actual boot process.
– Moab
Aug 11 '15 at 23:09
It should, the firmware is a mini OS that enumerates all attached hardware before the actual boot process.
– Moab
Aug 11 '15 at 23:09
Also when you move a windows installation to different hardware, even if it is the same model exactly, widows activation may be inactivated.
– Moab
Aug 11 '15 at 23:12
Also when you move a windows installation to different hardware, even if it is the same model exactly, widows activation may be inactivated.
– Moab
Aug 11 '15 at 23:12
1
1
@Moab: That doesn't make sense. If the boot entries are stored in the system board's NVRAM then that means the second computer can't find the boot entries on the drive, since they're not there. Hence I don't see how it could possibly be able to boot from the drive. And yes, I know perfectly well about Windows activation but that's irrelevant to my question here.
– Mehrdad
Aug 11 '15 at 23:13
@Moab: That doesn't make sense. If the boot entries are stored in the system board's NVRAM then that means the second computer can't find the boot entries on the drive, since they're not there. Hence I don't see how it could possibly be able to boot from the drive. And yes, I know perfectly well about Windows activation but that's irrelevant to my question here.
– Mehrdad
Aug 11 '15 at 23:13
|
show 5 more comments
1 Answer
1
active
oldest
votes
Moab was right, the order is stored in the pc in NVRAM.
From the link Moab shared: (https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/)
“The UEFI boot manager is a firmware policy engine that can be configured by modifying architecturally defined global NVRAM variables. The boot manager will attempt to load UEFI drivers and UEFI applications (including UEFI OS boot loaders) in an order defined by the global NVRAM variables.”
And from the linux efibootmgr manual (a utility to manipulate the boot order etc, here: https://linux.die.net/man/8/efibootmgr ):
Note: efibootmgr requires that the kernel support access to EFI non-volatile variables
answered Dec 14 '18 at 18:31
Gord Wait
262
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f955525%2fwhere-is-the-uefi-boot-order-stored%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Moab was right, the order is stored in the pc in NVRAM.
From the link Moab shared: (https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/)
“The UEFI boot manager is a firmware policy engine that can be configured by modifying architecturally defined global NVRAM variables. The boot manager will attempt to load UEFI drivers and UEFI applications (including UEFI OS boot loaders) in an order defined by the global NVRAM variables.”
And from the linux efibootmgr manual (a utility to manipulate the boot order etc, here: https://linux.die.net/man/8/efibootmgr ):
Note: efibootmgr requires that the kernel support access to EFI non-volatile variables
answered Dec 14 '18 at 18:31
Gord Wait
262
add a comment |
Moab was right, the order is stored in the pc in NVRAM.
From the link Moab shared: (https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/)
“The UEFI boot manager is a firmware policy engine that can be configured by modifying architecturally defined global NVRAM variables. The boot manager will attempt to load UEFI drivers and UEFI applications (including UEFI OS boot loaders) in an order defined by the global NVRAM variables.”
And from the linux efibootmgr manual (a utility to manipulate the boot order etc, here: https://linux.die.net/man/8/efibootmgr ):
Note: efibootmgr requires that the kernel support access to EFI non-volatile variables
answered Dec 14 '18 at 18:31
Gord Wait
262
add a comment |
Moab was right, the order is stored in the pc in NVRAM.
From the link Moab shared: (https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/)
“The UEFI boot manager is a firmware policy engine that can be configured by modifying architecturally defined global NVRAM variables. The boot manager will attempt to load UEFI drivers and UEFI applications (including UEFI OS boot loaders) in an order defined by the global NVRAM variables.”
And from the linux efibootmgr manual (a utility to manipulate the boot order etc, here: https://linux.die.net/man/8/efibootmgr ):
Note: efibootmgr requires that the kernel support access to EFI non-volatile variables
answered Dec 14 '18 at 18:31
Gord Wait
262
Moab was right, the order is stored in the pc in NVRAM.
From the link Moab shared: (https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/)
“The UEFI boot manager is a firmware policy engine that can be configured by modifying architecturally defined global NVRAM variables. The boot manager will attempt to load UEFI drivers and UEFI applications (including UEFI OS boot loaders) in an order defined by the global NVRAM variables.”
And from the linux efibootmgr manual (a utility to manipulate the boot order etc, here: https://linux.die.net/man/8/efibootmgr ):
Note: efibootmgr requires that the kernel support access to EFI non-volatile variables
answered Dec 14 '18 at 18:31
Gord Wait
262
answered Dec 14 '18 at 18:31
Gord Wait
262
answered Dec 14 '18 at 18:31
Gord Wait
262
answered Dec 14 '18 at 18:31
Gord Wait
262
262
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f955525%2fwhere-is-the-uefi-boot-order-stored%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
In the firmaware of the system board Time for some reading also over here
– Moab
Aug 11 '15 at 21:56
1
@Moab: Oh what the heck. So if I move the drive to another instance of the same computer model it won't boot?
– Mehrdad
Aug 11 '15 at 22:07
It should, the firmware is a mini OS that enumerates all attached hardware before the actual boot process.
– Moab
Aug 11 '15 at 23:09
Also when you move a windows installation to different hardware, even if it is the same model exactly, widows activation may be inactivated.
– Moab
Aug 11 '15 at 23:12
1
@Moab: That doesn't make sense. If the boot entries are stored in the system board's NVRAM then that means the second computer can't find the boot entries on the drive, since they're not there. Hence I don't see how it could possibly be able to boot from the drive. And yes, I know perfectly well about Windows activation but that's irrelevant to my question here.
– Mehrdad
Aug 11 '15 at 23:13