I believe the automated repair is doing one or both of those and knowing which one works will help diagnose what Chameleon is doing that causes the issue in the first place. I think it would be instructive to try to manually fix Windows through the repair console by running fixboot. If you remove the stick after you click "repair" but before you click to confirm, I think it will keep the USB stick from getting screwed up. Doing the repair again will get Windows booting again. When that happens, you can fix the USB stick by renaming \boot\BCD.backup.001 to \boot\BCD. Well, yes, I could, but when it does the repair it evidently decides to write the MBR to the USB stick - or something like that - so that the USB stick is required in order to boot at all. Post added at 06:15 PM - Previous post was at 05:20 PM -Ī sidenote - I decided to see if I could put the Windows recovery CD on a bootable USB stick and use that. It would be nice if this annoyance could be avoided in the future. Running the Windows "repair" allows you to boot into Windows and then you can rerun EasyBCD and fix up the entries. Info: The selected entry could not be loaded because the application is missing or corrupt.Ī similar message greets you if you try to boot Windows.
#How to use easybcd to dual boot mac#
This was mentioned in passing in the NBI development thread, but I'm putting it here for further discussion.Īs several of us have noted, if you run NBI and ask it to (re)install Chameleon, then if you had been using EasyBCD to do the boot select you're greeted with this when you try to reboot Mac OS: