• Become a Premium Member for $25/year with no ads to improve your community experience.

CPU Compatibility List For macOS [Intel/AMD]

Striker

Moderator
Staff member
Donator
Joined
Oct 20, 2018
Messages
23
Motherboard
Gigabyte Z590 Vision G
CPU
Intel Core i9 11900F
Graphics
Sapphire Nitro plus Radeon RX590 Special Edition
OS X/macOS
10.13.x
Bootloader
  1. OpenCore (UEFI)
Mac
  1. Mac mini
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
CPU Compatibility List For OS X and macOS [Intel/AMD]

Overview


OS X and macOS do not support a major number of CPUs, unlike Windows or Unix.

QUICK INFO:
  • OS X & macOS support all CPUs till date, starting from Pentium 4
  • CPUs with 32-bit architecture only support OS X 10.4.1 to 10.6.8
  • CPUs with 64-bit architecture supports OS X 10.4.1 To macOS 12.0 (Current)
  • Intel versions of OS X & macOS requires SSE3
  • 64-bit versions of OS X & macOS requires SSSE3
  • macOS 10.12 i.e. macOS Sierra and newer requires SSE4
  • macOS 10.14 i.e. macOS Mojave and newer requires SSE4.2
  • SSE4.1 CPUs also supports macOS 12.0 (Current) with TELEMETRAP


CPU Limitations


With macOS, there are numerous CPU limitations you need to be aware of before buying a CPU or stepping into an installation as that would be a waste of time and resources, together. This is due to the limited amount of CPU Apple supports, so we're either limited by Apple or the patches community has created. For more info on CPU Limitations, see below.

General Limitations
The general limitations apply to both, Intel and AMD CPUs
  • Core/Thread Count
    • OS X 10.10 and older supports up to a maximum of 24 threads which means you cannot use a CPU with more than 12 Cores, including Dual CPUs.
    • OS X 10.11 and newer supports up to a maximum of 64 threads which means you cannot use a CPU with more than 32 Cores, including Dual CPUs.
  • Dual Socket
    • Dual Socket users using MacPro6,1, MacPro7,1, or iMacPro1,1 SMBIOS will need to use AppleMCEReporterDisabler in macOS Catalina 10.15 and later.

FOR INTEL CPUs
  • CPUs from 2012 are supported by Apple's VT-d function. Any prior CPU will lack VT-d feature even if provided by Intel.
  • Dual Socket CPUs are supported with up to a maximum of 64 threads. In addition, for Dual Socket CPU users, you will need to use AppleMCEReporterDisabler in macOS Catalina.
  • Pentium, Celeron and Atom
    • Pentium, Celeron, and Atom CPUs lack AVX instructions which is required for booting OS X/macOS. To use these CPUs under macOS, you need to use an AVX patch.
    • Ivy Bridge and Low-End CPUs running OS X 10.11 require a Fake CPUID and -xcpm boot flag for booting into macOS.
    • macOS 10.12 and newer requires an XCPM patch along with a Fake CPUID for booting into macOS.
  • Intel's Rocket Lake and Alder Lake CPUs are not natively supported by any OS X/macOS version and require a CPU spoof to boot, regardless of the bootloader.
FOR AMD CPUs
  • AMD CPUs are finally supported with the help of developers in this community. However, AMD CPUs can be used in a limited way but are seriously discouraged for any production related workload.
  • Mobile CPUs
    • AMD Mobile CPUs (Laptop CPUs) are generally not supported, regardless of GPU, whether integrated or dedicated.
  • Kernel DMA Protection
    • AMD CPUs do not support AMD-Vi on macOS, which is similar to Intel's VT-d feature, required for Kernel DMA Protection, demanded by several Thunderbolt Devices.
    • This includes all AMD CPUs. However, a workaround for this feature is to use macOS Sierra.
  • Adobe Support
    • Most of Adobe's suite relies on Intel's Memfast instruction set, resulting in crashes with AMD CPUs
    • You can disable functionality like RAW support to avoid crashing: Adobe Fixes
  • Virtual Machines relying on AppleHV
    • This includes VMWare, Parallels, Docker, Android Studio, etc
    • VirtualBox is the sole exception as they have their own hypervisor
    • VMware 10 and Parallels 13.1.0 do support their own hypervisor, however, using such outdated VM software poses a large security threat
  • Audio Distortion
    • There is a known Audio Distortion issue for the onboard audio chips. A workaround is to set the GPU to PCIe 3.0 speed.
  • 32-Bit support
    • For those still relying on 32-Bit software in Mojave and below, note that the Vanilla patches do not support 32-bit instructions
    • A workaround is to install a custom kernel, however, you lose iMessage support and no support is provided for these kernels
  • Stability issues on many apps
    • Audio-based apps are the most prone to issues, ie. Logic Pro
    • DaVinci Resolve has been known to have sporadic issues as well


RECOMMENDATIONS
  • From Ivy Bridge (Consumer Series) to Comet Lake for full native support.
  • Rocket Lake, Alder Lake and Raptor Lake (spoofed to Comet Lake)

Intel CPU Compatibility List



Intel Consumer Series
VendorCode NameSierraHigh SierraMojaveCatalinaBig SurMontereyNotes
IntelPreslerNoNoNoNoNoNo-
IntelCedar MillNoNoNoNoNoNo-
IntelConroeNoNoNoNoNoNo-
IntelKentsfieldNoNoNoNoNoNo-
IntelWolfdaleYesYesYesYesYesYes
  • CPU Spoof Required
  • No SSE4.2
  • No iGPU
IntelYorkfieldYesYesYesYesYesYes
  • CPU Spoof Required
  • No SSE4.2
  • No iGPU
IntelLynnfieldYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelBloomfieldYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelClarkdaleYesYesYesYesYesNot Tested
  • CPU Spoof Required iGPU
  • Patching Required (From macOS High Sierra)
IntelGulftownYesYesYesYesYesYes
  • CPU Spoof Require
  • No iGPU
IntelSandy BridgeYesYesYesYesYesYes
  • iGPU Patching Required (From macOS Mojave)
IntelIvy BridgeYesYesYesYesYesYes
  • iGPU Patching Required (For macOS Monterey)
IntelHaswellYesYesYesYesYesYes-
IntelCrystal WellYesYesYesYesYesYes-
IntelDevil's CanyonYesYesYesYesYesYes-
IntelBroadwellYesYesYesYesYesYes-
IntelSkylakeYesYesYesYesYesYes-
IntelKaby LakeYesYesYesYesYesYes-
IntelCoffee LakeYesYesYesYesYesYes
  • iGPU Supports From macOS Catalina
IntelComet LakeYesYesYesYesYesYes
  • iGPU Supports From macOS Catalina
IntelRocket LakeNoYesYesYesYesYes
  • CPU Spoof Required
  • iGPU Not Supported
IntelAlder LakeNoYesYesYesYesYes
  • CPU Spoof Required
  • iGPU Not Supported

Intel HEDT (High End Desktop)
VendorCode NameSierraHigh SierraMojaveCatalinaBig SurMontereyNotes
IntelNehalem EPYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelWestmere-EP/GulftownYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelSandy Bridge-EYesYesYesYesYesYes
  • No iGPU
IntelIvy Bridge-EYesYesYesYesYesYes
  • No iGPU
IntelHaswell-EYesYesYesYesYesYes
  • No iGPU
IntelBroadwell-EYesYesYesYesYesYes
  • No iGPU
IntelSkylake-X/WYesYesYesYesYesYes
  • No iGPU
IntelKaby Lake-XYesYesYesYesYesYes
  • No iGPU
IntelCascade Lake-X/WYesYesYesYesYesYes
  • No iGPU

Intel Server
VendorCode NameSierraHigh SierraMojaveCatalinaBig SurMontereyNotes
IntelConroeNoNoNoNoNoNo-
IntelKentsfieldNoNoNoNoNoNo-
IntelWoodcrestNoNoNoNoNoNo-
IntelClovertownNoNoNoNoNoNo-
IntelTigertonNoNoNoNoNoNo-
IntelWolfdaleYesYesYesYesYesYes
  • CPU Spoof Required
  • No SSE4.1(Some), SSE4.2
  • No iGPU
IntelYorkfieldYesYesYesYesYesYes
  • CPU Spoof Required
  • No SSE4.2
  • No iGPU
IntelHarpertownYesYesYesYesYesYes
  • CPU Spoof Required
  • No SSE4.2
  • No iGPU
IntelDunningtonYesYesYesYesYesYes
  • CPU Spoof Required
  • No SSE4.2
  • No iGPU
IntelLynnfieldYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelBloomfieldYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelGainestown/Nehalem EPYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelBeckton/Nehalem EXYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelClarkdaleYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelWestmere EP/EXYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelSandy BridgeYesYesYesYesYesYes
  • No iGPU
IntelSandy Bridge-EP/JaketownYesYesYesYesYesYes
  • No iGPU
IntelSandy Bridge-GladdenYesYesYesYesYesYes
  • No iGPU
IntelIvy BridgeYesYesYesYesYesYes
  • No iGPU
IntelIvy Bridge-GladdenYesYesYesYesYesYes
  • No iGPU
IntelIvy Bridge-EPYesYesYesYesYesYes
  • No iGPU
IntelIvy Bridge-EX/IvytownYesYesYesYesYesYes
  • No iGPU
IntelHaswell/EN/EP/EXYesYesYesYesYesYes
  • No iGPU
IntelLynx PointYesYesYesYesYesYes
  • No iGPU
IntelWellsburgYesYesYesYesYesYes
  • No iGPU
IntelBroadwellYesYesYesYesYesYes
  • No iGPU
IntelBroadwell-DE/H/EP/EXYesYesYesYesYesYes
  • No iGPU
IntelHewitt lakeYesYesYesYesYesYes
  • No iGPU
IntelSkylake-X/SP/DE/DTYesYesYesYesYesYes
  • No iGPU
IntelKaby LakeYesYesYesYesYesYes
  • No iGPU
IntelKaby Lake-DTYesYesYesYesYesYes
  • No iGPU
IntelCoffee LakeYesYesYesYesYesYes
  • No iGPU
IntelCooper LakeYesYesYesYesYesYes
  • No iGPU
IntelComet LakeYesYesYesYesYesYes
  • No iGPU
IntelIce LakeYesYesYesYesYesYes
  • No iGPU
IntelRocket LakeYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU
IntelTiger LakeYesYesYesYesYesYes
  • CPU Spoof Required
  • No iGPU

Intel Mobile CPU
VendorCode NameSierraHigh SierraMojaveCatalinaBig SurMontereyNotes
IntelYonahNoNoNoNoNoNo-
IntelMeromNoNoNoNoNoNo-
IntelPenrynYesYesYesYesYesYes
  • CPU Spoof Required
  • No SSE4.2
  • No iGPU
IntelClarksfieldYesYesYesYesYesYes
  • CPU Spoof Required
  • iGPU Patching Required (From macOS High Sierra)
IntelArrandaleYesYesYesYesYesYes
  • CPU Spoof Required
  • iGPU Patching Required (From macOS High Sierra)
IntelSandy Bridge-MYesYesYesYesYesYes
  • iGPU Patching Required (From macOS Mojave)
IntelIvy Bridge-MYesYesYesYesYesYes
  • iGPU Patching Required (For macOS Monterey)
IntelHaswell/Haswell-MB/LPYesYesYesYesYesYes-
IntelCrystal WellYesYesYesYesYesYes-
IntelBroadwell/Broadwell-H/U/YYesYesYesYesYesYes-
IntelSkylake-/H/U/YYesYesYesYesYesYes-
IntelKaby Lake-H/U/YYesYesYesYesYesYes-
IntelKaby Lake RYesYesYesYesYesYes-
IntelKaby Lake GYesYesYesYesYesYes
  • iGPU Not Supported
IntelAmber lake-YYesYesYesYesYesYes
  • iGPU Supports From macOS Mojave
IntelCoffee Lake-H/U/H-RefreshYesYesYesYesYesYes
  • iGPU Supports From macOS High Sierra
IntelWhiskey LakeYesYesYesYesYesYes
  • iGPU Supports From macOS High Sierra
IntelComet Lake-H/UYesYesYesYesYesYes
  • iGPU Supports From macOS Catalina
IntelCannon lake-UYesYesYesYesYesYes
  • iGPU Supports From macOS Catalina
IntelIce Lake-U/YYesYesYesYesYesYes
  • iGPU Supports From macOS Catalina
IntelTiger Lake-H35/UP3/UP4YesYesYesYesYesYes
  • CPU Spoof Required
  • iGPU Not Supported


AMD CPU Compatibility List

AMD Consumer Series
VendorCode NameSierraHigh SierraMojaveCatalinaBig SurMontereyNotes
AMDZambeziYesYesYesYesYesYes
AMDVisheraYesYesYesYesYesYes
AMDZurichNoNoNoNoNoNo
AMDValenciaNoNoNoNoNoNo
AMDInterlagosNoNoNoNoNoNo
AMDBristol RidgeYesYesYesYesYesYes
AMDKabini
AMDBeema
AMDMullins
AMDTemashNoNoNoNoNoNo
AMDNaples
AMDWhitehaven
AMDSummit Ridge
AMDRaven RidgeiGPU Not Supported
AMDDali
AMDColfax
AMDPinnacle Ridge
AMDPicasso
AMDRome
AMDMatisse
AMDCastle Peak
AMDRenoir
AMDLucienne
AMDVermeer
AMDCezanne
AMDMilan
 
Last edited by a moderator:
HELP GUYS I HAVE ASUS PRIME A320M-K WITH BRISTOL RIDGE PROCESSOR AND 16 GB RAMS DDR4 IS IT POSSIBLE TO INSTALL MAC OS MONTEREY ...IF IT IS PLEASE HELP ...I HAVE ATTACHED MY SPECS
 

Attachments

  • Screenshot 2022-11-26 182000.jpg
    Screenshot 2022-11-26 182000.jpg
    86.9 KB · Views: 47
HELP GUYS I HAVE ASUS PRIME A320M-K WITH BRISTOL RIDGE PROCESSOR AND 16 GB RAMS DDR4 IS IT POSSIBLE TO INSTALL MAC OS MONTEREY ...IF IT IS PLEASE HELP ...I HAVE ATTACHED MY SPECS
Mostly Ryzen series are supported.
 
I have a working VirtualBox + Monterey setup on an 8600K (Coffee Lake) system that I'm trying to migrate to a 13900K (Raptor Lake). However, the virtual machine will not boot on the 13900K. I get the initial screen of text, and it looks good, but then it just sits there (hung). On the 8600K, after a second or so, the screen is cleared and more text starts scrolling.

I tried to get the "hostcpuids" from the 8600K system and install them in the virtual machine via VBoxManage, but that didn't work. Seeing your suggestion to spoof Comet Lake, I then found a log trace of a Comet Lake machine and tried to inject that configuration, but that also failed. Here are the VBoxManager commands that I used for that:

Code:
VBoxManage modifyvm Monterey --cpuidset 00000000  00000016 756e6547 6c65746e 49656e69
VBoxManage modifyvm Monterey --cpuidset 00000001  000a0653 00100800 7ffafbbf bfebfbff
VBoxManage modifyvm Monterey --cpuidset 00000002  76036301 00f0b5ff 00000000 00c30000
VBoxManage modifyvm Monterey --cpuidset 00000003  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 00000004  1c004121 01c0003f 0000003f 00000000
VBoxManage modifyvm Monterey --cpuidset 00000004  1c004122 01c0003f 0000003f 00000000
VBoxManage modifyvm Monterey --cpuidset 00000004  1c004143 00c0003f 000003ff 00000000
VBoxManage modifyvm Monterey --cpuidset 00000004  1c03c163 03c0003f 00002fff 00000006
VBoxManage modifyvm Monterey --cpuidset 00000004  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 00000005  00000040 00000040 00000003 11142120
VBoxManage modifyvm Monterey --cpuidset 00000006  000027f7 00000002 00000001 00000000
VBoxManage modifyvm Monterey --cpuidset 00000007  00000000 029c67af 40000000 bc000400
VBoxManage modifyvm Monterey --cpuidset 00000008  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 00000009  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 0000000a  07300404 00000000 00000000 00000603
VBoxManage modifyvm Monterey --cpuidset 80000000  80000008 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 80000001  00000000 00000000 00000121 2c100800
VBoxManage modifyvm Monterey --cpuidset 80000002  65746e49 2952286c 726f4320 4d542865
VBoxManage modifyvm Monterey --cpuidset 80000003  35692029 3430312d 43203030 40205550
VBoxManage modifyvm Monterey --cpuidset 80000004  392e3220 7a484730 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 80000005  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 80000006  00000000 00000000 01006040 00000000
VBoxManage modifyvm Monterey --cpuidset 80000007  00000000 00000000 00000000 00000100
VBoxManage modifyvm Monterey --cpuidset 80000008  00003027 00000000 00000000 00000000

What am I doing wrong? Do I need to install a hackentosh bootloader like people running on bare metal?
 
I have a working VirtualBox + Monterey setup on an 8600K (Coffee Lake) system that I'm trying to migrate to a 13900K (Raptor Lake). However, the virtual machine will not boot on the 13900K. I get the initial screen of text, and it looks good, but then it just sits there (hung). On the 8600K, after a second or so, the screen is cleared and more text starts scrolling.

I tried to get the "hostcpuids" from the 8600K system and install them in the virtual machine via VBoxManage, but that didn't work. Seeing your suggestion to spoof Comet Lake, I then found a log trace of a Comet Lake machine and tried to inject that configuration, but that also failed. Here are the VBoxManager commands that I used for that:

Code:
VBoxManage modifyvm Monterey --cpuidset 00000000  00000016 756e6547 6c65746e 49656e69
VBoxManage modifyvm Monterey --cpuidset 00000001  000a0653 00100800 7ffafbbf bfebfbff
VBoxManage modifyvm Monterey --cpuidset 00000002  76036301 00f0b5ff 00000000 00c30000
VBoxManage modifyvm Monterey --cpuidset 00000003  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 00000004  1c004121 01c0003f 0000003f 00000000
VBoxManage modifyvm Monterey --cpuidset 00000004  1c004122 01c0003f 0000003f 00000000
VBoxManage modifyvm Monterey --cpuidset 00000004  1c004143 00c0003f 000003ff 00000000
VBoxManage modifyvm Monterey --cpuidset 00000004  1c03c163 03c0003f 00002fff 00000006
VBoxManage modifyvm Monterey --cpuidset 00000004  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 00000005  00000040 00000040 00000003 11142120
VBoxManage modifyvm Monterey --cpuidset 00000006  000027f7 00000002 00000001 00000000
VBoxManage modifyvm Monterey --cpuidset 00000007  00000000 029c67af 40000000 bc000400
VBoxManage modifyvm Monterey --cpuidset 00000008  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 00000009  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 0000000a  07300404 00000000 00000000 00000603
VBoxManage modifyvm Monterey --cpuidset 80000000  80000008 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 80000001  00000000 00000000 00000121 2c100800
VBoxManage modifyvm Monterey --cpuidset 80000002  65746e49 2952286c 726f4320 4d542865
VBoxManage modifyvm Monterey --cpuidset 80000003  35692029 3430312d 43203030 40205550
VBoxManage modifyvm Monterey --cpuidset 80000004  392e3220 7a484730 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 80000005  00000000 00000000 00000000 00000000
VBoxManage modifyvm Monterey --cpuidset 80000006  00000000 00000000 01006040 00000000
VBoxManage modifyvm Monterey --cpuidset 80000007  00000000 00000000 00000000 00000100
VBoxManage modifyvm Monterey --cpuidset 80000008  00003027 00000000 00000000 00000000

What am I doing wrong? Do I need to install a hackentosh bootloader like people running on bare metal?

Both the CPUs are compatible. Not sure why are you using VirtualBox over a Bare metal setup which will be not be more stable but will perform much better in terms of performance.
 
I have many VMs with many versions of MacOS and Windows. They are more or less portable between host machines (at least for older CPUs) and can be reimaged easily.

Anyway, any idea what the issue is? As I said, I just copied the guest from an 8600K to a 13900K and now it's hanging during boot. Should I try installing a bootloader (Clover?) and the other tools used to get a hackentosh running on bare metal?
 
I have many VMs with many versions of MacOS and Windows. They are more or less portable between host machines (at least for older CPUs) and can be reimaged easily.

Anyway, any idea what the issue is? As I said, I just copied the guest from an 8600K to a 13900K and now it's hanging during boot. Should I try installing a bootloader (Clover?) and the other tools used to get a hackentosh running on bare metal?

Yes, that's more better approach.
 
I'd be installing them inside the guest machine, not on my host of course,. This hasn't been needed with VirtualBox for several MacOS releases.

So far I tried:
- Disabling the effiency cores in the BIOS
- Disabling Hyperthreading in the BIOS
- Disabling Virtualization in the BIOS (VB won't run without, so no go here)
 
I'd be installing them inside the guest machine, not on my host of course,. This hasn't been needed with VirtualBox for several MacOS releases.

So far I tried:
- Disabling the effiency cores in the BIOS
- Disabling Hyperthreading in the BIOS
- Disabling Virtualization in the BIOS (VB won't run without, so no go here)

Why not setup it as a Bare Metal on a separate disk?
 
As mentioned, VMs are much more flexible. I may have 20 MacOS VMs sitting around and I can run any one of them easily, or create a temporary copy of one, use it and then delete the used one.

Anyway, I found a solution here. Several of the built-in CPU types work, such as "Intel Core i7-6700K". Wasn't needed on the 8600K but apparently is on the 13900K.
 

Latest posts

Forum statistics

Threads
1,376
Messages
13,330
Members
19,601
Latest member
AloneWarrior15