“Failed to open/Failed to load image” messages for EFI files
I've just bought a new laptop Acer Aspire E5-575-584A with only one SSD and its comes with an Acer Linux distribution. I installed Lubuntu 16.04 fine, but when I installed Ubuntu GNOME 16.04.02 something happened. Finally I installed Ubuntu 14.04 and the error is still the same.
I am new to this and I'm confused about the UEFI-Legacy installation. I've tried a lot of things but nothing works. My laptop cannot boot from ssd, only from a Liveusb/cd. But when I try for a new installation it seems that the ssd has the Ubuntu 14.04. I've got this message when I open it and I cannot find an answer on the web :
Failed to open EFIMicrosoftBootmax64.efi - Not Found
Failed to load image EFIMicrosoftBootmax64.efi - Not Found
Failed to star MokManager : Not Found
Failed to open EFIMicrosoftBootgrub64x.efi - Not Found
Failed to load image EFIMicrosoftBootgrubx64.efi : Not Found
start_image() returned Not Found
AND afters one-two seconds the message becomes:
Failed to open EFIBootmax64.efi - Not Found
Failed to load image EFIBootmax64.efi - Not Found
Failed to star MokManager : Not Found
Failed to open EFIBootgrub64x.efi - Not Found
Failed to load image EFIBootgrubx64.efi : Not Found
start_image() returned Not Found
This is my Boot Repair log
boot grub2 uefi grub-efi
edited May 17 '18 at 7:04
Zanna
50.1k13131240
asked Apr 9 '17 at 21:10
Polem
85
add a comment |
I've just bought a new laptop Acer Aspire E5-575-584A with only one SSD and its comes with an Acer Linux distribution. I installed Lubuntu 16.04 fine, but when I installed Ubuntu GNOME 16.04.02 something happened. Finally I installed Ubuntu 14.04 and the error is still the same.
I am new to this and I'm confused about the UEFI-Legacy installation. I've tried a lot of things but nothing works. My laptop cannot boot from ssd, only from a Liveusb/cd. But when I try for a new installation it seems that the ssd has the Ubuntu 14.04. I've got this message when I open it and I cannot find an answer on the web :
Failed to open EFIMicrosoftBootmax64.efi - Not Found
Failed to load image EFIMicrosoftBootmax64.efi - Not Found
Failed to star MokManager : Not Found
Failed to open EFIMicrosoftBootgrub64x.efi - Not Found
Failed to load image EFIMicrosoftBootgrubx64.efi : Not Found
start_image() returned Not Found
AND afters one-two seconds the message becomes:
Failed to open EFIBootmax64.efi - Not Found
Failed to load image EFIBootmax64.efi - Not Found
Failed to star MokManager : Not Found
Failed to open EFIBootgrub64x.efi - Not Found
Failed to load image EFIBootgrubx64.efi : Not Found
start_image() returned Not Found
This is my Boot Repair log
boot grub2 uefi grub-efi
edited May 17 '18 at 7:04
Zanna
50.1k13131240
asked Apr 9 '17 at 21:10
Polem
85
add a comment |
I've just bought a new laptop Acer Aspire E5-575-584A with only one SSD and its comes with an Acer Linux distribution. I installed Lubuntu 16.04 fine, but when I installed Ubuntu GNOME 16.04.02 something happened. Finally I installed Ubuntu 14.04 and the error is still the same.
I am new to this and I'm confused about the UEFI-Legacy installation. I've tried a lot of things but nothing works. My laptop cannot boot from ssd, only from a Liveusb/cd. But when I try for a new installation it seems that the ssd has the Ubuntu 14.04. I've got this message when I open it and I cannot find an answer on the web :
Failed to open EFIMicrosoftBootmax64.efi - Not Found
Failed to load image EFIMicrosoftBootmax64.efi - Not Found
Failed to star MokManager : Not Found
Failed to open EFIMicrosoftBootgrub64x.efi - Not Found
Failed to load image EFIMicrosoftBootgrubx64.efi : Not Found
start_image() returned Not Found
AND afters one-two seconds the message becomes:
Failed to open EFIBootmax64.efi - Not Found
Failed to load image EFIBootmax64.efi - Not Found
Failed to star MokManager : Not Found
Failed to open EFIBootgrub64x.efi - Not Found
Failed to load image EFIBootgrubx64.efi : Not Found
start_image() returned Not Found
This is my Boot Repair log
boot grub2 uefi grub-efi
edited May 17 '18 at 7:04
Zanna
50.1k13131240
asked Apr 9 '17 at 21:10
Polem
85
I've just bought a new laptop Acer Aspire E5-575-584A with only one SSD and its comes with an Acer Linux distribution. I installed Lubuntu 16.04 fine, but when I installed Ubuntu GNOME 16.04.02 something happened. Finally I installed Ubuntu 14.04 and the error is still the same.
I am new to this and I'm confused about the UEFI-Legacy installation. I've tried a lot of things but nothing works. My laptop cannot boot from ssd, only from a Liveusb/cd. But when I try for a new installation it seems that the ssd has the Ubuntu 14.04. I've got this message when I open it and I cannot find an answer on the web :
Failed to open EFIMicrosoftBootmax64.efi - Not Found
Failed to load image EFIMicrosoftBootmax64.efi - Not Found
Failed to star MokManager : Not Found
Failed to open EFIMicrosoftBootgrub64x.efi - Not Found
Failed to load image EFIMicrosoftBootgrubx64.efi : Not Found
start_image() returned Not Found
AND afters one-two seconds the message becomes:
Failed to open EFIBootmax64.efi - Not Found
Failed to load image EFIBootmax64.efi - Not Found
Failed to star MokManager : Not Found
Failed to open EFIBootgrub64x.efi - Not Found
Failed to load image EFIBootgrubx64.efi : Not Found
start_image() returned Not Found
This is my Boot Repair log
boot grub2 uefi grub-efi
boot grub2 uefi grub-efi
edited May 17 '18 at 7:04
Zanna
50.1k13131240
asked Apr 9 '17 at 21:10
Polem
85
edited May 17 '18 at 7:04
Zanna
50.1k13131240
asked Apr 9 '17 at 21:10
Polem
85
edited May 17 '18 at 7:04
Zanna
50.1k13131240
edited May 17 '18 at 7:04
Zanna
50.1k13131240
edited May 17 '18 at 7:04
Zanna
50.1k13131240
50.1k13131240
asked Apr 9 '17 at 21:10
Polem
85
asked Apr 9 '17 at 21:10
Polem
85
asked Apr 9 '17 at 21:10
Polem
85
85
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Your computer uses EFI firmware, and the Boot Repair output looks like the computer came with a Windows installation that you deleted and replaced with Ubuntu. I know you say it came with "an Acer Linux distribution," which is why I'm leading with what your Boot Repair output suggests, since the two are at odds. My suspicion is that, for whatever reason (maybe a defective firmware), Acer installed their Linux boot loader in a way that makes it look like the Windows boot loader, and the computer is still trying to boot via that boot loader. Other changes must have deleted follow-up boot loader programs, resulting in the error messages you're seeing.
I can think of several ways to fix this problem, but none of them is guaranteed to work, so you may need to try multiple approaches. I'll describe a couple that are most likely to work....
Method 1: Boot Repair
- Boot your Ubuntu installation medium in "try before installing" mode.
- Launch Boot Repair.
- Click the Advanced Options item.
- Select the "Backup and Rename Windows EFI Files" option.
- Click Apply to run Boot Repair.
Method 2: rEFInd
- Download the CD-R or USB flash drive version of my rEFInd boot manager from the links here.
- Create a medium using the image you downloaded.
- Boot into your firmware setup utility and disable Secure Boot. Unfortunately, how you do this varies from one system to another. See this page of mine for several examples of how to do it.
- Boot with the rEFInd medium.
- In rEFInd, select a Linux kernel image (
Boot bootvmlinuz...) to boot your current Ubuntu installation. - Install rEFInd by using the Debian package or PPA.
- Reboot. If rEFInd comes up, you should be able to boot Ubuntu and you'll be good. If not....
- Boot with the rEFInd medium you prepared earlier, and boot to Ubuntu, as in step #5.
- Open a terminal and type
sudo mvrefind /boot/efi/EFI/ubuntu /boot/efi/EFI/Microsoft/Boot. - Reboot. With any luck, rEFInd will appear.
You may optionally re-enable Secure Boot, and you may want to delete redundant boot loader files from /boot/efi/EFI/*/ directories or edit refind.conf in /boot/efi/EFI/refind/ or /boot/efi/EFI/Microsoft/Boot to uncomment and add boot loaders to the dont_scan_dirs or dont_scan_files lines.
answered Apr 10 '17 at 14:02
Rod Smith
35.1k43870
add a comment |
It happened to me when trying to boot from live USB with Ubuntu LTS 18.10 on a Huawei Matebook Pro.
What worked for me is to just disable secure boot on bios.
answered Dec 28 '18 at 21:41
Eduardo Chico
31
New contributor
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f903005%2ffailed-to-open-failed-to-load-image-messages-for-efi-files%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
Your computer uses EFI firmware, and the Boot Repair output looks like the computer came with a Windows installation that you deleted and replaced with Ubuntu. I know you say it came with "an Acer Linux distribution," which is why I'm leading with what your Boot Repair output suggests, since the two are at odds. My suspicion is that, for whatever reason (maybe a defective firmware), Acer installed their Linux boot loader in a way that makes it look like the Windows boot loader, and the computer is still trying to boot via that boot loader. Other changes must have deleted follow-up boot loader programs, resulting in the error messages you're seeing.
I can think of several ways to fix this problem, but none of them is guaranteed to work, so you may need to try multiple approaches. I'll describe a couple that are most likely to work....
Method 1: Boot Repair
- Boot your Ubuntu installation medium in "try before installing" mode.
- Launch Boot Repair.
- Click the Advanced Options item.
- Select the "Backup and Rename Windows EFI Files" option.
- Click Apply to run Boot Repair.
Method 2: rEFInd
- Download the CD-R or USB flash drive version of my rEFInd boot manager from the links here.
- Create a medium using the image you downloaded.
- Boot into your firmware setup utility and disable Secure Boot. Unfortunately, how you do this varies from one system to another. See this page of mine for several examples of how to do it.
- Boot with the rEFInd medium.
- In rEFInd, select a Linux kernel image (
Boot bootvmlinuz...) to boot your current Ubuntu installation. - Install rEFInd by using the Debian package or PPA.
- Reboot. If rEFInd comes up, you should be able to boot Ubuntu and you'll be good. If not....
- Boot with the rEFInd medium you prepared earlier, and boot to Ubuntu, as in step #5.
- Open a terminal and type
sudo mvrefind /boot/efi/EFI/ubuntu /boot/efi/EFI/Microsoft/Boot. - Reboot. With any luck, rEFInd will appear.
You may optionally re-enable Secure Boot, and you may want to delete redundant boot loader files from /boot/efi/EFI/*/ directories or edit refind.conf in /boot/efi/EFI/refind/ or /boot/efi/EFI/Microsoft/Boot to uncomment and add boot loaders to the dont_scan_dirs or dont_scan_files lines.
answered Apr 10 '17 at 14:02
Rod Smith
35.1k43870
add a comment |
Your computer uses EFI firmware, and the Boot Repair output looks like the computer came with a Windows installation that you deleted and replaced with Ubuntu. I know you say it came with "an Acer Linux distribution," which is why I'm leading with what your Boot Repair output suggests, since the two are at odds. My suspicion is that, for whatever reason (maybe a defective firmware), Acer installed their Linux boot loader in a way that makes it look like the Windows boot loader, and the computer is still trying to boot via that boot loader. Other changes must have deleted follow-up boot loader programs, resulting in the error messages you're seeing.
I can think of several ways to fix this problem, but none of them is guaranteed to work, so you may need to try multiple approaches. I'll describe a couple that are most likely to work....
Method 1: Boot Repair
- Boot your Ubuntu installation medium in "try before installing" mode.
- Launch Boot Repair.
- Click the Advanced Options item.
- Select the "Backup and Rename Windows EFI Files" option.
- Click Apply to run Boot Repair.
Method 2: rEFInd
- Download the CD-R or USB flash drive version of my rEFInd boot manager from the links here.
- Create a medium using the image you downloaded.
- Boot into your firmware setup utility and disable Secure Boot. Unfortunately, how you do this varies from one system to another. See this page of mine for several examples of how to do it.
- Boot with the rEFInd medium.
- In rEFInd, select a Linux kernel image (
Boot bootvmlinuz...) to boot your current Ubuntu installation. - Install rEFInd by using the Debian package or PPA.
- Reboot. If rEFInd comes up, you should be able to boot Ubuntu and you'll be good. If not....
- Boot with the rEFInd medium you prepared earlier, and boot to Ubuntu, as in step #5.
- Open a terminal and type
sudo mvrefind /boot/efi/EFI/ubuntu /boot/efi/EFI/Microsoft/Boot. - Reboot. With any luck, rEFInd will appear.
You may optionally re-enable Secure Boot, and you may want to delete redundant boot loader files from /boot/efi/EFI/*/ directories or edit refind.conf in /boot/efi/EFI/refind/ or /boot/efi/EFI/Microsoft/Boot to uncomment and add boot loaders to the dont_scan_dirs or dont_scan_files lines.
answered Apr 10 '17 at 14:02
Rod Smith
35.1k43870
add a comment |
Your computer uses EFI firmware, and the Boot Repair output looks like the computer came with a Windows installation that you deleted and replaced with Ubuntu. I know you say it came with "an Acer Linux distribution," which is why I'm leading with what your Boot Repair output suggests, since the two are at odds. My suspicion is that, for whatever reason (maybe a defective firmware), Acer installed their Linux boot loader in a way that makes it look like the Windows boot loader, and the computer is still trying to boot via that boot loader. Other changes must have deleted follow-up boot loader programs, resulting in the error messages you're seeing.
I can think of several ways to fix this problem, but none of them is guaranteed to work, so you may need to try multiple approaches. I'll describe a couple that are most likely to work....
Method 1: Boot Repair
- Boot your Ubuntu installation medium in "try before installing" mode.
- Launch Boot Repair.
- Click the Advanced Options item.
- Select the "Backup and Rename Windows EFI Files" option.
- Click Apply to run Boot Repair.
Method 2: rEFInd
- Download the CD-R or USB flash drive version of my rEFInd boot manager from the links here.
- Create a medium using the image you downloaded.
- Boot into your firmware setup utility and disable Secure Boot. Unfortunately, how you do this varies from one system to another. See this page of mine for several examples of how to do it.
- Boot with the rEFInd medium.
- In rEFInd, select a Linux kernel image (
Boot bootvmlinuz...) to boot your current Ubuntu installation. - Install rEFInd by using the Debian package or PPA.
- Reboot. If rEFInd comes up, you should be able to boot Ubuntu and you'll be good. If not....
- Boot with the rEFInd medium you prepared earlier, and boot to Ubuntu, as in step #5.
- Open a terminal and type
sudo mvrefind /boot/efi/EFI/ubuntu /boot/efi/EFI/Microsoft/Boot. - Reboot. With any luck, rEFInd will appear.
You may optionally re-enable Secure Boot, and you may want to delete redundant boot loader files from /boot/efi/EFI/*/ directories or edit refind.conf in /boot/efi/EFI/refind/ or /boot/efi/EFI/Microsoft/Boot to uncomment and add boot loaders to the dont_scan_dirs or dont_scan_files lines.
answered Apr 10 '17 at 14:02
Rod Smith
35.1k43870
Your computer uses EFI firmware, and the Boot Repair output looks like the computer came with a Windows installation that you deleted and replaced with Ubuntu. I know you say it came with "an Acer Linux distribution," which is why I'm leading with what your Boot Repair output suggests, since the two are at odds. My suspicion is that, for whatever reason (maybe a defective firmware), Acer installed their Linux boot loader in a way that makes it look like the Windows boot loader, and the computer is still trying to boot via that boot loader. Other changes must have deleted follow-up boot loader programs, resulting in the error messages you're seeing.
I can think of several ways to fix this problem, but none of them is guaranteed to work, so you may need to try multiple approaches. I'll describe a couple that are most likely to work....
Method 1: Boot Repair
- Boot your Ubuntu installation medium in "try before installing" mode.
- Launch Boot Repair.
- Click the Advanced Options item.
- Select the "Backup and Rename Windows EFI Files" option.
- Click Apply to run Boot Repair.
Method 2: rEFInd
- Download the CD-R or USB flash drive version of my rEFInd boot manager from the links here.
- Create a medium using the image you downloaded.
- Boot into your firmware setup utility and disable Secure Boot. Unfortunately, how you do this varies from one system to another. See this page of mine for several examples of how to do it.
- Boot with the rEFInd medium.
- In rEFInd, select a Linux kernel image (
Boot bootvmlinuz...) to boot your current Ubuntu installation. - Install rEFInd by using the Debian package or PPA.
- Reboot. If rEFInd comes up, you should be able to boot Ubuntu and you'll be good. If not....
- Boot with the rEFInd medium you prepared earlier, and boot to Ubuntu, as in step #5.
- Open a terminal and type
sudo mvrefind /boot/efi/EFI/ubuntu /boot/efi/EFI/Microsoft/Boot. - Reboot. With any luck, rEFInd will appear.
You may optionally re-enable Secure Boot, and you may want to delete redundant boot loader files from /boot/efi/EFI/*/ directories or edit refind.conf in /boot/efi/EFI/refind/ or /boot/efi/EFI/Microsoft/Boot to uncomment and add boot loaders to the dont_scan_dirs or dont_scan_files lines.
answered Apr 10 '17 at 14:02
Rod Smith
35.1k43870
answered Apr 10 '17 at 14:02
Rod Smith
35.1k43870
answered Apr 10 '17 at 14:02
Rod Smith
35.1k43870
answered Apr 10 '17 at 14:02
Rod Smith
35.1k43870
35.1k43870
add a comment |
add a comment |
It happened to me when trying to boot from live USB with Ubuntu LTS 18.10 on a Huawei Matebook Pro.
What worked for me is to just disable secure boot on bios.
answered Dec 28 '18 at 21:41
Eduardo Chico
31
New contributor
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
It happened to me when trying to boot from live USB with Ubuntu LTS 18.10 on a Huawei Matebook Pro.
What worked for me is to just disable secure boot on bios.
answered Dec 28 '18 at 21:41
Eduardo Chico
31
New contributor
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
It happened to me when trying to boot from live USB with Ubuntu LTS 18.10 on a Huawei Matebook Pro.
What worked for me is to just disable secure boot on bios.
answered Dec 28 '18 at 21:41
Eduardo Chico
31
New contributor
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
It happened to me when trying to boot from live USB with Ubuntu LTS 18.10 on a Huawei Matebook Pro.
What worked for me is to just disable secure boot on bios.
answered Dec 28 '18 at 21:41
Eduardo Chico
31
New contributor
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 28 '18 at 21:41
Eduardo Chico
31
New contributor
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Dec 28 '18 at 21:41
Eduardo Chico
31
answered Dec 28 '18 at 21:41
Eduardo Chico
31
31
New contributor
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Eduardo Chico is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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.
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%2faskubuntu.com%2fquestions%2f903005%2ffailed-to-open-failed-to-load-image-messages-for-efi-files%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
