Dual-Boot Options
Last updated
Last updated
Scenario: The user is into professional Esports (Valorant) up to the national level and cannot allow OpenCore multi-booting to have any (potential or real) effect on Windows at all. The Windows install is highly optimized and frequently reinstalled from scratch with very specific graphics and licensing settings. Any appearance of a hardware change after the optimized install can potentially mess things up, which he already experienced with a change to the Nvidia driver settings of the GeForce 1650 Super. On the macOS side requirements are simple: boot into macOS mainly for Final Cut Pro, Logic Pro and Adobe CC. No special requirements for exact Bootcamp like behavior when rebooting. (Getting a dGPU that is optimized for both macOS and Esports with live streaming is still a challenge. Therefore currently on MacOS, only iGPU is used driving two 1080p monitors. A RX 6600 XT would be a good option to fulfill all requirements.)
This sets up Windows in a way which makes it behave like it is installed via Bootcamp on a real Mac.
This boots Windows in a way which makes SMBIOS updates exclusive to macOS only, avoiding a collision with existing Windows activation and custom software.
This boots Windows in a way which is completely separate from OpenCore as rEFInd will have no effect on Windows.
This boots Windows in a way which is completely separate as no other boot loaders are involved.
Each option has advantages and disadvantages. What you choose depends on your use case.
This sets up Windows in a way which makes it behave like it is installed via Bootcamp on a real Mac. macOS and Windows can interact via Startup Disk and Bootcamp utilities to determine the OS to boot next.
Dortania DEFAULTS in Config.plist:
TECHNICAL DETAILS of the OPENCORE DEFAULT MODE
All the modifications applied (to ACPI, NVRAM, SMBIOS, etc.) are supposed to be operating system agnostic, i.e. apply equally regardless of the OS booted. This enables Boot Camp software experience on Windows. ...
Windows may need to be reactivated. To avoid it consider setting SystemUUID to the original firmware UUID. Be aware that it may be invalid on old firmware, i.e., not random. If there still are issues, consider using HWID or KMS38 license or making the use Custom UpdateSMBIOSMode. Other nuances of Windows activation are out of the scope of this document and can be found online.
Remember to always use the latest version of Windows support software from Boot Camp, as versions prior to 6.1 do not support APFS, and thus will not function correctly. (Quotes are from the official OpenCore Reference Manual 0.7.8)
Many other interactions with Windows are mentioned in the Configuration.pdf (OpenCore Reference Manual) when searching the document.
EFFECT OF OPENCORE ON WINDOWS (ACPI)
Xiasl found that four additional SSDT tables (as configured in OpenCore) had been loaded before loading Windows. As these tables all used conditionals like If (_OSI ("Darwin")) they did not have any apparent effect upon Windows. But a custom patched DSDT could cause a BSOD when booting Windows through OpenCore, as reported by users. Theoretically, badly programmed SSDT patches could cause issues as well.
EFFECT OF OPENCORE ON WINDOWS (HWiNFO64)
When examining the differences on Windows using HWiNFO64 the following differences were noted: Windows loaded like it was installed on a Mac in Bootcamp with a mainboard manufacturer name of Acidanthera and Mac serial numbers.
Table 1: Data from HWiNFO64 Reports (obfuscated serials)
This table illustrates how Windows perceives the hardware depending on boot mode:
OpenCore Default Boot
OC-Custom, rEFInd, BIOS Boot
MAINBOARD
Mainboard Manufacturer
Acidanthera
Gigabyte Technology Co., Ltd.
Mainboard Name
Mac-ABBBBBBBBBBBBBB5
B360 M AORUS PRO
Mainboard Version
iMac19,1
x.x
Mainboard Serial Number
C099999999999999F
SYSTEM
System Manufacturer
Acidanthera
Gigabyte Technology Co., Ltd.
Product Name
iMac19,1
B360 M AORUS PRO
Product Version
1.0
Product Serial Number
C099999999999999F
UUID
08888882-7777-4444-3333-3CCCCCCCCCC1
03333334-0000-5555-11111-8DDDDDDDDDD9
Family
iMac
BIOS
BIOS Manufacturer
Acidanthera
American Megatrends Inc.
BIOS Date
12/16/2021
05/17/2019
BIOS Version
1715.80.5.0.0
F3
UEFI BIOS
Capable
Capable
BIOS Start Segment
0
F000
BIOS Size
0 MBytes
16 MBytes
System BIOS Version
5.13
5.13
SYSTEM ENCLORUSE
Case Type
All in One
Desktop
FIRMWARE VERSION INFORMATION
Reference Code - CPU
7.0.49.52
uCode Version
0.0.0.180
TXT ACM version
1.1.0.0
J6B2
Slot Designation
J6B2
J6B2
Slot Type
PCI Express
PCI Express
Slot Usage
Empty
In use
This boots Windows in a way which makes SMBIOS updates exclusive to macOS only, avoiding a collision with existing Windows activation and custom software, but BootCamp specific tools like the OS switcher in Windows might not work any more. When booting macOS through OpenCore, no significant changes were observed.
CHANGES in Config.plist:
TECHNICAL DETAILS of the OPENCORE CUSTOM-MODE
UpdateSMBIOSMode Custom— WriteSMBIOStables to work around firmware overwriting SMBIOS contents at ExitBootServices. ... Note: A side effect of using the Custom approach that it makes SMBIOS updates exclusive to macOS, avoiding a collision with existing Windows activation and custom OEM software but potentially obstructing the operation of Apple-specific tools.CustomSMBIOSGuid Yes— Performs GUID patching for UpdateSMBIOSMode Custom mode. (Quotes are from the official OpenCore Reference Manual 0.7.8)
EFFECT OF OPENCORE CUSTOM-MODE ON WINDOWS (ACPI)
Xiasl found that four additional SSDT tables (as configured in OpenCore) had been loaded before loading Windows. As these tables all used conditionals like If (_OSI ("Darwin")) they did not have any apparent effect upon Windows. But a custom patched DSDT could cause a BSOD when booting Windows through OpenCore, as reported by one user. Theoretically badly programmed SSDT patches could cause issues as well.
EFFECT OF OPENCORE CUSTOM-MODE ON WINDOWS (HWiNFO64)
When examining the differences on Windows using HWiNFO64 the following was noted: Windows appeared to load completely unchanged from loading Windows via rEFInd or via BIOS direct. No Mac specifics leaked into Windows.
See details in Table 1
This boots Windows in a way which is completely separate from OpenCore and rEFInd will have no effect on Windows. When selecting the macOS/OpenCore option in rEFInd, OpenCore is chain-loaded.
Configuration and installation of rEFInd will be discussed in the next Chapter.
EFFECT OF rEFInd ON WINDOWS (ACPI)
Xiasl found no additional SSDT tables, as rEFInd makes no such changes.
EFFECT OF rEFInd ON WINDOWS (HWiNFO64)
When examining the differences on Windows using HWiNFO64 the following was noted: Windows loaded completely unchanged from loading Windows via BIOS direct, as rEFInd makes no changes. No Mac specifics are able to leak into Windows.
See details in Table 1
This boots Windows in a way which is completely separate as no other boot loaders are involved. OpenCore is on the macOS drive and will only load when its disk is selected.
EFFECT OF BIOS ON WINDOWS (ACPI & HWiNFO64)
Since Windows loads via BIOS directly, the macOS disk has no effect at all upon the Windows ACPI tables or upon the Windows configuration. No Mac specifics are able to leak into Windows.
See details in Table 1
For the initially described Esports Gaming & Final Cut Pro Editing use case, only the rEFInd Boot or the BIOS Boot Menu options are completely safe. But for most people booting Windows via OpenCore, Option 1 or 2 are the recommended choices.
If you want the BootCamp experience with Windows, use Option 1, as intended by the OpenCore developers. No changes to your Config.plist are necessary. You will be able to use the Apple BootCamp utility and the Startup Disk to switch between Windows and macOS. Windows might need to be re-activated or may be difficult to activate. Some Windows apps might require your action due to the apparent hardware change.
If you want Windows (largely) unaffected by OpenCore, use Option 2 with Custom Mode. Make the required changes to your Config.plist and check that none of your SSDTs or Quirks impact Windows. Some of the BootCamp style integration between OpenCore and Windows might be lost.
If you want to be absolutely sure that even a misconfigured OpenCore cannot effect your Windows configuration, use Option 3 with rEFInd and follow the installation guide in the next chapter. The macOS StartUp Disk setting will no be able to influence which operating system is started by rEFInd, but for example different versions of macOS booted by OpenCore on the same computer can still be set via StartUp disk.
If you don't want to bother with installing rEFInd, but still want to be absolutely sure that even a misconfigured OpenCore cannot affect your Windows configuration, use Option 4 with the BIOS Boot Menu. You might forget to press the correct key on time and boot to the wrong OS. In some setups with iGPU and a macOS disabled dGPU, this option is quite cumbersome and prone to user error.
Except where otherwise noted, content on this site is licensed under the Creative Commons — Attribution-NonCommercial 4.0 International — CC BY-NC 4.0 license. Attribution by link to chriswayg · GitHub.
