Skip to content
AptioFixPkg drivers to workaround macOS compatibility with APTIO UEFI FW
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
Application Adapt TRB GUIDs to new EfiPkg convention. Feb 8, 2019
Include Reworked GOP protocol installation to be Apple-only Mar 14, 2019
Platform Fix DEBUG build Mar 14, 2019
.gitignore Switch to UDK2018 May 23, 2018
.travis.yml Fix DEBUG build Mar 14, 2019
AptioFixPkg.dec Reimplement AptioInputFix Sep 9, 2018
AptioFixPkg.dsc DSC: Declare missing LibraryClasses Apr 9, 2019
LICENSE.txt Update copyright information. Oct 11, 2018
macbuild.tool Build: Remove local mtoc copy Apr 13, 2019


Build Status Scan Status

AptioFixPkg drivers fixing certain UEFI APTIO Firmware issues relevant to booting macOS.

WARNING: The code in this repository should be considered to be a proof of concept draft quality, and is only intended to be used as a software implementation guide. Due to the lack of time, this codebase may contain partially understood reverse-engineering samples, almost no documentation, hacks, and absolute ignorance of EDK2 codestyle.


Reference driver to shim AMI APTIO proprietary mouse & keyboard protocols for File Vault 2 GUI input support.
Generally modified UsbKbDxe works better on APTIO V, but for Z77, Z87, and similar AptioInputFix may be the only solution.


  • Sends pressed keys to APPLE_KEY_MAP_DATABASE_PROTOCOL
  • Fixes mouse movement via EFI_SIMPLE_POINTER_PROTOCOL


Fork of the original OsxAptioFix2 driver with a cleaner (yet still terrible) codebase and improved stability and functionality.

Important Notes: To debug boot.efi errors on 10.13, aside the usual verbose (-v) boot-arg, you may need a boot.efi patch or an nvram preference. Either is necessary to get sensible error messages instead of 'does printf work??', but the patch may help in case you have issues when reading nvram.

Before using AptioMemoryFix please ensure that you have:

  • Most up-to-date UEFI BIOS firmware (check your motherboard vendor website).

  • Fast Boot and Hardware Fast Boot disabled in BIOS if present.

  • Above 4G Decoding or similar enabled in BIOS if present.
    WARNING: On some motherboards (notably ASUS WS-X299-PRO) this option causes adverse effects, and must be disabled. While no other motherboards with the same issue are known, consider this option to be first to check if you have erratic boot failures.

  • VT-d disabled in BIOS if present (you could also drop ACPI DMAR table with a bootloader).

  • No slide boot argument present in NVRAM or anywhere else (it is not necessary unless you cannot boot at all or see No slide values are usable! Use custom slide! message from AptioMemoryFix).

  • CFG Lock (MSR 0xE2 write protection) disabled in BIOS if present (consider patching it otherwise if you have enough skills). See VerifyMsrE2 section for more details.

  • CSM disabled in BIOS if present (you may need to flash GOP ROM on NVIDIA 6xx/AMD 2xx or older, using GopUpdate or AMD UEFI GOP MAKER could simplify things).

  • EHCI/XHCI Hand-off enabled in BIOS only if boot stalls unless USB devices are disconnected.

  • VT-x, Hyper Threading, Execute Disable Bit enabled in BIOS if present.

  • While it may not be required, sometimes you have to disable Thunderbolt support, Intel SGX, and Intel Platform Trust in BIOS if present. When debugging sleep issues you may want to (temporarily) disable Power Nap and automatic power off, which appear to sometimes cause wake to black screen or bootloop issues on older platforms. The particular issues may vary, but in general you should check ACPI tables first. Here is an example of a bug found in some Z68 motherboards. To turn Power Nap and the others off run the following commands in Terminal:

    • sudo pmset autopoweroff 0
    • sudo pmset powernap 0
    • sudo pmset standby 0

    Note, that these settings may reset at hardware change and in certain other circumstances. To view their current values run pmset -g.

Note, if you see a lot of Start/End lines in verbose mode you must ensure you do not have bootercfg variable stored in NVRAM. See this post for details. If it still does not help you could use the following command in Terminal (either with System Integrity Protection disabled or from Recovery HD):

sudo nvram bootercfg="log=0 debug=0"

Features (compared to the original)

  • Automatically finds the available memory region for boot.efi to use
  • Implements KASLR support for systems where certain slides cannot be used
  • Adds Safe Mode support on systems with used lower addresses
  • Ensures no slide argument leak to the operating system
  • Attempts to more properly handle the memory mappings
  • Implements read-only and write-only RT variables beneficial to Lilu plugins
  • Works around missing gUnicodeCollation and PlatformLang on several firmwares
  • Fixes broken legacy hash services protocol (only MD5, SHA-1, SHA-256 are supported)
  • Ensures that GetTime does not report unspecified timezone
  • Supports boot.efi chainloading (e.g. via sudo nvram recovery-boot-mode=open)
  • Implements new mapping code when waking from hibernation (still not stable enough)


Erases several NVRAM variables that may affect your boot.


Certain firmwares fail to properly initialize 0xE2 MSR register (MSR_BROADWELL_PKG_CST_CONFIG_CONTROL) across all the cores. This application prints 0xE2 values of all the cores and reports 0xE2 status. The notable example of desyncrhonised 0xE2 MSR registers are several GIGABYTE UEFI firmwares for Intel 100 Series and Intel 200 Series chipsets.

CFG Lock option is available on most APTIO V firmwares, although it may be hidden from the GUI. If VerifyMsrE2 reports that your 0xE2 register is consistently locked, you may try to unlock this option directly.

  1. Download UEFITool and IFR-Extractor.
  2. Open your firmware image in UEFITool and find CFG Lock unicode string. If it is not present, your firmware does not support this and you should stop.
  3. Extract the Setup.bin PE32 Image Section that UEFITool found via Extract Body.
  4. Run IFR-Extractor on the extracted file (e.g. ./ifrextract Setup.bin Setup.txt).
  5. Find CFG Lock, VarStoreInfo (VarOffset/VarName): in Setup.txt and remember the offset right after it (e.g. 0x123).
  6. Download and run a modified GRUB Shell, thx to brainsucker for the binary. A more up to date version may be found in grub-mod-setup_var repo.
  7. Enter setup_var 0x123 0x00 command, where 0x123 should be replaced by your actual offset and reboot.

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.


You can’t perform that action at this time.