WIN 10 (previously dual boot) : grub cli showing before startup (hdd is 1st boot option)
I ' ve used my computer (dell) with both ubuntu and win 10 in dual boot, but I recently remove the ubuntu partition.
Since then, on every start, i've 3 times "checking media
" message shown ( with "fail" after a few seconds) ; then a grub command line shows up, I have to type "exit" in order to access the following screen :
I select the first one and only then, windows will load.
I've read about the onboard lan options that could cause the checking media message, but the 1st boot option in my BIOS is HDD.
After removing the linux partition, I've removed from the bios a related boot option, but it did not solve the problem...
I tried to add a new boot option, but did not find any available file!
Any help would be precious, I try ot to attempt anything on my own in order not to get stuck with a computer that wont even be able to launch windows...
( I've tried restore factory default
option, but no change )
boot bios grub
add a comment |
I ' ve used my computer (dell) with both ubuntu and win 10 in dual boot, but I recently remove the ubuntu partition.
Since then, on every start, i've 3 times "checking media
" message shown ( with "fail" after a few seconds) ; then a grub command line shows up, I have to type "exit" in order to access the following screen :
I select the first one and only then, windows will load.
I've read about the onboard lan options that could cause the checking media message, but the 1st boot option in my BIOS is HDD.
After removing the linux partition, I've removed from the bios a related boot option, but it did not solve the problem...
I tried to add a new boot option, but did not find any available file!
Any help would be precious, I try ot to attempt anything on my own in order not to get stuck with a computer that wont even be able to launch windows...
( I've tried restore factory default
option, but no change )
boot bios grub
add a comment |
I ' ve used my computer (dell) with both ubuntu and win 10 in dual boot, but I recently remove the ubuntu partition.
Since then, on every start, i've 3 times "checking media
" message shown ( with "fail" after a few seconds) ; then a grub command line shows up, I have to type "exit" in order to access the following screen :
I select the first one and only then, windows will load.
I've read about the onboard lan options that could cause the checking media message, but the 1st boot option in my BIOS is HDD.
After removing the linux partition, I've removed from the bios a related boot option, but it did not solve the problem...
I tried to add a new boot option, but did not find any available file!
Any help would be precious, I try ot to attempt anything on my own in order not to get stuck with a computer that wont even be able to launch windows...
( I've tried restore factory default
option, but no change )
boot bios grub
I ' ve used my computer (dell) with both ubuntu and win 10 in dual boot, but I recently remove the ubuntu partition.
Since then, on every start, i've 3 times "checking media
" message shown ( with "fail" after a few seconds) ; then a grub command line shows up, I have to type "exit" in order to access the following screen :
I select the first one and only then, windows will load.
I've read about the onboard lan options that could cause the checking media message, but the 1st boot option in my BIOS is HDD.
After removing the linux partition, I've removed from the bios a related boot option, but it did not solve the problem...
I tried to add a new boot option, but did not find any available file!
Any help would be precious, I try ot to attempt anything on my own in order not to get stuck with a computer that wont even be able to launch windows...
( I've tried restore factory default
option, but no change )
boot bios grub
boot bios grub
asked Jan 7 at 16:19
singe batteursinge batteur
1082
1082
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This Answer is adopted from Dell Support for Windows 10, the same link provides a solution for other windows' too.
You can also do it from windows
cmd
mentioned in this answer
The GPT structure deals with a lot of the problems that the Bootsect command was designed to remedy in MBR. However if you find yourself in need of repairing the EFI bootloader, you can follow the instructions below :
If you do have the Installation Media :
Insert the Media (DVD/USB) in your PC and restart.
Boot from the media.
Select Repair Your Computer.
Select Troubleshoot.
Select Advanced Options.
Choose Command Prompt from the menu :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS - EFI System Partition) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoot
If you don't have the Installation Media :
Restart your PC
Tap rapidly on the key once the PC has turned on, but before the Windows Splash Screen appears.
Please be aware this may take several attempts. The timing for this option was shortened significantly from that in Windows 7.
Select Repair your computer from the menu that appears.
Select Command Prompt from the Advanced Options tab in the Troubleshoot screen :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoo
t
The next step is the same across all the operating systems at this point :
Rebuild the BCD store
First run the command below to backup the old BCD :
ren BCD BCD.old
Now recreate it using this command :
bcdboot c:Windows /l en-us /s <boot letter>: All
Thanks, I tried, but the next start did not change, even if all the commands you gave me returned succes mesages. I then added "-" signs in front of onboard IP4 and IP6 boot options in BIOS, that make quite no sense with no explanation... and now it works well. I will mark your answer because it might have been part of the solution ! good day
– singe batteur
Jan 8 at 15:12
Good that it gave you hint, and now you have solved the problem. Good luck
– Amir-Mousavi
Jan 8 at 18:32
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%2f1391544%2fwin-10-previously-dual-boot-grub-cli-showing-before-startup-hdd-is-1st-boot%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
This Answer is adopted from Dell Support for Windows 10, the same link provides a solution for other windows' too.
You can also do it from windows
cmd
mentioned in this answer
The GPT structure deals with a lot of the problems that the Bootsect command was designed to remedy in MBR. However if you find yourself in need of repairing the EFI bootloader, you can follow the instructions below :
If you do have the Installation Media :
Insert the Media (DVD/USB) in your PC and restart.
Boot from the media.
Select Repair Your Computer.
Select Troubleshoot.
Select Advanced Options.
Choose Command Prompt from the menu :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS - EFI System Partition) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoot
If you don't have the Installation Media :
Restart your PC
Tap rapidly on the key once the PC has turned on, but before the Windows Splash Screen appears.
Please be aware this may take several attempts. The timing for this option was shortened significantly from that in Windows 7.
Select Repair your computer from the menu that appears.
Select Command Prompt from the Advanced Options tab in the Troubleshoot screen :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoo
t
The next step is the same across all the operating systems at this point :
Rebuild the BCD store
First run the command below to backup the old BCD :
ren BCD BCD.old
Now recreate it using this command :
bcdboot c:Windows /l en-us /s <boot letter>: All
Thanks, I tried, but the next start did not change, even if all the commands you gave me returned succes mesages. I then added "-" signs in front of onboard IP4 and IP6 boot options in BIOS, that make quite no sense with no explanation... and now it works well. I will mark your answer because it might have been part of the solution ! good day
– singe batteur
Jan 8 at 15:12
Good that it gave you hint, and now you have solved the problem. Good luck
– Amir-Mousavi
Jan 8 at 18:32
add a comment |
This Answer is adopted from Dell Support for Windows 10, the same link provides a solution for other windows' too.
You can also do it from windows
cmd
mentioned in this answer
The GPT structure deals with a lot of the problems that the Bootsect command was designed to remedy in MBR. However if you find yourself in need of repairing the EFI bootloader, you can follow the instructions below :
If you do have the Installation Media :
Insert the Media (DVD/USB) in your PC and restart.
Boot from the media.
Select Repair Your Computer.
Select Troubleshoot.
Select Advanced Options.
Choose Command Prompt from the menu :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS - EFI System Partition) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoot
If you don't have the Installation Media :
Restart your PC
Tap rapidly on the key once the PC has turned on, but before the Windows Splash Screen appears.
Please be aware this may take several attempts. The timing for this option was shortened significantly from that in Windows 7.
Select Repair your computer from the menu that appears.
Select Command Prompt from the Advanced Options tab in the Troubleshoot screen :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoo
t
The next step is the same across all the operating systems at this point :
Rebuild the BCD store
First run the command below to backup the old BCD :
ren BCD BCD.old
Now recreate it using this command :
bcdboot c:Windows /l en-us /s <boot letter>: All
Thanks, I tried, but the next start did not change, even if all the commands you gave me returned succes mesages. I then added "-" signs in front of onboard IP4 and IP6 boot options in BIOS, that make quite no sense with no explanation... and now it works well. I will mark your answer because it might have been part of the solution ! good day
– singe batteur
Jan 8 at 15:12
Good that it gave you hint, and now you have solved the problem. Good luck
– Amir-Mousavi
Jan 8 at 18:32
add a comment |
This Answer is adopted from Dell Support for Windows 10, the same link provides a solution for other windows' too.
You can also do it from windows
cmd
mentioned in this answer
The GPT structure deals with a lot of the problems that the Bootsect command was designed to remedy in MBR. However if you find yourself in need of repairing the EFI bootloader, you can follow the instructions below :
If you do have the Installation Media :
Insert the Media (DVD/USB) in your PC and restart.
Boot from the media.
Select Repair Your Computer.
Select Troubleshoot.
Select Advanced Options.
Choose Command Prompt from the menu :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS - EFI System Partition) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoot
If you don't have the Installation Media :
Restart your PC
Tap rapidly on the key once the PC has turned on, but before the Windows Splash Screen appears.
Please be aware this may take several attempts. The timing for this option was shortened significantly from that in Windows 7.
Select Repair your computer from the menu that appears.
Select Command Prompt from the Advanced Options tab in the Troubleshoot screen :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoo
t
The next step is the same across all the operating systems at this point :
Rebuild the BCD store
First run the command below to backup the old BCD :
ren BCD BCD.old
Now recreate it using this command :
bcdboot c:Windows /l en-us /s <boot letter>: All
This Answer is adopted from Dell Support for Windows 10, the same link provides a solution for other windows' too.
You can also do it from windows
cmd
mentioned in this answer
The GPT structure deals with a lot of the problems that the Bootsect command was designed to remedy in MBR. However if you find yourself in need of repairing the EFI bootloader, you can follow the instructions below :
If you do have the Installation Media :
Insert the Media (DVD/USB) in your PC and restart.
Boot from the media.
Select Repair Your Computer.
Select Troubleshoot.
Select Advanced Options.
Choose Command Prompt from the menu :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS - EFI System Partition) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoot
If you don't have the Installation Media :
Restart your PC
Tap rapidly on the key once the PC has turned on, but before the Windows Splash Screen appears.
Please be aware this may take several attempts. The timing for this option was shortened significantly from that in Windows 7.
Select Repair your computer from the menu that appears.
Select Command Prompt from the Advanced Options tab in the Troubleshoot screen :
Type and run the command :
diskpart
Type and run the command :
sel disk 0
Type and run the command :
list vol
Verify that the EFI partition (EPS) is using the FAT32 file system and assign a drive letter to it (Assign a letter that isn't already in use.):
Type and run the command :
sel vol <number of volume>
Type and run the command :
assign letter=<drive letter>:
Type and run the command :
exit
In order to repair the boot record :
Type and run the command :
cd /d <drive letter>:EFIMicrosoftBoot
Type and run the command :
bootrec /FixBoo
t
The next step is the same across all the operating systems at this point :
Rebuild the BCD store
First run the command below to backup the old BCD :
ren BCD BCD.old
Now recreate it using this command :
bcdboot c:Windows /l en-us /s <boot letter>: All
answered Jan 7 at 16:35
Amir-MousaviAmir-Mousavi
53148
53148
Thanks, I tried, but the next start did not change, even if all the commands you gave me returned succes mesages. I then added "-" signs in front of onboard IP4 and IP6 boot options in BIOS, that make quite no sense with no explanation... and now it works well. I will mark your answer because it might have been part of the solution ! good day
– singe batteur
Jan 8 at 15:12
Good that it gave you hint, and now you have solved the problem. Good luck
– Amir-Mousavi
Jan 8 at 18:32
add a comment |
Thanks, I tried, but the next start did not change, even if all the commands you gave me returned succes mesages. I then added "-" signs in front of onboard IP4 and IP6 boot options in BIOS, that make quite no sense with no explanation... and now it works well. I will mark your answer because it might have been part of the solution ! good day
– singe batteur
Jan 8 at 15:12
Good that it gave you hint, and now you have solved the problem. Good luck
– Amir-Mousavi
Jan 8 at 18:32
Thanks, I tried, but the next start did not change, even if all the commands you gave me returned succes mesages. I then added "-" signs in front of onboard IP4 and IP6 boot options in BIOS, that make quite no sense with no explanation... and now it works well. I will mark your answer because it might have been part of the solution ! good day
– singe batteur
Jan 8 at 15:12
Thanks, I tried, but the next start did not change, even if all the commands you gave me returned succes mesages. I then added "-" signs in front of onboard IP4 and IP6 boot options in BIOS, that make quite no sense with no explanation... and now it works well. I will mark your answer because it might have been part of the solution ! good day
– singe batteur
Jan 8 at 15:12
Good that it gave you hint, and now you have solved the problem. Good luck
– Amir-Mousavi
Jan 8 at 18:32
Good that it gave you hint, and now you have solved the problem. Good luck
– Amir-Mousavi
Jan 8 at 18:32
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%2f1391544%2fwin-10-previously-dual-boot-grub-cli-showing-before-startup-hdd-is-1st-boot%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