ADD WINDOWS 10 BOOT EFI AFTER INSTALLED OS X & CLOVER UEFI Simple

[BlackSlash]

I find I enjoy helping other OS X self builder's and enthusiasts with their systems after I've been helped many times myself by this very community. This is a "straight to the point" guide, not "how I did it guide".


HERE WE GO

This guide has no guarantee it will work for you as it did for me. Use this information at your own risk.

This all inclusive guide is targeted for helping others using UEFI booting of Windows 10 alongside their OS X using the Clover boot loader 'UEFI' option installed on the OS X partition through latest EL Captain Multi-beast version 8xx. If you're using Clover legacy boot settings this guide won't be for you . . . .

so again --->'Not For Legacy Booting' nor older motherboards that don't have ability for UEFI booting.

It is most important that your bios settings are all properly set for UEFI booting. tonymacx86 has plenty of members in this community that have already posted guides to explain how to properly set up your Bios for UEFI boot so I won't be spending any time explaining this.


THE PROBLEM:

You post installed CLOVER UEFI boot loader to your OS X partition, achieved booting OS X UEFI but Windows 10 you can't.


THE DESIRE:

You want the holy grail. The same ability to boot your Windows 10 from the Clover boot loader just like OS X.



HERE'S HOW:

Attached bottom of this post is a zip file containing the proper configured Windows 10 UEFI contents for adding to your Clover boot installation within your permanent OS X partition. Download the zip file and open it. Once zip file is opened reveals the main folder. Inside you'll discover 2 objects. #1 A folder labled 'Microsoft' and #2 a Windows BOOTX64-win.efi file. I'll explain later in steps #9 and #10 for exactly where to place these items. Once completed you should have no problem booting Windows 10 from your Clover boot loader UEFI installation equally without hiccup just like booting OS X from that same Clover UEFI installation.

This guide designed for simplicity of how to rather an explanation as to why.

1. Boot into Windows 10 directly by using keyboard hot key such as F8 or F12 (you likely require the bios boot settings being switched back to the legacy boot options 1st in order to do this.)

2. Once booted back into Windows 10. Open command window 'run as administrator'

3. enter command: bcdboot C:\Windows /s C: /f uefi

4. You should then see a following message "Boot files successfully created". 1st step success!

5. Restart computer, enter bios & reset the bios legacy boot settings back to UEFI boot settings if need be.

6. Clover boot options should now be back. Now boot into OS X El Captain or your whatever OS X installation.

7. You now should see a Windows 10 drive and possibly a reserve drive mounted on the OS X desktop. Leave them there.

8. Using an EFI mounter like 'Clover configurator' mount OS X 'EFI' partition. Follow next 2 steps as specified.

9. Open the mounted 'EFI' drive/folder on the OS X desktop then simply drag the attached entire 'Microsoft' folder inside that 'EFI' folder. Don't mess with any contents within 'Microsoft' folder. It is configured to boot Windows 10 UEFI. Just drag the folder as specified.

For those who are still newbies learning your way around OS X and have attempted to mount your EFI drive/folder but do not see it mounted on your desktop try this:

A. Open Finder (smiley face square icon bottom of your desktop)
B. Now left click the actual word 'Finder' located at top left corner of your desktop for revealing a list of selactable options.
C. Select Preferences
D. Under 'show these items under desktop' make sure 'Hard Disks' is checked (EFI drive should now be seen mounted on desktop)


10. Now take BOOTX64-win.efi and drag that file into the 'BOOT' folder sitting inside underneath same 'EFI' folder. You now are completely done.

11. Other Points Need Mentioned to avoid mistakes. Underneath 'EFI' folder make sure you put nothing in the Apple or Clover folders. Leave them alone. The Microsoft folder should now be seen listed or being grouped among APPLE, BOOT & CLOVER folders under 'EFI' after you dragged it there. The only file you'll put within another folder is placing BOOTX64-win.efi inside that 'BOOT' folder sitting inside the "EFI' folder.

12. You can unmount Windows 10 or any mounted partitioner for that matter on the OS X desktop simply by right clicking then selecting 'eject' from the list.

13. Hopefully now a restart back into the Clover provide you booting options either OS X or Windows without problem.

I hope this simple explanation for multiboot of OS X and Windows works for you. God Bless.

nope still the same problems my quote.

Can you elaborate on this as to give some more insight to what you mean here stated above, as I have the fake CPUID, What does this mean to me ? and, How this could be of a hinderance to me ? Trying to dual boot win 10 and Sierra because as far as I see this particular code or to me is, Looks more like a file association problem with windows 10 more than a Sierra problem or clover boot problem but I could be wrong and thats not to say that it is not either or all of the above mentioned combined together in saying that this is the error message that I get, windows\system32\winload.efi error code:0xc0000225 . File association problem ! Hmm maybe maybe not. This error is also followed by please press enter to continue, Nothing happens when you do. Followed by please press F8 to fix. nothing happens here either. followed by press esc which brings you back to the firmware which in my case brings me back to the bios oh I will add that my bios is F5 firmware grade 5.

My problem I think may be very simple to a Dev or even programmer or even to anyone that has file association skills, so I appeal to one of you guys if any reading this article,
Now!
All that said and done,
To the point at hand,
I can see all my drives included the windows 10 operating system files through Sierra I can also change these files so I would like to know what I need to do to fix my boot in problem from clover and what files I need to move around or change in Windows 10 from Sierra to have dual boot take affect on the next boot.

One thing I forgot to mention but I think theres no need but I will mention it again is that in the clover firmware I see the option to boot in to windows 10 and on clicking it gives the above problem or error message.

Just a quick edit too I have been looking through the internet on other forums and these forums keeps bringing me back to this discussion here so it is why I posted here.

https://www.tonymacx86.com/threads/...stalled-os-x-clover-uefi-simple.182919/page-3
Followed these steps to see windows 10 in clover boot loader. only to get to the above mentioned.

 

[BlackSlash]

No idea why Clover would have put this back the way it was. Top screen is when everything was working just fine.

View attachment 212646

Take it from me, reading these forums is sending me mad I need to take a break.
Each time I tried all these steps in this forum and other forums brings me back to the same problem which I feel is a file association problem as this is where i am stuck at when booting from boot clover,
windows\system32\winload.efi error code:0xc0000225
This is where I am at right now.
https://www.tonymacx86.com/threads/...talled-os-x-clover-uefi-simple.182919/page-10

 

[Going Bald]

Take it from me, reading these forums is sending me mad I need to take a break.
Each time I tried all these steps in this forum and other forums brings me back to the same problem which I feel is a file association problem as this is where i am stuck at when booting from boot clover,
windows\system32\winload.efi error code:0xc0000225
This is where I am at right now.
https://www.tonymacx86.com/threads/...talled-os-x-clover-uefi-simple.182919/page-10

Not a file association problem - this error code indicates is a missing or corrupt winload.efi file. You need to repair your Win10 boot file.

 

[BlackSlash]

Not a file association problem - this error code indicates is a missing or corrupt winload.efi file. You need to repair your Win10 boot file.

Any idea then on how I can fix this do you know of any one with this similar problem I have looked far and wide throughout the internet and keep being redirected to this post here.

 

[Going Bald]

Any idea then on how I can fix this do you know of any one with this similar problem I have looked far and wide throughout the internet and keep being redirected to this post here.

shows step by step what to do.

 

[BlackSlash]

shows step by step what to do.

Thanks for that the vid was awesome but sorry to put you through that but I hope it helps someone else because I found what my problem was it was the wrong installation of windows 10 pro and the new update fixed the UEFI setting in windows 10 pro 1703 build when I updated this I found away from there that explains the video where you hit command the choice s just underneath it to edit UEFI and just reboot and viola my install of windows 10 was UEFI but when booting did not straight in to windows 10 pro I had to change the bios round to read legacy Mode to see the 950 pro NVMe drive reformat it to GPT then rebooted back to bios then followed instruction to install Sierra from the beginning in UEFI if that makes any sense.
The old install of windows on the 950 PRO was eft legacy mode install don't ask how I did that I don't know I didn't think it was possible but it is with these drive.

 

[fliptwister]

Thanks Logan Grey. I was unable to dual boot (2 different hard drives) from Clover and now I can.

 

[ajschot]

Take it from me, reading these forums is sending me mad I need to take a break.
Each time I tried all these steps in this forum and other forums brings me back to the same problem which I feel is a file association problem as this is where i am stuck at when booting from boot clover,
windows\system32\winload.efi error code:0xc0000225
This is where I am at right now.
https://www.tonymacx86.com/threads/...talled-os-x-clover-uefi-simple.182919/page-10

I have the same problem... i will see what happens when window sis updated... when i tried to install windows 10 1703 i could not format the disk so i used and old disc that was lating arround and that worked only giving me thetm same erre as you have. I hope it will work when updated to 1703

 

[wallybear]

FIX For Only Windows Loading :
After these steps is quite possible that your Notebook/PC is only Booting Windows Partition or drive , to fix it follow theses steps:

1. Go to Bios Setting.
2. Found option like "Add NEW Boot Entry" [ option only available after setting boot mode to UFEI ]
3. Add Name (Your Choice) & Path = " EFI\CLOVER\CLOVERX64.efi "
4. Save setting and reboot again into BIOS.
5. Move Your this new Boot Entry in Top of Your Boot Mode or Boot Priority .
6. Save BIOS Setting and Restart Normally.

If your BIOS lacks the "add new boot entry" option (e.g. my HP Elite 8300 doesn't have it) you can still add the entry with the following procedure:

1. Download a Linux Live CD and boot fom it (I used Linux Mint 18.2)
2. go to terminal as super user (sudo su) and enable module efivars: modprobe efivars
   
3. use efibootmgr (if missing do apt-get install efibootmgr) to add the Clover entry: efibootmgr -c -L "UEFI Clover" -l "\EFI\CLOVER\CLOVERX64.EFI" ("UEFI Clover" is the label that will be displayed, you are free to use another name)
4. The new BIOS entry will get an ID similar to BootXXXX where XXXX is a 4-digit number (in my case was Boot0003); you can run efibootmgr without parms to see the current BIOS boot entries.
5. Let's move our entry as the first one to boot: efibootmgr -o XXXX (the 4-digits of yout entry)
6. Done. You can restart your Mac and select your new entry to boot in Clover.

The new entry will be deleted only if you reset your BIOS.

 

[danieldbird]

Thanks, post #1 worked for me.