Jump to content

[GUIDE] Dual-Boot for Windows 10/11 and macOS on the same disk (Windows installed first, macOS installed first, empty drive)

kushwavez

By kushwavez,
in Clover Guides

 Share
33 posts in this topic

Recommended Posts

makk
makk
Posted
Posted (edited)

@kushwavez

 

I was not offended by your kind post. I am frustrated and if I may have seemed to have been so, Apologies!!

I just need more to go on.

And yes OC is creating no boot situation for Windows inside OC. which should not...

I've tried and tested a several help guides which did not help

 

What I was seeking to know is you wrote up top the Manual installing of Windows which I have to do anyway to select Windows 10 Pro ( MS issue looks like can't select Pro because no Drop Down Menu shows up on the Installer )

 

So here are my questions to you as you have several experiences under your belt.

 

Right I am on the Windows on this triple boot in OC 2 Macs, 1 Microsoft.

 

I had to do the manual installing of Windows.. check

So right now I do not have a working Icon in OC for Windows, there is one there but not working.

I wanted to remove that one so OC does not reference it. and I would not either.

I like the Theme I am using in OC which I tried to find for Clover and not found.

 

What I did was this:

 

At the Installer page for Windows partition selecting window,

deleted the pre-formatted one.

Then SHIFT+F10 to CMD Prompt

 

created efi and named it System, assigned it a letter of V  200mb

created windows primary named it windows assigned it letter W

exit diskpart

 

at the prompt:

bcdboot W:\Windows /s V: /f UEFI

exit

restart

in OC selected the Windows Icon no boot.

 

Then I tried all this map_table.txt and placed in Misc>Entry as stated in the guides by these nice people here.

The icons show up in OC but cannot boot.

 

Went into Open Shell and selected the FS for Microsoft and ran \EFI\Microsoft\Boot\bootmgfw.efi, did not boot

 

What you wrote for the guide is

to omit> /f UEFI < when executing> bcdboot W:\Windows /s V: <

 

I was concerned about a no boot situation for Windows if > /f UEFI < is left out. because I am using F9 to Boot in the Menu in BIOS.


Plus the>  bcdedit /set {bootmgr} path \EFI\OC\OpenCore.efi  < I ran this

 

I'm still not seeing the roots here.

 

What I am using is minipartition free one to view the EFI for Windows but cannot copy it.

 

Do you know how to mount the EFI in Windows so I can copy it?

 

Edited by makk
makk
makk
Posted
Posted
15 minutes ago, makk said:

@kushwavez

 

I was not offended by your kind post. I am frustrated and if I may have seemed to have been so, Apologies!!

I just need more to go on.

And yes OC is creating no boot situation for Windows inside OC. which should not...

I've tried and tested a several help guides which did not help

 

What I was seeking to know is you wrote up top the Manual installing of Windows which I have to do anyway to select Windows 10 Pro ( MS issue looks like can't select Pro because no Drop Down Menu shows up on the Installer )

 

So here are my questions to you as you have several experiences under your belt.

 

Right I am on the Windows on this triple boot in OC 2 Macs, 1 Microsoft.

 

I had to do the manual installing of Windows.. check

So right now I do not have a working Icon in OC for Windows, there is one there but not working.

I wanted to remove that one so OC does not reference it. and I would not either.

I like the Theme I am using in OC which I tried to find for Clover and not found.

 

What I did was this:

 

At the Installer page for Windows partition selecting window,

deleted the pre-formatted one.

Then SHIFT+F10 to CMD Prompt

 

created efi and named it System, assigned it a letter of V  200mb

created windows primary named it windows assigned it letter W

exit diskpart

 

at the prompt:

bcdboot W:\Windows /s V: /f UEFI

exit

restart

in OC selected the Windows Icon no boot.

 

Then I tried all this map_table.txt and placed in Misc>Entry as stated in the guides by these nice people here.

The icons show up in OC but cannot boot.

 

Went into Open Shell and selected the FS for Microsoft and ran \EFI\Microsoft\Boot\bootmgfw.efi, did not boot

 

What you wrote for the guide is

to omit> /f UEFI < when executing> bcdboot W:\Windows /s V: <

 

I was concerned about a no boot situation for Windows if > /f UEFI < is left out. because I am using F9 to Boot in the Menu in BIOS.


Plus the>  bcdedit /set {bootmgr} path \EFI\OC\OpenCore.efi  < I ran this

 

I'm still not seeing the roots here.

 

What I am using is minipartition free one to view the EFI for Windows but cannot copy it.

 

Do you know how to mount the EFI in Windows so I can copy it?

 

 

 

How to Boot Windows from USB with EFI on it?  I need to copy the EFI onto USB incase of danger.

 

Like in these hacky's we can use a USB with EFI on it to boot either Clover or OC.

makk
makk
Posted
Posted

@kushwavez

 

Found Explorer++ works to view and copy the EFI once it is given permission in Windows.

 

Need a workaround I think to get this to Security where Sharing can't happen

makk
makk
Posted
Posted (edited)

I was able to copy finally the EFI folder in Windows and port it.

But since I performed the manual method install outside of OC, the Windows partition did not 

show up in Open Shell as an FSxx for OC to use.  Link database.

 

It is listed as BLK14: < need an FS10 to reference Windows Partition 

 

The Microsoft EFI is listed as FS9:

 

The OpenCore partition which I created is listed as FS8:

 

Need to know how to make BLK14 become FS10.

Edited by makk
kushwavez
kushwavez
Posted
  • Author
Posted (edited)

I am starting to lose you. 
I think you are overcomplicate this too much. 

 

Your problem is that OC can't boot Windows but Clover can, I don't think this has to do anything with boot order or anything like that, it has to do something with OpenCore itself. as I said, many people had problems with OC booting Win. 

 

My suggest is: Wipe the whole disk, Install macOS first (that will create a correct 200 MB EFI so you don't need to mess with bcdboot, Install Win after, then you have 2 options.

  1. use BootloaderChooser then select OC or Clover. Choose Clover if you want to boot Windows. (so in Windows bcdedit /set {bootmgr} path \EFI\Boot\BootX64.efi after you downloaded the bootloaderchooser efi there, alternatively you can create a new boot entry for this with EasyUEFI too and leaving bcdedit alone) 
  2. Create two new boot entry with EasyUEFI (or linux), one pointing to /EFI/CLOVER/CLOVERX64.efi (or OpenCore.efi) with for ex. name macOS, the second entry pointing to /EFI/Microsoft/bootmgfw.efi with for example Win. With that, If you select macOS with F12 UEFI Boot selection (or whatever the boot key is) Clover or OC will come up and can boot macOS, the other (Win) will boot Windows, or you can select your drive name, I think that'll boot Windows too. 

But I think the easiest is just use Clover for Win boot (option 1.). I am doing that way too. As many people, me too, having problems with OC booting Windows. For example it breaks my wifi on my Lenovo T440, ACPI error and won't boot on my i7-3770 pc, but on my X1 Carbon 6th and on an Acer Aspire I don't have any problems with that so this is really hardware-specific. So I am leaving OC alone... And just using Clover to boot Windows, because Clover launches Win natively without touching anything.

 

sidenote about omitting /f UEFI 

if you have GPT disk and GPT installer then you don't need to specify this, it'll be UEFI even if you won't use /f  

 

edit: you can also use "mountvol b: /s" cmd to mount the system efi from win, and use explorer++ or total commander in admin mode to manage it

Edited by kushwavez
makk
makk
Posted
Posted
6 hours ago, kushwavez said:

I am starting to lose you. 
I think you are overcomplicate this too much. 

 

Your problem is that OC can't boot Windows but Clover can, I don't think this has to do anything with boot order or anything like that, it has to do something with OpenCore itself. as I said, many people had problems with OC booting Win. 

 

My suggest is: Wipe the whole disk, Install macOS first (that will create a correct 200 MB EFI so you don't need to mess with bcdboot, Install Win after, then you have 2 options.

  1. use BootloaderChooser then select OC or Clover. Choose Clover if you want to boot Windows. (so in Windows bcdedit /set {bootmgr} path \EFI\Boot\BootX64.efi after you downloaded the bootloaderchooser efi there, alternatively you can create a new boot entry for this with EasyUEFI too and leaving bcdedit alone) 
  2. Create two new boot entry with EasyUEFI (or linux), one pointing to /EFI/CLOVER/CLOVERX64.efi (or OpenCore.efi) with for ex. name macOS, the second entry pointing to /EFI/Microsoft/bootmgfw.efi with for example Win. With that, If you select macOS with F12 UEFI Boot selection (or whatever the boot key is) Clover or OC will come up and can boot macOS, the other (Win) will boot Windows, or you can select your drive name, I think that'll boot Windows too. 

But I think the easiest is just use Clover for Win boot (option 1.). I am doing that way too. As many people, me too, having problems with OC booting Windows. For example it breaks my wifi on my Lenovo T440, ACPI error and won't boot on my i7-3770 pc, but on my X1 Carbon 6th and on an Acer Aspire I don't have any problems with that so this is really hardware-specific. So I am leaving OC alone... And just using Clover to boot Windows, because Clover launches Win natively without touching anything.

 

sidenote about omitting /f UEFI 

if you have GPT disk and GPT installer then you don't need to specify this, it'll be UEFI even if you won't use /f  

 

edit: you can also use "mountvol b: /s" cmd to mount the system efi from win, and use explorer++ or total commander in admin mode to manage it

 

@kushwavez

 

Thank you..

 

OC breaks a few things, patching and all several times overs.

Too much patching.

 

Wow lots of breakage on your end there.

 

Things were good until i installed windows in OC.  after that XXIT hit the fan. done 5 wipes.

 

I spent a lot of time getting OC fine tuned so it's not a simple thing.

 

 

 

makk
makk
Posted
Posted

Had a no boot with 5145 Clover and which I blew ten fuses 😤

 

Seems that when swapping from OC to Clover there leaves little to be liked.

 

So reinstalled twice more because the full wipe did not take on the first go around. Need to do super clean wipe.

 

Running Clover 5144 with success Windows in Volume disk0s4. 

 

No name for MS EFI and no /f UEFI

No MSR partition

executed:> bcdboot C:\Windows /s B: 

executed:> bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.EFI

 

for Clover Custom>Entry> Windows, Windows and that's it.

Booted like a champ.

 

Thank you for your help! It took a bit to get it. Precision.

The trick I found is asa you state.  

 

Leave out the label, the /f UEFI and the bcdedit.

Also Windows needs C as drive letter.

 

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 TB     disk0

   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1

   2:                 Apple_APFS ⁨Container disk1⁩         974.0 GB   disk0s2

   3:                        EFI ⁨NO NAME⁩                 209.7 MB   disk0s3

   4:       Microsoft Basic Data ⁨Windows⁩                 49.8 GB    disk0s4

 

  • 3 years later...
arsradu
arsradu
Posted
Posted (edited)

This worked incredibly well! Thank you!

I needed first scenario (Windows installed first, 100MB EFI partition resize and all that). Didn't need the installation part, since I already had it installed on another partition.

So, basically I just needed a way to boot both OC and Windows, from the same EFI. And I found it thanks to your topic. THANK YOU!

 

The only thing is that, because I had a 16MB Recovery partition near the EFI one, and after both of them, some unallocated space, since it couldn't create 200MB EFI by shifting the Recovery to the right, it left the 100MB space that it used to take for EFI empty, and created the 200MB partition after the Recovery one, on the Unallocated space.

So, before it was: EFI > 16MB Partition (assuming for Recovery), > 4.something GB unallocated space (I have no idea where did that come from but...it was useful here) > Windows NTFS partition

 

Now it's like this: 101MB unallocated space > 16MB Partition (probably Recovery), 200MB EFI > 4.1GB unallocated space > Windows NTFS partition.

 

I guess I could delete the Recovery partition, remove EFI again and recreate it, this way it should be the first partition in the list... But anyway, very nice tutorial. Really well explained! It helped me a lot!

 

Update: yep, that was it. Deleted Recovery partition, redid the steps to delete and recreate EFI partition, and that's it. Now EFI is the first partition, followed by unallocated space, and Windows NTFS partition.

Edited by arsradu
 Share
Go to topic listing
×
×
  • Create New...