[BUG] Claude Desktop fails to launch on Windows 11 25H2 (Build 26200) — CoworkVMService crashes during HCS DLL initialization

Status Fixed / completed
Maintainer reply None cached
Activity 6 comments · opened Feb 15, 2026 · closed Feb 15, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Key details to include:

Windows 11 Pro, version 25H2, Build 26200
Claude Desktop version 1.1.3189.0 (MSIX)
Error: "We are sorry, Claude Desktop failed to launch. Please check for updates and try again"
Event Viewer shows CoworkVMService EventID 1 with data: [HCS] Initializing HCS DLLs... followed by "Incorrect function"
main.log is 0 bytes — app crashes before writing any logs
Same Claude Desktop works perfectly on Windows 11 Home 24H2 (Build 26100) with identical install
Intel i7-10510U, Hyper-V fully enabled
Tried: clean installs, removing all AppData/Packages, removing MSIX package, disabling Hyper-V, disabling Container features (Docker remnants), removing CoworkVMService, Developer Mode enabled — nothing helps
The app has no graceful fallback — if CoworkVMService fails, the entire app crashes instead of falling back to Chat-only mode

What Should Happen?

Claude windows app should have started at least without cowork option

Error Messages/Logs

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="CoworkVMService" />
<EventID Qualifiers="0">1</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2026-02-15T09:37:41.1737908Z" />
<EventRecordID>82277</EventRecordID>
<Correlation />
<Execution ProcessID="3048" ThreadID="0" />
<Channel>Application</Channel>
<Computer>viz-laptop</Computer>
<Security />
</System>
<EventData>
<Data>[HCS] Initializing HCS DLLs...</Data>
</EventData>
</Event>

PS C:\WINDOWS\system32> Get-Item "C:\Users\vijay\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\main.log" | Select-Object FullName, Length, LastWriteTime

FullName                                                                                           Length LastWriteTime
--------                                                                                           ------ -------------
C:\Users\vijay\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\main.log      0 2/15/2026 3:26:16 PM

Steps to Reproduce

Have a Windows 11 Pro machine running version 25H2 (Build 26200)
Ensure Hyper-V and all virtualization features are enabled
Download Claude Desktop installer from claude.ai/download
Run ClaudeSetup.exe — installation completes successfully
Launch Claude Desktop from Start menu
App shows error dialog: "We are sorry, Claude Desktop failed to launch. Please check for updates and try again. If issue persists contact support"
Check Windows Event Viewer → Application log → CoworkVMService EventID 1 shows: [HCS] Initializing HCS DLLs... followed by "Incorrect function"
Check %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\main.log — file is 0 bytes (app crashes before writing logs)

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.1.3189.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

The exact same installer and account works perfectly on Windows 11 Home 24H2 (Build 26100) on a different machine
Issue persists after: complete uninstall + clean reinstall, deleting all AppData/Packages folders, removing MSIX package via Remove-AppxPackage, removing CoworkVMService via sc.exe delete, disabling full Hyper-V (keeping only VirtualMachinePlatform), disabling leftover Docker Container features, enabling Developer Mode, multiple reboots
The app force-starts CoworkVMService on every launch and crashes entirely when it fails — there is no fallback to Chat-only mode

Update: The original launch crash was resolved in a later Claude Desktop update. However, I then hit a second issue — Cowork failing with:

HCS operation failed: HRESULT 0xc03a001a
"Virtual hard disk files must be uncompressed and unencrypted and must not be sparse."

Root Cause: My C: drive had "Compress this drive to save disk space" enabled. The VHDX files in the VM bundle inherited NTFS compression, which Hyper-V rejects. Even after decompressing the files and all parent directories, the error persisted because a stale HNS network and cached VM state from the failed attempts were still registered.

Fix (PowerShell as Admin):

  1. Disable drive-level compression: Right-click C: drive → Properties → uncheck "Compress this drive to save disk space"
  1. Decompress the Claude package directory and all parent folders:
compact /u /s:"$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc" *.*
# Also decompress each parent directory individually with:
# compact /u "<path>" for each folder in the chain
  1. Remove the stale Cowork HNS network:
Get-HnsNetwork | Where-Object { $_.Name -like "*cowork*" } | Remove-HnsNetwork
  1. Restart Hyper-V services:
Stop-Service CoworkVMService -Force -ErrorAction SilentlyContinue
Restart-Service vmcompute
Restart-Service vmms
  1. Delete the VM bundle to force a clean download:
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles"
  1. Launch Claude Desktop → Cowork starts successfully.

Key takeaway: Decompressing the VHDX files alone is not enough. The stale HNS network and VM registration from failed attempts must also be removed, otherwise Hyper-V keeps trying to use the old (compressed) VM configuration.

Suggestion to Anthropic: The Cowork VM setup should check for NTFS compression on the bundle path before attempting to start the VM, and surface a clear error message if detected. The "Reinstall workspace" option should also clean up HNS networks and stale VM state.

View original on GitHub ↗

6 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/25829
  2. https://github.com/anthropics/claude-code/issues/25505
  3. https://github.com/anthropics/claude-code/issues/25419

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Alex-Saad · 6 months ago

Environment:
OS: Windows 11 Pro 25H2 (Build 26200.7462) — received via standard Windows Update, not Insider Programme
Hardware: Dell Latitude 7400 (physical machine, confirmed not a VM)
Installer: Claude Setup.exe (direct download from claude.ai/download)

Windows Features enabled:
Microsoft-Hyper-V-All ✅
HypervisorPlatform ✅
VirtualMachinePlatform ✅
WSL2 installed with Ubuntu ✅

Services running:
vmms (Running, Automatic)
vmcompute (Running, Manual)
hns (Running, Manual)

Relevant log output from cowork_vm_node.log:
2026-02-21 10:21:44 [info] [cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported), checking for stale bundle...
2026-02-21 10:22:37 [warn] [startVM] VM not supported (win32/x64), skipping
Error shown in UI:

"Virtualization is not enabled. Claude's workspace requires hardware virtualization (Hyper-V). Enable virtualization in your computer's BIOS/UEFI settings, then restart."

This error is misleading — hardware virtualization is confirmed enabled and all required features are active. The issue appears to be yukonSilver incorrectly flagging this win32/x64 environment as unsupported despite full Hyper-V support being present.

lennymatei · 6 months ago

I also have the same issue and getting the same error. Unable to use Claude Cowork

deep-surf · 6 months ago

System Info:

OS: Windows 11 Pro 26200 (25H2)
Virtualization: Enabled in BIOS
Hyper-V: Enabled (all features including Windows Hypervisor Platform)
bcdedit hypervisorlaunchtype: Auto
Hyper-V services: Running
Issue:
Even with all virtualization settings properly configured, Claude Desktop shows the error: "Virtualization is not activated. Claude's workspace requires hardware virtualization (Hyper-V)."

This issue persists after:

Enabling virtualization in BIOS/UEFI
Enabling Hyper-V, Windows Hypervisor Platform, and Windows Sandbox via optionalfeatures
Setting bcdedit /set hypervisorlaunchtype auto
Multiple reboots
Please prioritize a fix for Windows 11 25H2 (Build 26200). This appears to affect multiple users on this build.

bullstadili · 6 months ago

Device: ASUS TUF Gaming FX516P
CPU: 11th Gen Intel Core i5-11300H @ 3.10GHz
RAM: 16 GB
OS: Windows 11 Pro Build 26200 (10.0.26200)
App Version: Claude Desktop 1.1.3963
Install Method: Tested both Microsoft Store and direct installer from claude.ai/download

Error:
HCS operation failed: failed to create compute system: HcsWaitForOperationResult failed with HRESULT 0x80370102
"Cannot create system 'cowork-vm' since Hyper-V is not installed on the host."

Troubleshooting already completed:

Intel VT-x and VT-d confirmed Enabled in ASUS BIOS (Advanced Mode)
System Information shows all 4 Hyper-V requirements as Yes
All Hyper-V Windows features enabled (Microsoft-Hyper-V-All, Hypervisor, Services, Tools, Management)
HypervisorPlatform: Enabled
vmms (Hyper-V Virtual Machine Management): Running
vmcompute (Hyper-V Host Compute Service): Running
BCD hypervisorlaunchtype: Auto
VBS/Memory Integrity: Disabled
No Docker, VMware, VirtualBox, WSL2, or conflicting virtualization software installed
No HAXM/Android emulator remnants
168 GB free disk space
Cleared claude-code-vm and vm_bundles folders
Ran Claude as Administrator
Multiple full restarts performed

Note: WMI reports VirtualizationFirmwareEnabled: False despite BIOS showing VT enabled — possibly a firmware reporting issue specific to this hardware/OS build combination.

github-actions[bot] · 6 months ago

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.