Grub2 has no windows 7 loader in 18.4
When I installed 18.4 beside of windows 7 and not functioning 16.4. Grub2 menu there was no Windows but two 16.4. Here are what I received from boot repair software: http://paste.ubuntu.com/p/6sJFxVTSDf/. Getting windows back is more important, but two 16.4s are not needed at all.
dual-boot grub2
add a comment |
When I installed 18.4 beside of windows 7 and not functioning 16.4. Grub2 menu there was no Windows but two 16.4. Here are what I received from boot repair software: http://paste.ubuntu.com/p/6sJFxVTSDf/. Getting windows back is more important, but two 16.4s are not needed at all.
dual-boot grub2
You have mixed BIOS/MBR and UEFI installs. UEFI & BIOS are not compatible and once you start booting in one mode, you cannot switch, or grub only boots other installs in same boot mode. You should be able to use Boot-Repair booted in BIOS/Legacy/CSM boot mode and reinstall grub-pc (BIOS version) to MBR. Normally UEFI boot uses gpt partitioned drives, but all your drives are MBR(msdos).
– oldfred
Aug 29 '18 at 20:12
Try runningsudo update-grub
when you boot 18.04, see if windows 7 boot option is added to the boot selection.
– Bernard Wei
Aug 30 '18 at 0:50
Unfortunately update-grub did not help. When 16.04 don't work in my computer the only way seems to be reinstall 18.04 on BIOS mode, if it is possible. Thanks for clearing the problem. mava
– user583532
Aug 31 '18 at 12:03
Please don’t put the solution into the question. Use the answer field below instead. askubuntu.com/help/self-answer And please do not use signature under your posts.
– Melebius
Sep 4 '18 at 12:31
I posted your solution as a community-wiki answer below. Feel free to repost it as your own answer to get the reputation related to it. Then ping me in a comment to this question, so I can delete the community-wiki answer. If you’ve got another problem (“The sound is not functioning.”), please post it as a new question with enough HW details.
– Melebius
Sep 6 '18 at 7:28
add a comment |
When I installed 18.4 beside of windows 7 and not functioning 16.4. Grub2 menu there was no Windows but two 16.4. Here are what I received from boot repair software: http://paste.ubuntu.com/p/6sJFxVTSDf/. Getting windows back is more important, but two 16.4s are not needed at all.
dual-boot grub2
When I installed 18.4 beside of windows 7 and not functioning 16.4. Grub2 menu there was no Windows but two 16.4. Here are what I received from boot repair software: http://paste.ubuntu.com/p/6sJFxVTSDf/. Getting windows back is more important, but two 16.4s are not needed at all.
dual-boot grub2
dual-boot grub2
edited Sep 6 '18 at 7:23
Melebius
4,59651839
4,59651839
asked Aug 29 '18 at 19:36
user583532user583532
13
13
You have mixed BIOS/MBR and UEFI installs. UEFI & BIOS are not compatible and once you start booting in one mode, you cannot switch, or grub only boots other installs in same boot mode. You should be able to use Boot-Repair booted in BIOS/Legacy/CSM boot mode and reinstall grub-pc (BIOS version) to MBR. Normally UEFI boot uses gpt partitioned drives, but all your drives are MBR(msdos).
– oldfred
Aug 29 '18 at 20:12
Try runningsudo update-grub
when you boot 18.04, see if windows 7 boot option is added to the boot selection.
– Bernard Wei
Aug 30 '18 at 0:50
Unfortunately update-grub did not help. When 16.04 don't work in my computer the only way seems to be reinstall 18.04 on BIOS mode, if it is possible. Thanks for clearing the problem. mava
– user583532
Aug 31 '18 at 12:03
Please don’t put the solution into the question. Use the answer field below instead. askubuntu.com/help/self-answer And please do not use signature under your posts.
– Melebius
Sep 4 '18 at 12:31
I posted your solution as a community-wiki answer below. Feel free to repost it as your own answer to get the reputation related to it. Then ping me in a comment to this question, so I can delete the community-wiki answer. If you’ve got another problem (“The sound is not functioning.”), please post it as a new question with enough HW details.
– Melebius
Sep 6 '18 at 7:28
add a comment |
You have mixed BIOS/MBR and UEFI installs. UEFI & BIOS are not compatible and once you start booting in one mode, you cannot switch, or grub only boots other installs in same boot mode. You should be able to use Boot-Repair booted in BIOS/Legacy/CSM boot mode and reinstall grub-pc (BIOS version) to MBR. Normally UEFI boot uses gpt partitioned drives, but all your drives are MBR(msdos).
– oldfred
Aug 29 '18 at 20:12
Try runningsudo update-grub
when you boot 18.04, see if windows 7 boot option is added to the boot selection.
– Bernard Wei
Aug 30 '18 at 0:50
Unfortunately update-grub did not help. When 16.04 don't work in my computer the only way seems to be reinstall 18.04 on BIOS mode, if it is possible. Thanks for clearing the problem. mava
– user583532
Aug 31 '18 at 12:03
Please don’t put the solution into the question. Use the answer field below instead. askubuntu.com/help/self-answer And please do not use signature under your posts.
– Melebius
Sep 4 '18 at 12:31
I posted your solution as a community-wiki answer below. Feel free to repost it as your own answer to get the reputation related to it. Then ping me in a comment to this question, so I can delete the community-wiki answer. If you’ve got another problem (“The sound is not functioning.”), please post it as a new question with enough HW details.
– Melebius
Sep 6 '18 at 7:28
You have mixed BIOS/MBR and UEFI installs. UEFI & BIOS are not compatible and once you start booting in one mode, you cannot switch, or grub only boots other installs in same boot mode. You should be able to use Boot-Repair booted in BIOS/Legacy/CSM boot mode and reinstall grub-pc (BIOS version) to MBR. Normally UEFI boot uses gpt partitioned drives, but all your drives are MBR(msdos).
– oldfred
Aug 29 '18 at 20:12
You have mixed BIOS/MBR and UEFI installs. UEFI & BIOS are not compatible and once you start booting in one mode, you cannot switch, or grub only boots other installs in same boot mode. You should be able to use Boot-Repair booted in BIOS/Legacy/CSM boot mode and reinstall grub-pc (BIOS version) to MBR. Normally UEFI boot uses gpt partitioned drives, but all your drives are MBR(msdos).
– oldfred
Aug 29 '18 at 20:12
Try running
sudo update-grub
when you boot 18.04, see if windows 7 boot option is added to the boot selection.– Bernard Wei
Aug 30 '18 at 0:50
Try running
sudo update-grub
when you boot 18.04, see if windows 7 boot option is added to the boot selection.– Bernard Wei
Aug 30 '18 at 0:50
Unfortunately update-grub did not help. When 16.04 don't work in my computer the only way seems to be reinstall 18.04 on BIOS mode, if it is possible. Thanks for clearing the problem. mava
– user583532
Aug 31 '18 at 12:03
Unfortunately update-grub did not help. When 16.04 don't work in my computer the only way seems to be reinstall 18.04 on BIOS mode, if it is possible. Thanks for clearing the problem. mava
– user583532
Aug 31 '18 at 12:03
Please don’t put the solution into the question. Use the answer field below instead. askubuntu.com/help/self-answer And please do not use signature under your posts.
– Melebius
Sep 4 '18 at 12:31
Please don’t put the solution into the question. Use the answer field below instead. askubuntu.com/help/self-answer And please do not use signature under your posts.
– Melebius
Sep 4 '18 at 12:31
I posted your solution as a community-wiki answer below. Feel free to repost it as your own answer to get the reputation related to it. Then ping me in a comment to this question, so I can delete the community-wiki answer. If you’ve got another problem (“The sound is not functioning.”), please post it as a new question with enough HW details.
– Melebius
Sep 6 '18 at 7:28
I posted your solution as a community-wiki answer below. Feel free to repost it as your own answer to get the reputation related to it. Then ping me in a comment to this question, so I can delete the community-wiki answer. If you’ve got another problem (“The sound is not functioning.”), please post it as a new question with enough HW details.
– Melebius
Sep 6 '18 at 7:28
add a comment |
1 Answer
1
active
oldest
votes
This answer was originally posted by the OP as a part of the question.
The solution was reinstalling 18.04, after making changes to BIOS (Legacy) on the computer. All 3rd party drivers are taken within the installation.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1070251%2fgrub2-has-no-windows-7-loader-in-18-4%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 was originally posted by the OP as a part of the question.
The solution was reinstalling 18.04, after making changes to BIOS (Legacy) on the computer. All 3rd party drivers are taken within the installation.
add a comment |
This answer was originally posted by the OP as a part of the question.
The solution was reinstalling 18.04, after making changes to BIOS (Legacy) on the computer. All 3rd party drivers are taken within the installation.
add a comment |
This answer was originally posted by the OP as a part of the question.
The solution was reinstalling 18.04, after making changes to BIOS (Legacy) on the computer. All 3rd party drivers are taken within the installation.
This answer was originally posted by the OP as a part of the question.
The solution was reinstalling 18.04, after making changes to BIOS (Legacy) on the computer. All 3rd party drivers are taken within the installation.
edited Sep 6 '18 at 7:30
community wiki
2 revs
Melebius
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1070251%2fgrub2-has-no-windows-7-loader-in-18-4%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
You have mixed BIOS/MBR and UEFI installs. UEFI & BIOS are not compatible and once you start booting in one mode, you cannot switch, or grub only boots other installs in same boot mode. You should be able to use Boot-Repair booted in BIOS/Legacy/CSM boot mode and reinstall grub-pc (BIOS version) to MBR. Normally UEFI boot uses gpt partitioned drives, but all your drives are MBR(msdos).
– oldfred
Aug 29 '18 at 20:12
Try running
sudo update-grub
when you boot 18.04, see if windows 7 boot option is added to the boot selection.– Bernard Wei
Aug 30 '18 at 0:50
Unfortunately update-grub did not help. When 16.04 don't work in my computer the only way seems to be reinstall 18.04 on BIOS mode, if it is possible. Thanks for clearing the problem. mava
– user583532
Aug 31 '18 at 12:03
Please don’t put the solution into the question. Use the answer field below instead. askubuntu.com/help/self-answer And please do not use signature under your posts.
– Melebius
Sep 4 '18 at 12:31
I posted your solution as a community-wiki answer below. Feel free to repost it as your own answer to get the reputation related to it. Then ping me in a comment to this question, so I can delete the community-wiki answer. If you’ve got another problem (“The sound is not functioning.”), please post it as a new question with enough HW details.
– Melebius
Sep 6 '18 at 7:28