Why doesn't it work?

[RaSystemlord]

Lots of discussions why VMware doesn't work here and there. Kasper brought up, in another thread, interesting points on "who's fault it is?" I  think there was something right in that.

So, I asked two "experts": ChatGPT 3.5 (free) and Deepseek. Obviously, theit answers are not literally true. They have the same typical instruction to "use the latest". I think it has been established here that don't use literally "the latest", but use the latest big number, 17, and in detail 17.5.2 if you want your systems to work. But anyway, here is first the answer from ChatGPT 3.5. In the following Post, I have Deepseek's answer. They are in-line, but have some different details.

ChatGPT 3.5
The question: Why doesn't VMware Workstation work on modern computers? Is there a specific reason why I doesn't work on AMD but does work on Intel?

The answer: 

VMware Workstation can run on modern computers, but there are a few key reasons why it may not work as expected, especially on AMD systems. The main issues stem from CPU compatibility, security features, and software support.

1. Microsoft Hyper-V Conflicts
Modern versions of Windows (10 and 11) enable Hyper-V by default if you have features like Windows Subsystem for Linux (WSL2), Virtual Machine Platform, or Windows Sandbox enabled.
VMware Workstation does not work well when Hyper-V is active because Hyper-V takes control of the CPU's virtualization extensions (VT-x for Intel, AMD-V for AMD), preventing VMware from accessing them.
On Intel CPUs, VMware has made improvements to work alongside Hyper-V (using "Windows Hypervisor Platform" mode), but on AMD CPUs, this mode is unstable or not fully supported.
2. AMD CPU Compatibility Issues
Older versions of VMware Workstation had poor optimization for AMD's Zen architecture (Ryzen, Threadripper, EPYC), leading to crashes and poor performance.
Nested virtualization (running a VM inside a VM) on AMD is often broken or unreliable due to differences in how AMD-V works compared to Intel VT-x.
VMware has historically optimized more for Intel CPUs, since Intel has been dominant in enterprise environments.
3. Windows 11 & Security Features (VBS)
Windows 11 enables Virtualization-Based Security (VBS) and Memory Integrity (HVCI) by default.
These security features use Hyper-V-like technologies, even if Hyper-V itself is "disabled" in Windows settings.
This prevents VMware from accessing the CPU's virtualization features, causing errors or crashes.
Again, Intel CPUs handle this better because VMware has worked to improve compatibility with Hyper-V on Intel.

4. BIOS/UEFI Virtualization Settings
Some AMD motherboards disable SVM (Secure Virtual Machine Mode) by default. If this is off, VMware Workstation won't work.
On Intel, VT-x is more consistently enabled by default.
How to Fix VMware Workstation on AMD?
If you're having trouble running VMware Workstation on an AMD system, try these steps:

1.
Disable Hyper-V
Open PowerShell (as admin) and run:

2.
Check BIOS Settings

Enable SVM Mode (for AMD) or VT-x (for Intel) in BIOS/UEFI.

3.
Disable Windows Security Features

Turn off Memory Integrity in Windows Security → Device Security → Core Isolation.
Disable Virtualization-Based Security (VBS) via Group Policy.

4.
Use a Newer Version of VMware

VMware Workstation 17+ has improved support for Hyper-V mode on Intel but still struggles on AMD.

Alternative Solutions
If VMware still won't work, you can try:

Oracle VirtualBox (which also struggles with Hyper-V but works better on AMD).
Hyper-V (if you're OK with using Microsoft's virtualization instead of VMware).
KVM (Kernel-based Virtual Machine) if you're using Linux.
Would you like help troubleshooting your specific setup? Let me know what errors you're seeing!

[RaSystemlord]

And here is the Deepseek.

The question (the same): Why doesn't VMware Workstation work on modern computers? Is there a specific reason why I doesn't work on AMD but does work on Intel?

The answer:

VMware Workstation is a popular virtualization software that allows users to run multiple operating systems on a single physical machine. However, there are specific reasons why VMware Workstation might not work optimally or at all on some modern computers, particularly those with AMD processors, while functioning well on Intel-based systems. Here are the key factors:

1. Hardware Virtualization Support
VMware Workstation relies heavily on hardware virtualization features provided by the CPU, such as Intel VT-x (for Intel processors) and AMD-V (for AMD processors). If these features are not enabled in the BIOS/UEFI, VMware Workstation will not function properly.

Intel vs. AMD Differences: While both Intel and AMD provide hardware virtualization support, there are differences in how these technologies are implemented. Some older versions of VMware Workstation may not fully support newer AMD architectures or may require updates to work correctly.

2. Compatibility with AMD Processors
Historical Issues: In the past, VMware Workstation had better optimization for Intel processors due to Intel's dominant market share in the virtualization space. AMD processors, especially older ones, sometimes faced compatibility issues.

Nested Virtualization: AMD's nested virtualization support (e.g., running a hypervisor inside a virtual machine) has historically lagged behind Intel's. This can cause issues when using VMware Workstation on AMD systems, particularly for advanced use cases.

Driver and Firmware Support: VMware Workstation relies on specific drivers and firmware support. If AMD's firmware or drivers are not fully compatible with VMware's requirements, issues may arise.

3. Software Updates and Support
Outdated VMware Versions: If you're using an older version of VMware Workstation, it may not support newer AMD processors or chipsets. VMware regularly releases updates to support the latest hardware, so using an outdated version could lead to compatibility issues.

AMD-Specific Bugs: Some versions of VMware Workstation may have bugs or limitations specific to AMD processors. These are often addressed in later updates, but if you're not using the latest version, you might encounter problems.

4. Operating System and Driver Compatibility
VMware Workstation depends on the host operating system and its drivers to interact with the hardware. If the OS or its drivers are not properly configured or updated, VMware may not work correctly, regardless of whether you're using Intel or AMD.

AMD GPU Drivers: If your system uses an AMD GPU, there could be conflicts with VMware's virtual GPU implementation. Ensuring that your GPU drivers are up to date can help mitigate these issues.

5. BIOS/UEFI Settings
Both Intel and AMD systems require specific BIOS/UEFI settings to enable virtualization features. If these settings are not enabled, VMware Workstation will not function properly. Common settings to check include:

Intel VT-x or AMD-V (hardware virtualization)

Intel VT-d or AMD IOMMU (for device passthrough)

On some systems, these settings may be disabled by default.

6. Workarounds and Solutions
Update VMware Workstation: Ensure you're using the latest version of VMware Workstation, as newer versions include better support for modern hardware, including AMD processors.

Enable Virtualization in BIOS/UEFI: Check your system's BIOS/UEFI settings and enable hardware virtualization features.

Update Drivers and Firmware: Make sure your system's chipset, GPU, and other drivers are up to date.

Check VMware Compatibility Guide: VMware provides a compatibility guide for supported hardware and operating systems. Verify that your system meets the requirements.

Conclusion
VMware Workstation may not work on some modern computers, particularly AMD-based systems, due to differences in hardware virtualization support, software compatibility, and BIOS/UEFI settings. However, these issues can often be resolved by updating VMware Workstation, enabling the necessary BIOS/UEFI settings, and ensuring that your system's drivers and firmware are up to date. If you're still experiencing issues, consider reaching out to VMware support or consulting their documentation for AMD-specific troubleshooting steps.

[RaSystemlord]

Any takers on these answers? 

kasper?

[kasper]

Yes.   AMD seems to suffer more so with this HyperV being enabled issue.   I have several AMD pcusers (4000, 7000 and 8000 series) and each one requires different changes in order to make sure HyperV is not enabled.   And I use the latest chipset and drivers for all.   My worst case scenario to disable HyperV requires changes to the boot loader which is a painful process.    So on a Windows 11 24h2 host, the OS at boot time is making some desions on whether HyperV is enabled.  What is curious is that Broadcom hardware is now competing with Intel and AMD.

[RaSystemlord]

Thanks for the added info.

This is also good to know for anybody planning to buy a new PC, like me. It seems that newer (ASUS ROG Strix) models are using Intel and older ones, still sold today, use Ryzen. 

Like these "experts" say and my collegues confirmed, some other virtualization software packages are not free from problems either. Perhaps Microsoft products are, because they have created these problems in Windows OS.