Yes, you can use WSL2 on Windows 10 Enterprise 22H2 with VMware Workstation 17 Pro without installing the Hyper-V feature. Modern versions of VMware utilize a different virtualization driver that coexists peacefully with WSL2’s underlying hypervisor, allowing both environments to run simultaneously without requiring the full Hyper-V Windows feature to be enabled.
Understanding the Virtualization Landscape
Historically, running multiple hypervisors like VMware and Hyper-V caused significant conflicts because they both attempted to take exclusive control of the hardware virtualization extensions (VT-x/AMD-V). This led to the common belief that enabling one required disabling the other. However, Microsoft introduced the Hypervisor Platform optional component in later updates to Windows 10, which allows Hyper-V to share the hardware with other Type-2 hypervisors.
VMware Workstation 17 Pro has been optimized to work within this shared environment. It no longer requires the legacy Hyper-V platform to be fully installed or active in the traditional sense. Instead, it relies on the VIX API and specific kernel drivers that interact with the Windows Hypervisor Platform. This means your system can run VMware VMs while WSL2 runs its lightweight Linux containers in the background. The key is ensuring that the correct Windows components are present, even if the "Hyper-V" management role is not turned on.
Required Windows Components for Coexistence
To ensure stability between WSL2 and VMware Workstation 17 Pro, you must enable specific optional Windows features. These features provide the necessary APIs for virtualization sharing without giving full administrative control over the hypervisor layer to VMware or WSL independently.
First, ensure that
Virtual Machine Platform is enabled. This feature provides the infrastructure for WSL2 to run. You can enable it via PowerShell by running:
Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -NoRestart
This command installs the necessary hypervisor support without activating the full Hyper-V Manager interface.
Second, verify that
Windows Hypervisor Platform is enabled. This is the critical bridge that allows VMware to talk to the same hypervisor layer as WSL2. Without this, VMware may fail to start or cause BSOD errors. Enable it using:
Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform -NoRestart
After enabling these features, a system restart is mandatory to load the new kernel drivers.
Verifying Driver Installation
Once rebooted, you can verify that the hypervisor is running correctly by opening Command Prompt and typing
systeminfo. Look for the line "Hyper-V Requirements." It should state that a hypervisor has been detected. If it says "None of the hypervisor features were present," your configuration is incomplete, and WSL2 will fall back to WSL1 or fail entirely.
For VMware, launch Workstation 17 Pro and create a test VM. If the VM boots successfully and shows CPU usage in Task Manager, the integration is working. Note that performance may vary slightly compared to bare-metal VMware, but for development purposes, the impact is negligible.
Configuring WSL2 and VMware Settings
While the base OS supports both, fine-tuning settings ensures optimal performance and prevents resource contention. WSL2 uses dynamic memory allocation, but it can sometimes consume more RAM than necessary, starving VMware VMs. To mitigate this, set a memory limit for your WSL2 instance.
Create or edit the file
%USERPROFILE%\.wslconfig in your Windows user directory. Add the following lines to restrict WSL2 memory usage:
[wsl2]
memory=4GB
processors=2
Adjust the values based on your total system RAM. This ensures that when you are running heavy VMware VMs, WSL2 does not monopolize your resources.
Additionally, check VMware’s compatibility settings. In VMware Workstation 17 Pro, go to
Edit > Preferences > Performance. Ensure that "Use hardware-assisted virtualization" is checked. This setting allows VMware to leverage the same VT-x/AMD-V instructions that WSL2 uses, rather than trying to emulate them in software, which would severely degrade performance.
Network Considerations
WSL2 and VMware both create virtual network adapters. Occasionally, this leads to IP conflicts or routing issues. If you cannot ping from WSL2 to a VMware VM, check your Windows Firewall rules. Ensure that the "Private Network" profile is applied to the virtual adapters created by VMware and WSL. You can manage this in
Control Panel > Network and Sharing Center > Change advanced sharing settings.
For seamless file access between the two, consider mounting NFS shares or using the built-in interoperability features. If you need to access Linux files from Windows, refer to our guide on
Accessing Linux Files from Windows Side with WSL2. Similarly, if you require persistent storage solutions, look into
Mounting NFS Shares from WSL in Windows 10 for robust data persistence across reboots.
Troubleshooting Common Issues
If VMware fails to start after enabling WSL2, check the Event Viewer for errors related to
VMM or
Hvix. Often, simply restarting the
vmware-hostd service resolves transient lockouts. Use the Services app to restart the VMware Host Agent.
If WSL2 becomes unresponsive or slow, it might be due to excessive disk I/O contention with VMware. Ensure that your virtual disks are stored on an SSD, preferably an NVMe drive. Mechanical hard drives struggle with the random I/O patterns generated by both hypervisors simultaneously. For users experiencing sluggishness, see our article on
Troubleshooting Unresponsive WSL2 on Windows 10.
Ensure that your BIOS/UEFI settings have Intel VT-x or AMD-V enabled. If this is disabled in firmware, neither WSL2 nor VMware Workstation will function correctly. Additionally, disable "Core Isolation" or "Memory Integrity" in Windows Security if you encounter specific driver signing errors, as these security features can sometimes interfere with third-party hypervisor drivers.
Frequently Asked Questions
Does enabling WSL2 automatically install the full Hyper-V role?
No, enabling WSL2 only activates the Virtual Machine Platform and Hypervisor Platform optional features. It does not install the full Hyper-V management tools or turn on the Hyper-V service unless explicitly configured. This keeps the overhead minimal and preserves compatibility with VMware.
Can I run VMware ESXi host on the same machine as WSL2?
No, VMware ESXi is a Type-1 hypervisor that requires exclusive access to the hardware. It cannot coexist with Windows-based Type-2 hypervisors like WSL2 or VMware Workstation. You would need a separate physical machine or a nested virtualization setup with significant performance penalties.
Why is my VMware VM running slowly after installing WSL2?
The slowdown is likely due to resource contention, particularly CPU scheduling or memory limits. WSL2 may be consuming available RAM, leaving less for the VMware VM. Adjusting the
.wslconfig file to limit WSL2 memory usage often resolves this issue immediately.
Do I need to disable Core Isolation to run both?
In most cases, no. However, if you experience driver signature verification errors or BSODs, temporarily disabling Memory Integrity in Windows Security Devices may help. Re-enable it once you have identified the conflicting driver, as it provides important security benefits.
How do I check if the Hypervisor Platform is actually running?
Open Command Prompt and run
systeminfo. Look for the "Hyper-V Requirements" section. If it states "A hypervisor has been detected," the platform is active. If it says none were detected, you need to reinstall the Virtual Machine Platform feature and reboot.