Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Virtualization » Downgrade VMware Workstation: Fix the Processor does not support xsave on VMware Workstation
  • officelicensedeactivation
    Remove Office license file: How do you change the account that Office says it belongs to on a Mac JIRA|Confluence|Apps
  • FailedRegistration
    DNS Bad key 9017: The Cluster Name registration failed of one or more associated DNS names Virtualization
  • Featured image 3
    How to fix White Screen in Microsoft Teams Windows
  • PetitPotam
    PetitPotam attack on Active Directory Certificate Services: How to mitigate NTLM Relay PetitPotam attack on AD CS Security | Vulnerability Scans and Assessment
  • NortonEvents
    View and Clear or Print Norton Security Events on a Mac Anti-Virus Solution
  • Fix Windows Installer Service Could Not Be Accessed Error
    How to Fix the “Windows Installer Service Could Not Be Accessed” Error While Installing an Application Windows
  • banner 5
    How to fix Wi-Fi not connecting on Windows 11 Windows
  • How to Convert Google Forms Into Microsoft Forms banner
    Convert Google Forms Into Microsoft Forms Microsoft Exchange/Office/365

Downgrade VMware Workstation: Fix the Processor does not support xsave on VMware Workstation

Posted on 23/01/202418/07/2025 Christian By Christian 1 Comment on Downgrade VMware Workstation: Fix the Processor does not support xsave on VMware Workstation
Downgrade

In this article, you will learn how to Downgrade VMware Workstation in order to fix the Processor does not support xsave on VMware Workstation. If you installed Workstation 17.5, it appears to have a hard requirement for a Sandy Bridge or later architecture Intel processor that contains the XSAVE instruction. Please see How to upgrade and downgrade PIP on Windows, How to upgrade and downgrade PIP on Windows, and How to install Windows Server 2022 on VMware Workstation. Below is an interesting conversation from the VMware community.

The XSAVE instructions provide a performance/efficiency boost to the virtualization processing. The VMware supported processor advice is imprecise and misleading. I believe they really mean Sandy Bridge or later generation Intel CPUs. Sandy Bridge CPUs were introduced in 2011, and I believe this is what VMware means when they say “processor introduced in 2011 and later”.

I also suspect this includes Atom/Celeron/Pentium CPUs based on Sandy Bridge or later architectures. There were Atom processors released after 2011 that are based on pre-Sandy Bridge microarchitectures. We’ve seen instances where users are reporting that they don’t work with Workstation 17.5 for the same reason: no XSAVE instruction. I don’t know for sure if later generation Atom CPUs will work. Your option as I see it is to back off to Workstation 17.0 or remain on Workstation 16.

Below are the system requirements. Based on the conversation above, I did everything to work around this issue, but no success. Therefore, I had to downgrade eventually. For Processor Requirements for Host System

  • Intel Sandy Bridge or newer CPU
  • AMD Bulldozer or newer CPU

For Supported Host Operating Systems

  • Windows 10 20H1 build 19041.264 or newer according to the VMware documentation.

Why was the error prompted?

The device processor lacks the requirements and is not compatible. To fix this issue, you might need to consider upgrading your hardware to a processor that supports the required virtualization features. Below is the error prompted after upgrading to VMware Workstation 17.x

You can use third-party tools or commands to check if your processor supports the required features. For example, CPU-Z is a popular tool for checking processor details. Or use the native windows feature called Task manager. On the performance tab, you should be able to find the CPU information.

Processor does not support xsave

Note: The command to disable or remove the hyperv feature does not work.

Solution: Downgrade VMware Workstation 17 to v16

To downgrade your virtual machine hardware compatibility, please follow the steps below.

Shut down the virtual machine. Downgrade the virtual hardware by right-clicking the virtual machine and click Manage.

Manage-VM

Click Change Hardware Compatibility. The Change Hardware Compatibility Wizard opens.

Click Next, then select Workstation 16.0 Pro  from the Hardware Compatibility dropdown.Click Next.

Change Hardware compatibility

On the wizard below, click Next.

Hardware-compatibility-wizard

Under the Hardware Compatibility, select the version you wish to downgrade to.

Select-Hardware-compatibility

Desired version selected.

Selected-Hardware-compatibility

Select your choice when asked to create a clone or alter the virtual machine. Click Next.

Alter-VM-configuration

Click Finish, and click Close.

Finish

Now the option to upgrade is now available to the VM again.

For my second VM

Since I have not upgraded it before, I have the option to upgrade via the VMware library.

Downgrade-VM-Hardware-compatibility
Follow the same steps as above!

See how to use the Program Compatibility Troubleshooter to Test Application Compatibility on Windows 11, and how to Bypass unsupported CPU and Processor by upgrading to Windows 11 via Windows Update.

Manually uninstall VMware Workstation Pro 17.x. 

You can also do this via the Control Panel. Here I am using the Windows Settings to remove VMware Workstation.

Windows-settings-programs-and-features

Click on Modify

Modify-VMware-Workstation

On the setup wizard, click Next

Workstation-setup

Select Remove

Remove-Workstation

Both are selected by default and I am fine with this. Click Next.

Remove-products

Finally, click on Remove

Remove-VMware-Workstation

Hit the finish button to complete this step.

Finish-uninstall

You are required to restart the device for the changes to take effect.

Restart-device

Download VMware Workstation

Navigate to the VMware Workstation Download Center. Based on your requirements, click Go to Downloads for VMware Workstation 14 for Windows or VMware Workstation 16 for Windows. Please see How to use the Program Compatibility Troubleshooter to Test Application Compatibility on Windows 11.

Note: You will have to uninstall VMware Tools, and then re-install VMware Tools for Workstation 16.x Pro. Do not forget to reboot the virtual machine when prompted.

Select-VMware-Workstation

Select the version you wish to install. In my case, v16

Select-VMware-workstation-v16.0

Click Download.

Download-Product
Click on the executable file downloaded to run the setup

For the rest steps, please see this guide on how to install VMware Workstation 17 on Windows. Also, seehow to How to install ESXi on VirtualBox, and how to fix ESXi VMB 411 Halting: Virtualbox Nested VT-X/AMD-V greyed out.

Run-VMware-workstation-16-1

Hit the install button as shown below.

Install-Workstation-16.x

License-or-Finish-Workstation-v16-setup

Enter the license key

Enter-License

And that is all. Click finish to complete this step.

Finish-setup

You will be required to restart your device as well.

Restart-device-1

As you can see, access is possible again

Can-now-access-VM-again

I hope you found this article useful on how to “Downgrade VMware Workstation: Fix the Processor does not support xsave on VMware Workstation”. Please feel free to leave a comment below.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Click to share on X (Opens in new window) X
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on Pinterest (Opens in new window) Pinterest
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Telegram (Opens in new window) Telegram
  • Click to share on WhatsApp (Opens in new window) WhatsApp
  • Click to share on Pocket (Opens in new window) Pocket
  • Click to share on Mastodon (Opens in new window) Mastodon
  • Click to share on Bluesky (Opens in new window) Bluesky
  • Click to share on Threads (Opens in new window) Threads
  • Click to share on Nextdoor (Opens in new window) Nextdoor
Virtualization Tags:Microsoft Windows, VMware, Windows Server 2016

Post navigation

Previous Post: How to Disable Copilot in Windows and Microsoft Edge
Next Post: How to disable side-channel mitigations on VMware Workstation

Related Posts

  • Screenshot
    Setup iSCSI Target and Storage LUN on Synology DS923+ for VBR Reviews
  • VMware
    How to install Windows Server 2022 on VMware Workstation Virtualization
  • Map and disconnect Virtual Disk in VMware Workstation
    Map and disconnect Virtual Disk in VMware Workstation Virtualization
  • Untitled Design 25
    Install and Configure Hyper-V on Windows Server Server 2019, and 2022 via the Server Manager, PowerShell or DISM Virtualization
  • cannot connect to the virtual machine try to connect again HyperV
    Could not connect to virtual machine try to connect again Hyper-V Virtualization
  • sandbox
    How to Configure Windows Sandbox Virtualization

More Related Articles

Screenshot Setup iSCSI Target and Storage LUN on Synology DS923+ for VBR Reviews
VMware How to install Windows Server 2022 on VMware Workstation Virtualization
Map and disconnect Virtual Disk in VMware Workstation Map and disconnect Virtual Disk in VMware Workstation Virtualization
Untitled Design 25 Install and Configure Hyper-V on Windows Server Server 2019, and 2022 via the Server Manager, PowerShell or DISM Virtualization
cannot connect to the virtual machine try to connect again HyperV Could not connect to virtual machine try to connect again Hyper-V Virtualization
sandbox How to Configure Windows Sandbox Virtualization

Comment (1) on “Downgrade VMware Workstation: Fix the Processor does not support xsave on VMware Workstation”

  1. Avatar photo Sasa says:
    06/11/2024 at 7:35 PM

    Isnt easier just to Open command prompt as an administrator, run:
     
    bcdedit /set hypervisorlaunchtype off

    and then reboot the computer.

    No needs to change version of VMWare at all

    Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

sysadmin top30a
 
  • officelicensedeactivation
    Remove Office license file: How do you change the account that Office says it belongs to on a Mac JIRA|Confluence|Apps
  • FailedRegistration
    DNS Bad key 9017: The Cluster Name registration failed of one or more associated DNS names Virtualization
  • Featured image 3
    How to fix White Screen in Microsoft Teams Windows
  • PetitPotam
    PetitPotam attack on Active Directory Certificate Services: How to mitigate NTLM Relay PetitPotam attack on AD CS Security | Vulnerability Scans and Assessment
  • NortonEvents
    View and Clear or Print Norton Security Events on a Mac Anti-Virus Solution
  • Fix Windows Installer Service Could Not Be Accessed Error
    How to Fix the “Windows Installer Service Could Not Be Accessed” Error While Installing an Application Windows
  • banner 5
    How to fix Wi-Fi not connecting on Windows 11 Windows
  • How to Convert Google Forms Into Microsoft Forms banner
    Convert Google Forms Into Microsoft Forms Microsoft Exchange/Office/365

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,841 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.