Jump to content
19 posts in this topic

Recommended Posts

(These instructions are already posted on various Internet sites but from time to time they are requested by a user so I publish them in the guides).
 
To add an entry in Misc> Entries of config.plist you need to know the path to the operating system boot loader.

For a Windows disk, you must know the path to the BOOTX64.EFI file located in the EFI\BOOT folder into the EFI partition. This path must be in EFI format and must match the PCI device where BOOTX64.EFI is located.

 

The simplest method to find out the path the is using the UEFI Shell (OpenShell.efi), an OpenCore tool that is usually displayed in the start menu. Selecting UEFI Shell, runs a shell in which we can write commands.

 

On startup it displays a list of all detected EFI paths, they may have different prefixes:

  • BLKX: they are all scanned disks / partitions.
  • FSX: these are all file systems that can be browsed.
  • PciRoot (0x0) / Pci (AxB, CxD) / Sata (or Nvme)... are disk types (SATA AHCI or NVMe).
  • HD (X, GPT, <PARTUUID>, ...) or HD (X, MBR) are partitions where X is a number, GPT / MBR is the partitioning scheme followed by the partition identifier PARTUUID.

 

To find which of those paths is the macOS EFI partition you must do so:
 
1. FSX command: (where X is a number starting from zero) places the prompt on that partition. For example, typing FS0: (note colon) the prompt is placed in the root directory of FS0.
 
2. To find out if it is what we are looking for, use the ls command to list files and folders (dir also works) and cd to change to a directory (cd.. go up one level in the directory). If there is an EFI folder, you have to enter it (cd EFI) to find out if it is the Windows folder (EFI> Microsoft> Boot). If there is no EFI folder or the one there is is not from Windows, we move to the next device with FS1: and repeat the process. Sometimes it is necessary to enter several devices to find the correct one (FS0:, FS1:, FS2:, FS3:, etc.).

shell2.png.6f8d9b00206fe8fee7cc30f896d4aa57.png
 
3. Once the Windows EFI folder is located, its FSX number must be noted.
 
4. Run map> map_table.txt. This creates a text file map_table.txt where the prompt was located when using the map command.
 
5. Exit the Shell with exit and restart to enter macOS.
 
Back on macOS, mount the volume that contains the map_table.txt file:

 

diskutil list
sudo diskutil mount disk0s1

(change disk0s1 by the real volume).
 
Open map_table.txt with a text editor and locate the EFI path of the FSX device you noted in a previous step.

The path to the Windows boot loader consists of 2 parts, an EFI path to the partition with the EFI folder + a path to the boot loader within the EFI folder. We already know that the path to the boot loader is EFI\BOOT\BOOTX64.EFI. The EFI path to the EFI partition is taken from map_table.txt by copying the line that corresponds to the Windows EFI folder.
 
The line with the EFI path looks like this (example):

PciRoot(0x0)/Pci(0x1D,0x0)/Pci(0x0,0x0)/NVMe(0x1,18-CC-1C-49-8B-44-1B-00)/HD(1,GPT,DF3F0348-A4F8-4A34-9C86-963B0E98F2BE,0x800,0x54747)

The path to the boot loader is like this:

EFI\BOOT\BOOTX64.EFI

 You have to join both paths by inserting a forward slash / and a backslash \ between the 2 strings:

PciRoot(0x0)/Pci(0x1D,0x0)/Pci(0x0,0x0)/NVMe(0x1,18-CC-1C-49-8B-44-1B-00)/HD(1,GPT,DF3F0348-A4F8-4A34-9C86-963B0E98F2BE,0x800,0x54747)/\EFI\BOOT\BOOTX64.EFI

This is the path to be entered in the Path key of the custom entry in Misc> Entries in the config.plist file. The custom entry would look like this (example):

        <key>Entries</key>
        <array>
            <dict>
                <key>Arguments</key>
                <string></string>
                <key>Auxiliary</key>
                <false/>
                <key>Comment</key>
                <string>Windows 10</string>
                <key>Enabled</key>
                <true/>
                <key>Flavour</key>
                <string>Windows10:Windows</string>
                <key>Name</key>
                <string>Windows</string>
                <key>Path</key>
                <string>PciRoot(0x0)/Pci(0x1D,0x0)/Pci(0x0,0x0)/NVMe(0x1,18-CC-1C-49-8B-44-1B-00)/HD(1,GPT,DF3F0348-A4F8-4A34-9C86-963B0E98F2BE,0x800,0x54747)/\EFI\BOOT\BOOTX64.EFI </string>
                <key>TextMode</key>
                <false/>
            </dict>
        </array>

Note1: Notice that there are no spaces in the Path key.

 

Note2: Notice that I have written the path to the Windows boot loader like this:

EFI\BOOT\BOOTX64.EFI 

as it is in OpenCore's Sample.plist. But there is a backup copy of BOOTX64.EFI in EFI\Microsoft\Boot named bootmgfw.efi, so we can also write the Windows boot loader path in this way:

EFI\Microsoft\Boot\bootmgfw.efi

 

Edited by miliuco
  • Like 3
  • Thanks 4
  • 1 year later...

Thanks! Just got a chance to read this guide. 

ScanPolicy (Integer) = 2687747, I guess this will hide Windows.

 

Per your guide, I don't understand #4.  Example at FS0:\EFI\> type Run map or type map_table.txt

 

Edited by loganMac
  • Like 1
  • 11 months later...

thanks been awhile,  question: @antuneddu

 

the flavours part: what to put in?

 

I got it.

 

Windows11Pro:Windows

Windows10Pro:Windows

 

I have been able to have 3 Windows boot icons on OpenCore.

 

the 1st one boots into the Windows dual boot menu which has both plus 1.

Windows 11 Pro

Windows 10 Pro

Macrium Reflect

 

then 2 icons besides that

 Windows11Pro

 Windows10Pro

then all the rest of the icons such as UEFI Shell, NVRAM RESET, Clean Nvram, Shutdown....

 

in a single line:>   Windows Windows11Pro Windows10Pro CleanNvam UEFI Shell Shutdown .....

 

On the side, now if we can get RTX Geforce to run on the hacks that would be super cool.

 

Thanks for keeping this post up!

 

Have good week you two

Edited by makk
  • Like 2
  • 2 months later...

Have done the dortania config and root directory efi files, but not detecting all installs.

 

Have invoked the shell for PCI entries and added custom entries that failed to display and boot as intended.

 

However, the original question was, what does open core search for, and where, in detecting a linux installation.

 

Thanks for suggestions, but would appreciate if someone could specifically answer this question.

  • 1 year later...

@webipsum  

 

Yes, problem solved.
I've always used custom entries for various reasons, like having Windows in the GUI after macOS, customizing the icon, the name...
This time, however, after installing Win 25h2 (Dev Channel).


It didn't work anymore. I won't list the tests I did to get it to work, I thought something had changed in the latest Win.

 

Simply by starting with Clover, I noticed that the path saved during the shell with OC was different and incomplete.

 

This is what Clover showed:

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0xFFFF,0x0)/HD(1,GPT,BD026231-7FDA-4422-B556-236278080610,0x800,0x64800)

 

This is what was obtained from the Shell

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0xFFFF,0x0)/HD(1,GPT,BD026231-7FDA-4422-B556-236278080610)

 

I simply copied what Clover showed as the Path and boom ! Windows booted from OC again.

 

But I still had a question: why had Shell saved the incomplete Path?

 

I found the answer by replacing OpenShell.efi 1.0.5 with one recovered from an old EFI OC 0.8.3.

 

Well, the old OpenShell.efi saves the complete Path, while the new one doesn't.

 

I don't know if I should file a Bugtracker issue or not.

 

Spoiler

IMG_20250728_170939.png.d3d75556c9949d86e7adf84961ad9ca5.png

 

  • Like 2
30 minutes ago, Anto65 said:

This is what was obtained from the Shell

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0xFFFF,0x0)/HD(1,GPT,BD026231-7FDA-4422-B556-236278080610)

How big is the openshell.efi file you used in the OC Tools folder?
1,1MB ou 1,2MB?
 

Edited by webipsum
1,1MB ou 1,2MB?
3 hours ago, Anto65 said:

I'll answer you here, so at least Cyberdevs doesn't frustrate us

I don't appreciate this, not even as a joke, I've spent two hours to clean up the mess in Tahoe topic not to mention the countless hours (we spend) to keep this forum clean from spams and other unrelated junk so you guys have a clean and organized forum, so yeah I don't appreciate this at all!

  • Like 4
  • Thanks 2
18 hours ago, Cyberdevs said:

I don't appreciate this, not even as a joke, I've spent two hours to clean up the mess in Tahoe topic not to mention the countless hours (we spend) to keep this forum clean from spams and other unrelated junk so you guys have a clean and organized forum, so yeah I don't appreciate this at all!

 

Thank you @Cyberdevs for caring those situations.

 

And for all, as we're all grew up guys, just remember one of the Forum Rules: 

 

"No Flaming. This includes racism, threatening, personal attacks, victimization or hateful content. Retaliation will not be tolerated either; if a member has broken a rule, please use the report feature on the forum and the staff will deal with the situation appropriately."

  • Like 4

hello  all

 

sorry   for my english  noy my natural language ..
 

Having encountered two problems, I've come across this thread, and perhaps someone can offer some advice.
A few years ago, using only Clover, I was able to customize the graphical menu. I've practically forgotten everything since using OpenCore as my launcher.

As you can see on the screen, I was able to retrieve the path to customize Windows 11. first problem for the icon, it obviously doesn't work. The second problem is that I want hide the icon and the initial Windows text from OpenCore. I remember that you have to use ScanPolicy and probably other options to select in OCAT.

 

ty by advance

 

 

Spoiler

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,64277B47-6E9C-4969-A7BA-D6B56C671171,0x800,0x64000)/\\EFI\\Microsoft\\Boot\\bootmgfw.efi
PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,64277B47-6E9C-4969-A7BA-D6B56C671171,0x800,0x64000)/\\EFI\\Microsoft\\Boot\\bootx64.efi.icns

 

image.png.f853e68ef3254646f616213be4700ad1.png

 

???

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,64277B47-6E9C-4969-A7BA-D6B56C671171,0x800,0x64000)/\\EFI\\Microsoft\\Boot\\bootmgfw.efi

 

It should be like this

 

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,64277B47-6E9C-4969-A7BA-D6B56C671171,0x800,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi

 

 

  • Like 1
  • Thanks 1

Hello
In my first copy and paste, I didn't check, but I'm using the correct parameters and no Windows icon, so I'll have to dig deeper, but I don't know which way to go, haha.

Thanks for the info.  and  good  weekend 

Best regards

 

Spoiler

Capturedcran2025-08-0107_23_54.thumb.png.02c79c252f9d7a2ea9e0dae7bad82878.png

Capturedcran2025-08-0107_25_33.thumb.png.463f57a02c946b0bcbac8dd55fe0277a.png

 

image.png.ccc9b758b4587e28c2d0bf3cb69297c9.png

 

  • Like 1

Rename the icon within the theme , as you declared it in "Flavor."
In your case,
Windows 11 Pro.icns

 

if you want use Windows-11-Pro-24h2.icns   Screenshot2025-08-01alle10_35_55.png.60e7aa5d4a32bc05f437a1d9aae2d980.png

 

Then 

 

Spoiler

<dict>
                <key>Arguments</key>
                <string></string>
                <key>Auxiliary</key>
                <false/>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>Flavour</key>
                <string>Windows-11-Pro-24h2:Windows</string>
                <key>Name</key>
                <string>Windows-11-Pro-24h2</string>
                <key>Path</key>
                <string>PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0xFFFF,0x0)/HD(1,GPT,BD026231-7FDA-4422-B556-236278080610,0x800,0x64800)/\EFI\Microsoft\BOOT\bootmgfw.efi</string>
                <key>TextMode</key>
                <false/>
            </dict>
 

 

Edited by Anto65
  • Like 1
  • Thanks 1
×
×
  • Create New...