d-one Posted March 30, 2016 Share Posted March 30, 2016 Hello. I'm having some problems trying to get my bootloader to boot windows from the boot menu, my first few attempts to get my Hackintosh up and running was to try dual boot from the same drive, then I gave up and decided to have a separate SSD drive for Windows 10 and another for OSX. So, from the bootloader OSX loads fine, but Windows either can't find the drive or just restarts the machine, I'm guessing the bootloader somehow is not getting the correct SSD path to boot windows...? Selecting "windows system reserved" - Reboots the PC. Selecting "Win10 SSD" - Reboots the PC. Selecting "Mac OSX"- Boots into OSX just fine. However if i press F11 to select boot drive before the boot loader boots and select my windows drive then windows boots just fine, so the issue is with Clover. Here is my bootlog.log from Clover http://pastebin.com/8N1QUBgX Terminal DiskUtil list: Disk Utility info: HELP? Link to comment Share on other sites More sharing options...
Allan Posted March 30, 2016 Share Posted March 30, 2016 Using the search bar, this guide can help you: [Guide] Dual-boot with Windows 10 and Clover - Legacy or UEFI This video is very interessant: Hackintosh - Windows 10 Dual Boot - Step by Step 1 Link to comment Share on other sites More sharing options...
d-one Posted March 31, 2016 Author Share Posted March 31, 2016 But thats a guide to install, i already have everything installed. Do i really need to reinstall? thats a major pain in between the buttocks Link to comment Share on other sites More sharing options...
Allan Posted March 31, 2016 Share Posted March 31, 2016 In fusion71au's topic, you can see how manage the folders for Windows in UEFI mode. And in the video, if you have installed Windows in that way - ok. But you can check if your BIOS settings are similar. So, your job is just read and watch, will take 10-15 min...if you want of course! Link to comment Share on other sites More sharing options...
fusion71au Posted March 31, 2016 Share Posted March 31, 2016 @d-one, If you want to keep your legacy Windows installation on disk0 untouched, you can leave the Windows bootloader in charge of booting Windows. When you want to boot into OSX, you can chainload to Clover/Chameleon on disk1 - see Using EasyBCD to Chainload Chameleon or Clover from the legacy Windows Bootloader Good Luck! Link to comment Share on other sites More sharing options...
phantom101 Posted March 31, 2016 Share Posted March 31, 2016 Similar issue. I write it here: In this week I installed Mac OSX El Capitan on my Hackintosh without problems. Everything works fine. Yesterday i tried to install Windows too on another SSD.I've unplug the SSD with OSX and Install Windows successfully. But now in my bootloader I have 4 Windows options:1. Boot Windows from Legacy Hd22. Boot Windows from Legacy Hd43. Boot Windows from Recovery4. (Another one that I don't remember with a strange (?) icon) None of this works. But if I try to boot windows from BIOS, everythings works fine. Why? Should I install bootloader again? Should I change something from BIOS? If you find a solution, let me know. Link to comment Share on other sites More sharing options...
d-one Posted April 1, 2016 Author Share Posted April 1, 2016 In fusion71au's topic, you can see how manage the folders for Windows in UEFI mode. And in the video, if you have installed Windows in that way - ok. But you can check if your BIOS settings are similar. So, your job is just read and watch, will take 10-15 min...if you want of course! I can't manage a folder a don't have, i don't think my issue has anything to do with my bios settings, but maybe I'm just being dumb here. So far from what i've read my problem was the fact that i installed windows on a MBR formatted drive instead of a GPT, doing so i have no EFI on my windows drive and therefore clover boot loader can't boot it. Of course i can just press F11 at startup and chose my windows drive and windows starts just fine, instead of booting into clover, but for simplicity i rather have 1 boot loader for everything. @d-one, If you want to keep your legacy Windows installation on disk0 untouched, you can leave the Windows bootloader in charge of booting Windows. When you want to boot into OSX, you can chainload to Clover/Chameleon on disk1 - see Using EasyBCD to Chainload Chameleon or Clover from the legacy Windows Bootloader Good Luck! Thanks for your reply. Well, that would work but if i understood correctly its basically the same as pressing F11 to select boot drive at startup, it just ask's me what to load automatically, só i basically end up with 2 "boot loaders". Similar issue. I write it here: In this week I installed Mac OSX El Capitan on my Hackintosh without problems. Everything works fine. Yesterday i tried to install Windows too on another SSD. I've unplug the SSD with OSX and Install Windows successfully. But now in my bootloader I have 4 Windows options: 1. Boot Windows from Legacy Hd2 2. Boot Windows from Legacy Hd4 3. Boot Windows from Recovery 4. (Another one that I don't remember with a strange (?) icon) None of this works. But if I try to boot windows from BIOS, everythings works fine. Why? Should I install bootloader again? Should I change something from BIOS? If you find a solution, let me know. It's exactly the same problem as me. The problem is not on your clover boot loader , it's in how you installed windows. AFAIK theres 2 solutions. 1. If its a brand new install of windows and you don't have much data there that you care about, just format the drive and reinstall Windows for UEFI boot on a GPT formatted drive. Theres tons of tutorials for that, you will have a EFI on the windows drive and clover will recognise it just fine and boot it, some tutorials strongly advise you to unplug all other hard drives when doing so. 2. Manually create a EFI folder on the NTFS MBR windows drive. This worked for me, i now have and extra "Boot Microsoft EFI boot menu from Drive-Name" in clover boot loader and selecting it boots windows just fine, the only issue is that windows shutdown button gets a bit 'confused' and you need to create a custom very simple .bat to shutdown correctly. Here is how to do it (I won't paste the link to the original post as i think its not allowed to link to other forums, this was not written by myself, nor am i responsible if you mess up your installs, I'm just sharing the info that worked for me) I found a solution to this without any re-partitioning. I am assuming that this affects NTFS formatted Windows partitions as both of mine are NTFS formatted on an MBR drive and I have the same problem. This solution should work for Windows 8, Windows 8.1 and Windows 10. It will also work for Windows 7 but requires a little extra work and access to some binaries from Windows 8 or higher. Firstly, let me explain that ideally one would want to install Windows for UEFI boot on a GPT formatted drive. Windows will automatically create the required EFI directory structure and populate the necessary files. Clover would then automatically recognise the Windows bootx64.efi file in its expected place and the bootable UEFI Windows partitions should appear in Clover. However, as myself and evidently others have discovered, if Windows has been installed for booting from the MBR, then this file is not present and although the NTFS partitions show in Clover as legacy drives, they cannot be booted. However, it is possible to work around this problem and create the C:\EFI directory structure and the required files post-install using the Windows bcdboot tool. It is not usually advisable to use an MBR partition for UEFI boot, but so long as the required Windows EFI files and BCD structure exist, Clover will recognise them and and boot into the Windows partition. I cannot take credit for this solution because I found it on a Linux forum where it was applied to the GRUB bootloader, but I tested it on my machine and it does also work with Clover. I will eventually convert my Windows HDD to a GPT formatted disk but for now, this appears to solve the problem for me. The process is actually quite simple, but before proceeding, the usual disclaimer applies. I will not be responsible for any damage caused to your system! Back up your Windows partition before proceeding and use the process at your own risk! As a pre-requisite, the NTFS.efi driver will need to be present in your Clover EFI/CLOVER/drivers64UEFI directory. I have seen recommendations to have HFSplus.efi or VboxHfs-64.efi there as well, but these are probably not necessary for a Windows boot from NTFS. I have a dual boot Windows setup on one HDD and OSX on another HDD. This process did not affect the MBR or the standard Windows BCD boot loader. If you have Chimera + OSX, then it will not affect Chimera either. You will probably also have the Clover bootloader configured to boot OSX or be using a bootable USB drive with Clover to boot the machine from. It is useful to have some other way of getting into your OSes. It might also be useful to have a Windows install DVD or USB drive handy just in case it becomes necessary to repair the Windows startup in the event that something goes wrong. Boot into Windows 8/8.1/10 and check whether a C:\EFI folder already exists. If Windows is being booted in legacy mode from an MBR, there shouldn't be one. If there is one then Windows may already be configured for UEFI boot and the partition should already be recognized in Clover. If there is no C:\EFI folder, then it is probably safe to proceed. Open a Command window with Run as Administrator. Issue the following command: bcdboot C:\Windows /s C: /f uefi Most likely Windows is on drive C: otherwise substitute the appropriate drive letter. This command does two things: (1) Creates the C:\EFI directory structure and populates it with the appropriate files and (2) creates a BCD database for UEFI boot and an NVRAM entry for the partition. Explanation as follows: C:\Windows - we want to boot the Windows installation at C:\Windows; /s - we want to write the EFI folder to system partition identified as drive C; /f uefi - we want to write a UEFI BCD to C:/EFI rather than an MBR BCD to C:\boot for MBR booting. Once this has been done, there should now be a C:\EFI folder. Under this there will be a Boot and a Microsoft folder. Under Boot you will find bootx64.efi, and under Microsoft will be further boot files including the BCD. If C:\EFI has been created and populated then reboot into Clover and the partition should now appear as an EFI bootable Windows disk in Clover. If you are dual booting Windows 8, 8.1 or 10, then other partitions can be made available to Clover in the same way by booting into the appropriate version of Windows and performing the same command, but taking care to use the appropriate drive letter for the Windows system in question. While booted into it will usually be drive C: though. The bcd boot command in Windows 7 does not support the /f parameter so this will not work under Windows 7. However, if you have access to Windows 8 or 10, then I found that it was possible to copy the BCD tool files from the later version of Windows and use them while booted into Windows 7. I copied the following files, which are found under C:\Windows\system32 into a new folder that was also accessible to Windows 7. I guess they could also be copied to a USB drive: bcd.dll bcdboot.exe bcdedit.exe bcdprov.dll bcdsrv.dll Do NOT copy them into C:\Windows\system32 under Windows 7 but create a separate folder to hold them. You will need to boot into Windows 7, open a command prompt with Run as Administrator and navigate to the directory where you copied the files and execute the same command as above from that directory. Now that Clover is booting our legacy partitions using UEFI, we no longer need the legacy partition entries. To tidy these up, use the Clover Configurator. Backup your config.plist, then load it in Clover Configurator. In the Gui section there are some settings under the 'Scan' heading. By default this will be set to 'Auto=yes'. Change it to 'Custom' and then check Entries and Tool. Leave Legacy unchecked. By default Clover includes all kernels so there is no need to set anything under Kernel. This worked fine on my system and I can now boot into OSX Yosemite, El Capitan as well as Windows 10 and Windows 7 using Clover. Shutdown .bat. Create .bat file (for example shutdown.bat) with code shutdown.exe /s /t 00 4. (Another one that I don't remember with a strange (?) icon) As long as you know the names of the volumes you can open the clover configurator and under GUI you can hide whatever boot icons you want to keep things clean. Here is an example, in mine i have "DATA" and "Recovery HD" hidden só my boot menu is clean. Link to comment Share on other sites More sharing options...
phantom101 Posted April 1, 2016 Share Posted April 1, 2016 I solved very easily When I got home, first of all I've tried to boot windows 10 (from bootloader, obviously) from the icon "Boot Microsoft EFI from EFI". It started! But it was strange...so, i try to boot with OSX and it started too. Ok, I restarted again, tried to start Windows partition with the same option but..Black screen (like yesterday! Damn.). Then, I remembered an user on another forum advice: "It still failed to boot, but after digging around in some forums, I went into the BIOS and set Windows Features to Windows 8 and set CSM Support to Never. This fixed the issue, and I was finally able to boot Windows from Clover." After changing this option, Windows always start correctly from "Boot Microsoft EFI from EFI"! Very good, nothing else to do. Everything is working now. Link to comment Share on other sites More sharing options...
Recommended Posts