Coffee Lake

Starting Point

You'll want to start with the sample.plist that OpenCorePkg provides you and rename it to config.plist. Next, open up your favourite XML editor like ProperTree and we can get to work.

Users of ProperTree will also get the benifit of running the Snapshot function which will add all the Firmware drivers, kexts and SSDTs into your config.plist

Do note that images will not always be the most up-to date so please read the text below them.



The above ACPI patch is only an example, please read below for more info


This is where you'll add SSDT patches for your system, these are most useful for laptops and OEM desktops but also common for USB maps, disabling unsupported GPUs and such.

For us we'll need a couple SSDTs to bring back functionality that Clover provided:


    • Allows for native CPU power managment, Clover alternative would be under Acpi -> GenerateOptions -> PluginType. Do note that this SSDT is made for systems where AppleACPICPU attaches CPU0, though some ACPI tables have theirs starting at PR00 so adjust accordingly.


    • Fixes USB power and correct your EC devices, needed for all Catalina users.


    • This is the 300 series RTC patch, required for most B360, B365, H310, H370, Z390 which prevent systems from booting macOS. Aternative is SSDT-RTC0 for when AWAC SSDT doesn't work(Z370 users do not apply)

For those having troubles understanding the SSDTs regarding plugin type and EC can use CoprNewt's SSDTTime to properly setup your SSDT. The rest of the SSDTs can be compiled with MaciASL, don't forget that ompiled SSDTs have a .aml extension(Assembled).


This drops certain ACPI tabes from loading, for us we can ignore this


This section allows us to dynamically modify parts of the ACPI (DSDT, SSDT, etc.) via OpenCore. macOS usually does not care much about ACPI, so in the majority of the cases, you need to do nothing here.

  • Comment

    • Name of patch

  • Count

    • How many time the patch is applied, 0 will apply to all instances

  • Enabled

    • Self explanitory, enables or disables the patch

  • Find

    • The original name in ACPI

  • Replace

    • The new name in ACPI, length must match original

Quirk: Settings for ACPI.

  • FadtEnableReset: NO

    • Enable reboot and shutdown on legacy hardware, not recommended unless needed

  • NormalizeHeaders: NO

    • Cleanup ACPI header fields, only relevant for macOS High Sierra 10.13

  • RebaseRegions: NO

    • Attempt to heuristically relocate ACPI memory regions, not needed unless custom DSDT is used.

  • ResetHwSig: NO

    • Needed for hardware that fail to maintain hardware signature across the reboots and cause issues with waking from hibernation

  • ResetLogoStatus: NO

    • Workaround for OEM Windows logo not drawing on systems with BGRT tables.



This section is dedicated to quirks relating to boot.efi patching with FwRuntimeServices, the replacement for AptioMemoryFix.efi


This section is allowing devices to be passthrough to macOS that are generally ignored, most users can ignore this section.


  • AvoidRuntimeDefrag: YES

    • Fixes UEFI runtime services like date, time, NVRAM, power control, etc

  • DevirtualiseMmio: YES

    • Reduces Stolen Memory Footprint, expands options for Slide=N values and generally useful for most firmwares

  • DisableSingleUser: NO

    • Disables use of Cmd+S and -s, this is closer to the behaviour of T2 based machines

  • DisableVariableWrite: NO

    • Needed for systems with non-functioning NVRAM like Z390 and such

  • DiscardHibernateMap: NO

    • Reuse original hibernate memory map, only needed for certain legacy hardware

  • EnableSafeModeSlide: YES

    • Allows for slide values to be used in Safemode

  • EnableWriteUnprotector: YES

    • Removes write protection from CR0 register during their execution

  • ForceExitBootServices: NO

    • Ensures ExitBootServices calls succeeds even when MemoryMap has changed, don't use unless necessary)

  • ProtectCsmRegion: NO

    • Needed for fixing artifacts and sleep-wake issues, AvoidRuntimeDefrag resolves this already so avoid this quirk unless necessary

  • ProvideCustomSlide: YES

    • If there's a conflicting slide value, this option forces macOS to use a pseudo-random value. Needed for those receiving Only N/256 slide values are usable! debug message

  • SetupVirtualMap: YES

    • Fixes SetVirtualAddresses calls to virtual addresses

  • ShrinkMemoryMap: NO

    • Needed for systems with large memory maps that don't fit, don't use unless necessary



Add: Sets device properties from a map.

This section is set up via Headkaze's Intel Framebuffer Patching Guide and applies only one actual property to begin, which is the ig-platform-id. The way we get the proper value for this is to look at the ig-platform-id we intend to use, then swap the pairs of hex bytes.

If we think of our ig-plat as 0xAABBCCDD, our swapped version would look like DDCCBBAA

The two ig-platform-id's we use are as follows:

  • 0x3E9B0007 - this is used when the iGPU is used to drive a display

    • 07009B3E when hex-swapped

  • 0x3E920003 - this is used when the iGPU is only used for compute tasks and doesn't drive a display

    • 0300923E when hex-swapped

Worth noting that for 10.12 -> 10.13.5, you would need to fake the iGPU to the same values in the Kaby Lake guide, as this was before native Coffee Lake iGPU showed up.

We also add 2 more properties, framebuffer-patch-enable and framebuffer-stolenmem. The first enables patching via WhateverGreen.kext, and the second sets the min stolen memory to 19MB. This is usually unnecessary, as this can be configured in BIOS.

I added another section as well that shows a fake device-id for the i3-8100's UHD 630. This has a different device id than the UHD 630 found on the 8700k, for instance, (3e918086 vs 3e928086 ).

For this - we follow a similar procedure as our above ig-platform-id hex swapping - but this time, we only work with the first two pairs of hex bytes. If we think of our device id as 0xAABB0000, our swapped version would look like 0xBBAA0000. We don't do anything with the last 2 pairs of hex bytes.

The device-id fake is set up like so:

  • 0x3e920000 - this is the device id for the UHD 630 found on an 8700k

    • 923e0000 when hex swapped

Note: FakeID is only required for High Sierra, Mojave doesn't require this

PciRoot(0x0)/Pci(0x1f,0x3) -> Layout-id

  • Applies AppleALC audio injection, you'll need to do your own research on which codec your motherboard has and match it with AppleALC's layout. AppleALC Supported Codecs.

Keep in mind that some motherboards have different device locations, you can find yours by either examining the device tree in IOReg or using gfxutil. Please note that ADR for HDAS/HDEF is 0x001F0003 and Path = PciRoot(0x0)/Pci(0x1f,0x3), PciRoot(0x0)/Pci(0x1b,0x0) is generally for haswell and earlier. You can find your audio path with the following(Do note not all audio controllers are called HDEF, sometimes being known as HDAS, AZAL, HDAU and such):

path/to/gfxutil -f HDEF

Do note that layout-id is a Data value meaning you will need to convert from Number to HEX so Layout=5 would be interpreted as <05000000> and Layout=11 would be <0B000000>

Fun Fact: The reason the byte order is swapped is due to Endianness, specifcally Little Endians that modern CPUs use for ordering bytes. The more you know!

Block: Removes device properties from map, for us we can ignore this



Add: Here's where you specify which kexts to load, order matters here so make sure Lilu.kext is always first! Other higher priority kexts come after Lilu such as VirtualSMC, AppleALC, WhateverGreen, etc. Please see the Kext sectionf or what kexts we recommend.

  • BundlePath

    • Name of the kext

    • ex: Lilu.kext

  • Enabled

    • Self explaitroy, either enables or diables the kext

  • Executableath

    • Path to the actual executable hidden within the kext, you can see what path you kext has by right clicking and selecting Show Package Contents. Generally they'll be Contents/MacOS/Kext but some have kexts hiddin within under Plugin folder. Do note that Plist only kexts do not need this filled in.

    • ex: Contents/MacOS/Lilu

  • PlistPath

    • Path to the info.plist hidden within the kext

    • ex: Contents/Info.plist

Emulate: Needed for spoofing unsupported CPUs like Pentiums and Celerons

  • CpuidMask: When set to Zero, original CPU bit will be used

    • <Clover_FCPUID_Extended_to_4_bytes_Swapped_Bytes> | 00 00 00 00 | 00 00 00 00 | 00 00 00 00

    • ex: CPUID 0x0306A9 would be A9 06 03 00 | 00 00 00 00 | 00 00 00 00 | 00 00 00 00

  • CpuidData: The value for the CPU spoofing

    • FF FF FF FF | 00 00 00 00 | 00 00 00 00 | 00 00 00 00

    • Swap 00 for FF if needing to swap with a longer value

Block: Blocks kexts from loading. Sometimes needed for disabling Apple's trackpad driver for some laptops.

Patch: Patches both the kernel and kexts (this is where you would add AMD CPU patches).


  • AppleCpuPmCfgLock: NO

    • Only needed when CFG-Lock can't be disabled in BIOS, Clover counterpart would be AppleIntelCPUPM. Please verify you can disable CFG-Lock, most systems won't boot with it on so requiring use of this quirk

  • AppleXcpmCfgLock: NO

    • Only needed when CFG-Lock can't be disabled in BIOS, Clover counterpart would be KernelPM. Please verify you can disable CFG-Lock, most systems won't boot with it on so requiring use of this quirk

  • AppleXcpmExtraMsrs: NO

    • Disables multiple MSR access needed for unsupported CPUs like Pentiums and certain Xeons

  • CustomSMBIOSGuid: NO

    • Performs GUID patching for UpdateSMBIOSMode Custom mode. Usually relevant for Dell laptops

  • DisableIOMapper: YES

    • Needed to get around VT-D if either unable to disable in BIOS or needed for other operating systems

  • ExternalDiskIcons: YES

    • External Icons Patch, for when internal drives are treated as external drives but can also make USB drives internal. For NVMe on Z87 and below you just add built-in property via DeviceProperties.

  • LapicKernelPanic: NO

    • Disables kernel panic on AP core lapic interrupt, generally needed for HP systems. Clover equivalent is Kernel LAPIC

  • PanicNoKextDump: YES

    • Allows for reading kernel panics logs when kernel panics occurs

  • PowerTimeoutKernelPanic: YES

    • Helps fix kernel panics relating to power changes with Apple drivers in macOS Catalina, most notably with digital audio.

  • ThirdPartyTrim: NO

    • Enables TRIM, not needed for NVMe but AHCI based drives may require this. Please check under system report to see if your drive supports TRIM

  • XhciPortLimit: YES

    • This is actually the 15 port limit patch, don't rely on it as it's not a guaranteed solution for fixing USB. Please create a USB map when possible.

The reason being is that UsbInjectAll reimplements builtin macOS functionality without proper current tuning. It is much cleaner to just describe your ports in a single plist-only kext, which will not waste runtime memory and such



Boot: Settings for boot screen (leave as-is unless you know what you're doing)

  • HibernateMode: None

    • Best to avoid hibernation with hackintoshes all together

  • HideSelf: YES

    • Hides the EFI partition as a boot option in OC's boot picker

  • PollAppleHotKeys: YES

    • Allows you to use Apple's hot keys during boot, depending on the firmware you may need to use UsbKbDxe.efi instead of OpenCore's builtin support. Do note that if you can select anything in OC's picker, disabling this option can help. Popular commands:

      • Cmd+V: Enables verbose

      • Cmd+Opt+P+R: Cleans NVRAM

      • Cmd+R: Boots Recovery partition

      • Cmd+S: Boot in Singleuser mode

      • Option/Alt: Shows boot picker when ShowPicker set to NO, alternative is ESC key

  • Timeout: 5

    • This sets how long OpenCore will wait until it automatically boots from the default selection

  • ShowPicker: YES

    • Shows OpenCore's UI, needed for seeing your available drives or set to NO to follow default option

  • UsePicker: YES

    • Uses OpenCore's default GUI, set to NO if you wish to use a different GUI

Debug: Debug has special use cases, leave as-is unless you know what you're doing.

  • DisableWatchDog: YES (Useful for when OpenCore is stalling on something while booting, can also help for early macOS boot issues)

Security: Security is pretty self-explanatory.

  • AllowNvramReset: YES

    • Allows for NVRAM reset both in the boot picker and when pressing Cmd+Opt+P+R

  • RequireSignature: NO

    • We won't be dealing vault.plist so we can ignore

  • RequireVault: NO

    • We won't be dealing vault.plist so we can ignore as well

  • ScanPolicy: 0

  • 0 allows you to see all drives available, please refer to Security section for furthur details

Tools Used for running OC debugging tools like clearing NVRAM

  • Name

    • Name shown in OpenCore

  • Enabled

    • Self explanitory, enables or disables

  • Path

    • Path to file after the Tools folder

    • ex: Shell.efi

Entires: Used for specifying iregular boot paths that can't be found naturally with OpenCore

  • Name

    • Name shown in boot picker

  • Enabled

    • Self explanitory, enables or disables

  • Path

    • PCI route of boot drive, can be found with the OpenCoreShell and the map command

    • ex: PciRoot(0x0)/Pci(0x1D,0x4)/Pci(0x0,0x0)/NVMe(0x1,09-63-E3-44-8B-44-1B-00)/HD(1,GPT,11F42760-7AB1-4DB5-924B-D12C52895FA9,0x28,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi



Add: 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 (Booter Path, majority can ignore but )

  • UIScale:

    • 01: Standard resolution(Clover equivalent is 0x28)

    • 02: HiDPI (generally required for FileVault to function correctly on smaller displays, Clover equivalent is 0x2A)

7C436110-AB2A-4BBB-A880-FE41995C9F82 (System Integrity Protection bitmask)

  • boot-args:

    • -v - this enables verbose mode, which shows all the behind-the-scenes text that scrolls by as you're booting instead of the Apple logo and progress bar. It's invaluable to any Hackintosher, as it gives you an inside look at the boot process, and can help you identify issues, problem kexts, etc.

    • dart=0 - this is just an extra layer of protection against Vt-d issues, keep in mind this requires SIP to be disabled

    • debug=0x100 - this disables macOS's watchdog which helps prevents a reboot on a kernel panic. That way you can (hopefully) glean some useful info and follow the breadcrumbs to get past the issues.

    • keepsyms=1 - this is a companion setting to debug=0x100 that tells the OS to also print the symbols on a kernel panic. That can give some more helpful insight as to what's causing the panic itself.

    • shikigva=40 - this flag is specific for Nvidia users. It enables a few Shiki settings that do the following (found here):

      • 8 - AddExecutableWhitelist - ensures that processes in the whitelist are patched.

      • 32 - ReplaceBoardID - replaces board-id used by AppleGVA by a different board-id. Do note that this generally needed for systems running Nvidia GPUs

  • csr-active-config: Settings for SIP, generally recommended to manually change this within Recovery partition with csrutil via the recovery partition

csr-active-config is set to E7030000 which effectively disables SIP. You can choose a number of other options to enable/disable sections of SIP. Some common ones are as follows:

  • 00000000 - SIP completely enabled

  • 30000000 - Allow unsigned kexts and writing to protected fs locations

  • E7030000 - SIP completely disabled

  • nvda_drv: <>

  • For enabling Nvidia WebDrivers, set to 31 if running a Maxwell or Pascal GPU. This is the same as setting nvda_drv=1 but instead we translate it from text to hex, Clover equivalent is NvidiaWeb. AMD and Intel users should leave this area blank.

  • prev-lang:kbd: <>

  • Needed for non-latin keyboards in the format of lang-COUNTRY:keyboard, recommeneded to keep blank though you can specify it:

Block: Forcibly rewrites NVRAM variables, do note that Add will not overwrite values already present in NVRAM so values like boot-args should be left.

LegacyEnable: NO

  • Allows for NVRAM to be stored on nvram.plist, needed for systems without native NVRAM


  • Used for assigning NVRAM variables, used with LegacyEnable set to YES



For setting up the SMBIOS info, we'll use acidanthera's macserial application.

To get the SMBIOS info generated with macserial, you can run it with the -a argument (which generates serials and board serials for all supported platforms). You can also parse it with grep to limit your search to one SMBIOS type.

For this Coffee Lake example, I chose the iMac18,1 SMBIOS - this is done intentionally for compatibility's sake. There are two main SMBIOS used for Coffee Lake:

  • iMac18,1 - this is used for computers utilizing the iGPU for displaying.

  • iMac18,3 - this is used for computers using a dGPU for displaying, and an iGPU for compute tasks only.

    • Note: While iMac19,1 and iMac19,2 are a closer match, these SMBIOS are not compatible with versions of macOS older than 10.14.5 and not all fixes are compatible with them(ie: USBInjectAll)

To get the SMBIOS info generated with macserial, you can run it with the -a argument (which generates serials and board serials for all supported platforms). You can also parse it with grep to limit your search to one SMBIOS type.

With our iMac18,1 example, we would run macserial like so via the terminal:

macserial -a | grep -i iMac18,1

Which would give us output similar to the following:

iMac18,1 | C02T8SZNH7JY | C02707101J9H69F1F
iMac18,1 | C02VXBYDH7JY | C02753100GUH69FCB
iMac18,1 | C02T7RY6H7JY | C02706310GUH69FA8
iMac18,1 | C02VD07ZH7JY | C02737301J9H69FCB
iMac18,1 | C02TQPYPH7JY | C02720802CDH69FAD
iMac18,1 | C02VXYYVH7JY | C02753207CDH69FJC
iMac18,1 | C02VDBZ0H7JY | C02737700QXH69FA8
iMac18,1 | C02VP0H6H7JY | C02746300CDH69FJA
iMac18,1 | C02VL0W9H7JY | C02743303CDH69F8C
iMac18,1 | C02V2NYMH7JY | C02728600J9H69FAD

The order is Product | Serial | Board Serial (MLB)

The iMac18,1 part gets copied to Generic -> SystemProductName.

The Serial part gets copied to Generic -> SystemSerialNumber.

The Board Serial part gets copied to Generic -> MLB.

We can create an SmUUID by running uuidgen in the terminal (or it's auto-generated via CorpNewt's GenSMBIOS script) -and that gets copied to Generic -> SystemUUID.

We set Generic -> ROM to either an Apple ROM (dumped from a real Mac), your NIC MAC address, or any random MAC address (could be just 6 random bytes, for this guide we'll use 11223300 0000)

Automatic: YES

  • Generates PlatformInfo based on Generic section instead of DataHub, NVRAM, and SMBIOS sections

  • SpoofVendor: YES

    • Swaps vendor field for Acidanthera, generally not safe to use Apple as a vendor in most case

      UpdateDataHub: YES

  • Update Data Hub fields


  • Update NVRAM fields


  • Updates SMBIOS fields

UpdateSMBIOSMode: Create

  • Replace the tables with newly allocated EfiReservedMemoryType, use Custom on Dell laptops requiring CustomSMBIOSGuid quirk



ConnectDrivers: YES

  • Forces .efi drivers, change to NO will automatically connect added UEFI drivers. This can make booting slightly faster, but not all drivers connect themselves. E.g. certain file system drivers may not load.

Drivers: Add your .efi drivers here

Input: Related to boot.efi keyboard passthrough used for for FileVault and Hotkey support

  • KeyForgetThreshold: 5

    • The delay between each key input when holding a key down, for best results use 5 milliseconds

  • KeyMergeThreshold: 2

    • The lengh of time that a key will be registered before resetting, for best results use 2 milliseconds

  • KeySupport: YES

    • Enables OpenCore's built in key support, do not use with UsbKbDxe.efi

  • KeySupportMode: Auto

    • Keyboard translation for OpenCore

  • KeySwap: NO

    • Swaps Option and Cmd key

  • PointerSupport: NO

    • Used for fixing broken pointer support, commonlu used for Z87 Asus boards

  • PointerSupportMode:

    • Specifies OEM protocol, currently only supports Z87 and Z97 ASUS boards so leave blank

  • TimerResolution: 50000

    • Set architecture timer resolution, Asus boards use 60000 for the interface

Protocols: (Most values can be ignored here as they're meant for real Macs/VMs)

  • ConsoleControl: YES

    • Replaces Console Control protocol with a builtin version, set to YES otherwise you may see text output during booting instead of nice Apple logo. Required for most APTIO firmware

  • FirmwareVolume: NO

    • Fixes UI regarding Filevault, set to YES for better FileVault compatibilty

  • HashServices: NO

    • Fixes incorrect cusor size when running FileVault, set to YES for better FileVault compatibilty

  • UnicodeCollation: NO

    • Some older firmware have broken unicode collation, fixes UEFI shell compatibility on these systems(generally IvyBridge and older)


  • AvoidHighAlloc: NO

    • Workaround for when te motherboard can't properly access higher memory in UEFI Boot Services. Avoid unless necessary(affected models: GA-Z77P-D3 (rev. 1.1))

  • ExitBootServicesDelay: 0

    • Only required for very specific use cases like setting to 5 for ASUS Z87-Pro running FileVault2

  • IgnoreInvalidFlexRatio: NO

    • Fix for when MSR_FLEX_RATIO (0x194) can't be disabled in the BIOS, required for all pre-skylake based systems

  • IgnoreTextInGraphics: NO

    • Fix for UI corruption when both text and graphics outputs happen, set to YES with SanitiseClearScreen also set to YES for pure Apple Logo(no verbose screen)

  • ProvideConsoleGop: YES

    • Enables GOP(Graphics output Protcol) which the macOS bootloader requires for console handle

  • ReleaseUsbOwnership: NO

  • Releases USB controller from firmware driver, avoid unless you know what you're doing. Clover equivalent is FixOwnership

  • RequestBootVarRouting: YES

    • Redirects AptioMemeoryFix from EFI_GLOBAL_VARIABLE_GUID to OC\_VENDOR\_VARIABLE\_GUID. Needed for when firmware tries to delete boot entries and is recommended to be enabled on all systems for correct update installation, Startup Disk control panel functioning, etc.

  • ReplaceTabWithSpace: NO

    • Depending on firmware, some system may need this to properly edit files in the UEFI shell when unable to handle Tabs. This swaps it for spaces instead but majority can ignore it but do note that ConsoleControl set to True may be needed

  • SanitiseClearScreen: YES

    • Fixes High resolutions displays that display OpenCore in 1024x768, recommened for user with 1080P+ displays

  • ClearScreenOnModeSwitch: NO

    • Needed for when half of the previously drawn image remains, will force black screen before switching to TextMode. Do note that ConsoleControl set to True may be needed

Cleaning up

And now you're ready to save and place it into your EFI.

For those having booting issues, please make sure to read the Troubleshooting section first and if your questions are still unanswered we have plenty of resources at your disposal: