Repository navigation
[BUG] Cowork shows "Virtualization is not enabled" on Windows 10 Pro despite Hyper-V fully enabled #27316
Description
Activity
Same issue on Dell Latitude 7490.
2. The log lines: yukonSilver not supported (status=unsupported) and VM not supported (win32/x64)
3. Claude Desktop version: 1.1.3918.0
4. Windows 11 Pro with Hyper-V is confirmed activeReacted by helderdelacoteSame issue on a Gigabyte motherboard, was work a day ago, updated and now says virtualization not enabled.
Same log line about yukonSilver not supported:
Log extract:
2026-02-21 08:20:10 [info] [deleteVMBundle] Reinstall files deleted (sessiondata.img and rootfs.img.zst preserved)
2026-02-21 08:23:29 [info] [cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported), checking for stale bundle...
2026-02-21 08:23:29 [info] [deleteVMBundle] Deleting reinstall files from C:\Users[REDACTED]\AppData\Roaming\Claude\vm_bundles\claudevm.bundle
2026-02-21 08:23:29 [info] [deleteVMBundle] Reinstall files deleted (sessiondata.img and rootfs.img.zst preserved)
2026-02-21 08:23:32 [warn] [startVM] VM not supported (win32/x64), skipping
2026-02-21 08:23:32 [info] [Callbacks] Initializing VM event callbacks...
2026-02-21 08:23:32 [info] [VM] Loading vmClient (TypeScript) module...
2026-02-21 08:23:32 [info] [VM] Module loaded successfully
2026-02-21 08:23:32 [info] [Callbacks] VM event callbacks initialized
2026-02-21 08:23:33 [warn] [startVM] VM not supported (win32/x64), skippingI am having the same issue "Virtualization is not enabled
Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart.". I have enabled Hyper-V, but I still get the same error. Initially, when i installed it, I did not have this error.Same issue on Windows 11 Pro on a Z590 Aorus Elite Gigabyte motherboard, also tried stopping VirtualBox services
Same issue here.
System:
- Windows 11 Pro (German locale)
- Intel Core i5-12600K
- MSI MPG Z690 EDGE WIFI
- 32 GB RAM
- Claude Desktop 1.1.3918 (fresh install)
Verification – everything is enabled:
- Intel Virtualization Technology enabled in BIOS (confirmed in MSI Click BIOS 5 → OC → CPU Features)
- Intel VT-D enabled in BIOS
- Hyper-V enabled in Windows Features (all sub-options)
- Virtual Machine Platform enabled
- Windows Hypervisor Platform enabled
bcdeditshowshypervisorlaunchtype Autosysteminfoconfirms: "A hypervisor has been detected"- Task Manager → CPU → Virtualization: Enabled
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -Allreturns Online: True
Steps taken:
- Enabled virtualization in BIOS
- Enabled all Hyper-V / VM features in Windows
- Set
bcdedit /set hypervisorlaunchtype auto - Multiple full restarts
- Complete uninstall + fresh reinstall of Claude Desktop
Error persists unchanged: "Virtualization is not enabled. Claude's workspace requires hardware virtualization (Hyper-V)."
I can confirm this issue on my Dell machine as well.
Dell Latitude 3420 after updating to 1.1.3918.
I spent quite a bit of time debugging it, and my results match the original report very closely:
- Hyper-V services are running (
hns,vmcompute,vmms,SharedAccess) - Hyper-V / Virtual Machine Platform / Windows Hypervisor Platform are enabled
bcdedit /set hypervisorlaunchtype autois set- BIOS virtualization is enabled (Intel VT-x / VT-d)
- Cowork still shows: “Virtualization is not enabled”
Additional notes from my troubleshooting:
- I initially saw HNS / ICS-related errors and reset the Windows network stack
- After reset, Cowork no longer throws the earlier network errors
- Now Cowork only shows the virtualization warning, even though Hyper-V is enabled and running
- Event Viewer shows Hyper-V virtual switches (including
Default Switchandcowork-vm-vnet) being created successfully, but CoworkVMService still logs repeated “Incorrect function” errors
This looks like a false negative in Cowork’s virtualization detection (or a Windows-specific compatibility issue in the latest version), rather than an actual BIOS/Hyper-V configuration problem.
Environment:
- Dell PC
- Windows 11 Pro Insiders (Beta) 25H2 26220.7872
- Claude Desktop / Cowork (latest)
If needed, I can provide:
systeminfoHyper-V output- Event Viewer logs (HNS / Hyper-V / CoworkVMService)
- Screenshots of the Cowork warning
- Hyper-V services are running (
I can reproduce this on Windows 10 Pro as well (different hardware).
My environment
- Windows 10 Pro (build 19045)
- ASUS Rampage V Extreme
- Intel i7-5930K
- Latest Claude Desktop (fresh install)
What I verified
-
BIOS virtualization is enabled (Intel VT-x)
-
Task Manager shows Virtualization: Enabled
-
Windows Features enabled:
- Hyper-V (with subcomponents)
- Virtual Machine Platform
- Windows Hypervisor Platform
-
Ran as Administrator:
bcdedit /set hypervisorlaunchtype auto(successful)
-
systeminfoconfirms:- "A hypervisor has been detected. Features required for Hyper-V will not be displayed."
-
Hyper-V virtual adapters exist, including:
- vEthernet (cowork-vm-vnet)
Current behavior
Claude Cowork still shows:
- "Virtualization is not enabled"
Extra notes
- In
AppData\Local\Claude\LogsI only see achrome-native-hostlog (MCP/Chrome integration), and I do not see a Cowork/VM log being created. - I also see MCP connection errors in the UI (
mcp-registry,Claude in Chrome), but Hyper-V itself appears to be working correctly.
This looks like a false virtualization detection on Windows 10, not a BIOS/Hyper-V configuration issue.
Dell PC
Edition Windows 11 Pro
Version 23H2
OS build 22631.6199
Experience Windows Feature Experience Pack 1000.22700.1108.0
Claude 1.1.3918 (a4b368) 2026-02-20T23:13:32.000ZVirtualization is not enabledClaude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart.PS C:\WINDOWS\system32> Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*Hyper*"} FeatureName : HypervisorPlatform State : Enabled FeatureName : Microsoft-Hyper-V-All State : Enabled FeatureName : Microsoft-Hyper-V State : Enabled FeatureName : Microsoft-Hyper-V-Tools-All State : Enabled FeatureName : Microsoft-Hyper-V-Management-PowerShell State : Enabled FeatureName : Microsoft-Hyper-V-Hypervisor State : Enabled FeatureName : Microsoft-Hyper-V-Services State : Enabled FeatureName : Microsoft-Hyper-V-Management-Clients State : EnabledSame issue. Does anybody got workaround?
Confirming the same issue on Windows 11 Pro (Build 26200).
Cowork tab shows "Virtualisierung ist nicht aktiviert" (German locale) despite Hyper-V being fully operational.
Verification via PowerShell (non-admin):
(Get-CimInstance Win32_ComputerSystem).HypervisorPresent→True-
vmcomputeservice → Running
-
-
vmmsservice → Running (StartType: Automatic)
-
-
-
-
(Get-ComputerInfo).HyperVisorPresent→True
Environment:
-
-
- Windows 11 Pro 10.0.26200
-
- Claude Desktop (latest, German locale)
-
-
- Hyper-V services fully running, WSL2 functional
-
same issue.
I got it to work yesterday after the latest update, and it not working again now.same issue; worked this morning for like 1h, took a break for 2h, came back to laptop, opened claude, got Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart.
Win11, Thinkpad T450s.
I feel empty...same issue.
Yoga Book 9i Gen 9 , Windows 11Anyone found a solution?
65 remaining items
I am having this same issue on a new DELL this morning. Still not working
I am having this same issue on a new DELL this morning. Still not working
Did you try installing the latest update? Available in the "Help" panel of the app.
Reacted by alexie-debug, wabmgh and Kenneth KI am having this same issue on a new DELL this morning. Still not working
Did you try installing the latest update? Available in the "Help" panel of the app.
thank you so much - it fixed - you are amazing - thankyou !
@JacquesAnthropic更新到 v1.1.3963 后即可正常工作。
Thank you very much, thank you allSame issue here — Windows 10 Pro 22H2, all virtualization confirmed working
System Specs
Component Value OS Windows 10 Pro 22H2 (Build 19045.6937) CPU Intel Core i7-7700K @ 4.20GHz RAM 32 GB Claude Desktop 1.1.3918 (a4b368) 2026-02-20 Cowork Error
Virtualization is not enabled. Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart.
Troubleshooting performed (all confirmed working)
1. BIOS — Virtualization enabled
- Intel VT-x / AMD SVM enabled in ASUS BIOS (Advanced → CPU Configuration)
- Task Manager → Performance → CPU → Virtualization: Enabled ✅
2. Hyper-V Windows Feature — Enabled
PS> Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-VFeatureName : Microsoft-Hyper-V
DisplayName : Hyper-V-Plattform
State : Enabled ✅
3. Hypervisor launch type — Auto
PS> bcdedit /enum | findstr hypervisorlaunchtype hypervisorlaunchtype Auto ✅4. Hyper-V services — Running
PS> Get-Service vmcompute, vmms # Both: Status = Running ✅5. Windows Fast Startup — Disabled
- Disabled via Power Options to ensure clean boot
- Performed full shutdown via
shutdown /s /t 0and cold boot - No change
6. WSL — Checked
PS> wsl --status # *(please fill in result)*Conclusion
Every system-level virtualization check passes. The issue is clearly on the app side — Cowork's platform detection rejects Windows 10 Pro (
win32/x64) despite Hyper-V being fully functional. The error message is misleading, suggesting a BIOS issue when in reality it appears to be a platform support / detection bug.I am still getting the same issue; using a Claude version from 2/11/2026 as a workaround but its very unstable. Lots of issues>
Environment
- Windows 11 Pro, Build 10.0.26200.7840 (x64)
- Installed via winget (
Anthropic.Claude) - Tested on versions 1.1.3963 and 1.1.4010
- Claude subscription: Pro Plan
Symptoms
Only the Chat and Code tabs are visible. No Cowork tab. SettingsidebarModeto"cowork"inclaude_desktop_config.jsoncauses the app to fail to launch with the error: "Claude Desktop failed to Launch — We are so sorry, Claude Desktop failed to launch. Please check for updates and try again. If the issue persists, contact support."Log output (
cowork_vm_node.log)[cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported), checking for stale bundle... [startVM] VM not supported (win32/x64), skipping [Callbacks] Swift VM addon not available for callbacksTroubleshooting steps completed
- Confirmed Intel VT-x enabled in BIOS
- Enabled all Hyper-V features (were disabled on first install): Microsoft-Hyper-V-All, VirtualMachinePlatform, HypervisorPlatform — all now Enabled
- Manually registered and started CoworkVMService using
cowork-svc.exefrom the resources folder — service ran successfully but made no difference - Confirmed
smol-bin.x64.vhdxis present in resources folder — VM bundle is there - Performed multiple full uninstall → delete AppData → reboot → reinstall cycles
- Upgraded to 1.1.4010 after clean reinstall
- Installed WSL2 with Ubuntu —
wsl --statusconfirms WSL2 running correctly
Additional notes
- This is a Squirrel-based install (no MSIX), so the
Add-AppxPackageworkaround from this thread does not apply - Forcing
sidebarMode: "cowork"in config causes a hard launch failure with the error above, suggesting the app is aware of the mode but crashes when platform detection blocks initialisation - A second machine built from the same Windows image works correctly with Cowork, suggesting the bug may be triggered by Hyper-V being disabled at the time of first install, with no recovery path even after enabling it and performing clean reinstalls
ked for me on Windows 10 Enterprise 22H2 (Build 19045):**
Despite having all Hyper-V features enabled, VirtualMachinePlatform, HypervisorPlatform, Containers, and Windows Sandbox — the "Virtualization is not available" error persisted across multiple restarts and a fresh Claude Desktop reinstall.
What actually fixed it (all 3 steps were needed):
- Delete the VM bundle to force a fresh download:
-
- Get-Process claude | Stop-Process -Force
- Start-Sleep -Seconds 3
- Remove-Item "$env:APPDATA\Claude\vm_bundles" -Recurse -Force -ErrorAction SilentlyContinue
-
- Restart the CoworkVMService:
-
- Restart-Service CoworkVMService
-
- Launch Claude Desktop as Administrator (right-click > Run as administrator)
After this, the error was gone and Cowork loaded successfully. The key insight is that the VM bundle can get into a bad state and needs to be deleted so the app re-downloads it fresh — combined with running as admin.
Same Issue
why is the issue closed?
I had this exact same issue and managed to fix it. Here is what worked for me:
Check Task Manager: Go to Task Manager > Performance > CPU. Check the bottom right to see if Virtualization is "Disabled". If it is, you need to restart into your BIOS and enable it (look for Intel VT-x, AMD-V, or SVM).
Turn on Windows Features: Search your Windows start menu for "Turn Windows features on or off".
Enable Hyper-V: In that list, make sure to check the boxes for Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform.
Click OK, let Windows apply the changes, and Restart your PC.
After doing this, the app booted up perfectly for me. Hope this helps!Same problem here.
Windows 10 PRO.
Claude Version 1.1.6452 (5afc23)Went all the way through Claude's instructions to try to fix it but no luck. Checked that Virtualization is enabled in Windows.
What's Wrong?
Cowork shows "Virtualization is not enabled. Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart." — despite Hyper-V being fully enabled and all related services running correctly.Restarting does not resolve the issue.
System Info
Property Value OS Windows 10 Pro Claude Desktop version (add your version here) Installation method Standard installer
Verification Steps Completed
Check Result vmcompute service ✅ Running vmms service ✅ Running Hyper-V enabled via Enable-WindowsOptionalFeature ✅ Done bcdedit hypervisorlaunchtype ✅ Set to Auto Get-NetNat ❌ Returns empty Get-HnsNetwork (cowork-vm-nat) ❌ Returns empty %APPDATA%\Claude\logs folder ❌ Does not exist — VM never initializes Restarted computer multiple times ✅ Done
Expected Behavior
Cowork should detect that Hyper-V is enabled and all required services are running, initialize the VM, create the logs folder, and allow access to the workspace.Actual Behavior
Cowork shows the BIOS error message and never attempts to start the VM. No logs are generated and the %APPDATA%\Claude\logs folder is never created.
Steps to Reproduce
- Install Claude Desktop on Windows 10 Pro
- Enable Hyper-V via
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All - Verify vmcompute and vmms services are running
- Open Claude Desktop and navigate to the Cowork tab
- Observe the "Virtualization is not enabled" error — VM never initializes
SOLVED I had the same issue and after many tries discovered that the Intel virtualization Service was disabled in the BIOS setup. Enabled and worked.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
- locked as resolved and limited conversation to collaborators
on Mar 26, 2026
Preflight Checklist
What's Wrong?
Cowork tab shows "Virtualization is not enabled. Claude's workspace requires
hardware virtualization (Hyper-V). Enable virtualization in your computer's
BIOS/UEFI settings, then restart." — despite all virtualization settings
being fully enabled and confirmed working.
Steps taken:
Error persists unchanged after all of the above.
What Should Happen?
Cowork should detect that hardware virtualization is fully enabled at both
the BIOS and Windows level, successfully start the VM, and allow access to
the Cowork workspace without showing the "Virtualization is not enabled" error.
Error Messages/Logs
Steps to Reproduce
Attempted fixes (error persists after all of these):
4. Restart PC and enter BIOS via F2 (Dell)
5. Navigate to Advanced → CPU Configuration
6. Enable "Intel Virtualization Technology" and "VT for Direct I/O"
7. Save with F10 and restart
8. Press Windows + R → type optionalfeatures → enable:
Claude Model
None
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
Claude 1.1.3918 (a4b368) 2026-02-20T23:13:32.000Z
Platform
Other
Operating System
Windows
Terminal/Shell
Other
Additional Information
No response