• About us
  • Contact us
  • Privacy Policy
GEEKrar
  • Home
  • Virtual Machines
    • VMware
    • VirtualBox
  • Mobile
    • Android
    • iOS
  • News
    • Windows (Microsoft)
    • iOS (Apple)
  • Discord
  • Windows
  • Mac
  • THE FORUM
No Result
View All Result
  • Home
  • Virtual Machines
    • VMware
    • VirtualBox
  • Mobile
    • Android
    • iOS
  • News
    • Windows (Microsoft)
    • iOS (Apple)
  • Discord
  • Windows
  • Mac
  • THE FORUM
No Result
View All Result
GEEKrar
No Result
View All Result
Home Mac

How to Fix The CPU has been disabled by the guest OS

Ali by Ali
July 7, 2022
in Mac, VMware
117
How to Fix The CPU has been disabled by the guest OS

How to Fix The CPU has been disabled by the guest OS

878
SHARES
12.5k
VIEWS
Share on TwitterShare on Facebook

All right! After you’re basically done with the virtual machine configuration, everything should work great. But things don’t go always as expected. When you switch on the machine, you’ll see a lovely screen with an error that points to “The CPU have been disabled by default. Power off or reset the virtual machine”. Here’s How to Fix The CPU has been disabled by the guest OS

While Windows computer isn’t the default system to install macOS. The important thing is, Apple doesn’t support installing macOS on non-Apple hardware and is neither willing to do. But that’s not the only one who does this. Perhaps, when we use the patch for VMware, that is because, unlike VirtualBox, VMware Workstation Player doesn’t support installing macOS by default. In this case, when you try to install macOS on VMware without the patch, you’ll end up without installing.

Since installing macOS, whatever version isn’t the supported way, there will be likely problems messing around. Whether you’ve an Intel or AMD processor, you’ll probably need to play the tricky steps. But if you’re installing Mojave on an AMD system, you’ll need to pull off a few more steps including the actual steps which are for both processors. This is a tiny change but really matters. How to Fix The CPU has been disabled by the guest OS

There are several reasons which might cause the problem. The first one is that you may have not configured the virtual machine for your AMD system. While AMD systems are different from Intel ones, we will need to use the different config key for setting up correctly. The other reason that the error can pop up is if you’ve installed the VMware or VirtualBox while the Hyper-v is installed.

While this problem usually happens when installing macOS on VMware, so we will take a look at How to Fix The CPU has been disabled by the guest OS

Table of Contents

  • Change The VM Hardware Compatibility to 10.x
  • Add The Config Key For The Virtual Machine (For AMD Systems Only)
  • Here are some important fixes given by one of our users @DOUG! Thanks man, so many people found this helpful so I have added your comment to the post for easier access…

Change The VM Hardware Compatibility to 10.x

All the usual installing steps are important, but you need to perform some more steps in addition to them. The nice thing is, it’s all done from the vmx file. There are two ways you do get it done. The first way you could do it is from the VMware with the wizard. The other way you could do is from the vmx file. We’ll move with the easier one. This is simple as we have covered you with every step with shots.  Here’s how to do it real quick. How to Fix The CPU has been disabled by the guest OS

Go ahead and navigate to the virtual machine files. Now right click on the .vmx file and select Open with and choose Notepad.

Open VMX with Notepad
Open VMX with Notepad

When the file opened, change the version number to 10. It will change the virtual machine hardware compatibility to 10.

Change The VM Hardware Compatibility to 10
Change The VM Hardware Compatibility to 10

If you miss changing the hardware compatibility of the machine from VMware, you’ll likely encounter this problem.

  • How to Fix This virtual machine requires AVX2 but AVX is not present

Add The Config Key For The Virtual Machine (For AMD Systems Only)

Now without closing the .vmx file, copy the following code and paste it at the end of all lines. If you’ve the config key smc.version = 0 already there, you may remove it and paste this in place of it. It should look like this.

cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
cpuid.1.edx = “0000:1111:1010:1011:1111:1011:1111:1111”
featureCompat.enable = “FALSE”

How to Fix The CPU has been disabled by the guest OS
Insert Code

When you’re done with it, simply save it.

Save
Save

And you’re all set! All there’s left to do is switch the machine on and proceed with the installation.

Power on virtual machine
Power on the virtual machine

That’s all well and good. Everything should work

Here are some important fixes given by one of our users @DOUG! Thanks man, so many people found this helpful so I have added your comment to the post for easier access…

Managed to get it working on VMWare 16.0 & a 3700X after looking at the vmware logs for a bit.

Several issues:

1) Ensure you are using normal double-quotes. When copying and pasting it’ll use pretty quotes but vmware will complain (not a valid boolean, etc.)

2) Disabling featureCompat.enable is only supported on hardware versions less than 9. Change that to TRUE (probably can just delete but haven’t tested that yet)

3) cpuid.ss & cpuid.ds are no longer supported on the cpus so need to be removed from the enabled features. Change cpuid.1.edx line to

“0000:0111:1000:1011:1111:1011:1111:1111”

4) With those changes I was then able to bump the virtualHW.version back up to 16.

Tags: CPUfixFix the CPU has been disabledFix The CPU has been disabled by the guest operating systemHas been DisabledHow toHow to FixHow to Fix The CPU has been disabled by the guest operating systemThe CPUThe CPU has been disabled by the guest operating system
Previous Post

SWIFT Programming for Beginners: Tips and Tricks

Next Post

How to Fix This Virtual Machine Requires AVX2 But AVX is Not Present

Ali

Ali

Next Post
How to Fix This Virtual Machine Requires AVX2 But AVX is Not Present

How to Fix This Virtual Machine Requires AVX2 But AVX is Not Present

Comments 117

  1. KikiManjaro says:
    2 weeks ago

    Thanks ! I was having the same error with MacOs Ventura, this fix all my problems

    Reply
  2. Mounir says:
    2 months ago

    You’re amaziing. thank you

    Reply
  3. Rick says:
    3 months ago

    You absolute legend.

    Reply
  4. Witek says:
    3 months ago

    For anyone that has a mouse issue i just enabled USB 2.0 port in VM options

    Reply
  5. yeah budy ligth weight says:
    5 months ago

    you are fucking good man 🙂 Work the ventura 13

    Reply
  6. Matt says:
    6 months ago

    For anyone that has a mouse that doesn’t work, what I did was left the version as 10 and I could use the mouse. Good luck!

    Reply
  7. Mario says:
    9 months ago

    I am having issues with mouse and keyboard, I am not able to use any of it when the installation starts. Is there any fix to this? Thanks

    Reply
  8. Menlho says:
    10 months ago

    Even if the post is outdated, combined with the DOUG tips and comment section I managed to boot MacOs 12

    Here’s my end of file, I didnt swap the VmwareHW version, let it to 19.

    cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
    cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
    cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
    cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
    cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
    cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
    cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
    cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111”
    featureCompat.enable = “TRUE”

    Reply
    • Menlho says:
      10 months ago

      I have a Ryzen 7

      Reply
    • Razvan RAZ says:
      9 months ago

      Hi,
      can you or anyone else please help me with a config for

      Device name DESKTOP-8O7EQC1
      Processor AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G 1.80 GHz
      Installed RAM 4.00 GB (3.83 GB usable)
      Device ID A33F8BEC-F33C-42B7-BA40-22021F6EA1C8
      Product ID 00330-80000-00000-AA751
      System type 64-bit operating system, x64-based processor
      Pen and touch No pen or touch input is available for this display

      Many thanks!
      Razvan

      Reply
    • Andy says:
      7 months ago

      That worked for me Thank you!

      Reply
    • Murat says:
      5 months ago

      Thank you so much mate, one solution is this 🙂

      Reply
    • Amir says:
      2 weeks ago

      thanks man i tried everything finally ur config helped me out of this

      Reply
  9. Foxtrot813 says:
    10 months ago

    downgrade the version of the VM to v10x

    now manually edit the .VMX VM cnfiguration file (use notepad)

    now find and change the line from false to true
    featureCompat.enable = “TRUE”

    then add this

    smc.version = “0”
    cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
    cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
    cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
    cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
    cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
    cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
    cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
    cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111”
    smbios.reflectHost = “TRUE”
    hw.model = “MacBookPro14,3”
    board-id = “Mac-551B86E5744E2388”

    this worked on me for
    AMD FX 6300 CPU
    VMWARE Workstation 16.1
    Unlocker 4.13 (yes is already out!)

    PD: dont change virtual cpu count, keep 1 core and 2 threads.

    Good luck and spread da word :3

    Reply
    • anux says:
      9 months ago

      YOU man did a great job after many attempt finally i can run thank you very much

      Reply
    • nostre says:
      3 months ago

      after so many guides that was the solution for me!
      i have am 5900x
      after i add this to my config file it worked
      thank you

      Reply
  10. Soul says:
    1 year ago

    For my AMD Ryzen 7 5700U
    Ofcourse DOUG’s insights helped, so thank you.

    My end of VMX file-

    cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
    cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
    cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
    cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
    cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
    cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
    cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
    cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111”

    REMOVED featureCompat.enable = “FALSE”
    Bumped the virtualHW.version back up to 16.
    And macOS Big Sur Beta fired up.
    Wanted to share what worked for me so it helps others.
    Thank you.
    Soul

    Reply
    • Charlie Pedulla says:
      1 year ago

      Works adding this lines on vmx file!!
      My cpu: AMD Ryzen 5 4500U

      Thanks!

      Reply
    • Slartibartfast says:
      11 months ago

      Doug’s settings didn’t quite work for me, but these ones did. VM HW version is 19. Thanks.

      Running macOS 11.1 on 3.19 GHz Ryzen 7 5800H – Asus ROG Strix G17 gaming laptop (2021)

      Reply
    • saveroo says:
      11 months ago

      Ryzen 5900x here, it worked, delted featureCompat as well. and keep virtualHW.version = “18”, with guest os Mac OS X Sierra

      Reply
    • Daniel says:
      11 months ago

      Thanks man! That worked for me for MacOS Monterey already!

      Reply
    • Zaid says:
      9 months ago

      ryzen 7 4800h Worked for me!! thank you LEGEND

      Reply
    • Larry says:
      5 months ago

      You are right!
      REMOVE featureCompat.enable = “FALSE” works!
      The macOS installer start successfully!

      Reply
  11. Gabor Koltai says:
    1 year ago

    read the detailed fix for AMD Ryzen 7 5800X:
    https://stackoverflow.com/a/70764448/11192062

    maybe solve problems for other AMD Ryzen 5xxx series CPUs as well.

    Reply
    • Ali says:
      1 year ago

      Thanks for sharing the link

      Reply
    • ysquare says:
      10 months ago

      It works for me, thanks! AMD 5600G

      Reply
  12. koltaig says:
    1 year ago

    AMD Ryzen 7 5800X

    needs to be change the cpuid.1.edx

    from: cpuid.1.edx = “0000:1111:1010:1011:1111:1011:1111:1111”

    to: cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111”
    Full vmx modification:

    smc.version = “0”

    cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”

    cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”

    cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”

    cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”

    cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”

    cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”

    cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”

    cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111”

    smbios.reflectHost = “TRUE”

    hw.model = “MacBookPro14,3”

    board-id = “Mac-551B86E5744E2388”
    VM hardware: 15.X
    VM host sw config:

    VMWARE Workstation PRO 16.2.1 and unlocker 3.0.2

    Reply
    • Wenbin FAN says:
      1 year ago

      GREAT JOB! It works for me finally! Thanks 😀

      VMWare 16.2.0 / Auto-Unlocker 1.13 / macOS 12 // AMD 5900X

      Reply
  13. Asif says:
    1 year ago

    Hello Ali, This was really helpful. I just installed it on Ryzen 5 3600 🙂 Thanks

    Reply
    • Ali says:
      1 year ago

      thats great! thanks for letting me know

      Reply
    • DIckniggabitch says:
      1 year ago

      Mine doesn’t work. The error was:

      Feature ‘cpuid.ds’ was absent, but must be present.

      Feature ‘cpuid.ss’ was absent, but must be present.

      Module ‘FeatureCompatLate’ power on failed.

      Value ““FALSE”” for variable “featureCompat.enable” is not a valid boolean value. Using value “TRUE”.

      Failed to start the virtual machine.

      Virtualization is turnt on and other virtual machines were running well.

      Reply
  14. jonniijoe says:
    1 year ago

    The last comment really did the trick for me, VMWare Workstation Pro 16 running Big Sur on
    virtualHW.version = 19 (default setting)

    Reply
  15. Santosh says:
    1 year ago

    Awesome it worked! Thank you so much

    Reply
  16. tim says:
    1 year ago

    On Ryzen 3900x / win 10 with vmware WS and player I had to delete featureCompat.enable = “TRUE” – then it finally worked. Thanks!

    Reply
    • Ali says:
      1 year ago

      Great! thanks for your notes

      Reply
      • dlfz.stuff says:
        1 year ago

        I am using VMWare Workstation 16.1 it loads half way and starts again and again
        tried all the changes below I am using a 3900x / Win 10 Pro I am getting this error
        Value aeoe0ae cant do it exactly but says for variable “smc.version” is not a valid integer value. x using value “-1”.

        Thanks for your Help !!!! Don

        Reply
        • Ali says:
          1 year ago

          I think you can try change the Hardware Version to Version 10 and don´t fill in the line “smc.version = “0”

          Reply
          • dflz.Network says:
            1 year ago

            Got IOS loaded and starts up but now I cant get the mouse to work so l cant proceed with the install when l try to hit next after it picks the country the mouse is gone and l have to do Ctrl Alt Del to get out of the windows Stuck here

          • Ali says:
            1 year ago

            sorry for the late reply, i saw your post in the forum. let me know if you are still having mouse issues

          • dlfz.Network says:
            1 year ago

            Thanks All Up and Running this would not be possible without this Forum !!!

          • Ali says:
            1 year ago

            awesome man!

  17. moris says:
    1 year ago

    ABSOLUTELY AMAZING

    Reply
    • Ali says:
      1 year ago

      awesome!

      Reply
  18. Paul says:
    1 year ago

    Thanks a million Doug, finally a working Sierra VM after adding your suggested lines and realising I had to change the double quotes, modify cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111” and changing featureCompat.enable = “TRUE”
    VM running well on a Ryzen 3 3200G. You did great work researching this so we don’t have to, much appreciated.

    Reply
    • Paul says:
      1 year ago

      Ah I see my thanks should go to Ali too! Sorry.

      Reply
  19. Yap says:
    1 year ago

    Thanks man, used up 8 hours grinding to solve the problem, what you did saved me :). Thanks a lot

    Reply
  20. G says:
    2 years ago

    I love you Doug. Finally got High Sierra to install after many hours of trying in both VirtualBox and VMWare…

    Reply
  21. GG-Garry says:
    2 years ago

    Thank You! Your suggestions worked!

    Reply
  22. Daniel says:
    2 years ago

    What the heck the DOUG solution did WORK!
    Thanks man!!

    Reply
  23. Rushane Ho Quee says:
    2 years ago

    I followed the steps and it didn’t work for meat first. what i will say is the steps resolve most of my issues. I got stuck at the “How to Fix This virtual machine requires AVX2 but AVX is not present” I resolve that by click the link above that talks about the issues. The resolution for that was change virtual hardware version to 10.

    Reply
  24. Jailson Pacagnan Santana says:
    2 years ago

    thank you!

    Reply
  25. zz says:
    2 years ago

    Thank you Doug! Your suggestions worked!

    Reply
  26. murat says:
    2 years ago

    Thanks a lot :))

    Started with trouble with my Linux Journey….this promises nothing good for me as windows administrator.

    Reply
  27. fd says:
    2 years ago

    You need to restrict the VM to two cores 1 cpu for this to work

    Reply
    • Ali says:
      2 years ago

      Thanks for noting this

      Reply
    • Doug says:
      2 years ago

      You might want to check that. I’m running 2 processors x 4 cores and MacOS sees them fine.

      [~] sysctl -a | grep hw\..*cpu:
      hw.ncpu: 8
      hw.activecpu: 8
      hw.physicalcpu: 8
      hw.logicalcpu: 8

      Reply
  28. Steveo says:
    2 years ago

    Hi Doug,
    Thank you thank you thank you!!!!
    This is what worked for me:

    smc.version = “0”
    cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
    cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
    cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
    cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001″
    cpuid.1.eax = “0000:0000:0000:0001:0000:0110:1010:0101”
    cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
    cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
    cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111”
    featureCompat.enable = “TRUE”

    nothing else nothing more I have lost hope after trying for days to get big sur on vmware, i even read that it won’t happen if I have an APU, low and behold I couldn’t believe it when I saw the installation going on!
    Quick question: I noticed that the sound while playing a youtube video is choppy, having never dealt with a mac before is there a driver fix perhaps for this?
    Also I tried to create an Apple ID but it seems to be stuck and not following through.
    Peace
    Steve

    Reply
    • Ali says:
      2 years ago

      Hey Steveo, Yeah Doug is awesome with that fix, and has help a lot of us out. I will check around and see if there is any known issues with audio or drive updates. We’re launching a forum to help users find solutions to these issues. Sign up whenever you can! forum.geekrar.com, we’ll start opening up the discussion board next month

      Reply
      • Steveo says:
        2 years ago

        Just did, thank you Ali 🙂

        Reply
    • Doug says:
      2 years ago

      I have no idea on the audio, only use the VM for Xcode and don’t have an audio device configured.

      I didn’t create an Apple ID in MacOS, however am successfully using ones that I had created previously, if that helps.

      Reply
    • Ubi says:
      2 years ago

      You are awesome. Thank you.

      Reply
    • Jonney Alaska says:
      1 year ago

      Thank you so much !!!!!!!!
      Working on Big Sur on AMD Ryzen 9

      Reply
    • Icarus Phoenix says:
      10 months ago

      Worked for me to emulate Mojave in VMWare Player 16 in Windows 11
      My specs is Ryzen 3550H

      Reply
  29. Anonymous says:
    2 years ago

    -Update to my previous comment-
    The following line: cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
    gives me the following error (shortened it for ease):

    “Feature ‘cpuid.pclmulqdq, *ssse3 *sse41 *sse42 *aes’ was absent but must be present
    Module FeatureCompatLate power on failed.”

    FYI my Workshop is 16.

    Reply
    • Doug says:
      2 years ago

      These changes are primary for AMD users to fool MacOS into thinking that an AMD CPU is an Intel CPU.

      In particular, the cpuid.0.eax line specifices a Nehalem-based processor, and other the cpuid.0.* lines spell out ‘GenuineIntel’. The cpuid.1.* lines are used to specify particular features. In your case, you’ve turned on the bits that tell the VM your CPU supports pclmulqdq, ssse3, sse41, sse42 & aes but when VMWare tries to validate that it determines that your physical CPU doesn’t actually support those features.

      Most likely your CPU is too old to support running the newer MacOS versions. Sorry.

      Reply
  30. Anonymous says:
    2 years ago

    Doesn’t. Even. Work. Person with an Intel CPU coming through.
    I guess i’m one of those unlucky chosen ones that will never ever have these damn fancy things to work.

    Reply
    • Ali says:
      2 years ago

      I feel the same way, I’ve had plenty of issues with intel. which os are you installing?

      Reply
  31. Antonis_35 says:
    2 years ago

    I own a Ryzen 9 3900X, and I made all the recommended changes to the vmx file (including those from Doug), but when I try to start the VM I get the below errors:

    Feature ‘cpuid.ds’ was absent, but must be present.
    Feature ‘cpuid.ss’ was absent, but must be present.
    Module ‘FeatureCompatLate’ power on failed.
    Failed to start the virtual machine.

    I checked and all the quotation marks are correct.

    Reply
    • aj says:
      2 years ago

      Change featureCompat.enable = “False” to “True

      Reply
  32. elvinXCs says:
    2 years ago

    FINALLY It works on my Ryzen 7
    Thank you 😭😭😭

    Reply
  33. Roberto says:
    2 years ago

    You saved my day 🙂
    AMD Ryzen 3950x, 32GB, Windows 10, VMWARE Workstation 16, guest MacOS 10.13.6
    Point 2) and 3) are the tricks.

    Reply
  34. Also Doug says:
    2 years ago

    You Glorious Bastard, Thank you Doug. You fixed everything with one post.

    Reply
  35. Mat says:
    2 years ago

    Thanks for the fix!

    Reply
  36. stephen boyle says:
    2 years ago

    this saved my bacon on an AMD EPYC processor! thank you!

    Reply
  37. Eric Proxy says:
    2 years ago

    This is the working solution for my AMD Ryzen 7 4700U

    Reply
  38. Euclides Cardoso Júnior says:
    2 years ago

    Thank you… save my day.

    Reply
  39. your says:
    2 years ago

    Thanks

    Reply
  40. cookiefj says:
    2 years ago

    you save me!
    important #2 and #3.

    Reply
  41. Ting says:
    2 years ago

    I got the same issue

    Reply
  42. DougTheLegend says:
    2 years ago

    You are fucking legend

    Reply
  43. Alex says:
    2 years ago

    Thank you – this sorted it out for me!

    Reply
  44. Tom says:
    2 years ago

    Doug, you are a freakin genious!

    Reply
  45. Niklas K says:
    2 years ago

    Thank you so much. I wasted so many hours getting a macOS VM to work and this finally solved the problem (Ryzen 3700X)

    Reply
    • Ting says:
      2 years ago

      How did you do? I use AMD RYZEN 7 4000 Series, Could help me please!

      Reply
  46. Amir says:
    2 years ago

    Thank you so much for your contribution.

    I had the same issue and followed your instructions to resolve the issue.

    It is working fine now.

    Reply
    • Ali Nazarii says:
      2 years ago

      great to hear

      Reply
  47. Mike S says:
    2 years ago

    Legend Doug

    Reply
    • Ali Nazarii says:
      2 years ago

      Agreed

      Reply
  48. Doug says:
    2 years ago

    Managed to get it working on VMWare 16.0 & a 3700X after looking at the vmware logs for a bit.

    Several issues:

    1) Ensure you are using normal double-quotes. When copying and pasting it’ll use pretty quotes but vmware will complain (not a valid boolean, etc.)

    2) Disabling featureCompat.enable is only supported on hardware versions less than 9. Change that to TRUE (probably can just delete but haven’t tested that yet)

    3) cpuid.ss & cpuid.ds are no longer supported on the cpus so need to be removed from the enabled features. Change cpuid.1.edx line to

    “0000:0111:1000:1011:1111:1011:1111:1111”

    4) With those changes I was then able to bump the virtualHW.version back up to 16.

    Reply
    • Ali Nazarii says:
      2 years ago

      Thanks for your findings. This will be helpful to the community.

      Reply
    • steve says:
      2 years ago

      It worked like a charm. thanks, doug.

      Reply
    • bob knobby says:
      2 years ago

      This worked for me on Ryzen 3950x, using the same CPU id keys.

      Seconding, if you’re copy/pasting to notepad, make sure you edit the quotes, as their character string on this website is not a regular quote. Delete them and re-enter the proper keyboard quote key for each one.

      Reply
    • Ramakrishna ch says:
      2 years ago

      Thank you so much ,after changing the foll0wing it starts working
      1)featureCompat.enable = “TRUE”
      2)cpuid.1.edx line to “0000:0111:1000:1011:1111:1011:1111:1111”
      (I am using Ryzen-5 3500U).Thank you again

      Reply
  49. Gaffar says:
    2 years ago

    I was able to run the VM on 3950X Processor with the following VMX details :

    .encoding = “windows-1252”
    config.version = “8”
    virtualHW.version = “10”
    pciBridge0.present = “TRUE”
    pciBridge4.present = “TRUE”
    pciBridge4.virtualDev = “pcieRootPort”
    pciBridge4.functions = “8”
    pciBridge5.present = “TRUE”
    pciBridge5.virtualDev = “pcieRootPort”
    pciBridge5.functions = “8”
    pciBridge6.present = “TRUE”
    pciBridge6.virtualDev = “pcieRootPort”
    pciBridge6.functions = “8”
    pciBridge7.present = “TRUE”
    pciBridge7.virtualDev = “pcieRootPort”
    pciBridge7.functions = “8”
    vmci0.present = “TRUE”
    hpet0.present = “TRUE”
    ich7m.present = “TRUE”
    board-id.reflectHost = “TRUE”
    displayName = “macOS Catalina”
    guestOS = “darwin19-64”
    nvram = “macOS Catalina.nvram”
    virtualHW.productCompatibility = “hosted”
    gui.exitOnCLIHLT = “FALSE”
    powerType.powerOff = “soft”
    powerType.powerOn = “soft”
    powerType.suspend = “soft”
    powerType.reset = “soft”
    usb.vbluetooth.startConnected = “TRUE”
    smc.present = “TRUE”
    smbios.restrictSerialCharset = “TRUE”
    firmware = “efi”
    tools.syncTime = “FALSE”
    sound.autoDetect = “TRUE”
    sound.virtualDev = “hdaudio”
    sound.fileName = “-1”
    sound.present = “TRUE”
    numvcpus = “8”
    cpuid.coresPerSocket = “8”
    memsize = “32000”
    sata0.present = “TRUE”
    sata0:0.fileName = “macOS Catalina.vmdk”
    sata0:0.present = “TRUE”
    sata0:1.deviceType = “cdrom-image”
    sata0:1.fileName = “C:\Users\Leon\Downloads\macOS Catalina ISO by Geekrar\macOS Catalina ISO by Geekrar\macOS Catalina Final [Geekrar].iso”
    sata0:1.present = “TRUE”
    usb.present = “TRUE”
    ehci.present = “TRUE”
    usb_xhci.present = “TRUE”
    ethernet0.connectionType = “nat”
    ethernet0.addressType = “generated”
    ethernet0.virtualDev = “e1000e”
    ethernet0.present = “TRUE”
    extendedConfigFile = “macOS Catalina.vmxf”
    floppy0.present = “FALSE”
    smc.version = “0”
    vhv.enable = “TRUE”
    numa.autosize.cookie = “80001”
    numa.autosize.vcpu.maxPerVirtualNode = “8”
    uuid.bios = “56 4d be 15 17 2a 61 bb-54 bc 19 ea 20 f5 a1 5f”
    uuid.location = “56 4d be 15 17 2a 61 bb-54 bc 19 ea 20 f5 a1 5f”
    sata0:0.redo = “”
    pciBridge0.pciSlotNumber = “17”
    pciBridge4.pciSlotNumber = “21”
    pciBridge5.pciSlotNumber = “22”
    pciBridge6.pciSlotNumber = “23”
    pciBridge7.pciSlotNumber = “24”
    usb.pciSlotNumber = “32”
    ethernet0.pciSlotNumber = “160”
    sound.pciSlotNumber = “33”
    ehci.pciSlotNumber = “34”
    usb_xhci.pciSlotNumber = “192”
    vmci0.pciSlotNumber = “35”
    sata0.pciSlotNumber = “36”
    svga.vramSize = “134217728”
    vmotion.checkpointFBSize = “134217728”
    vmotion.checkpointSVGAPrimarySize = “268435456”
    ethernet0.generatedAddress = “00:0c:29:f5:a1:5f”
    ethernet0.generatedAddressOffset = “0”
    vmci0.id = “552968543”
    monitor.phys_bits_used = “40”
    cleanShutdown = “TRUE”
    softPowerOff = “FALSE”
    usb_xhci:6.speed = “2”
    usb_xhci:6.present = “TRUE”
    usb_xhci:6.deviceType = “hub”
    usb_xhci:6.port = “6”
    usb_xhci:6.parent = “-1”
    usb_xhci:7.speed = “4”
    usb_xhci:7.present = “TRUE”
    usb_xhci:7.deviceType = “hub”
    usb_xhci:7.port = “7”
    usb_xhci:7.parent = “-1”
    toolsInstallManager.updateCounter = “4”
    usb:1.speed = “2”
    usb:1.present = “TRUE”
    usb:1.deviceType = “hub”
    usb:1.port = “1”
    usb:1.parent = “-1”
    usb_xhci:4.present = “TRUE”
    usb_xhci:4.deviceType = “hid”
    usb_xhci:4.port = “4”
    usb_xhci:4.parent = “-1”
    sata0:1.startConnected = “TRUE”
    toolsInstallManager.lastInstallError = “21004”
    tools.remindInstall = “TRUE”
    cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
    cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
    cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
    cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
    cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
    cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
    cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
    cpuid.1.edx = “0000:1111:1010:1011:1111:1011:1111:1111”
    featureCompat.enable = “FALSE”

    Reply
    • Ting says:
      2 years ago

      I’m using RYZEN 7 4800H, Could you help me please!

      Reply
      • Annonymous says:
        2 years ago

        Using Ryzen 5 3550H below worked for me

        config.version = “8”
        virtualHW.version = “9”

        smbios.reflectHost = “TRUE”
        hw.model = “MacBookPro14,3”
        board-id = “Mac-551B86E5744E2388”
        cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
        cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
        cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
        cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
        cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
        cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
        cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
        cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111”
        featureCompat.enable = “TRUE”

        Reply
        • Ali says:
          2 years ago

          Thanks for sharing this

          Reply
  50. Merlin Erdogmus says:
    3 years ago

    I also get:”

    Error while powering on : feature ‘cpuid.ds’ was absent, but must be present.

    feature cpuid.ss was absent, but must be present

    feature cpuid.intel was abset but must be present

    module featurecompatlate power on failed

    value (random unreadable text) for variable featurecompat.enable is not a valid boolean value
    using value TRUE

    failed to start virtual machine”

    Reply
  51. Lou says:
    3 years ago

    Same here with a Ryzen 3800X: “Failed to start the virtual machine.”

    Reply
    • alex says:
      2 years ago

      Using Ryzen 5 3550H below worked for me

      config.version = “8”
      virtualHW.version = “9”

      smbios.reflectHost = “TRUE”
      hw.model = “MacBookPro14,3”
      board-id = “Mac-551B86E5744E2388”
      cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
      cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
      cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
      cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
      cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
      cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
      cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
      cpuid.1.edx = “0000:0111:1000:1011:1111:1011:1111:1111”
      featureCompat.enable = “TRUE”

      Reply
      • Gabriel Preihs says:
        1 year ago

        Worked for me, you are a god !

        Reply
  52. Yujin says:
    3 years ago

    Mine also prompts “Failed to start Virtual Machine“

    Ryzen 2600

    Reply
  53. Chanchana Sornsoontorn says:
    3 years ago

    This is exactly what happens to me. I use AMD Ryzen 7 3700X

    Reply
  54. Adam Joel Stepansky says:
    3 years ago

    Anyone figure this out for 15.5 with AMD? New error appears regarding feature cpuids

    Reply
  55. David Schlender says:
    3 years ago

    I had the same issue. Did you find a solution to this?

    Reply
  56. Angel says:
    3 years ago

    What/???

    Reply
  57. StigNerg says:
    3 years ago

    I have done all this steps. I still cant rund mac mojave, I use AMD ryzen 7, 2700

    Reply
    • StigNerg says:
      3 years ago

      no.. mac Catalina

      Reply
  58. Gary Stewart says:
    3 years ago

    That’s a few us with amd CPUs following all the fixes and ending up with “Failed to start the virtual machine” any ideas?

    Reply
  59. Danijel Lukic says:
    3 years ago

    At first inserted:
    smc.version = “0”

    Getting the Message that Guest turned off CPU.

    Then changed the Version from 16 to 10
    Then added the following (Because i have an AMD CPU):
    cpuid.0.eax = “0000:0000:0000:0000:0000:0000:0000:1011”
    cpuid.0.ebx = “0111:0101:0110:1110:0110:0101:0100:0111”
    cpuid.0.ecx = “0110:1100:0110:0101:0111:0100:0110:1110”
    cpuid.0.edx = “0100:1001:0110:0101:0110:1110:0110:1001”
    cpuid.1.eax = “0000:0000:0000:0001:0000:0110:0111:0001”
    cpuid.1.ebx = “0000:0010:0000:0001:0000:1000:0000:0000”
    cpuid.1.ecx = “1000:0010:1001:1000:0010:0010:0000:0011”
    cpuid.1.edx = “0000:1111:1010:1011:1111:1011:1111:1111”
    featureCompat.enable = “FALSE”

    Now i get the following error:
    Failed to start the virtual machine

    Reply
  60. bubba says:
    3 years ago

    Thanks for pointing this out!

    Reply
  61. Gary Stewart says:
    3 years ago

    “Failed to start the virtual machine.” error message for me as well, any ideas?

    Reply
  62. Fernando Suarez Ornani says:
    3 years ago

    “Failed to start the virtual machine.” (no more explanation). What can I do?
    Regarding “feature cpuid.ss was absent” and the like, beware that the lines that you have to add have the wrong quotations. For example:
    featureCompat.enable = “FALSE”
    Should be:
    featureCompat.enable = “FALSE”
    Same goes for CPUID lines, although they wont give you errors.

    Reply
  63. SAURISH MONGA says:
    3 years ago

    Error while powering on : feature ‘cpuid.ds’ was absent, but must be present.

    feature cpuid.ss was absent, but must be present

    feature cpuid.intel was abset but must be present

    module featurecompatlate power on failed

    value (random unreadable text) for variable featurecompat.enable is not a valid boolean value
    using value TRUE

    failed to start virtual machine

    this is the error i got from following this. Im using amd processor what should i do?

    Reply
  64. Ahmad Syarbini says:
    3 years ago

    Error while powering on : feature ‘cpuid.ds’ was absent, but must be present.

    feature cpuid.ss was absent, but must be present

    feature cpuid.intel was abset but must be present

    module featurecompatlate power on failed

    value (random unreadable text) for variable featurecompat.enable is not a valid boolean value
    using value TRUE

    failed to start virtual machine

    this is the error i got from following this. Im using ryzen 7 2700. please help.

    Reply
  65. suy uy says:
    4 years ago

    I can install vmware tool after this step

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

  • Trending
  • Comments
  • Latest
How To Bypass Mega Download Limits (2021 Method)

How To Bypass Mega Download Limits (2021 Method)

July 12, 2022
Download macOS Ventura ISO file

Download macOS Ventura ISO file

January 18, 2023
Download macOS Monterey ISO Release Candidate (v12.0.1)

Download macOS Monterey ISO Release Candidate (v12.0.1)

August 27, 2022
Bypass Mega download limits

How To Bypass Mega Download Limits 2022 (Alternative Method)

September 21, 2022
Install macOS Catalina on VirtualBox

Install macOS Catalina on VirtualBox on Windows PC

118
How to Fix The CPU has been disabled by the guest OS

How to Fix The CPU has been disabled by the guest OS

117
Install macOS Catalina on VMware on Windows PC

Install macOS Catalina on VMware on Windows PC

81
Install macOS Catalina on VirtualBox on AMD Systems

How to Install macOS Catalina on VirtualBox on AMD Systems

80
How to Create an Educational APP: A Friendly Guide

How to Create an Educational APP: A Friendly Guide

February 3, 2023
4 Tips for Getting a Job in IT

4 Tips for Getting a Job in IT

January 31, 2023
What Is a Service Mesh? 5 Business Benefits

What Is a Service Mesh? 5 Business Benefits

January 31, 2023
A history of proxy servers and their evolution over time.

A history of proxy servers and their evolution over time.

January 30, 2023

Recent News

How to Create an Educational APP: A Friendly Guide

How to Create an Educational APP: A Friendly Guide

February 3, 2023
4 Tips for Getting a Job in IT

4 Tips for Getting a Job in IT

January 31, 2023
What Is a Service Mesh? 5 Business Benefits

What Is a Service Mesh? 5 Business Benefits

January 31, 2023
A history of proxy servers and their evolution over time.

A history of proxy servers and their evolution over time.

January 30, 2023
Facebook Twitter Youtube
GEEKrar

We are a team of skilled writers, editors and tech enthusiasts that help you how to get tech into work, pros and cons, explain hows and whys, hacks, and fixes of new modern tech.

Browse by Category

  • Android (24)
  • Discord (3)
  • Downloads (12)
  • Featured (11)
  • Internet (199)
  • iOS (25)
  • Mac (88)
  • News (428)
    • iOS (Apple) (283)
    • Windows (Microsoft) (117)
  • Reviews (3)
  • Tech (17)
  • Virtual Machine (24)
  • VirtualBox (75)
  • VMware (66)
  • Windows (77)

Recent News

How to Create an Educational APP: A Friendly Guide

How to Create an Educational APP: A Friendly Guide

February 3, 2023
4 Tips for Getting a Job in IT

4 Tips for Getting a Job in IT

January 31, 2023

© 2022 geekRAR.com

No Result
View All Result

© 2022 geekRAR.com

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
Do not sell my personal information.
Cookie settingsACCEPT
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT
Go to mobile version