CPU Compatibility List For macOS [Intel/AMD]

[Striker]

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

Vendor	Code Name	Sierra	High Sierra	Mojave	Catalina	Big Sur	Monterey	Notes
Intel	Presler	No	No	No	No	No	No	-
Intel	Cedar Mill	No	No	No	No	No	No	-
Intel	Conroe	No	No	No	No	No	No	-
Intel	Kentsfield	No	No	No	No	No	No	-
Intel	Wolfdale	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No SSE4.2 No iGPU
Intel	Yorkfield	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No SSE4.2 No iGPU
Intel	Lynnfield	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Bloomfield	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Clarkdale	Yes	Yes	Yes	Yes	Yes	Not Tested	CPU Spoof Required iGPU Patching Required (From macOS High Sierra)
Intel	Gulftown	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Require No iGPU
Intel	Sandy Bridge	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Patching Required (From macOS Mojave)
Intel	Ivy Bridge	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Patching Required (For macOS Monterey)
Intel	Haswell	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Crystal Well	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Devil's Canyon	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Broadwell	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Skylake	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Kaby Lake	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Coffee Lake	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Supports From macOS Catalina
Intel	Comet Lake	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Supports From macOS Catalina
Intel	Rocket Lake	No	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required iGPU Not Supported
Intel	Alder Lake	No	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required iGPU Not Supported

Intel HEDT (High End Desktop)

Vendor	Code Name	Sierra	High Sierra	Mojave	Catalina	Big Sur	Monterey	Notes
Intel	Nehalem EP	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Westmere-EP/Gulftown	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Sandy Bridge-E	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Ivy Bridge-E	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Haswell-E	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Broadwell-E	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Skylake-X/W	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Kaby Lake-X	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Cascade Lake-X/W	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU

Intel Server

Vendor	Code Name	Sierra	High Sierra	Mojave	Catalina	Big Sur	Monterey	Notes
Intel	Conroe	No	No	No	No	No	No	-
Intel	Kentsfield	No	No	No	No	No	No	-
Intel	Woodcrest	No	No	No	No	No	No	-
Intel	Clovertown	No	No	No	No	No	No	-
Intel	Tigerton	No	No	No	No	No	No	-
Intel	Wolfdale	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No SSE4.1(Some), SSE4.2 No iGPU
Intel	Yorkfield	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No SSE4.2 No iGPU
Intel	Harpertown	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No SSE4.2 No iGPU
Intel	Dunnington	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No SSE4.2 No iGPU
Intel	Lynnfield	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Bloomfield	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Gainestown/Nehalem EP	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Beckton/Nehalem EX	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Clarkdale	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Westmere EP/EX	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Sandy Bridge	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Sandy Bridge-EP/Jaketown	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Sandy Bridge-Gladden	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Ivy Bridge	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Ivy Bridge-Gladden	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Ivy Bridge-EP	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Ivy Bridge-EX/Ivytown	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Haswell/EN/EP/EX	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Lynx Point	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Wellsburg	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Broadwell	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Broadwell-DE/H/EP/EX	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Hewitt lake	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Skylake-X/SP/DE/DT	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Kaby Lake	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Kaby Lake-DT	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Coffee Lake	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Cooper Lake	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Comet Lake	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Ice Lake	Yes	Yes	Yes	Yes	Yes	Yes	No iGPU
Intel	Rocket Lake	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU
Intel	Tiger Lake	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No iGPU

Intel Mobile CPU

Vendor	Code Name	Sierra	High Sierra	Mojave	Catalina	Big Sur	Monterey	Notes
Intel	Yonah	No	No	No	No	No	No	-
Intel	Merom	No	No	No	No	No	No	-
Intel	Penryn	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required No SSE4.2 No iGPU
Intel	Clarksfield	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required iGPU Patching Required (From macOS High Sierra)
Intel	Arrandale	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required iGPU Patching Required (From macOS High Sierra)
Intel	Sandy Bridge-M	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Patching Required (From macOS Mojave)
Intel	Ivy Bridge-M	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Patching Required (For macOS Monterey)
Intel	Haswell/Haswell-MB/LP	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Crystal Well	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Broadwell/Broadwell-H/U/Y	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Skylake-/H/U/Y	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Kaby Lake-H/U/Y	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Kaby Lake R	Yes	Yes	Yes	Yes	Yes	Yes	-
Intel	Kaby Lake G	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Not Supported
Intel	Amber lake-Y	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Supports From macOS Mojave
Intel	Coffee Lake-H/U/H-Refresh	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Supports From macOS High Sierra
Intel	Whiskey Lake	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Supports From macOS High Sierra
Intel	Comet Lake-H/U	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Supports From macOS Catalina
Intel	Cannon lake-U	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Supports From macOS Catalina
Intel	Ice Lake-U/Y	Yes	Yes	Yes	Yes	Yes	Yes	iGPU Supports From macOS Catalina
Intel	Tiger Lake-H35/UP3/UP4	Yes	Yes	Yes	Yes	Yes	Yes	CPU Spoof Required iGPU Not Supported

AMD CPU Compatibility List

AMD Consumer Series

Vendor	Code Name	Sierra	High Sierra	Mojave	Catalina	Big Sur	Monterey	Notes
AMD	Zambezi	Yes	Yes	Yes	Yes	Yes	Yes
AMD	Vishera	Yes	Yes	Yes	Yes	Yes	Yes
AMD	Zurich	No	No	No	No	No	No
AMD	Valencia	No	No	No	No	No	No
AMD	Interlagos	No	No	No	No	No	No
AMD	Bristol Ridge	Yes	Yes	Yes	Yes	Yes	Yes
AMD	Kabini
AMD	Beema
AMD	Mullins
AMD	Temash	No	No	No	No	No	No
AMD	Naples
AMD	Whitehaven
AMD	Summit Ridge
AMD	Raven Ridge							iGPU Not Supported
AMD	Dali
AMD	Colfax
AMD	Pinnacle Ridge
AMD	Picasso
AMD	Rome
AMD	Matisse
AMD	Castle Peak
AMD	Renoir
AMD	Lucienne
AMD	Vermeer
AMD	Cezanne
AMD	Milan

 

[wonder1033]

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

 

[EliteMacx86]

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.

 

[ThomasF]

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:

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?

 

[EliteMacx86]

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:

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.

 

[ThomasF]

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?

 

[EliteMacx86]

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.

 

[ThomasF]

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)

 

[EliteMacx86]

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?

 

[ThomasF]

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.