Manually Installing Windows: No Way To Boot "W" In Opencore; Need Expert Help

[makk]

Greetings OC lovers and developers,

I have this current situation.

 

Rundown: Windows 10 Pro no direct install from installer on auto install.

No menu to select it in the installer "Windows 10 Pro" the option does not exist and direct installs "Windows 10 Home."

To circumvent, once at the "select"  drive/volume portion of the installer, hit two keys: Shift+F10 to bring up command prompt.

initiate diskpart, create the necessary partitions and exit.

next initiated:>  bcdboot C:\Windows /s B: enter.  Omitted on purpose /f UEFI as recommended by others.

exit command prompt exit installer, reboot.

In Opencore the Windows Icon appears as the first one in the set on the left with subsequent OS's to the right.

 

Clicked on the Windows Icon got black screen.

Used the Shell app and looked at the FS's. Found FS1: for EFI Microsoft.  

ran from FS0:\EFI\Microsoft\Boot\bootmgfw.efi  <. black screen.

same from FS1:

 

From FS0: map > map_table.txt.

 

Boot into Monterey to look at the mappings.

 

(No folder for Microsoft in the EFI; just Boot and OC)

 

Maptable.txt reveals no FSx: for Microsoft Windows filesystem. but blk4: is listed as Microsoft Windows Data partition.

from the map.txt this is what is revealed:

 

BLK4: Alias(s):

          PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(3,GPT,86FADCD0-0D91-459C-877B-A026D533E2FD,0xC8800,0x5D8C000)

 

What I think at this current moment is to make this a Filesystem and if it is possible how to do it in Shell.

 

Should be like this result:

FS10: Alias(s):HD1a0a3:;BLK4:

      PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(3,GPT,86FADCD0-0D91-459C-877B-A026D533E2FD,0xC8800,0x5D8C000)/\Windows\system32\winload.efi

 

 

 

NOTE: What has been done thus far to get Windows to boot from Opencore so we know that the recommended has been done.

Since this is not a AUTO Install as normal, and is Manual Install, a folder called Microsoft is not created in the EFI when

we mount the EFI.The only folders are as mentioned above. In the Shell program FS1: is there and is the EFI for Microsoft.

 

First Time:

In diskpart for the efi as follows:

create partition efi size=200

format quick fs=fat32 label="System"

instead,

format quick fs=fat32 

assign letter="B"

create the primary and format it and assign a letter.

exit

 

to install Windows flavor you want:  

dism /Get-WimInfo /WimFile:D:\Sources\install.wim (replace D with USB drive letter) <> Notice install.wim (over 4GB). Used the app that makes it possible

dism /Apply-Image /ImageFile:D:\Sources\install.wim /Index:6 /ApplyDir:C:\ (replace D with USB drive letter)

bcdboot W:\windows /s S: /f UEFI <> if Windows is solo

 

bcdboot C:\Windows /s B: <> if Windows is part of dual booting

 

Boot into Windows with BIOS F9. Opencore does not have the Windows Data portion to initiate it.

Once Windows finished installing the preliminaries and entered the Desktop GUI mode, ran Command Prompt ( in elevated mode)

 

ran the following:

 

bcdedit /set "{bootmgr}" path \EFI\OC\OpenCore.efi" enter.

exit and reboot. 

Still no can boot due to no Windows Data partition set as FSx: in Shell.

 

In OpenCore config.plist,

 

Misc> Bless folder entered \EFI\Microsoft\Boot\bootmgfw.efi

Entry> created an entry from the map_table.txt for the EFI as:

PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,CB79BD5A-ECF8-4938-959F-F68BBD661A1A,0x64800,0x64000)/\EFI\BOOT\BOOTx664.efi

Windows:Windows10Pro

Windows 10 Pro

 

END of what was done as per recommended.

 

But since there is no FSx: in the mappings for Windows data disk0s3

Shell has no idea which one to use.

 

Thus the need to know how to make BLK4: into FS10: as outlined above.

 

Reading through the UEFI pdf, is like reading a spec. book. Need an instructional guide, (step by step) to complete it.

 

 

 

 

 

 

map_table.txt.zip map-tableMSW.txt.rtf.zip Windows Boot Manager BCDEDIT.zip

Edited April 10, 2022 by makk

[STLVNUB]

I keep saying try Windows Installer, there is NO VIRUS in it.

You are doing far to much work than necessary.

Installs its own Bootloader ON THE DISK IT INSTALLS TO

Selectable in Clover, Haven't triedOC but I suspect it will do same

I have installed w11 to USB key NO PROBLEM

Like I Said, Give it a try

Edit: It ends up having is own ESP i.e

BOOT/BOOTX6.efi so Clover boots it so will OC

Edited April 6, 2022 by STLVNUB
clarify

[makk]

1 hour ago, STLVNUB said:

I keep saying try Windows Installer, there is NO VIRUS in it.

You are doing far to much work than necessary.

Installs its own Bootloader ON THE DISK IT INSTALLS TO

Selectable in Clover, Haven't triedOC but I suspect it will do same

I have installed w11 to USB key NO PROBLEM

Like I Said, Give it a try

Edit: It ends up having is own ESP i.e

BOOT/BOOTX6.efi so Clover boots it so will OC

Much appreciated. but did not work from inside OC.

Clover works fine.

 

I can boot windows from BIOS F9.

Just not from OC.  

 

 

[STLVNUB]

1 hour ago, makk said:

Much appreciated. but did not work from inside OC.

Clover works fine.

 

I can boot windows from BIOS F9.

Just not from OC.  

 

 

Well thats weird, it should work. Maybe big bug in OC

[STLVNUB]

Rolls eyes and thinks WTF

I will not be putting anymore input into this

Obviously you guys want to do THINGS THE HARD WAY
 

Edited April 6, 2022 by STLVNUB

[Ellybz]

Picture speaks for itself I suppose. OpenCore 0.8.0 . Booting the USB Windows 10 installer thru OpenCore is flawless. ( Tested -> Selection of drive to format/install Win10 ). 

USB installer was formatted NTFS.

HideAuxiliary = YES/True

Scan Policy: 20675331

 

 

 

 

 

Edited April 7, 2022 by Ellybz

[Guest 5T33Z0]

Use Ventoy https://github.com/ventoy/Ventoy

It's a universal boot stick type thingy with a GUI which can run installers straight from almost any ISO (Windows, Linux, etc.) except macOS.

So basically, you let ventoy prepare a USB flash drive

Throw the Windows ISO on it

Boot from the Flash Drive, select the ISO you want to run and then Windows can be installed.

No terminal wizardry required

 

Edited April 7, 2022 by 5T33Z0

[jpz4085]

On 4/6/2022 at 3:01 AM, makk said:

I can boot windows from BIOS F9.

Just not from OC.  

Your OpenCore configuration or ACPI patching probably need adjusted to boot Windows. Post the OC folder from your EFI partition so we can examine it.

Once that's addressed then you can install and boot Windows through OpenCore without using Rube Goldberg type workarounds.

Edited April 8, 2022 by jpz4085

[ammoune78]

Rolls eyes and thinks WTF
I will not be putting anymore input into this
Obviously you guys want to do THINGS THE HARD WAY
 

It wasn't my intention@STLVNUB , on my Mac, it's the only way as we don't have a boot screen GPU and Windows write on that small nvram secure boot things, so only way is to use OpenCore. Then it's the only guide i've found useful as it installs in UEFI mode. And for poster that struggles with that method, i only saw that guide will be useful for him. Please don't paranoid, and i see you as a respective friend, but don't throw this friendship a way with these behaviors.
Honestly i didn't mean other thing than give the guy a useful link from what i know and my experience with similar installation stuck that i had.
I saw you liked my reply but i don't know what happened from yesterday to today, and excuse me if i'm mistaking or not understanding.

[makk]

2 hours ago, jpz4085 said:

Your OpenCore configuration or ACPI patching probably need adjusted to boot Windows. Post the OC folder from your EFI partition so we can examine it.

Once that's addressed then you can install and boot Windows through OpenCore without using Rube Goldberg type workarounds.

@jpz4085  Thank you,

 

Dudes pay attention:

 

Had a manual install:  Windows 10 Pro is not selectable from the normal install path. No Drop Down Menu; No Menu.

Probably Have to edit some file inside to make it happen. 

 Dowloaded the ISO direct from MS shaft factory.

Performed install with Shift+F10> Command Prompt. 

 

 

EFI on google drive:

 

https://drive.google.com/file/d/1LYGm_g8cS5lI1jgxUQuIKM4sY9MY6tKP/view?usp=sharing

On 4/6/2022 at 1:49 AM, STLVNUB said:

I keep saying try Windows Installer, there is NO VIRUS in it.

You are doing far to much work than necessary.

Installs its own Bootloader ON THE DISK IT INSTALLS TO

Selectable in Clover, Haven't triedOC but I suspect it will do same

I have installed w11 to USB key NO PROBLEM

Like I Said, Give it a try

Edit: It ends up having is own ESP i.e

BOOT/BOOTX6.efi so Clover boots it so will OC

@STLVNUB  

 

I need it on the hard on the drive. For the SSD software options.

Edited April 8, 2022 by makk

[makk]

See the problem starts with MS Shaft factory not giving us a Menu to select which Flavor of Windows 10 we want to install.

So if one wants 'Windows 10 Pro' version, one has to use the 'Manual' Method which I found out perhaps doesn't put the necessary

information for OpenCore to boot.  

 

MS Shaft Factory has it set on the ISO download as 'default' Windows 10 Home. < Super! I found a banana!  

20 hours ago, Ellybz said:

Picture speaks for itself I suppose. OpenCore 0.8.0 . Booting the USB Windows 10 installer thru OpenCore is flawless. ( Tested -> Selection of drive to format/install Win10 ). 

USB installer was formatted NTFS.

HideAuxiliary = YES/True

Scan Policy: 20675331

 

 

 

 

 

@Ellybz

 

That is really nice looking boot menu!

 

What is the theme?

 

 

Edited April 8, 2022 by makk

[makk]

17 hours ago, 5T33Z0 said:

Use Ventoy https://github.com/ventoy/Ventoy

It's a universal boot stick type thingy with a GUI which can run installers straight from almost any ISO (Windows, Linux, etc.) except macOS.

So basically, you let ventoy prepare a USB flash drive

Throw the Windows ISO on it

Boot from the Flash Drive, select the ISO you want to run and then Windows can be installed.

No terminal wizardry required

 

@5T33Z0

 

Does this one allow the Menu Selecting for Flavor of Windows? 

Index

1 is Home

2 is Home with some option

3 is Education

4 is Teacher's Pet

5 is Some other version

6 is Pro  << Advanced Options

7 is Pro N << European

8 is Pro xx << Some lesser form still better than Home.

9 is xxxx

10 is xxxxx

 

This menu above is only available if one hacks a file before installing. I don't know which file to hack.

This Index is available in Manual Installing method.

 

There was before the Flavor menu was available.  Says on the site you can choose which one you want, but when you burn it to USB run the install the which one you want has no menu so it just runs through and installs Windows 10 Home. Which I don't care for. Home version is limited and cranky. Makes one blow a fuse when working with it.

 

Corporate version, education version, teacher's version, business version, home, and pro versions, ultimate version.

All these versions. 

 

 

Edited April 8, 2022 by makk

[Guest 5T33Z0]

It does what I said: it runs the ISO.

 

You decide, which Edition will be installed in the setup dialog. If a windows license is present from a previous install, it will install the edition the license is for.

 

Otherwise you need to do this: https://www.intowindows.com/how-to-select-pro-edition-while-installing-windows-10/

 

[makk]

39 minutes ago, 5T33Z0 said:

It does what I said: it runs the ISO.

 

You decide, which Edition will be installed in the setup dialog. If a windows license is present from a previous install, it will install the edition the license is for.

 

Otherwise you need to do this: https://www.intowindows.com/how-to-select-pro-edition-while-installing-windows-10/

 

@5T33Z0 OMG! You're the man of the week!

 

Thank you so much! This will resolve this boot monkey business.

Have a good day!

[makk]

Here's a website Esplayning this 

 

https://osbuilder.osdeploy.com/docs/untitled-4/windows-10-setup-and-the-ei.cfg

 

https://answers.microsoft.com/en-us/windows/forum/all/installing-windows-10-pro-instead-of-home/fb62c4e8-8829-41ba-817c-aff3cca51b3b

 

Official MS Shaft factory

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-edition-configuration-and-product-id-files--eicfg-and-pidtxt?view=windows-11

[makk]

17 hours ago, 5T33Z0 said:

It does what I said: it runs the ISO.

 

You decide, which Edition will be installed in the setup dialog. If a windows license is present from a previous install, it will install the edition the license is for.

 

Otherwise you need to do this: https://www.intowindows.com/how-to-select-pro-edition-while-installing-windows-10/

 

 

Didn't work. must be a MS shaft issue now.

Have to find a workaround that.

 

seriously did not work

[jpz4085]

On 4/7/2022 at 10:34 PM, makk said:

Had a manual install:  Windows 10 Pro is not selectable from the normal install path. No Drop Down Menu; No Menu.

Let's start over with this and make sure you have the correct version. Click the link below and select the multi-edition ISO as pictured.

https://www.microsoft.com/en-us/software-download/windows10ISO

Once you've downloaded the image file format a USB flash drive as MBR/exFAT then mount the ISO and copy all the files to the USB. You can also extract and copy the ISO contents to the USB using Keka.

Next add the exFAT driver from OcBinaryData to your OC/Drivers folder and config.plist under UEFI/Drivers. Then set the Misc/Security/Scan Policy to 0 temporarily so you can see the flash drive in the OC picker.

 

Before you attempt to boot the Windows installer see the attached AML files. I have wrapped the macOS ACPI patches in _OSI "Darwin" statements to prevent Windows from using them. The EC and HPET tables should be good to use. The SSDT-4x0G2b.dsl file needs further editing for compatibility. You will need to add Else statements containing the original unmodified code from your DSDT to the Darwin checks for the _PTS, _WAK, BITF, BTST, SBTC, GBTI and GBTC methods. Or at least maybe references to the renamed originals similar to the RDSS/XDSS and _OSI/XOSI methods. Proper ACPI patching is critical to multi booting with OpenCore. If you need further help with that post your original DSDT/SSDT files for reference.

SSDT.zip

[Guest 5T33Z0]

For Ventoy, exFat driver is not required. It's detected by OC out of the box. I just tested it.

[makk]

On 4/9/2022 at 4:17 AM, 5T33Z0 said:

For Ventoy, exFat driver is not required. It's detected by OC out of the box. I just tested it.

@5T33Z0

 

Ok I believe you, I'm on Mac which one works on MacOS? I see 

three flavors 1) Windows.ZIP, 2) Live.ISO, No)Linux.TAR.GZ files.

 

I'm assuming (forgive the insolence and incredulousness) Live.iso for MacOS?

 

With Rufus, It should work on any machine. with no problems ??

 

In Windows I used Rufus 3.17 and it created a --screenshot

Win10P --screenshot

UEFI_NTSF --screenshot

 

So far with this setup, it has booted twice from inside OpenCore and then putt out like limp rag. never booted inside OpenCore again.  I've messed with this for 5 months now started December Last Year with OpenCore. I have success with Clover as is with no need to edit or add anything to configs.

I've tried every combo read all pages, but, no one that has a success story with this same laptop and same configs.

OpenCore obviously has to be set right in this laptop.  Some config that has to be added, disabled or enabled. But I don't know which one.

Debug enabled during installs and reboots.  I have tried the blind routine and enabled, disabled in config.plist and had either no boot, or some wild stuff.

So I stopped that idea.

 

Let me know what works in MacOS thank you!

 

 

Edited April 10, 2022 by makk

[makk]

On 4/9/2022 at 12:58 AM, jpz4085 said:

Let's start over with this and make sure you have the correct version. Click the link below and select the multi-edition ISO as pictured.

https://www.microsoft.com/en-us/software-download/windows10ISO

Once you've downloaded the image file format a USB flash drive as MBR/exFAT then mount the ISO and copy all the files to the USB. You can also extract and copy the ISO contents to the USB using Keka.

Next add the exFAT driver from OcBinaryData to your OC/Drivers folder and config.plist under UEFI/Drivers. Then set the Misc/Security/Scan Policy to 0 temporarily so you can see the flash drive in the OC picker.

 

Before you attempt to boot the Windows installer see the attached AML files. I have wrapped the macOS ACPI patches in _OSI "Darwin" statements to prevent Windows from using them. The EC and HPET tables should be good to use. The SSDT-4x0G2b.dsl file needs further editing for compatibility. You will need to add Else statements containing the original unmodified code from your DSDT to the Darwin checks for the _PTS, _WAK, BITF, BTST, SBTC, GBTI and GBTC methods. Or at least maybe references to the renamed originals similar to the RDSS/XDSS and _OSI/XOSI methods. Proper ACPI patching is critical to multi booting with OpenCore. If you need further help with that post your original DSDT/SSDT files for reference.

SSDT.zip 7.72 kB · 1 download

 

 

@jpz4085

 

Thanks so much! 

 

Can you give me an example of your thoughts when referring to the latter above about "Or at least maybe references to the renamed"

 

I used Rufus (see above screenshots in post before this one)  to make the USB booter as recommended on the OC page or at least they mention it that way.  

 

But what happened is I have to F9 boot menu to select it "USB External Hardrive" for it to boot even with ExFat in OC.

WTF?!  

 

Clover no issues exact same setup minus a few ACPI patches and 2 SSDT's. Have in drivers's UEFI:  fat.efi, and NTFS.efi in Clover.

Boots right into Windows no issues.

 

Last night rolled back to OC 7.4, from 7.9.  removed a few statements and same results.

Maybe I should try OC 6.0?

 

I am determined to get OC to boot Windows on this rig.

 

I also tried Boot Camp with OC, what happened was a no go. Did not happen

OC is always the culprit.  

 

 

 

 

 

 

[makk]

On 4/6/2022 at 10:59 AM, ammoune78 said:

If you want OpenCore to boot your windows partition, follow this guide instructions, it will bcdboot command then from macOS or open the EFI partition windows is on the same disk, create EFI empty folder and grab Microsoft folder from the early created EFI using bcdboot command and paste it on EFI folder windows is installed on the same disk. That way you can boot windows using OpenCore, Mac or PC doesn't matter

https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/

 

@ammoune78

 

Thank you much!

 

It did not work but once and then afterwards no  boot from inside OpenCore.

 

[makk]

There was a web link where a person used rsync to copy to USB on MacOS.

 

hdiutil to mount the windows.iso flavor

 

hdiutil mount xxx.iso

 

then 'rsync -r' the entire mounted iso into the USB.  this then circumvented the fat32 limit of 4GB?  I don't recall offhand.

 

format as fat32 guid/gpt for the data to be copied to  with EFI partition for booting with the files like in Rufus.

 

so it would mentally look this:

GUID the entire USB

EFI Fat32

DATA Fat32? 

 

 

Another one to circumvent the Fat32 limit of 4GB

 

Update April 2020: One of the files in the Windows 10 ISO – install.wim – is now too large to copy over to a FAT-32 formatted USB drive. So I'll show you how to copy it over separately. —FAT32 Limit of 4Gb copy

1 Check the install.wim or install.esd file for it’s size. 

##NOTE: Rufus 3.13 - 3.17 has no problems creating the installer##

 

First run this command to copy over everything but that file:

rsync -vha --exclude=sources/install.wim /Volumes/CCCOMA_X64FRE_EN-US_DV9/* /Volumes/WIN10

 

Then run this command to install Homebrew (if you don't have it installed on your Mac yet):

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

 

Then use Homebrew to install a tool called wimlib with this terminal command:

brew install wimlib

 

Then go ahead and create the directory that you're going to write the files into:

mkdir /Volumes/WIN10/sources

 

Then run this command. Note that this process may take several hours, you may see 0% progress until it finishes. Don't abort it. It will use wimlib to split the install.wim file into 2 files less than 4 GB each (I use 3.8 GB in the following command), then copy them over to your USB:

wimlib-imagex split /Volumes/CCCOMA_X64FRE_EN-US_DV9/sources/install.wim /Volumes/WIN10/sources/install.swm 3800

 

Once that's done, you can eject your USB from your Mac inside Finder. Note that Windows will automatically rejoin these files later when you're installing.

 

** Depending on Hardware for the Format on USB GPT or MBR

If GPT Fails redo the whole process by formatting first the USB to MBR.

Fat32 has a 4Gb file size limit.

Edited April 10, 2022 by makk

[makk]

So it gets quite extensive due to Fat32 4Gb limit.

 

Thus tools like Rufus has no problems with this because it creates a GUID USB formatted see below "diskutil list" of that USB:

 

NOTICE that EFI is disk3s2 and Windows data is disk3s1.

Any how this USB should in all intents and purposes work regardless. However in this rig it flops does not work for OpenCore. 

 

/dev/disk3 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *7.8 GB     disk3

   1:       Microsoft Basic Data ⁨WIN10P⁩                  7.8 GB     disk3s1

   2:       Microsoft Basic Data ⁨UEFI_NTFS⁩               1.0 MB     disk3s2

 

 

bobo@bobos-MacBook-Pro ~ % diskutil info disk3s2

   Device Identifier:         disk3s2

   Device Node:               /dev/disk3s2

   Whole:                     No

   Part of Whole:             disk3

 

   Volume Name:               UEFI_NTFS

   Mounted:                   Yes

   Mount Point:               /Volumes/UEFI_NTFS

 

   Partition Type:            Microsoft Basic Data

   File System Personality:   MS-DOS FAT12

   Type (Bundle):             msdos

   Name (User Visible):       MS-DOS (FAT12)

 

   OS Can Be Installed:       No

   Media Type:                Generic

   Protocol:                  USB

   SMART Status:              Not Supported

   Volume UUID:               D6E20E30-608D-3908-86ED-66D0DAD3CB2C

   Disk / Partition UUID:     B5CAB128-AECE-40D3-9415-2A21A467181B

   Partition Offset:          7758358528 Bytes (15153044 512-Byte-Device-Blocks)

 

   Disk Size:                 1.0 MB (1048576 Bytes) (exactly 2048 512-Byte-Units)

   Device Block Size:         512 Bytes

 

   Volume Total Space:        1.0 MB (1028096 Bytes) (exactly 2008 512-Byte-Units)

   Volume Used Space:         895.0 KB (894976 Bytes) (exactly 1748 512-Byte-Units) (87.1%)

   Volume Free Space:         133.1 KB (133120 Bytes) (exactly 260 512-Byte-Units) (12.9%)

   Allocation Block Size:     2048 Bytes

 

   Media OS Use Only:         No

   Media Read-Only:           No

   Volume Read-Only:          No

 

   Device Location:           External

   Removable Media:           Removable

   Media Removal:             Software-Activated

 

   Solid State:               Info not available

bobo@bobos-MacBook-Pro ~ % diskutil info disk3s1

   Device Identifier:         disk3s1

   Device Node:               /dev/disk3s1

   Whole:                     No

   Part of Whole:             disk3

 

   Volume Name:               WIN10P

   Mounted:                   Yes

   Mount Point:               /Volumes/WIN10P

 

   Partition Type:            Microsoft Basic Data

   File System Personality:   NTFS

   Type (Bundle):             ntfs

   Name (User Visible):       Windows NT File System (NTFS)

 

   OS Can Be Installed:       No

   Media Type:                Generic

   Protocol:                  USB

   SMART Status:              Not Supported

   Disk / Partition UUID:     7D22BBB2-381B-4126-A124-6992B1F7DDC4

   Partition Offset:          1048576 Bytes (2048 512-Byte-Device-Blocks)

 

   Disk Size:                 7.8 GB (7757309952 Bytes) (exactly 15150996 512-Byte-Units)

   Device Block Size:         512 Bytes

 

   Volume Total Space:        7.8 GB (7757307904 Bytes) (exactly 15150992 512-Byte-Units)

   Volume Used Space:         5.9 GB (5905399808 Bytes) (exactly 11533984 512-Byte-Units) (76.1%)

   Volume Free Space:         1.9 GB (1851908096 Bytes) (exactly 3617008 512-Byte-Units) (23.9%)

   Allocation Block Size:     4096 Bytes

 

   Media OS Use Only:         No

   Media Read-Only:           No

   Volume Read-Only:          Yes (read-only mount flag set)

 

   Device Location:           External

   Removable Media:           Removable

   Media Removal:             Software-Activated

 

   Solid State:               Info not available

[makk]

Neither of the above worked for me on this rig due to OpenCore config for me not set well.

 

So for this rig, need a proper OpenCore config.  So far not a single one has worked.

Two conditions exist:

1 boot sequence> click on Windows Icon> to initiate>  '\EFI\Microsoft\Boot\bootmgfw.efi' with reboot and direct back to Opencore boot menu.

2 boot sequence> click on Windows Icon>  '\EFI\Microsoft\Boot\bootmgfw.efi' > to initiate> '\Windows\system32\windload.efi'  and get dots then stops and then reboots.

 

in OC config.plist need the following or the boot table gets hosed and no boot situation for any OS's in OpenCore or Clover.

Booter>ProtectSecureBoot = true or yes, 'enabled'  

UEFI> Quirks>RequestBootVarRouting = true or yes, 'enabled'

 

I tried this one which leaves out the SMBIOS information to be passed to Windows, which also left MacOS without them in About This Mac.. LOL! 

Kernel>CustomSMBIOSGuid = true or yes, 'enabled'

 

Whatever Clover does, works. So My Suggestion is to Implement Clover style for OC.. perhaps this would be favorable?  

[makk]

@jpz4085

 

After reviewing the work you have so kindly done for EC and HPET ( I completely forgetting windows needs IRQ for these and the other necessaries )

Duh! arrhhh... too fixated on booting windows like Mac. lol..

 

I suggest having OpenCore in the executable, when selecting the Windows Icon to boot, to bypass OC configs

and allow Windows to boot. A complete allowance of Windows to boot as it needs to. 

Clover somehow does this I think. It allows Windows what it needs to boot and run.

Instead of taking control just let it pass through. This way, no need to set configs in plist that could potentially mess with MacOS's and other OS's.

 

If you could show me how to write these 'else' statements I need tutoring! Apology! and really Thank YOU!