It means that there was no MS bootloader (of any sort) located on the first primary partition (obviously because Win7 kept the second primary as boot partition). I was able to fix this by booting via the second primary partition into Windows 7 and running “ bcdboot.exe C:Windows C: ” on.

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 uefiMost 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:Windowssystem32 into a new folder that was also accessible to Windows 7. I guess they could also be copied to a USB drive:bcd.dllbcdboot.exebcdedit.exebcdprov.dllbcdsrv.dllDo NOT copy them into C:Windowssystem32 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. Thanks, this was a lifesaver.I got the same legacy HD Windows drives in Clover that would fail to boot.I added the PBR option in Clover Configurator and that boot worked for a few days.Then I randomly started getting this strange error when booting from that Windows via Clover:BlInitializeLibrary failed 0xc00000bbGoogle didn't help much, seems it's a rare error and people don't really know what caused it. Probably the most insight came from a windows forum where they said:'Cause0' style='box-sizing: border-box; outline: none; margin-right: auto; margin-left: auto; max-width: 1600px; width: 956.594px;'This problem occurs because the boot firmware on the computer generates lots of memory fragmentation.Note Not all 'BlInitializeLibrary failed XXX' errors are caused by this issue.Workaround0' style='box-sizing: border-box; outline: none; margin-right: auto; margin-left: auto; max-width: 1600px; width: 956.594px;'We recommend that you do not let boot firmware create large amounts of fragmentation.

Large memory fragmentation degrades the overall startup performance and causes problems.More information0' style='box-sizing: border-box; outline: none; margin-right: auto; margin-left: auto; max-width: 1600px; width: 956.594px;'At the pre-boot stage, Windows Boot Manager sets the maximum number of global memory descriptor for a 64-bit UEFI system at 512. If the boot firmware creates a large amount of memory fragmentation, the memory descriptor count may exceed the set limit.

This causes the 'BlInitializeLibrary failed XXX' error.Note This design applies only to the current operating system releases, including Windows 10, Windows Server 2016, and Windows Server 2012 R2. We do not guarantee that this design will apply to future versions.' Anyways, that didn't help much. Still not sure why I got that error but I guessed that booting into those legacy HD drivers from the beginning might work. I used your trick, by going into command line with my Windows USB install disk, and this new boot works! Hopefully it stays working.

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.

Numi a calculator app for mac. I copied the following files, which are found under C:Windowssystem32 into a new folder that was also accessible to Windows 7. I guess they could also be copied to a USB drive:bcd.dllbcdboot.exebcdedit.exebcdprov.dllbcdsrv.dllDo NOT copy them into C:Windowssystem32 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. This unfortunately didn't work for me on Win7.I just made a new Sierra install on a seperate SSD, and am now trying to boot Win7 and Win10 with it via Clover.Win10 boots with the trick mentioned above, but Win7 isnt been seen by Clover, don't know why. Both disks are MBR.Later i converted win7 MBR disk to GPT using AOMEI partition assistent, which creates an EFI partition on the disk. Now both Windows disks are beeing seen by clover (now GPT & MBR).

But i get an error when trying to boot Win7. After trying some times booting via Clover, Win7 sometimes starts, but sometimes gives me an strange error.Is it best to also convert the Win10 disk to GPT via AOMEI Partition Assistent?Or should i make a new install of Sierra using UEFI instead of Legacy version of Clover?Thanks in advance. This unfortunately didn't work for me on Win7.I just made a new Sierra install on a seperate SSD, and am now trying to boot Win7 and Win10 with it via Clover.Win10 boots with the trick mentioned above, but Win7 isnt been seen by Clover, don't know why. Both disks are MBR.Later i converted win7 MBR disk to GPT using AOMEI partition assistent, which creates an EFI partition on the disk. Quarkxpress updates for mac. Now both Windows disks are beeing seen by clover (now GPT & MBR). But i get an error when trying to boot Win7.

After trying some times booting via Clover, Win7 sometimes starts, but sometimes gives me an strange error.Is it best to also convert the Win10 disk to GPT via AOMEI Partition Assistent?Or should i make a new install of Sierra using UEFI instead of Legacy version of Clover?Thanks in advance. But i installed Sierra with unibeast in 'legacy' mode. After installing Sierra i installed multibeast with Clover also in Legacy mode. Can i just run multibeast again, and install Clover in UEFI mode?

Is that what you mean?Here is what happens;Clover loads up, showing 3 drives. Left to right: Win7, Win10, Sierra. (Win10 and Sierra both working good)Trying to Launch Win7:Then i get this error:Then, when booting from the Win7 disk only, i get this message. But Win7 starts normal when i choose: Start Windows Normally.Any ideas why win7 is not working here, and Win10 does work?

Locate your 'legacy' Clover folder, which may be on an EFI partition or somewhere else. Back it up e.g. To the desktop. If its on the EFI partition where you are going to re-install Clover remove it, if it is on 'Macintosh HD' or whatever you can leave it. Then install Clover UEFI with similar settings to before.

You can copy any kexts, additional files you actually need, from your Clover backup if you want.At this point you should add an entry to /efi/clover/cloverx64.efi using the EFI shell bcfg command (see Clover documentation folder), EasyUEFI from Windows or the efibootmgr command from Linux. Then in firmware settings set the boot order to boot the entry you created first.You may be able to boot Clover by selecting the disk where Clover is installed (identified as 'UEFI', the disk may appear in the menu twice if legacy boot options are presented) - however this is not guaranteed.If your Clover folder wasn't on the EFI partition before or you didn't have to move it you will still be able to boot the legacy way by selecting the same disk in firmware settings NOT identified as UEFI.Have a bootable Clover USB ready in case you cannot boot from the internal drive.

Bcdboot.exe E: windows /s E: /f ALL When I run this the BCD Help page shows as if I've entered an invalid option I'm installing windows 7 on a usb drive, my current os is Windows 7 as well.

BCDEDIT is the correct answer. BCDboot is a tool used to quickly set up a system partition, or to repair the boot environment located on the system partition. The system partition is set up by copying a small set of boot environment files from an installed Windows速 image. BCDboot also creates a Boot Configuration Data (BCD) store on the system partition with a new boot entry that enables you to boot to the installed Windows image. BCDEdit is a command-line tool for managing BCD stores.

It can be used for a variety of purposes, including creating new stores, modifying existing stores, adding boot menu parameters, and so on. BCDEdit serves essentially the same purpose as Bootcfg.exe on earlier versions of Windows, but with two major improvements: I'm pretty sure the correct answer is BCDedit. Not really BCDboot is a repair tool not a editor for the bootcfg.exe it can make changes to the BCD but as for the question it says add not repair a VHD to/in the boot menu. I see you don't have any Microsoft cert's yet is this going to be your first MS test? If so get ready there are questions just like this that they try to mislead you it's all in the small details one word changes the answer.

Right directly off my practice test it says the following: Q48: You have created a VHD with a disk image that you want to add to a client computer named PC-WS680. You have copied the VHD to PC-WS680 and attached it using the attach vdisk command.

Bcdboot C Windows S C

You now want to add the VHD to the Windows 7 Boot menu. A: You should consider using the BCDboot utility to copy the boot enivornment files and Boot Configuration Data (BCD) configuration from the Windows directory in the VHD to PC-WS680. Now if BCDedit would've been one of the options for an answer, i would've chose that. Wn7512bep epson drivers for mac. See how this can be tricky? Unless there is something I'm missing.