Gizmos Freeware Reviews  

Go Back   Gizmo's Freeware Forum > Freeware Forum > Linux

Reply
 
Thread Tools Display Modes
Old 05. Sep 2015, 09:14 PM   #1 (permalink)
Senior Member
 
Join Date: Oct 2012
Posts: 1,028
Default Grub not booting Windows

As mentioned in my other thread, I installed Linux Mint to dual boot with Windows 10. After installing Mint I followed Jojo's article to install Grub Customizer and set Windows to boot first. To cut the chase, this is where I am having a problem - I cannot get Windows to boot, at least not from the Grub menu. Just in case I am doing something wrong, here is a screenshot of my settings in Grub Customizer...



As you can see, I have selected the only Windows entry in the dropdown list. I then hit the Save button and exited via File→Exit. When I boot my computer I am taken to a dark screen with 4 entries, i.e....
  • Linux Mint 17.2 Cinnamon 64-bit
  • Advanced options for Linux Mint Cinnimon 64-bit
  • Windows Boot Manager (on /dev/sda2) [This entry is hightlighted by default]
  • System setup
I am assuming this is the Grub menu. So far, so good I think. However, when I hit Enter (with the Windows entry already highlighted) I am taken to another dark screen with the following text...
/EndEntire
file path: /ACPI(a0341d0,0)/PCI(2,1f)/Sata(0,0,0)/HD(2,e1800,32000,094eafafeb3db04e,2,2)/File(\EFI\Microsoft\Boot)/File(bootmgfw.efi)/EndEntire
error: cannot load image.

Press any key to continue...
No matter how many times I try to boot from the Windows entry it will fail and I will return to this screen/message. I may be wrong but I believe this message means Grub had a problem either finding or executing the Windows boot loader. Am I right?

Nevertheless, if I select Setup from the menu it boots into the UEFI. Furthermore, if I then change the boot order in the UEFI so that Windows is first, my computer bypasses the Grub menu and boots into Windows directly. In other word, I can boot into Windows after all, just not from the Grub menu.

One last piece of information which may play a part in solving this issue. When I was installing Mint I basically followed the instructions in this article (minus the creation of the Home partition). Near the end of the article, the author recommended I change the "Device for boot loader installation: to /dev/sda2 which is the Windows EFI boot partition. (See graphic below). And yes, I checked and it is the same on my computer so I went along with the instructions.



Did I do bad to follow the article mentioned above? Am I screwed? Is there any way to fix this so that Grub will work as it's suppose to?

All suggestions and inputs would be much appreciated. Thanks.
Joe A.TT is offline   Reply With Quote
Old 06. Sep 2015, 01:56 AM   #2 (permalink)
Maestro di Search
 
Jojo Yee's Avatar
 
Join Date: Jul 2008
Posts: 7,845
Default

Check if you've disabled SecureBoot Joe.

The Grub menu looks good to me, except that it may prompt you that error message if it chainloads Windows from the Grub menu with SecureBoot enabled. See this reported bug which affects many users.
Jojo Yee is offline   Reply With Quote
Old 06. Sep 2015, 02:35 AM   #3 (permalink)
Senior Member
 
Join Date: Oct 2012
Posts: 1,028
Default

You are an absolute genius Jojo. Thank you, thank you.

Now me. I really don't understand how Secure Boot got turned back on, honestly. I turned it off to install Mint and don't remember touching it after that. Anyway, I am just happy the problem is solved now.
Joe A.TT is offline   Reply With Quote
Old 09. May 2016, 04:24 PM   #4 (permalink)
Member
 
Join Date: May 2016
Posts: 1
Default

I have had a similar problem in the last few weeks dual booting Linux Mint 17.3 and Windows 7. It seems that the problem was caused by a Windows 7 update and the following change was needed in the Asus UEFI BIOS. Enter the Boot section of the BIOS > enter Secure Boot then change 'Windows UEFI mode' to 'Other OS'. Save and exit the BIOS. Following this change the Windows option in the GRUB dual boot menu actually works rather than throwing up the "/EndEntire file path .... error:cannot load image" type of message. I was alerted to the problem caused by this Windows update by a recent article in the UK magazine magazine ComputerActive. The error is due to Windows, not GRUB, in this case, and is particularly associated with ASUS BIOS/motherboards (like mine) but according to the magazine article "could affect any make of PC and any version of Windows". If you are just running Windows you get an error message when you try to boot, telling you to make the above change in the BIOS. I hope this post may help other people who have recently suffered problems of this sort.
Freebooter is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



All times are GMT +1. The time now is 09:42 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.