Windows boot manager with UEFI not loading
I had windows 10 preinstalled on my system with boot type UEFI mentioned in my lenovo ideal pad boot options. I dual booted with linux mint tara which worked fine with grub loader showing both the OS entries. Later on i decided to delete linux partition which happened to be the system FAT32 partion on which efi bootloader was installed i suppose . to get rid of grub i deleted the EFI dir from windows . Now i am not able to boot into windows as it is on a boot loop keeps saying System BootOrder not found. reSet to default. Help !
windows-10 multi-boot uefi bootloader
asked Jan 12 at 9:26
user3899994user3899994
1
add a comment |
I had windows 10 preinstalled on my system with boot type UEFI mentioned in my lenovo ideal pad boot options. I dual booted with linux mint tara which worked fine with grub loader showing both the OS entries. Later on i decided to delete linux partition which happened to be the system FAT32 partion on which efi bootloader was installed i suppose . to get rid of grub i deleted the EFI dir from windows . Now i am not able to boot into windows as it is on a boot loop keeps saying System BootOrder not found. reSet to default. Help !
windows-10 multi-boot uefi bootloader
asked Jan 12 at 9:26
user3899994user3899994
1
What is the manufacturer/model of your BIOS? Do you have access to the BIOS settings?
– Kivitoe
Jan 12 at 22:12
yes i do have access to BIOS settings. Boot is set to UEFI even ,legacy support option dint work cuz hdd is gpt so no mbr. on reinstalling linux grub is showing up windows bootloader which is booting to wimdows fine. but when i remove ubuntu entry from EFI partition boot option it goes back to same problem. All i want to convey here is that UEFI loads grub well but not windows bootmanager alone.
– user3899994
Jan 13 at 6:24
add a comment |
I had windows 10 preinstalled on my system with boot type UEFI mentioned in my lenovo ideal pad boot options. I dual booted with linux mint tara which worked fine with grub loader showing both the OS entries. Later on i decided to delete linux partition which happened to be the system FAT32 partion on which efi bootloader was installed i suppose . to get rid of grub i deleted the EFI dir from windows . Now i am not able to boot into windows as it is on a boot loop keeps saying System BootOrder not found. reSet to default. Help !
windows-10 multi-boot uefi bootloader
asked Jan 12 at 9:26
user3899994user3899994
1
I had windows 10 preinstalled on my system with boot type UEFI mentioned in my lenovo ideal pad boot options. I dual booted with linux mint tara which worked fine with grub loader showing both the OS entries. Later on i decided to delete linux partition which happened to be the system FAT32 partion on which efi bootloader was installed i suppose . to get rid of grub i deleted the EFI dir from windows . Now i am not able to boot into windows as it is on a boot loop keeps saying System BootOrder not found. reSet to default. Help !
windows-10 multi-boot uefi bootloader
windows-10 multi-boot uefi bootloader
asked Jan 12 at 9:26
user3899994user3899994
1
asked Jan 12 at 9:26
user3899994user3899994
1
asked Jan 12 at 9:26
user3899994user3899994
1
asked Jan 12 at 9:26
user3899994user3899994
1
asked Jan 12 at 9:26
user3899994user3899994
1
1
What is the manufacturer/model of your BIOS? Do you have access to the BIOS settings?
– Kivitoe
Jan 12 at 22:12
yes i do have access to BIOS settings. Boot is set to UEFI even ,legacy support option dint work cuz hdd is gpt so no mbr. on reinstalling linux grub is showing up windows bootloader which is booting to wimdows fine. but when i remove ubuntu entry from EFI partition boot option it goes back to same problem. All i want to convey here is that UEFI loads grub well but not windows bootmanager alone.
– user3899994
Jan 13 at 6:24
add a comment |
What is the manufacturer/model of your BIOS? Do you have access to the BIOS settings?
– Kivitoe
Jan 12 at 22:12
yes i do have access to BIOS settings. Boot is set to UEFI even ,legacy support option dint work cuz hdd is gpt so no mbr. on reinstalling linux grub is showing up windows bootloader which is booting to wimdows fine. but when i remove ubuntu entry from EFI partition boot option it goes back to same problem. All i want to convey here is that UEFI loads grub well but not windows bootmanager alone.
– user3899994
Jan 13 at 6:24
What is the manufacturer/model of your BIOS? Do you have access to the BIOS settings?
– Kivitoe
Jan 12 at 22:12
What is the manufacturer/model of your BIOS? Do you have access to the BIOS settings?
– Kivitoe
Jan 12 at 22:12
yes i do have access to BIOS settings. Boot is set to UEFI even ,legacy support option dint work cuz hdd is gpt so no mbr. on reinstalling linux grub is showing up windows bootloader which is booting to wimdows fine. but when i remove ubuntu entry from EFI partition boot option it goes back to same problem. All i want to convey here is that UEFI loads grub well but not windows bootmanager alone.
– user3899994
Jan 13 at 6:24
yes i do have access to BIOS settings. Boot is set to UEFI even ,legacy support option dint work cuz hdd is gpt so no mbr. on reinstalling linux grub is showing up windows bootloader which is booting to wimdows fine. but when i remove ubuntu entry from EFI partition boot option it goes back to same problem. All i want to convey here is that UEFI loads grub well but not windows bootmanager alone.
– user3899994
Jan 13 at 6:24
add a comment |
1 Answer
1
active
oldest
votes
The EFI folder contained subfolders for both the Mint GRUB2 bootloader and the Windows bootloader – and you deleted both. To reinstall the Windows bootloader, use bcdboot:
Boot from the Windows 10 install CD or USB. Make sure you boot it in UEFI mode (the firmware might have two very similar boot choices).
Choose the "recovery console" option. (I don't remember what the menu item is called, exactly, but ShiftF10 should open it anyway.)
Use
dir c:,dir d:, etc. to find your main Windows partition (with theWINDOWSfolder).Once you know the correct drive, run
bcdboot c:windows(replace c: with the correct letter).
answered Jan 12 at 9:50
grawitygrawity
235k36498552
thanks for the answer but tried the option already but no luck . C : is the drive letter for me , what i have learned so far from my research on the topic . the EFI looks for the system partition with FAT32 fs for the bootloader which is D: in my case where linux resided previously and EFI entries as well. Now that i have run bcdboot i have EFI on C: and D: as well with boot and Microsoft/Boot sub folder and both have bootmgr.efi in it but still somehow EFI firmware is not able to load it. I have Hiren's BootCD win10 live USB with bootice and easybcd
– user3899994
Jan 12 at 10:08
if you know how to tweak with this please let me know
– user3899994
Jan 12 at 10:08
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%2f1393458%2fwindows-boot-manager-with-uefi-not-loading%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
The EFI folder contained subfolders for both the Mint GRUB2 bootloader and the Windows bootloader – and you deleted both. To reinstall the Windows bootloader, use bcdboot:
Boot from the Windows 10 install CD or USB. Make sure you boot it in UEFI mode (the firmware might have two very similar boot choices).
Choose the "recovery console" option. (I don't remember what the menu item is called, exactly, but ShiftF10 should open it anyway.)
Use
dir c:,dir d:, etc. to find your main Windows partition (with theWINDOWSfolder).Once you know the correct drive, run
bcdboot c:windows(replace c: with the correct letter).
answered Jan 12 at 9:50
grawitygrawity
235k36498552
thanks for the answer but tried the option already but no luck . C : is the drive letter for me , what i have learned so far from my research on the topic . the EFI looks for the system partition with FAT32 fs for the bootloader which is D: in my case where linux resided previously and EFI entries as well. Now that i have run bcdboot i have EFI on C: and D: as well with boot and Microsoft/Boot sub folder and both have bootmgr.efi in it but still somehow EFI firmware is not able to load it. I have Hiren's BootCD win10 live USB with bootice and easybcd
– user3899994
Jan 12 at 10:08
if you know how to tweak with this please let me know
– user3899994
Jan 12 at 10:08
add a comment |
The EFI folder contained subfolders for both the Mint GRUB2 bootloader and the Windows bootloader – and you deleted both. To reinstall the Windows bootloader, use bcdboot:
Boot from the Windows 10 install CD or USB. Make sure you boot it in UEFI mode (the firmware might have two very similar boot choices).
Choose the "recovery console" option. (I don't remember what the menu item is called, exactly, but ShiftF10 should open it anyway.)
Use
dir c:,dir d:, etc. to find your main Windows partition (with theWINDOWSfolder).Once you know the correct drive, run
bcdboot c:windows(replace c: with the correct letter).
answered Jan 12 at 9:50
grawitygrawity
235k36498552
thanks for the answer but tried the option already but no luck . C : is the drive letter for me , what i have learned so far from my research on the topic . the EFI looks for the system partition with FAT32 fs for the bootloader which is D: in my case where linux resided previously and EFI entries as well. Now that i have run bcdboot i have EFI on C: and D: as well with boot and Microsoft/Boot sub folder and both have bootmgr.efi in it but still somehow EFI firmware is not able to load it. I have Hiren's BootCD win10 live USB with bootice and easybcd
– user3899994
Jan 12 at 10:08
if you know how to tweak with this please let me know
– user3899994
Jan 12 at 10:08
add a comment |
The EFI folder contained subfolders for both the Mint GRUB2 bootloader and the Windows bootloader – and you deleted both. To reinstall the Windows bootloader, use bcdboot:
Boot from the Windows 10 install CD or USB. Make sure you boot it in UEFI mode (the firmware might have two very similar boot choices).
Choose the "recovery console" option. (I don't remember what the menu item is called, exactly, but ShiftF10 should open it anyway.)
Use
dir c:,dir d:, etc. to find your main Windows partition (with theWINDOWSfolder).Once you know the correct drive, run
bcdboot c:windows(replace c: with the correct letter).
answered Jan 12 at 9:50
grawitygrawity
235k36498552
The EFI folder contained subfolders for both the Mint GRUB2 bootloader and the Windows bootloader – and you deleted both. To reinstall the Windows bootloader, use bcdboot:
Boot from the Windows 10 install CD or USB. Make sure you boot it in UEFI mode (the firmware might have two very similar boot choices).
Choose the "recovery console" option. (I don't remember what the menu item is called, exactly, but ShiftF10 should open it anyway.)
Use
dir c:,dir d:, etc. to find your main Windows partition (with theWINDOWSfolder).Once you know the correct drive, run
bcdboot c:windows(replace c: with the correct letter).
answered Jan 12 at 9:50
grawitygrawity
235k36498552
answered Jan 12 at 9:50
grawitygrawity
235k36498552
answered Jan 12 at 9:50
grawitygrawity
235k36498552
answered Jan 12 at 9:50
grawitygrawity
235k36498552
235k36498552
thanks for the answer but tried the option already but no luck . C : is the drive letter for me , what i have learned so far from my research on the topic . the EFI looks for the system partition with FAT32 fs for the bootloader which is D: in my case where linux resided previously and EFI entries as well. Now that i have run bcdboot i have EFI on C: and D: as well with boot and Microsoft/Boot sub folder and both have bootmgr.efi in it but still somehow EFI firmware is not able to load it. I have Hiren's BootCD win10 live USB with bootice and easybcd
– user3899994
Jan 12 at 10:08
if you know how to tweak with this please let me know
– user3899994
Jan 12 at 10:08
add a comment |
thanks for the answer but tried the option already but no luck . C : is the drive letter for me , what i have learned so far from my research on the topic . the EFI looks for the system partition with FAT32 fs for the bootloader which is D: in my case where linux resided previously and EFI entries as well. Now that i have run bcdboot i have EFI on C: and D: as well with boot and Microsoft/Boot sub folder and both have bootmgr.efi in it but still somehow EFI firmware is not able to load it. I have Hiren's BootCD win10 live USB with bootice and easybcd
– user3899994
Jan 12 at 10:08
if you know how to tweak with this please let me know
– user3899994
Jan 12 at 10:08
thanks for the answer but tried the option already but no luck . C : is the drive letter for me , what i have learned so far from my research on the topic . the EFI looks for the system partition with FAT32 fs for the bootloader which is D: in my case where linux resided previously and EFI entries as well. Now that i have run bcdboot i have EFI on C: and D: as well with boot and Microsoft/Boot sub folder and both have bootmgr.efi in it but still somehow EFI firmware is not able to load it. I have Hiren's BootCD win10 live USB with bootice and easybcd
– user3899994
Jan 12 at 10:08
thanks for the answer but tried the option already but no luck . C : is the drive letter for me , what i have learned so far from my research on the topic . the EFI looks for the system partition with FAT32 fs for the bootloader which is D: in my case where linux resided previously and EFI entries as well. Now that i have run bcdboot i have EFI on C: and D: as well with boot and Microsoft/Boot sub folder and both have bootmgr.efi in it but still somehow EFI firmware is not able to load it. I have Hiren's BootCD win10 live USB with bootice and easybcd
– user3899994
Jan 12 at 10:08
if you know how to tweak with this please let me know
– user3899994
Jan 12 at 10:08
if you know how to tweak with this please let me know
– user3899994
Jan 12 at 10:08
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.
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%2f1393458%2fwindows-boot-manager-with-uefi-not-loading%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
What is the manufacturer/model of your BIOS? Do you have access to the BIOS settings?
– Kivitoe
Jan 12 at 22:12
yes i do have access to BIOS settings. Boot is set to UEFI even ,legacy support option dint work cuz hdd is gpt so no mbr. on reinstalling linux grub is showing up windows bootloader which is booting to wimdows fine. but when i remove ubuntu entry from EFI partition boot option it goes back to same problem. All i want to convey here is that UEFI loads grub well but not windows bootmanager alone.
– user3899994
Jan 13 at 6:24