Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580


Nov 11, 2018
Asus ProArt Z690-Creator
RX 6800 XT
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
CaseySJ's Comet Lake-S in BeQuiet! Pure Base 500DX:
Gigabyte Z490 Vision-D - i5-10400 - UHD 630 - AMD RX 580

(Please do not quote this guide in its entirety. Post a link instead.)
(See this post for how to refer to a Guide or Mini-Guide.)


Refer to the Z390 Designare thread for answers to a large number of questions

See Problem Reporting Guidelines

Only BIOS F5, F6 and F20 are recommended, but USB 3.x devices will not hot-connect over the two Thunderbolt ports; they will hot-connect over front-panel USB-C port. These devices will work on Thunderbolt ports if they are connected before boot.


FAQ: Fixing OCS Warnings

April 1, 2021: Should you consider Z590 and Rocket Lake? Please see this post by @dehjomz.​

NOTE 1A: Monterey and Ventura Users:
  • 03 Aug 2023: Ventura 13.4, Sonoma and newer: Please follow this procedure to enable i225-V or i226-V Ethernet port.
  • (old procedure) To enable the Intel i225-V Ethernet port, please follow this procedure.
NOTE 1B: The following devices/drivers may cause problems:
  • Updated list of NVMe SSDs to avoid.
  • If using or planning to use Samsung 950 Pro, 960 Evo/Pro, or 970 Evo/Pro NVMe SSDs it may be necessary to disable TRIM. Refer to this post by Vit9696.
  • The MQUPIN Fenvi T919 may cause wake-from-sleep and other issues. It should be avoided if possible. Refer to this post for more information.
  • BIOSTAR NVMe SSDs can conflict with NVMeFix.kext.
  • SK Hynix P31 Gold NVMe SSDs are currently not compatible with macOS. Details here.
  • In Windows, do not install Intel Optane drivers (which are part of Intel Rapid Storage). These drivers can change BIOS SATA port configuration from AHCI to Intel Optane. macOS requires "AHCI".
  • AMD Vega 56, Vega 64, and Radeon VII users: Please remove boot argument agdpmod=pikera.

NOTE 3: If you're facing issues with either MQUPIN or Fenvi FV-T919, try the YOUBO. At least three users have found this card to work where all others have failed.

NOTE 4: If you're using a Samsung NVME SSD or planning to buy one, please read this post carefully.

NOTE 5: If using system names iMac20,1 or iMac20,2 it is necessary to use USBInjectAll 0.7.6, which can be downloaded from here. This has already been done in the EFI for OpenCore 0.6.2 and newer.

NOTE 6a: To try on-board Intel AX201 wireless (WiFi and Bluetooth 5), please refer to this post.

NOTE 6b: Latest information on OpenIntelWireless 2.0.0-alpha with support for 802.11ac and 802.11ax (WiFi 5 and WiFi 6).

NOTE 7: Not sure whether to buy an Intel "K" or non-"K" CPU? Check this post for some advice.

NOTE 8a: Some Corsair power supplies (such as HX1000i, HX1200i, H80i, H120i, etc.) feature a USB connector that allows the operating system to monitor various power supply parameters. Unfortunately, this will prevent the system from entering sleep. These power supplies must be avoided or their USB cables must not be connected.

NOTE 8b: Corsair Commander Pro must be avoided. This device appears to macOS as an Uninterruptible Power Supply (UPS) and prevents sleep. No known solution exists in Big Sur at this time. Update 5 May 2021: Corsair Commander Pro can be used in conjunction with CommanderProFix available from GitHub by clicking here. Thanks to @zakinster for pointing this out.

NOTE 8c: Thunderbolt monitors must also be avoided. They may not turn on in BIOS or in the boot loader. They may also not wake from sleep. Their on-board devices may not work either. Too many problems are being reported and there are no solutions. No support will be provided for issues with Thunderbolt monitors. However, please see this post by @nottooshabby that applies to Apple Thunderbolt Display, but might work as well on other Thunderbolt displays as well (keyword "might").

  1. Components
  3. Installation Procedure
  4. Tech Talk
  5. Troubleshooting / FAQ
  6. Summary
  7. Benchmarks
  8. Acknowledgements
  9. Edits / Updates
Components: New

Gigabyte Z490 Vision-D Motherboard with Built-In Thunderbolt 3 (Titan Ridge) Controller

Intel Core i5-10400 Comet Lake-S Processor

BeQuiet! Pure Base 500DX

G.Skill TridentZ 32GB RGB Memory (2 x 16GB) Dual Channel DDR4 3200 MHz

Sabrent 256GB Rocket NVMe PCIe NVMe SSD - Used for OS and Apps

Fenvi FV-T919 WiFi / Bluetooth Wireless Card

Alternative WiFi/BT if others are failing on your system: YOUBO Fenvi FV-T919

Corsair RM580x 850W Fully Modular Gold Power Supply

BeQuiet! Shadow Rock 3 Air Cooler
Newegg: N/A

Arctic MX-4 Thermal Paste (2019 Edition)

Components: Already Owned

AOC Agon 27-inch 1440p Monitor

Amazon: N/A
Newegg: N/A

MSI Radeon RX 580 Armor OC with 8GB GDDR5 Memory

Logitech K780 Wireless USB Mac/Win/iOS Keyboard

Logitech M510 Wireless USB Mouse - connected to same USB receiver as keyboard

Samsung Bar Plus 32GB USB 3.0 Flash Disk (for installation)

Components: Bootable Backup

128GB or 256GB SATA SSD (any 128GB or 256GB SATA SSD is okay)

External USB 3 Enclosure for SATA SSD

Carbon Copy Cloner by Bombich Software

Components: Optional

USB-C to DisplayPort Cable (allows iGPU to drive a DisplayPort monitor)

USB-C to USB-C cable with USB 3.1 Gen 2 support (connect iPad Pro to any USB-C/Thunderbolt port)

USB 2.0 Two-Way Splitter for Internal USB Header (if you need more than 2 internal USB 2 connections)

USB 2.0 Four-Way Splitter for Internal USB Header (if you need maximum internal connections)



Gigabyte's Z490 Vision-D is the successor to the popular Z390 Designare. This build guide continues the legacy of that board, taking into account everything learned over the previous 18 months. The Hackintosh scene has never been as vibrant as it is today, with exciting developments taking place such as:
  • OpenCore boot loader and the N-D-K fork that provides enhanced support for Windows dual boot
  • Native driver for Intel WiFi modules (in progress)
  • Native driver for Intel Bluetooth modules (in progress; see Troubleshooting / FAQ)
  • Thunderbolt Bus and Local Node activation (requires firmware flashing on Titan Ridge systems)
  • Native NVRAM support on 300-series and now 400-series boards
A Hackintosh has never been as close to a real Mac as it is today. By following this build guide or any other, we should not expect the Hackintosh to be a perfect clone of a real Mac.

Component Choices:
When I assembled my first Hackintosh in November 2018 I had no first hand experience with the different types of components available. This time around, however, I had a clear goal and at least some experience necessary to choose more wisely.

The two primary and essential goals were (a) quietness and (b) compactness. In my previous experience, liquid all-in-one coolers and attendant radiator fans were too noisy and often required a USB connection for thermal management through a proprietary app. This time around, the choice was abundantly clear: air cooling with direct connection to motherboard fan headers. With the latest VirtualSMC and accompanying SMCSuperIO, macOS directly regulates the fans. Due to some limitations, however, the Vision-D's first 5 fan connectors should be used -- and used in order. Avoid using Fan Headers 6 and above, and do not skip a fan header. For example, if the system has 3 fans, they should start with header 1 and be connected to consecutive fan headers 1, 2, 3. Each fan header is labeled on the board. Fans are regulated by BIOS/firmware during boot, but transition to macOS seamlessly, which spins them down slightly and automatically for silent operation.

Compactness was achieved with the BeQuiet! Pure Base 500DX. Although the same physical size as the popular NZXT H510 (which I also own), the Pure Base 500DX excels for these reasons:
  • Elegant and minimal addressable RGB lighting controlled by ARGB header (supports Gigabyte RGB Fusion 2)
  • Thicker side glass panel compared to NZXT H510
  • 240mm and 280mm radiator support on top (only 120/140 on NZHT H510)
  • Perforated or mesh front panel for improved airflow
  • Installation of two SATA SSDs on the front side in recessed compartments (very nice touch)
  • Separate audio and microphone jacks on front panel (H510 has a single combo jack with a Y-splitter cable)
  • USB-C and USB 3.1 ports on front; lack of USB 2 ports on front panel is a wonderful thing as we'll see later in the build guide
  • Sound deadening material on the right side cover
Installation Notes:
This guide uses OpenCore to install macOS 10.15 Catalina and supports both an AMD discrete GPU and internal IGPU to drive the display monitor. Some of the high level specifications of this build are listed below for informational purposes. It's not necessary at this time to understand what they mean.
  • Uses N-D-K fork of OpenCore 0.5.8 with N-D-K graphical boot picker (Update: N-D-K fork of OpenCore has not been updated; please use attached OpenCore 0.7.4)
  • Uses VirtualSMC by acidanthera (GitHub)
  • Uses Lilu, the plug-in manager for a set of essential drivers
  • Uses WhateverGreen, a Lilu plug-in, for managing IGPU and AMD GPU
  • Uses AppleALC, a Lilu plug-in, for managing internal Realtek ALC-1220 audio, and sets Audio Layout ID to 11
  • Uses NVMeFix, a Lilu plug-in, for managing power consumption on NVMe SSDs
  • Uses a custom SSDT for Thunderbolt hot-plug
  • Uses a custom SSDT for configuring USB ports, which:
    • Disables USB 2 protocol from all USB-C/Thunderbolt ports
      • 19 Jun 2020 Update: The new V2-OC-0.5.9-STD-Z490-VISION-D zip enables USB 2 protocol on all USB-C/Thunderbolt ports. This is accomplished with a new SSDT-UIAC-VISION-D-V2.aml and enabling the Kernel quirk XhciPortLimit in the OpenCore config.plist.
      • 04 Oct 2021 Update: OpenCore 0.7.4 has been released; ZIP file has been added.
    • Disables on-board Intel Bluetooth module residing on HS14
  • Uses a combination of SSDT and driver (kext) for enabling true one-key wake from sleep
  • Uses RehabMan's FakePCIID to enable compatibility with on-board audio and Intel i225 2.5Gbit Ethernet port
  • Applies keyboard patches by "Wern" to enable brightness control via F1/F2 keys
  • Sets boot argument shikigva=80 for improved Sidecar and DRM performance
  • Sets boot argument agdpmod=pikera for compatibility with AMD NAVI GPUs (RX 5500, 5600, 5700)
    • This may enable HDR mode by default on HDR-capable monitors, which can produced washed out colors (lack of contrast). If not using a NAVI GPU, this boot argument can be removed
  • Uses an EFI tool called CFGLock.efi by German hackintosher Brumbaer to unlock MSR 0xE2; special thanks to @tecnicasopr for informing us of this tool
    • 13 Jul 2020 Update: Firmware (BIOS) version F5d has been released, in which MSR 0xE2 is unlocked by default! This is really good news and we can skip the steps for manually unlocking MSR 0xE2. 26 Jul 2020: Firmware (BIOS) F5 has been released, which supersedes F5d.
The Intel CNVi WiFi 6 / Bluetooth 5 card that comes preinstalled on the Vision-D should not be removed. It can be used in Windows and Linux. Moreover, experimental drivers are available even for macOS. Because the module is plugged into a CNVi socket, it cannot be replaced by a Broadcom or other non-Intel or non-CNVi module.

The Titan Ridge Thunderbolt controller will work with macOS without the need for any firmware flashing. It will allow device to hot plug as well. But the controller will operate in "Internal Connection Manager" or ICM mode in which macOS cannot activate Thunderbolt Bus or Thunderbolt Local Node. Therefore, System Information --> Thunderbolt will report No drivers are loaded. This is okay and does not indicate that Thunderbolt is disabled; in fact it only indicates that Thunderbolt Bus is disabled. In most cases the lack of Thunderbolt Bus will not matter, but if a particular Thunderbolt device fails to connect then report the problem in this thread.

On the Z390 Designare, a procedure was created to unlock CFG-Lock (MSR 0xE2) using modgrubshell on a dedicated USB flash disk. On the Z490 Vision-D, however, the process is much easier thanks to an EFI tool called CFGLock.efi by German hackintosher Brumbaer. Use of this tool is discussed in Step 7 of the Installation section below. Unlocking MSR 0xE2 enables native macOS X CPU Power Management (XCPM). [This is no longer necessary with firmware (BIOS) version F5 and newer, because CFG Lock is unlocked by default.]

Recommendations for Windows Dual Boot:
If this system is intended to be a dual boot system with Windows, then the Windows SSD should contain its own EFI partition. This will ensure that (a) OpenCore recognizes and boots Windows, and (b) Windows does not interfere with the EFI partition on the macOS SSD. We can use the macOS Disk Utility to format the Windows SSD with Format=exFAT and Scheme=GUID Partition Map. The Windows installer will later reformat the exFAT partition to NTFS.

Additionally, the presence of a macOS disk may confuse the Windows installer. If Windows is to be installed on an NVMe SSD, it should be installed into the NVMe slot closest to the CPU. This will prevent future Windows Feature Updates from interfering with the EFI partition on the macOS SSD. Broadcom drivers for a Fenvi FV-T919 or other Mac-compatible Broadcom WiFi/BT module should not be installed in Windows. This allows Windows to use the Intel AX201 WiFi 6 / Bluetooth 5 module instead. See also Windows 10 Installation Notes in the Troubleshooting / FAQs section.

Installation Overview:
Before we start, let's get acquainted with the big picture. These steps will unfold as we proceed through the installation procedure. While macOS is installing, do not walk away from the system because there can be one or two sudden reboots, which will require attention.
  1. Create USB install disk on a Mac or existing Hackintosh.
  2. Boot Hackintosh from USB install disk by pressing F12 at BIOS splash screen and select USB disk
  3. OpenCore boot picker will appear.
  4. Choose Install MacOS and wait for macOS installer to load and run.
  5. When the installer appears, choose your language and then run Disk Utility to format the internal macOS SSD.
  6. Then begin macOS installation on the newly formatted SSD.
  7. This begins Phase 1 and a progress bar will appear, stating X Minutes Remaining. This is usually 5 minutes.
  8. macOS installer will suddenly reboot in order to begin Phase 2.
  9. When machine reboots, press F12 at BIOS splash screen and again select USB disk.
  10. OpenCore boot picker will again appear.
  11. This time the internal macOS SSD must be selected (it should have been auto-selected for you).
  12. This begins Phase 2 and will take the bulk of the time.
  13. At the completion of this phase the system should gracefully reboot.
  14. When machine reboots, press F12 at BIOS splash screen and again select USB disk.
  15. OpenCore boot picker will again appear.
  16. Again pick the internal macOS SSD in order to complete the installation. The MacOS Welcome screen should appear.
  17. During the Welcome process it's okay to:
    • Enter WiFi password and login to WiFi network
    • Enable Location Services
    • Create user account and set password
    • Sign in to iCloud and App Store
    • Enable Siri
  18. After logging in to macOS, the EFI folder from USB install disk is copied to the EFI partition on the macOS SSD to make it bootable; this is the only real post-installation step
  19. Safely eject USB install disk from macOS
  20. Reboot and allow system to boot from the internal macOS SSD
  21. Congratulations, you are now up and running!
Make a Backup:
Having a functional baseline is essential for future troubleshooting and peace of mind. This single investment can make the difference between a happy Hackintosh experience and a miserable one. Components needed for the backup are listed above in Components: Bootable Backup. The size of the backup disk only needs to be as large as the amount of data to be backed up. If the original disk is 1TB, for example, but it contains only 60GB of data then the backup disk can be as small as 64GB (if available) or 96GB. A relatively small backup disk can be used at the beginning and replaced with a higher capacity disk in the future as the need arises. Backup procedure is presented below in Step 13.

Installation Procedure

A picture paints a thousand words, so the following diagram may be a useful visual aid to understanding the flow:
Install and Post Install Disks.png

Create USB Install Disk:
We begin by creating a USB install disk containing (a) the macOS installer and (b) an EFI partition with the OpenCore boot loader, as shown on the left side of the figure above. A fast and reliable USB 3.x flash disk such as the Samsung Bar Plus listed in Components will speed up the process. It should be at least 16GB.

Step 1: Open the spoiler below and download macOS.
  1. Click here to visit the gibMacOS site on GitHub.
  2. Click the large green button labeled Code, and select Download ZIP.
  3. Unzip the file if it does not unzip automatically. The files will be in your Downloads directory in a folder called gibMacOS-master.
  4. In Finder, double-click gibMacOS.command from the gibMacOS-master folder. If macOS complains that the file was downloaded from the Internet and cannot be run, open System Preferences --> Security & Privacy --> General and click Open Anyway from the bottom of the window. Repeat this for any other downloaded application as needed.
  5. From the menu that appears, enter "1" for the latest macOS, or choose a different menu item.
  6. A number of files will now be downloaded and stored in the same gibMacOS-master directory, but in a new folder called macOS Downloads/publicrelease/xxx-xxxxxx...., where "xxx-xxxxxx..." will vary depending on the version of macOS that was selected.
  7. Depending on the size of the macOS installer (generally between 8GB and 12GB) and network download speed, wait an appropriate amount of time for the download to complete.
  8. When download is complete, all files will be present in the "xxx-xxxxxx..." folder. Press Q to quit.
  9. Big Sur Users: Now look inside the newly created "xxx-xxxxxx..." sub-folder in the gibMacOS-master/macOS Downloads/publicrelease folder. Here you will find a file called InstallAssistant.pkg. Launch this application and grant it permission from System Preferences --> Security & Privacy if it does not launch the first time. This will create Install macOS Big Sur in your Applications folder. Skip the remaining steps in this section.
  10. Catalina Users: Back in the gibMacOS-master folder double-click the file BuildmacOSInstallApp.command and once again click Open Anyway from System Preferences --> Security & Privacy if the command does not run.
  11. A single prompt will appear as follows:
  12. Select the "xxx-xxxxxx..." folder or any file inside that folder, and drag-and-drop it into the Terminal window.
  13. In a few seconds the macOS installer will appear inside the "xxx-xxxxxx..." folder, and it will be called Install macOS Catalina.
  14. Move this file to the Applications folder. The next step assumes that this file has been moved to Applications.
Step 2: Open the spoiler to install macOS Installer onto USB disk
  • Format the USB disk with Disk Utility.
  • Select View --> Show all Devices then click the parent name of the USB flash disk on the left sidebar. This is critical.
  • Select Erase and ensure that three items appear. Then enter the following as shown in green:
    • Name: Catalina-USB (use this exact name)
    • Format: MacOS Extended (Journaled) -- do not use APFS here
    • Scheme: GUID Partition Map
      Disk Utility for USB.png
  • Open a Terminal window and type:
  • sudo "/Applications/Install macOS" --volume /Volumes/Catalina-USB
  • Enter your Mac password when requested.
  • It will take a few minutes for this task to complete. Afterwards the USB install disk will be renamed to Install macOS Catalina.
  • Open the USB flash disk in Finder and confirm that a file called Install macOS Catalina exists.
Step 3: Open the spoiler to download essential utilities to your Mac or existing Hack.
Now copy these utilities to the USB install disk alongside the macOS installer.​
Step 4: Open the spoiler to prepare OpenCore configuration
OpenCore is the essential boot loader. Although it's in public beta at this time, it is highly configurable and modern. The configuration for Z490 Vision-D has largely been done in advance. It's only necessary to specify serial numbers and UUID. We proceed as follows:
  • Vision G owners (not Vision D) please refer now to the spoiler Modifications for Vision G, then return here and continue. Merge those instructions with the ones below.
  • Choose either Option 1 or Option 2 below, not both:
    • Option 1: Choose N-D-K version of OpenCore 0.5.8:
      • Download and unzip the attached file. The files will be inside a folder called Z490-VISION-D-EFI-NDK-058-V2
    • Option 2: Choose standard version of OpenCore 0.7.4:
      • Download and unzip the attached The files will be inside a folder called OC-074-VISION-D
  • Rename this folder to EFI
  • Inside will be two sub-folders: (a) BOOT and (b) OC
  • Inside the OC sub-folder locate these two files:
    • config-AMD-GPU.plist
    • config-Intel-iGPU.plist
  • If using AMD GPU to connect display monitor, rename config-AMD-GPU.plist to config.plist
  • If using Intel IGPU to connect display monitor, rename config-Intel-iGPU.plist to config.plist
  • Open config.plist file using OpenCore Configurator and click PlatformInfo page on the left side
  • Then click DataHub - Generic - PlatformNVRAM and choose iMac19,1 from the pop-up menu at the bottom as shown below.
    OpenCore DataHub.png
  • On the same page, click Generate next to ROM as shown:
    OpenCore ROM.png
  • Press CMD-S to save the modified OpenCore config file.
  • Mount the EFI partition of the USB install disk. This can be done using either (a) EFI Agent or (b) Hackintool or (c) Clover Configurator.
    • The EFI partition will appear as a new disk on the desktop or in Finder.
      USB Disk Icons.png
  • Copy the entire EFI folder from bullet 1 to the EFI partition on the USB flash disk.
Safely eject the USB install disk. It is ready to be inserted into the Z490 Vision-D.

Prepare Vision-D:
The remaining steps take place on the Z490 Vision-D.

Step 5: Open the spoiler and ensure that the system has been assembled properly.
  • Minimum power supply rating is 550 watts. Depending on the CPU and GPU, 650W or larger power supply should be used.
  • Ensure that 8-pin CPU power cable is attached (top left of motherboard: ATX_12V_2X4). If multiple GPUs or power-hungry PCIe cards are installed, also connect the PEG cable on the bottom right side of motherboard (refer to Vision-D user manual).
  • If using a WiFi/Bluetooth card such as Fenvi FV-T919, install it in the short PCIe x1 slot.
  • If M.2 SSDs are installed in any of the three M.2 slots, certain SATA ports become unavailable, as shown:
    SATA Port Restrictions.png
  • Ensure that thermal paste has been applied properly and CPU cooler is functional and connected to motherboard.
  • Ensure that the (empty) macOS internal SSD has been installed. It does not need to be formatted at this time.
Step 6: Open the spoiler and configure BIOS/Firmware parameters on Z490 Vision-D
BIOS F5 and F6 are recommended, but they do not provide Resizable BAR support for GPUs in Windows. BIOS F20 can be installed if Resizable BAR support is needed, but this will prevent USB-C devices from connecting to Thunderbolt ports in macOS.

Start the system and press DEL or F2 to enter BIOS Setup. Now we configure firmware parameters shown in the screenshots and listed below. It is necessary to start with Save & Exit --> Load Optimized Defaults because this pre-configures a set of parameters for us, and we make a few additional changes.
  • Press F2 if necessary to toggle into Advanced Mode
  • Save & Exit → Load Optimized Defaults
  • USB Audio users: Set CPU Base Clock to 100MHz
  • Favorites
    • Extreme Memory Profile(X.M.P) → Profile1
    • CSM Support → Disabled
    • VT-d → Enabled (Enable this for AppleVTD)
  • Settings IOPorts
    • Initial Display Output → PCIe 1 Slot (if GPU in slot 1) or IGFX (if using iGPU to display monitor)
    • Internal Graphics → Enabled (not Auto)
    • Above 4G Decoding → Enabled
  • Settings → IOPorts → Thunderbolt
    • Security Level → No Security
    • Optional: Thunderbolt Boot Support → Boot Once
      • Try this if using UAD audio interfaces or Thunderbolt Monitors
  • Settings → IOPorts → Thunderbolt → Discrete Thunderbolt Configuration
    • GPIO3 Force Pwr → Enabled
  • Settings → IOPorts → USB Configuration
    • XHCI Hand-off → Enabled
  • Boot → Windows 10 Features → Other OS
  • Boot → CSM Support (confirm that it's "Disabled")
  • Save & Exit → Save Profiles
    • Save your settings into one of eight available profile slots (see screenshot)
    • Also save settings into a file on USB disk (see screenshot). The USB install disk can be used for this purpose

Correction below: VT-d should be enabled
200531135748.png 200531135821.png 200531135840.png200531135853.png 200531135950.png 200531140019.png 200531140054.png
At this time F5 is the only recommended BIOS. Newer versions break Thunderbolt/USB-C on macOS and should be avoided.
  • USB Audio users: Set CPU Base Clock to 100MHz
F5d-Save and Exit.png

Correction below: VT-d should be enabled
F5d-Favorites.png F5d-IO Ports.png F5d-Thunderbolt Security.png F5d-Discrete TB3 Config.png F5d-USB Config.png F5d-Boot Settings.png F5d-Save to Disk 1.png
Step 7: Unlock MSR 0xE2 (CFG-Lock) -- Firmware (BIOS) F2 to F5a only
Firmware (BIOS) F5 for the first time exposes CFG-Lock parameter in BIOS Setup. Furthermore, CFG-Lock is unlocked by default on F5 (and newer), so this step can be skipped if firmware (BIOS) F5 or newer is installed. However, for firmware F2 through F5a the procedure below is required.

It is critically important now to unlock MSR 0xE2 (i.e. to set CFG-Lock to Disabled). This enables native CPU power management. The OpenCore configuration provided in this guide will fail to boot unless MSR 0xE2 is unlocked. Fortunately, the procedure is trivially simple, as follows:
  • If macOS has not yet been installed:
    • Boot the Z490 Vision-D with the USB install disk connected.
    • Press F12 at BIOS splash screen to open the BIOS boot menu and select the USB flash disk.
    • The OpenCore graphical boot picker will appear.
    • The second to last option (on the far right) will be CFG Lock -- select this option.
    • Press the space bar to reveal additional options.
  • If macOS is already fully installed:
    • Boot the Z490 Vision-D in the usual manner.
    • The OpenCore graphical boot picker will appear.
    • Press the space bar to reveal additional options.
    • The second to last option (on the far right) will be CFG Lock -- select this option.
  • The following should now appear:
Brumbaers CFG Unlock
1. 05 003E 0011 /CFG Lock/ VarStore Name: CpuSetup

Exactly 1 CFG Variable found: CFG Lock
In VarStore "CpuSetup" GUID: B08F97FF-E6E8-4193 - A9-97-5E-9E-9B-0A-DB-32 Offset: 003E Size: 1

Variable read: value 1
Do you want to toggle the value y/n ?
  • If Variable read: value is 1 it means CFG-Lock is enabled. Only in this case should we unlock it by pressing y and Enter.
    • When the task completes, the system should be rebooted.
    • Back at the OpenCore boot picker select the option to Restart the computer; this option is located at the bottom of the window.
  • If Variable read: value is 0 (or anything other than 1), press n and Enter This means CFG-Lock is already unlocked, so it should not be toggled.
URGENT: For firmware (BIOS) versions F2 to F5a only: Any time the motherboard BIOS/Firmware is flashed or CMOS Reset is performed, repeat Step 7. After post-installation is completed, the CFGLock tool will exist on the internal macOS SSD, so the USB install disk will not be needed.

Begin macOS Installation:
Now we begin the process of installing macOS.

Step 8: Open the spoiler to begin macOS Installation
Insert the USB flash disk into any USB 3 port on the rear IO panel or front of the PC case. A USB 3 port will speed up the overall process. Proceed as follows:
  • Reboot the system with the USB flash disk already inserted.
  • When the Gigabyte splash screen appears, press F12 to open the BIOS Boot Menu. This is different from the OpenCore boot pickerthat will appear in the next step.
    • Select the USB flash disk from the list and press Enter.
  • The N-D-K OpenCore Boot Picker will appear.
    • Choose the option Install MacOS.
    • This option from the boot picker is never selected again.
  • MacOS installer will take a few moments to load and run. If successful, it will ask for language preference and present a set of options, one of which will be Disk Utility.
    • Run Disk Utility and select View --> Show All Devices. This is critical.
    • Select the parent or top-level name of the macOS internal SSD and select Erase.
    • Three fields should appear, and the following entries should be made:
      • Name: Catalina (this can be changed any time after installation is completed)
      • Format: APFS
      • Scheme: GUID Partition Map
    • Double-check selections and settings, then click Erase to format the internal macOS SSD.
    • Then quit from Disk Utility.
  • Now select the option to begin macOS installation.
    • Accept the license terms.
    • Select the just-formatted internal macOS SSD as the target location.
  • This begins Phase 1.
  • WARNING: Do not leave the computer unattended during installation. The system can reboot suddenly once or twice, and will require manual intervention.
  • Within 5 minutes the system will auto reboot. Press F12 when the Gigabyte splash screen appears and select the USB install disk from the BIOS Boot Menu.
  • At the OpenCore boot picker there should be a new entry called simply MacOS.
    • Select MacOS from the OpenCore boot picker. However, it should already be selected.
  • This begins Phase 2, which can take 30-50 minutes. A sudden reboot is possible, so it's advisable to remain with the system.
    • Should a reboot occur, press F12 at the Gigabyte splash screen and select the USB install disk from the BIOS Boot Menu.
    • Then at the OpenCore boot picker, select MacOS once again. However, it should already be selected.
  • When installation completes, the familiar Welcome screen will appear and will guide the rest of the setup.
    • It is advisable to perform the following steps during the Welcomeprocess:
      • Enter WiFi password and login to WiFi network
      • Enable Location Services
      • Create user account and set password
      • Sign in to iCloud and App Store
      • Enable Siri
  • At the completion of the Welcome process, the macOS desktop will appear. All of the hard work is now done! But final touches remain.
Post Installation:
The macOS internal SSD is not bootable at this time because its EFI partition is empty. A boot loader (OpenCore) must be installed into the EFI partition. On the USB install disk are a number of essential utilities that were copied back at Step 3. Copy all of these utilities to the Applications folder on the macOS SSD.

Step 9: Copy EFI folder from USB flash disk to EFI partition of internal macOS SSD
  • Using EFI Agent, Hackintool, or OpenCore Configurator (Tools --> Mount EFI) mount the EFI partitions of both (a) USB flash disk and (b) macOS internal SSD.
  • Using Finder, copy the entire EFI folder from EFI partition of USB disk to EFI partition of macOS SSD.
    • This completes post-installation.
  • Safely eject the USB install disk and reboot the system.
  • When system reboots, do not press any key (i.e. do not press F12), but wait for the OpenCore boot picker to appear automatically.
  • Then select Catalina and ensure that the system boots up.
Step 10: Optionally install NativeBrightnessControl for adjusting brightness via F1/F2 keys
  • Native Brightness Control is supported on most but not all monitors. Monitors with HDMI 1.4/2.0+ and/or DisplayPort 1.1/1.2+ connectors are more likely to be compatible.
  • Download the app from GitHub by clicking here.
  • Copy the app to Applications folder and double-click to launch. It will relaunch automatically on startup.
    Brightness Control.png
Step 11: Final Adjustments
  • Disable Wake for Network Access in System Preferences --> Energy Saver
  • Enable Location Services in System Preferences --> Security & Privacy --> Privacy
Installation Verification:
Step 12:
Open the spoiler to check configuration of various system devices and verify installation.
A selected set of system devices can be checked/verified using System Information which can be invoked by holding OPTION key and clicking the Apple menu on the top left. The first menu item will be System Information. Audio, Bluetooth, Ethernet, and PCI devices can be checked right away. Thunderbolt is checked by examining the PCI page instead of the Thunderbolt page. (The Thunderbolt page will say No drivers are loaded because Thunderbolt Bus is not activated until the firmware is flashed. This is an optional and potentially risky step.)
System Info -> Audio.png System Info -> Bluetooth.png System Info -> Ethernet Cards.png System Info -> PCI.png
Check HEVC and H.264 hardware acceleration by running VideoProc. This is a commercial (paid) application, but comes with a trial period. Select Setting and then Options.
VideoProc 1.png VideoProc 2.png
If hardware acceleration is enabled, the resulting screen will look like this:

Create Backup:
A Hackintosh is not a real Macintosh. Apple does not test its operating system on Hackintosh. Apple does not provide assurance that macOS will work today or tomorrow on Hackintosh. When we decide to build a Hackintosh and entrust our digital lives to it, we must have the wisdom (a) to know that significant problems may occur and (b) to take proactive measures to guard against digital disaster. This build process will not be considered complete until a full bootable backup is made.

Step 13: Open the spoiler below to make a full bootable backup. Components needed for this are listed at the top of this guide in the section Components: Bootable Backup.

March 2023: The spoiler below is outdated. Please refer to the spoiler in STEP 11 after clicking here.
  • Install the backup SATA SSD into the USB 3 SSD enclosure and connect it to an available USB 3.x port.
  • Run Disk Utilityand format the SSD as follows:
    • Select View --> Show all devices
    • Select parent or top-level name of the external SATA SSD on the left sidebar
    • Click Eraseand specify three parameters:
      • Name: Catalina Backup (give it any name that is different from the internal macOS SSD)
      • Format: APFS
      • Scheme: GUID Partition Map
    • Click Erase once again to complete the process
  • Download a modified version of @byteminer's from the GitHub repository by clicking here.
    • Click the green button on the right side of the web page: Code, then choose Download ZIP.
      Screen Shot 2020-12-02 at 9.15.22 AM.png
    • It should then appear in the Downloads folder under EFIClone-master. Because of security precautions in macOS, run Terminaland clear the 'quarantine' flag as follows:
      • xattr -d ~/Downloads/EFIClone-master/
      • If the command succeeds, there will be no reply (it will run silently)
    • The script will be set to Test Mode by default. This allows the script to be test-run to confirm that it works properly. Leave it in Test Mode at this time.
  • Run Carbon Copy Cloner. If it's being run for the first time, pull down the Carbon Copy Cloner menu bar item (right next to Apple menu at the top left of the screen) and select Grant Full Disk Access to CCC... Follow the on-screen instructions.
  • Now select the Utilities menu on the menu bar and choose Reveal CCC's Scripts folder
    • A Finder window will open and the last item in the window will be a folder called Scripts
    • Copy (or from the Downloads/EFICLone-master folder to this Scripts folder, but hold down the OPTION key while dragging so that the file is 'copied' instead of 'moved'.
    • Now there will be two exact copies of (or EFIClone_v2): one in the original location and the other in the Scripts folder.
    • Select the same Utilities menu on the menu bar and notice that the last option in the menu has changed to Secure CCC's Scripts folder
      • Select this option to secure the Scripts folder
      • Now the script is capable of running
    • To create the backup task, we select the SOURCE disk and the DESTINATION disk. These are clearly labeled in the Carbon Copy Cloner main window.
    • Click SOURCE and select the macOS internal SSD
    • Click DESTINATION and select the external SATA SSD
    • Double check that the names of the SOURCE and DESTINATION disks are different
  • Just below the SOURCE and DESTINATION disks is an option called ADVANCED SETTINGS.
    • Click the adjacent chevron to expand ADVANCED SETTINGS
    • Three subsections will be revealed:
    • Leave the first two alone and click Run a Shell Script under AFTER COPYING FILES
      • A file selection window will appear that will point to the Scripts folder
      • Select (or EFIClone_v2) from the list
  • The backup job has now been configured. Save it by pressing CMD-S or File --> Save
  • Because the EFIClone script is in Test Mode, click Clone on the bottom right of the Carbon Copy Cloner window to perform a Test Run.
  • This will generate an activity log. Examine the log in Terminalby typing:
    • cd /System/Volumes/Data/Users/Shared
    • more EFIClone.log
  • Check that the list of Source Files looks correct. Press <spacebar> to page forward and <q> to quit the log.
  • If the log looks correct, the Test Mode flag must be set to N for No as follows:
    • Locate (or in the Downloads/EFIClone-master folder and edit the file with a text editor.
    • Somewhere in the first few lines we will see this: TEST_SWITCH="Y"
    • Change only this line to: TEST_SWITCH="N"
    • Save the file
  • From Carbon Copy Cloner, select Utilities --> Reveal CCC's Scripts folder once again
  • Drag and drop the modified to the Scripts folder
  • From Carbon Copy Cloner, select Utilities --> Secure CCC's Scripts folder once again
  • Press CMD-S or File --> Save to save the modified task
  • Now Carbon Copy Cloner is fully set up to clone both the SOURCE macOS partition and the SOURCE EFI partition to the DESTINATION
CCC configured view.png
CCC reveal scripts folder.pngCCC secure scripts folder.png

Congratulations, you made it!
Welcome to Hackintosh. Enjoy the new system and explore the wealth of information available on this forum and the Internet in general.

Tech Talk

Change CPU Name in
About this Mac:
If using an Intel i7 or i9 processor, About this Mac may incorrectly show Core i5. This can be fixed using the attached script, as follows:
  • Download to the Downloads folder and unzip. Do not move to a different folder.
  • Open Terminal and type:
    • sudo xattr -d ~/Downloads/
    • chmod +x ~/Downloads/
  • If this command succeeds, there should be no output from the command (it works silently).
  • Choose a name for the processor, but do not include the clock speed. CPU clock speed will be automatically specified.
    • Example 1: "6-Core Intel Core i5-10400"
    • Example 2: "8-Core Intel Core i7-10700K"
    • Example 3: "8-Core Intel Core i9-10900K"
  • Run the command as follows with the new name enclosed in quotes as shown:
cd Downloads
./ "6-Core Intel Core i5-10400"
  • Close About this Mac if it's open, and reopen it to see the change. A reboot is not needed.
  • NOTE: For some non-English systems the script may not work unless the target path inside the script is manually edited.
Thanks to @Gigamaxx for informing us of this procedure.

On-Board Devices:
The diagrams below describe the USB, Ethernet, and Audio ports enabled under macOS. Using the OpenCore kernel quick XhciPortLimit and a custom USB SSDT, all USB ports are supported. The macOS limit of 15 USB ports is exceeded, but the OpenCore kernel quirk XhciPortLimit allows safe operation.
Vision D IO Panel V2.png

In the diagram below we see that Z490 Vision-D contains two USB 2.0 headers along the bottom edge. Each is a 9-pin header that supports two USB ports, for a total of four USB 2.0 ports across the two headers. However, Gigabyte made a very welcome decision to assign all four of these ports to a single USB 2.0 Hub. This means that the four USB 2.0 internal ports count as a single USB port because they are redirected through the USB 2.0 hub. All four ports are part of HS11. HS12 is attached to an ITE Technology chip with product ID 0x5702. This is the RGB Fusion 2.0 controller.

In the USB SSDT, the front panel USB-C port (F_U32C) is set to Type 10 and uses SS01 if the USB-C connector is plugged in one orientation, and SS02 if the connector is flipped around and plugged in the other orientation.

Vision D Main Board V3.png

The diagrams below describe the USB, Ethernet, and Audio ports enabled under macOS. Because of a limit of 15 USB ports per USB (XHC) controller, some USB 2.x virtual ports were disabled. A USB 3.x physical port supports both USB 3 and USB 2 protocols, and these are considered to be two virtual ports. No more than 15 virtual ports are allowed per controller.

Rear IO.png

In the diagram below we see that Z490 Vision-D contains two USB 2.0 headers along the bottom edge. Each is a 9-pin header that supports two USB ports, for a total of four USB 2.0 ports across the two headers. However, Gigabyte made a very welcome decision to assign all four of these ports to a single USB 2.0 Hub. This means that the four USB 2.0 internal ports count as a single USB port because they are redirected through the USB 2.0 hub. All four ports are part of HS11. However, HS12 is attached to an ITE Technology chip with product ID 0x5702.

Vision D Main Board.png

RGB Fusion 2.0:
Both the Vision D and Vision G support Gigabyte's RGB Fusion 2.0 via the ITE Tech 0x5702 controller. It is likely that the same controller is found across all of Gigabyte's Z490 boards that support RGB Fusion 2.0. Fortunately, the controller is mapped to USB port HS12, which allows us to reverse engineer the USB data stream and duplicate that functionality in a liquidctl driver that runs under macOS.
  • Complete instructions for installing liquidctl are posted here.
  • A visual glance at some RGB color modes is posted here.
On the Vision D there are seven lighting channels, of which five are standard RGB and two are Addressable-RGB. Their names and locations are shown here:

Explanation of Selected OpenCore Parameters:
A self-guided journey through OpenCore awaits...
OC - ACPI - SSDTs.pngOC - Booter.pngOC - DeviceProperties - 2.5Gbps Ethernet.pngOC - DeviceProperties - Audio.pngOC - DeviceProperties - WiFi and BT.pngOC - DeviceProperties - iGPU Headless.pngOC - DeviceProperties - iGPU Drive Monitor.pngOC - Kernel - kexts - v2.pngOC - Kernel - Patch.pngOC - Misc - Boot.pngOC - Misc - Debug.pngOC - Misc - Security.pngOC - Misc - Tools.pngOC - NVRAM - Boot Args and SIP.pngOC - NVRAM - Background Color.pngOC - PlatformInfo.pngOC - UEFI - APFS.pngOC - UEFI - Drivers.pngOC - UEFI - Input.pngOC - UEFI - Output - Max Resolution.png

Thunderbolt Bus Activation:
Thunderbolt with hot-plug functionality works properly just by following the build guide. However, because Apple and Intel jointly developed Thunderbolt, Apple has created a more thorough implementation compared to Windows and Linux. We can think of Thunderbolt as operating in two modes:
  • Standard Mode, also known as ICM or Internal Connection Manager mode.
  • Extended Mode, in which macOS implements a number of extended capabilities.
Switching from Standard Mode to Extended Mode is purely optional, but it brings the system closer to a real Mac. Extended Mode provides these additional capabilities:
  • Thunderbolt Bus and Local Node
  • Thunderbolt Ethernet bridge to connect two Macs over Thunderbolt cable
  • Target Disk Mode in which a Hackintosh can connect to a real Mac's hard drives when the real Mac is placed into Target Disk Mode
  • eGPU support. This allows eGPUs to connect and disconnect. Additionally, a menu bar icon allows the eGPU to be disconnected safely.
  • QNAP, OWC, and possibly other Thunderbolt NAS support.
  • Support for some Thunderbolt 1 legacy devices such as Apple Thunderbolt Display.
For a more complete list, refer to this post.

Unfortunately, to enable Extended Mode it is necessary to flash the Thunderbolt firmware chip located on the back side of the motherboard. This incurs risk of physical and electrical damage, so extreme caution must be taken. The choice to pursue Extended Mode should also be carefully considered.

We assume no responsibility or liability for any damage that may occur.

Details of flashing the Thunderbolt chip are located in these posts. Do not skip any of the links. (Following the Thunderbolt DROM Micro-Guide is also necessary.)
For full control over Thunderbolt DROM (view, edit, verify, export), refer to this Mini-Guide. A copy of the original unmodified Thunderbolt firmware (NVM 50) for Gigabyte Z490 Vision D is posted here.

SSDT-EC for Vision D:
When this build guide was initially created, it was used to install Catalina 10.15.4 using OpenCore 0.5.8. At the time it was found that creating a fake 'EC' device, which is normally required for Catalina, prevented the system from booting. The fake EC device was therefore removed from the OpenCore 0.5.8 ZIP.

With OpenCore 0.5.9 and Catalina 10.15.5, however, this problem no longer exists. Therefore the OpenCore 0.5.9 ZIP attached below contains a customized SSDT-EC.aml for the Vision D. It may work on other Gigabyte Z490 boards as well. Use of this SSDT is recommended.

USB Type C Ports and USB 2.0 Protocol:
There is an important distinction between physical connectors and the data protocols they support. Examples of physical connectors are (a) HDMI connector, (b) DisplayPort connector, (c) Mini-HDMI connector, (d) Mini-DisplayPort connector, (e) Micro-HDMI connector, (f) USB Type A, (g) USB Type B, (h) USB Type C, (i) Micro-USB, (j) Mini-USB, and even (k) SD Card connector.
Examples of data protocols are (a) HDMI 1.1, (b) HDMI 1.2, (c) HDMI 1.4, (d) HDMI 2.0, (e) DisplayPort 1.1, (f) DisplayPort 1.2, (g) DisplayPort 1.4, (h) USB 1.1, (i) USB 2.0, (j) USB 3.0, (k) USB 3.1 Gen 1, (l) USB 3.1/3.2 Gen 2, (m) SD card, (n) SDHC, (o) SDXC, (p) SDUC, etc.

When we look at a normal size HDMI connector we know from experience that not all such connectors support all HDMI data protocols. Some HDMI cables with normal size connectors are only certified for HDMI 1.1 or 1.4, but cannot carry HDMI 2.0 traffic.

Similarly, USB connectors and protocols are independent. We might assume that all USB Type C connectors must be capable of carrying all USB data protocols including USB 3.1/3.2 Gen 2. However, this is false and causes a fair bit of consumer confusion.

For example, Apple's 2018 and newer iPad Pros support USB 3.1/3.2 data protocols, but the USB Type C cable that accompanies the iPad Pro only supports USB 2.0 data protocol. If this cable is used, it will connect to one of the HSxx USB 2 ports on the Hackintosh. Apple's iPhone only supports USB 2.0 protocol, so Lightning-to-USB-C cables will also connect to HSxx ports.

To connect a 2018+ iPad Pro, the ideal solution is to use a USB-C to USB-C cable that explicitly supports USB 3.1/3.2 Gen 2 speeds. An example of such a cable is provided at the top of this guide in the section Components: Optional.

Modifications for Z490 Vision G:
Gigabyte's Z490 Vision G is somewhat of a cousin to the Vision D. The OpenCore configuration provided for the Vision D may be adapted for the Vision G by following the steps in the spoiler below.
  1. In the OpenCore ACPI folder, replace SSDT-UIAC-VISION-D-V2.aml with SSDT-UIAC-VISION-G-V2.aml located in the attached Vision G
  2. Then open config.plist in OpenCore Configurator and change the rename SSDT-UIAC-VISION-D-V2.aml to SSDT-UIAC-VISION-G-V2.aml in the ACPI section.
  3. Disable and/or remove SSDT-TB3HP.aml and SSDT-DTPG.aml from the ACPI section because the Vision G does not have an on-board Thunderbolt controller.
  4. Optional: Disable and/or remove IntelMausiEthernet.kext from the Kernel section. This driver is not used by the on-board 2.5 Gbps Ethernet port.
  5. Required: In BIOS, navigate to the IO Ports section and set Serial Port to Disabled.
  6. USB Audio users: Set CPU Base Clock to 100MHz (in BIOS).
  7. If using a GC-Titan Ridge Thunderbolt add-in-card, it is necessary to connect both the 3-pin and 5-pin Thunderbolt header cables to motherboard. Otherwise the card will not work and system will not sleep/wake properly. Refer to this post for details.
USB port layout for the Vision G is as follows:

Gigabyte Vision G USB Port Layout.png

Credit: @Ayvan

APFS Volumes and Reasons for Using:
There are many amazing yet underutilized features in macOS. APFS Volumes is a good example. It is the modern version of partitioning and allocates disk space on an as-needed basis instead of a predefined basis. This is especially helpful in the following scenarios:
  • Large home or user folder
  • Multiple users
  • Need for a scratch disk
  • Installing two versions of macOS on same disk
Some of the reasons for using APFS Volumes are:

Scenario 1: Large home or user folder
  • We have two NVMe M.2 SSDs, one for macOS and one for Windows.
  • EFI and macOS (just the System folders) take up relatively little space, but our home or user folder is huge.
  • We want to backup the EFI and macOS System on a regular basis and we want this backup to finish quickly.
  • We want to backup the huge home or user folder either through Time Machine or back it up to a large NAS or other drive.
  • We can accomplish this goal by creating an APFS volume dedicated for our home or user folder. Each APFS volume appears as its own disk, complete with a disk icon on the desktop.
Scenario 2: Multiple users
  • macOS allows multiple user accounts. In this case, however, each user is assigned their own home folder, and all home folders are in the single /Users directory.
  • We can instead give each user their own APFS volume, which can be backup up and managed separately from other users' volumes. Each APFS volume appears as its own disk, complete with a disk icon on the desktop.
Scenario 3: Need for a scratch disk
  • Some use cases benefit from having a scratch disk, which is a temporary holding place for data. This data does not need to be backed up or indexed by Spotlight.
  • We can also create an APFS volume for this purpose. Each APFS volume appears as its own disk, complete with a disk icon on the desktop.
Scenario 4: Installing two versions of macOS on same disk
  • With macOS 10.16 coming out later this year, some users may wish to install the new OS separately from Catalina, but on the same physical disk.
  • This can be done by creating an APFS volume for macOS 10.16. However, the same EFI folder must be capable of booting both operating systems (unless a separate USB boot disk is used for macOS 10.16).
This sounds good, but if we create separate APFS volumes for these use cases, don't we need to specify the size of each volume? And how can we know in advance the best way to size these volumes?

This is where APFS Volumes shine! Size does not need to be specified. Technically, we have the option to specify an initial size, but this is neither required nor really recommended. Instead, we create as many (but not too many) APFS volumes as we need. Each volume is a logical disk, and receives a disk icon on the desktop.

APFS introduces the concepts of (a) containers and (b) volumes. A container is, in effect, a fixed-size partition. Within the container are one or more volumes. Volumes use up the space inside their parent container. Over time, one volume might use up more space than another, and the container will fill up in an intelligent manner with no wasted space. Had we created fixed size partitions instead, it's possible that one or more partitions might never approach even 50% of the allocated capacity, and all of that disk space would go to waste. Fixed-size partitions are inherently wasteful.

The difference between (a) partitions and (b) volumes is illustrated below. Conventional partitions segment the disk into fixed-size sections, but this can be wasteful. In the example below, it's possible that one or more of the partitions might never approach their allocated size.

Screen Shot 2020-06-16 at 7.55.22 AM.png

With APFS Volumes, however, a single partition becomes the Container and inside we can create multiple Volumes. Each volume is a disk, complete with its own disk icon on the desktop. These volumes begin to consume space inside their container as data is written into them. Over time, each volume grows only in accordance with what it needs. There is no wasted disk space because unused space inside a container can be used by any of the volumes at any time.

Example: Create a new APFS volume named "Casey" and make it the home folder. This allows the home folder to be backed up separately from EFI and System.
  • APFS volumes are created in Disk Utility. We begin by selecting the Container disk in which the new volume is to be created:
    Disk Util - 1.png
  • Then we click "+" located next to "Volume" and specify a name:
    Disk Util - 2.png
  • Optionally we can click Size Options to specify a minimum and maximum size of the volume, but this defeats the purpose of dynamically-sized volumes. It's recommended to leave these values blank.
    Disk Util - 3.png
  • We click Add (in previous screenshot) and wait for the task to complete:
    Disk Util - 4.png
  • We can see that a new disk icon appears on the desktop:
    Disk Icons on Desktop.png
  • Now we assign the new disk volume to be our home or user folder. This is done from System Preferences --> Users & Groups:
    Move home folder - 1.png
  • After unlocking the padlock, we right-click on our user name and select Advanced Options... from the pop-up.
    Move home folder - 2.png
  • In Advanced Options we select Choose... and specify the new disk volume.
    Move home folder - 3.png
  • Note that macOS will not move or copy files from the existing home folder to the new home folder. We must do that ourselves.
  • We can also see that our new home volume can be backed up independently because it is in effect its own disk:
    New volume in CCC.png
Preserving Boot Order with Dual and Triple Boot Systems:
An issue with a dual-boot or triple-boot system (with MacOS, Windows and/or Linux) is that Windows and Linux may change the Boot Order specified in BIOS. After using Windows or Linux and rebooting, we often find that the system boots back into either Windows or Linux. Open the spoiler for a solution.
To avoid this problem, OpenCore provides the Boot Protect option. The default value is None, but if we change this to Bootstrap, then the boot order will be preserved and in fact BIOS will show OpenCore instead of a generic disk name.

  • Open config.plist in OpenCore Configurator and set Boot Protect to Bootstrap in the Misc --> Security section as shown.
  • Save and reboot.
OC - Boot Protect.png

If you now look at BIOS Setup --> Boot, you will see:
Reducing CPU Temps with Load Line Calibration and VCore:
Both Vision D and Vision G may boost CPU clocks on both "K" and non-K series Intel processors, which can lead to high CPU temperatures and therefore high fan speeds and higher noise. Fortunately, this issue can be addressed in a reasonably straightforward manner by adjusting three parameters in the Tweaker section of BIOS:
  • Vcore Voltage Mode --> set to Fixed Vcore
  • CPU Vcore --> set to 1.200V
  • CPU Vcore Loadline Calibration --> set to Low
Refer to this post for additional details and screenshots. Credit: @Ayvan
Additional information on Load Line Calibration (what it does, how it works) by @inapis.crazy

If Load Line Calibration is ineffective, refer to this post by @Uidi for an alternative method.

Configuring OpenIntelWireless drivers with OpenCore:
Refer to this mini-guide.

Fully Enable AppleVTD:
Enabling VT-d in macOS allows certain Thunderbolt devices such as those from Antelope Audio to work properly. In Big Sur, it also enables Apple's Thunderbolt-to-Gigabit Ethernet adapter, which is one of few Ethernet devices capable of AVB (Audio/Video Bridging). Refer to this post for details.

Troubleshooting / FAQ
This is a collection of troubleshooting hints and frequently asked questions (FAQ).
When using a DVI to HDMI cable or adapter to connect to a computer monitor (not TV), macOS may erroneously believe that a TV has a been connected, and therefore switch from RGB color space to YCbCr color space. This will result in a purple tint. There are at least two solutions:
Credit: @Ayvan
In some cases the error An error occurred validating the installer data. The download is either damaged or incomplete can appear during macOS installation if four memory DIMMs are installed (such as four 8GB modules). Temporarily remove two of the four modules (remove either A1/B1 or A2/B2). When macOS installation is complete, the modules can be reinstalled. Always shutdown the system and flip power switch on PSU to OFF when removing or installing memory modules.

Credit: @counterfactual
@Ayvan provides a good, concise answer to this question in this post.
Unfortunately not at this time. An effort was made to install Mojave 10.14.6, but it did not succeed. If or when a solution is found, this section will be updated.
At this time VideoProc is not compatible with AMD GPUs as stated by the company itself.

Also see this post about bitrate and HW versus SW encoding quality.

Credit: @jiffyslot and @doof
Certain AMD GPUs will be detected and listed in BIOS Setup, but when connecting a monitor to those GPUs, neither BIOS splash screen nor OpenCore boot menu will be displayed. This problem may be due to issues in the VBIOS of the GPU. A workaround is to enable CSM Support in BIOS Setup.

Update 2 Jul 2020: Updating to Vision D BIOS F5a may solve this problem.
The Corsair Commander Pro, when connected to one of the two internal USB 2.0 headers, may appear to macOS as an Uninterruptible Power Supply (UPS). This may in turn affect sleep and wake behavior. A workaround to this problem can be found by reading this post and the posts referenced within that post.

Credit: @jb007
25 Sep 2020: News Flash! Please see this post for latest information on WiFi 6 and BT 5.0 using on-board Intel CNVi Wireless Module.

If a Broadcom-based Bluetooth module is not installed, then it's possible to use a beta version of an Intel Bluetooth driver being developed by GitHub user zxystd. Instructions for doing so are provided in this post. Note, however, that the Handoff / Continuity family of features will not work.

Credit: @counterfactual
If the system contains only one NVMe SSD and no other drives, it is possible that Startup Disk will not appear in About this Mac. Although a proper solution is not known, the issue disappears when any number of additional drives are connected.

Credit: @LaurentMaldo
If persistent clicking noises are heard when using a UAD Apollo or Octo audio interface via Thunderbolt 3 at 192 kHz, please see this post:
Credit: @tonben
Unlike Clover's Default Boot Volume, OpenCore relies on System Preferences --> Startup Disk to specify the default boot volume. This is consistent with real Macs.
Startup Disk.png
There appears to be a bug in the implementation of PCIe Bifurcation in BIOS. Refer to this post for details.

Update 23 Jul 2020: In response to an online support ticket, Gigabyte explained that PCIe Bifurcation Support is for those cases where a PCIe Riser Cable is attached to Slot 1 and this riser cable is used to provide up to 3 external PCIe slots. In this case, all 16 lanes from the CPU can be assigned to Slot 1 and further bifurcated between the 3 external PCIe "sub-slots".
Until we find a better answer, whenever Boot Arguments are changed in config.plist --> NVRAM section, reset NVRAM at the OpenCore picker menu and reboot.
When the computer is simply shut down from within macOS (Apple Menu --> Shutdown) there is still some idle electrical current flowing to the motherboard. But if (a) the power switch on the Power Supply Unit (PSU) is flipped off or (b) power cable is pulled from the wall socket or (c) power strip or UPS is turned off then no electrical current will flow. When we subsequent power the system up, this is called a cold start. During cold starts, the firmware (BIOS) rescans the system for any hardware changes and will execute the "POST" sequence two times. It will seem as if the motherboard is rebooting. This is perfectly normal.
MacDrive is a Windows application that can read and write macOS disks. However, it seems to be adversely affecting Windows 10 (Update 2004) as described in this post. Until the problem is fixed, this application should be uninstalled in Windows.

Update 29 Jul 2020: OWC has acknowledged the problem and are working on a solution. A beta version is available to select users.

Credit: @lightmanrt
Gigabyte has implemented a CPU performance feature in the firmware (BIOS) that unfortunately has the effect of raising CPU temperature significantly (40C in idle for example). This also causes case fans to rev up and down frequently. This problem may not occur with all i7 and i9 CPUs, but if it does, the problem can be avoided by setting BIOS --> Load Line Calibration from Auto to Standard. Please refer to this post for additional information.

Credit: @techfreak85
While there are several reasons for getting this error during boot, if the error is preceded by AAPL: [EB|‘LD:LKC] } Err(0x9) then it may indicate a problem with slide value chosen by OpenCore. Slide values determine where in the UEFI memory map the macOS kernel will be loaded. If the memory region pointed to by a slide value is not large enough to accommodate the kernel, then the system will be unable to boot.
  • Refer to this post for an example of what the error looks like.
  • Refer to this post for one way of addressing the problem. It requires the debug version of OpenCore for determining the range of allowable slide values. Once a slide value has been selected and tested, the release version of OpenCore can once again be used.
Ask for assistance if needed.

Credit: @inapis.crazy
If you're using an Aquantia 10Gbps Ethernet card based on the AQC 107 controller, it may not work under macOS 11.x Big Sur. If so, the following patch may work:

* Find: 0F84C002 0000
* Replace: 660F1F44 0000

Please see this post.

Credit: @Diorama
If either or both the Apple Magic Mouse and Apple Magic Keyboard are connected to the system, the system will not enter sleep from the Apple Menu, nor will the system enter idle sleep unless the idle period has been changed to 30 minutes. By default, the idle period is around 15 minutes as specified in System Preferences --> Energy Saver.

Please see this post for details.

Credit: @RandC
WARNING: In Windows, do not install Intel Optane Drivers (part of Intel Rapid Storage drivers) because they will change BIOS --> SATA ports to Intel Optane instead of AHCI. SATA ports must be set to AHCI.

Please see this post for additional details on installing Windows 10.

If you are using an AMD Radeon VII GPU and finding that video rendering times with Final Cut Pro or other video editing applications are slower than expected, then it may be necessary to do the following:
  • In BIOS, set Initial Display Output to IGFX
  • In OpenCore Configurator, uncheck WhateverGreen.kext from the Kernel section
  • In OpenCore Configurator, change AAPL,ig-platform-id to 0x07009B3E (non-headless) in DeviceProperties
Please see this post for additional details and before/after render times.

Credit: @Diorama
The IntelMausi.kext does not support Wake on LAN in its default configuration. This driver controls the Intel i219 Ethernet port (the black one, not the red one). To enable Wake on LAN, the driver needs to be modified as described in this post. I've made these changes and compiled a RELEASE mode version of the driver, which is attached below. The filename is: IntelMausiWOL.kext

Credit: @xiuer
The brightness and volume on some -- not all -- monitors can be controlled via Brightness (F1/F2) and Volume Up/Down keys using the MonitorControl app on GitHub. Refer to this post for more information.
Some external 3.5" hard drive enclosures may not work reliably. Examples include:
  • Vantec NST-366SU3-BK
  • Vantec NST-380SU3-BK
Others, however, do work properly:
  • Vantec NST-D400SU3 (two-bay dock)
  • Orico 3588US3
Refer to this post for details.

Credit: @starchyfind
At the OpenCore Picker each bootable operating system is represented by a disk icon and a label under the icon. To change the label, follow the mini-guide located here (credit: @joevt)

Also see this post by @galisrule for additional cases.
When booting macOS from the OpenCore Picker, if you see the following error...

OCB: StartImage failed - Already started
Halting on critical error the following to recover:
  • At OpenCore Picker press <spacebar> to reveal additional options.
  • The option on the far right will be Reset NVRAM. Select that option.
  • When the system reboots, press DEL to enter BIOS Setup.
  • At the BOOT section, select the name of the macOS SSD to be the first Boot Priority even if the current first priority is "OpenCore".
  • Save changes and exit from BIOS Setup.
  • Now you should be able to boot macOS from the OpenCore Picker.
  • If you have a multi-boot system, go to System Preferences --> Startup Disk and choose the default startup volume.
Thanks to @starchyfind we have our first head-to-head CPU and GPU benchmark comparison across multiple SMBIOS names, including:
  • iMacPro 1,1
  • MacPro 7,1
  • iMac 20,2
  • iMac 20,1
  • iMac 19,1
Refer to this post for details.
User @maeluse has written a comprehensive post about his experiences with:
  • Intel Rapid Storage drivers (specifically we must avoid Intel Optane drivers from being installed)
  • Universal Audio Devices (UAD) device connection issues
  • "An error occurred validating the installer data"
  • Sizzling sound while recording audio with microphone connected to Apollo line input with Core Audio
This is a very information post:
Refer to this mini-guide for details on manually upgrading an existing version of OpenCore to the latest version.
Certain MSI RX 5700XT GPUs (and probably other MSI GPUs in the Navi family) may exhibit wake-from-sleep problems. Please refer to the post below for a DeviceProperties patch that may solve the problem.

Credit: @sffjawsh
Please see this post for instructions on enabling Slate VRS8 Thunderbolt Audio Interface. This is a tricky device and needs a special procedure.
To fix problems with "Unlock with Apple Watch", refer to this article on the Apple website:

Credit: @tdarkc
WARNING! Make a full bootable backup of Big Sur before attempting this.
The procedure for mounting root filesystem with read/write permissions is quite different in Big Sur compared to Catalina. The procedure is detailed in the following places:

Credit: @jabjabjab
With system names such as iMac19,1 and iMac20,2 we cannot use the tv app in macOS Big Sur due to DRM (digital rights management) issues. In the meantime, the workaround stated in this post might help. A more succinct version of that post is available here.

Credit: @lerass
The OpenCore EFI folder provided in this build guide sets the Boot Chime to play through AudioOut port 0, which is the green headphone jack on the rear IO panel or the front-panel headphone jack. However, to play the Boot Chime through the Optical Digital Output port on the rear IO panel, set AudioOut to 4 in OpenCore Configurator --> UEFI --> Audio section.

Credit: @Lukey1979
When attempting to boot a Windows disk using OpenCore it is possible to encounter acpi-bios-error. One solution for this is described in this post.
To install Mojave on the Z490 Vision D or Z490 Vision G, edit the Kernel --> Add section, and change:
  • Cpuid1Data to ED060900 00000000 00000000 00000000
  • Cpuid1Mask to FFFFFFFF 00000000 00000000 00000000
Save the config.plist and then boot the Mojave installer. Refer to this post for a screenshot.

Credit: @mikonmac
If HWMonitorSMC2 is not showing any GPU sensor information, follow the steps listed in this post.
AMD's RX 6000 series GPUs are not currently supported in macOS. While we wait for native drivers to appear (hopefully) we can temporarily hide the 6000-series GPU from macOS so that the system boots up properly and sleeps/wakes properly. Refer to this mini-guide for details.

For a brief technical explanation of the SSDT, refer to this post.
A brief look at OpenCanopy 0.6.8
AMD RX 6000 series GPUs tend to work best when the System Product Name is MacPro7,1. Unfortunately, this often produces a series of annoying memory notifications. We can finally avoid this problem by configuring memory modules properly in OpenCore config.plist as described in this post.

Credit: @rj510
In some rare cases, a macOS update initiated by System Preferences --> Software Update or by running the full installer may go through a couple of reboot cycles but not finish properly. If this happens, try the remedy described in this post.
See this post for a detailed explanation of the SIP bit flags.
Switching to iMacPro1,1 may fix problems related to Apple Music lossless and other playback issues. Refer to this post for details.
Refer to this post for instructions on enabling and disabling AppleVTD in OpenCore 0.7.2 and later. Some Windows boot problems can be solved by disabling AppleVTD.
Refer to this post for an OpenCore EFI suitable for installing macOS High Sierra. Credit: @marth
To create and customize a Thunderbolt SSDT using the beautifully designed HackinDROM website by @Inqnuam, refer to this post.
Not every Z490 Vision D owner has an unusable Intel i225-V Ethernet port in Monterey. Whether the port works or not depends on the firmware installed on the port. Some Z490 Vision D owners are luckier than others; if your i225-V port does not connect in Monterey, see this post for a solution.
This is a rare problem, but if both of the on-board Ethernet ports have the same MAC address, it is necessary to program the correct unique MAC addresses. The procedure is explained here by @R-88.
Please refer to this post for details on the problem and the solution. How the patch works is described in this Patch Theory post.


What Works

  • Reboot, shutdown, sleep, wake
  • Continuity features: Handoff, AirDrop, Unlock with Apple Watch, Continuity Camera, Sidecar
  • iGPU for compute tasks including QuickSync, Preview, Quick Look, HEVC, H.264
  • WiFi and Bluetooth
  • Thunderbolt with hot plug (Thunderbolt Bus requires firmware flashing)
  • Built-in audio
What Doesn't Work
  • On-board HDMI port; this also affect Z390 Designare and may be due to changes in macOS Catalina or WhateverGreen
    • On-board HDMI port is working once again, starting with WhateverGreen 1.4.1 and Lilu 1.4.6
  • USB 3.x devices will not hot-connect on either of the two Thunderbolt ports, but they will hot-connect on front-panel USB-C port. These devices will work on Thunderbolt ports if they are connected before boot.
What May or May Not Work
  • Three or more monitors may require some experimentation or workaround; the make/model of the monitor can make a difference; advisable to use current generation monitors that support HDMI 1.4/2.0 and DisplayPort 1.1/1.2/1.4.
  • Flatscreen TVs may require manually reducing Refresh Rate in System Preferences --> Displays to 30Hz and in some cases also disabling HDR or Deep Color modes on the TV.
  • Thunderbolt 1 devices by and large will not work unless Thunderbolt firmware is flashed.

Vision D Benchmarks.png


Special thanks to the following:

Edits / Updates
  • 01 Jun 2020: Draft 1
  • 05 Jun 2020: Rev 1
  • 08 Jun 2020: Added N-D-K version of 0.5.9 is not yet available so standard OpenCore 0.5.9 has been added. To switch from 0.5.8 to this version of 0.5.9, start by backing up or renaming the existing EFI folder. After downloading and unzipping the attached OpenCore 0.5.9 ZIP, rename the top level folder to EFI and move it to the EFI partition. Make a note of the existing MLB, System Serial Number, and System UUID.
    • If using AMD GPU, open the new config-AMD-GPU.plist and enter MLB, System Serial Number, and System UUID into the PlatformInfo --> DataHub - Generic - PlatformNVRAM section. Then rename this file to config.plist
    • If using iGPU to drive a display monitor, open the new config-Intel-iGPU.plist and enter MLB, System Serial Number, and System UUID into the PlatformInfo --> DataHub - Generic - PlatformNVRAM section. Then rename this file to config.plist
  • 10 Jun 2020: Added Modifications for Z490 Vision G
  • 13 Jun 2020: Added USB Type C Ports and USB 2.0 Protocol
  • 13 Jun 2020: Added Troubleshooting / FAQ
  • 16 Jun 2020: Added APFS Volumes and Reasons for Using
  • 19 Jun 2020: Replaced Vision G Package with new version (see README inside the package)
  • 19 Jun 2020: Added that enables USB 2 protocol on all USB-C ports; this is done by using a new SSDT-UIAC-VISION-D-V2.aml and enabling the kernel quirk XhciPortLimit
  • 13 Jul 2020: Step 7 updated for firmware (BIOS) version F5d/F5 that uses a revised GUI and exposes CFG-Lock in the GUI
  • 23 Jul 2020: Added Preserving Boot Order with Dual and Triple Boot Systems
  • 29 Jul 2020: Added Step 5 to Vision G section (under Tech Talk) for disabling Serial Port in BIOS
  • 03 Aug 2020: Updated the guide for OpenCore 0.6.0
  • 07 Sep 2020: Updated the guide for OpenCore 0.6.1
  • 07 Sep 2020: Added Reducing CPU Temps with Load Line Calibration and VCore in Tech Talk
  • 10 Sep 2020: Re-uploaded OC 0.6.1 EFI ZIP with USBInjectAll version 0.7.6 that adds compatibility with iMac20,1 and iMac20,2
  • 25 Sep 2020: Added Performance comparison across several SMBIOS names in Troubleshooting / FAQ section.
  • 27 Sep 2020: Added Extensive User Write-Up -- Intel Optane, UAD Drivers, UAD Sizzling Sound, etc. in Troubleshooting / FAQ section.
  • 06 Oct 2020: Updated the guide for OpenCore 0.6.2
  • 03 Nov 2020: Updated the guide for OpenCore 0.6.3
  • 07 Dec 2020: Updated the guide for OpenCore 0.6.4
  • 04 Jan 2021: Updated the guide for OpenCore 0.6.5
  • 08 Jan 2021: Updated the OpenCore 0.6.5 EFI to enable Fake CPU ID on Catalina and newer versions
  • 02 Feb 2021: Updated the guide for OpenCore 0.6.6
  • 04 Feb 2021: Updated new EFI for OpenCore 0.6.6 that goes back to HfsPlus.efi instead of using OpenHfsPlus.efi due to problems found with OpenHfsPlus.efi
  • 04 Mar 2021: Updated the guide for OpenCore 0.6.7
  • 05 Apr 2021: Updated the guide for OpenCore 0.6.8
  • 03 May 2021: Updated the guide for OpenCore 0.6.9
  • 07 Jun 2021: Updated the guide for OpenCore 0.7.0
  • 05 Jul 2021: Updated the guide for OpenCore 0.7.1
  • 03 Aug 2021: Updated the guide for OpenCore 0.7.2
  • 07 Sep 2021: Updated the guide for OpenCore 0.7.3
  • 04 Oct 2021: Updated the guide for OpenCore 0.7.4


    880 bytes · Views: 1,230
    3.4 MB · Views: 2,025
    3.8 MB · Views: 1,336
  • Vision G
    2.6 KB · Views: 1,396
    3.8 MB · Views: 1,845
    978 bytes · Views: 1,079
    56.2 KB · Views: 630
    4.8 MB · Views: 613
    4.7 MB · Views: 568
    4.2 MB · Views: 473
    4.2 MB · Views: 484
    4.3 MB · Views: 440
    4.3 MB · Views: 397
    4.4 MB · Views: 430
    5.7 MB · Views: 310
    4.6 MB · Views: 1,479
Last edited:
General note for those planning to port OpenCore from Z390 to Z490:

Screen Shot 2020-05-27 at 1.07.14 PM.png

Update: MSR 0xE2 has been unlocked using “CFGLock.efi” as explained in Step 7 of post 1.

Update 8 Jun 2020: With OpenCore 0.5.9 and Catalina 10.15.5 we can use SSDT-EC.aml attached here. This has already been added to the new OpenCore 0.5.9 ZIP file at the end of Post #1. This particular version of the SSDT is adapted for Vision D. Do not use the general SSDT-EC-USBX.aml from Dortania.


  • SSDT-EC.aml
    204 bytes · Views: 685
Last edited:
We are huge fans of Thermaltake's Core P3 and P5 style Cases.

There are not available so, I am repurposing another generic Corsair just for testing.

Will be at it soon.
** Update: if you downloaded the ZIP file in Post 1, please re-download because kexts folder was empty **
Last edited:
I experienced a power supply issue. A new EVGA DOA. I have a second a PSU from another build to be able to continue.

10pm and the Z490 test build is completed.
On to installation process.

I have seen your posted update and will proceed accordingly.
One query come to mind.

Previously, it was important to boot in Windows and install Gigabyte Drivers to "wake-up" the onboard TB options.
I have not done so. My assumption is that we do not need to.
I experienced a power supply issue. A new EVGA DOA. I have abscond a PSU from another build to be able to continue.

10pm and the Z490 test build is completed.
On to installation process.

I have seen your posted update and will proceed accordingly.
One query come to mind.

Previously, it was important to boot in Windows and install Gigabyte Drivers to "wake-up" the onboard TB options.
I have not done so. My assumption is that we do not need to.
Correct — Windows is absolutely not needed.
I thought windows/TB3 thing is for GC-Titan Ridge card, right?

I experienced a power supply issue. A new EVGA DOA. I have abscond a PSU from another build to be able to continue.

10pm and the Z490 test build is completed.
On to installation process.

I have seen your posted update and will proceed accordingly.
One query come to mind.

Previously, it was important to boot in Windows and install Gigabyte Drivers to "wake-up" the onboard TB options.
I have not done so. My assumption is that we do not need to.
I thought windows/TB3 thing is for GC-Titan Ridge card, right?
As I understood, Windows was required to get TB going on the motherboard.
@CaseySJ WE ARE UP!!!

Instructions were exquisite. Painless installation process.

My very first time with OC. I believe I am now a fan.

NVMe self booting, all looks quite splendid so far.

I am not going to fiddle until further communications from you.

Thank you ever so much,
@CaseySJ WE ARE UP!!!

Instructions were exquisite. Painless installation process.

My very first time with OC. I believe I am now a fan.

NVME self booting, all looks quite splendid so far.

I am not going to fiddle until further communications from you.

Thank you ever so much,
Good job! You were Test Subject #1, so it seems the procedure checks out.

P.S. Feel free to post a photo of the system, but remove EXIF information from photo. I use Photo Zapper from the Mac App Store.
Last edited: