the grub-efi-amd64-signed package failed to install into target error
I'm installing Ubuntu 18.04 dual boot beside windows 10. I got the following error
the grub-efi-amd64-signed package failed to install into target
And the machine doesn't boot. Note that my computer doesn't support UEFI. Thanks for your helps ...
system-installation
asked Feb 3 at 21:43
fedorafedora
225
add a comment |
I'm installing Ubuntu 18.04 dual boot beside windows 10. I got the following error
the grub-efi-amd64-signed package failed to install into target
And the machine doesn't boot. Note that my computer doesn't support UEFI. Thanks for your helps ...
system-installation
asked Feb 3 at 21:43
fedorafedora
225
Have you created an EFI partition?
– JerareYoshi
Feb 3 at 22:04
It must support UEFI, otherwise it would not be trying to install the UEFI version of grub. What brand/model system? If within last 5 years, it will be UEFI hardware. And vendors are required to install Windows in UEFI boot mode, but users can install in the now 35 year old BIOS with MBR partitions. Post this above from Ubuntu installer in live mode, terminal:sudo parted -l
– oldfred
Feb 3 at 22:26
add a comment |
I'm installing Ubuntu 18.04 dual boot beside windows 10. I got the following error
the grub-efi-amd64-signed package failed to install into target
And the machine doesn't boot. Note that my computer doesn't support UEFI. Thanks for your helps ...
system-installation
asked Feb 3 at 21:43
fedorafedora
225
I'm installing Ubuntu 18.04 dual boot beside windows 10. I got the following error
the grub-efi-amd64-signed package failed to install into target
And the machine doesn't boot. Note that my computer doesn't support UEFI. Thanks for your helps ...
system-installation
system-installation
asked Feb 3 at 21:43
fedorafedora
225
asked Feb 3 at 21:43
fedorafedora
225
asked Feb 3 at 21:43
fedorafedora
225
asked Feb 3 at 21:43
fedorafedora
225
asked Feb 3 at 21:43
fedorafedora
225
225
Have you created an EFI partition?
– JerareYoshi
Feb 3 at 22:04
It must support UEFI, otherwise it would not be trying to install the UEFI version of grub. What brand/model system? If within last 5 years, it will be UEFI hardware. And vendors are required to install Windows in UEFI boot mode, but users can install in the now 35 year old BIOS with MBR partitions. Post this above from Ubuntu installer in live mode, terminal:sudo parted -l
– oldfred
Feb 3 at 22:26
add a comment |
Have you created an EFI partition?
– JerareYoshi
Feb 3 at 22:04
It must support UEFI, otherwise it would not be trying to install the UEFI version of grub. What brand/model system? If within last 5 years, it will be UEFI hardware. And vendors are required to install Windows in UEFI boot mode, but users can install in the now 35 year old BIOS with MBR partitions. Post this above from Ubuntu installer in live mode, terminal:sudo parted -l
– oldfred
Feb 3 at 22:26
Have you created an EFI partition?
– JerareYoshi
Feb 3 at 22:04
Have you created an EFI partition?
– JerareYoshi
Feb 3 at 22:04
It must support UEFI, otherwise it would not be trying to install the UEFI version of grub. What brand/model system? If within last 5 years, it will be UEFI hardware. And vendors are required to install Windows in UEFI boot mode, but users can install in the now 35 year old BIOS with MBR partitions. Post this above from Ubuntu installer in live mode, terminal:
sudo parted -l– oldfred
Feb 3 at 22:26
It must support UEFI, otherwise it would not be trying to install the UEFI version of grub. What brand/model system? If within last 5 years, it will be UEFI hardware. And vendors are required to install Windows in UEFI boot mode, but users can install in the now 35 year old BIOS with MBR partitions. Post this above from Ubuntu installer in live mode, terminal:
sudo parted -l– oldfred
Feb 3 at 22:26
add a comment |
2 Answers
2
active
oldest
votes
First, use a Windows 10 USB stick to fix your partitions(known as "Fix the MBR" or Startup Repair). Make sure you have an EFI partition working with no problems. There are several tutorials on Google to clean and create a new EFI partition from the W10 USB CMD promtp.
Then, boot the Ubuntu USB, and select manual installation:
Create the followings partitions: /, SWAP, /home
Click to Install Now, and apply the changes.
Long time ago I had this issue, googling and doing this solved my problem.
Hope to get good news.
answered Feb 6 at 8:32
RonaldRonald
1681211
add a comment |
Here you go, The output of gparted -l command:
answered Feb 4 at 11:56
fedorafedora
225
Did you deactivate secure boot?
– Ronald
Feb 4 at 12:04
Yes, I disabled this feature.
– fedora
Feb 4 at 18:34
Is there anyone to help me solve this issue?
– fedora
Feb 5 at 9:00
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%2f1115368%2fthe-grub-efi-amd64-signed-package-failed-to-install-into-target-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
First, use a Windows 10 USB stick to fix your partitions(known as "Fix the MBR" or Startup Repair). Make sure you have an EFI partition working with no problems. There are several tutorials on Google to clean and create a new EFI partition from the W10 USB CMD promtp.
Then, boot the Ubuntu USB, and select manual installation:
Create the followings partitions: /, SWAP, /home
Click to Install Now, and apply the changes.
Long time ago I had this issue, googling and doing this solved my problem.
Hope to get good news.
answered Feb 6 at 8:32
RonaldRonald
1681211
add a comment |
First, use a Windows 10 USB stick to fix your partitions(known as "Fix the MBR" or Startup Repair). Make sure you have an EFI partition working with no problems. There are several tutorials on Google to clean and create a new EFI partition from the W10 USB CMD promtp.
Then, boot the Ubuntu USB, and select manual installation:
Create the followings partitions: /, SWAP, /home
Click to Install Now, and apply the changes.
Long time ago I had this issue, googling and doing this solved my problem.
Hope to get good news.
answered Feb 6 at 8:32
RonaldRonald
1681211
add a comment |
First, use a Windows 10 USB stick to fix your partitions(known as "Fix the MBR" or Startup Repair). Make sure you have an EFI partition working with no problems. There are several tutorials on Google to clean and create a new EFI partition from the W10 USB CMD promtp.
Then, boot the Ubuntu USB, and select manual installation:
Create the followings partitions: /, SWAP, /home
Click to Install Now, and apply the changes.
Long time ago I had this issue, googling and doing this solved my problem.
Hope to get good news.
answered Feb 6 at 8:32
RonaldRonald
1681211
First, use a Windows 10 USB stick to fix your partitions(known as "Fix the MBR" or Startup Repair). Make sure you have an EFI partition working with no problems. There are several tutorials on Google to clean and create a new EFI partition from the W10 USB CMD promtp.
Then, boot the Ubuntu USB, and select manual installation:
Create the followings partitions: /, SWAP, /home
Click to Install Now, and apply the changes.
Long time ago I had this issue, googling and doing this solved my problem.
Hope to get good news.
answered Feb 6 at 8:32
RonaldRonald
1681211
answered Feb 6 at 8:32
RonaldRonald
1681211
answered Feb 6 at 8:32
RonaldRonald
1681211
answered Feb 6 at 8:32
RonaldRonald
1681211
1681211
add a comment |
add a comment |
Here you go, The output of gparted -l command:
answered Feb 4 at 11:56
fedorafedora
225
Did you deactivate secure boot?
– Ronald
Feb 4 at 12:04
Yes, I disabled this feature.
– fedora
Feb 4 at 18:34
Is there anyone to help me solve this issue?
– fedora
Feb 5 at 9:00
add a comment |
Here you go, The output of gparted -l command:
answered Feb 4 at 11:56
fedorafedora
225
Did you deactivate secure boot?
– Ronald
Feb 4 at 12:04
Yes, I disabled this feature.
– fedora
Feb 4 at 18:34
Is there anyone to help me solve this issue?
– fedora
Feb 5 at 9:00
add a comment |
Here you go, The output of gparted -l command:
answered Feb 4 at 11:56
fedorafedora
225
Here you go, The output of gparted -l command:
answered Feb 4 at 11:56
fedorafedora
225
edited Feb 4 at 12:01
answered Feb 4 at 11:56
fedorafedora
225
answered Feb 4 at 11:56
fedorafedora
225
answered Feb 4 at 11:56
fedorafedora
225
225
Did you deactivate secure boot?
– Ronald
Feb 4 at 12:04
Yes, I disabled this feature.
– fedora
Feb 4 at 18:34
Is there anyone to help me solve this issue?
– fedora
Feb 5 at 9:00
add a comment |
Did you deactivate secure boot?
– Ronald
Feb 4 at 12:04
Yes, I disabled this feature.
– fedora
Feb 4 at 18:34
Is there anyone to help me solve this issue?
– fedora
Feb 5 at 9:00
Did you deactivate secure boot?
– Ronald
Feb 4 at 12:04
Did you deactivate secure boot?
– Ronald
Feb 4 at 12:04
Yes, I disabled this feature.
– fedora
Feb 4 at 18:34
Yes, I disabled this feature.
– fedora
Feb 4 at 18:34
Is there anyone to help me solve this issue?
– fedora
Feb 5 at 9:00
Is there anyone to help me solve this issue?
– fedora
Feb 5 at 9:00
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%2f1115368%2fthe-grub-efi-amd64-signed-package-failed-to-install-into-target-error%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
Have you created an EFI partition?
– JerareYoshi
Feb 3 at 22:04
It must support UEFI, otherwise it would not be trying to install the UEFI version of grub. What brand/model system? If within last 5 years, it will be UEFI hardware. And vendors are required to install Windows in UEFI boot mode, but users can install in the now 35 year old BIOS with MBR partitions. Post this above from Ubuntu installer in live mode, terminal:
sudo parted -l– oldfred
Feb 3 at 22:26