Environment
- Windows 10 Pro
- Claude Desktop installed via MSIX (x64)
- Cowork research preview
The problem
After a clean MSIX install, Cowork launches correctly. Then, without any update or trigger, it breaks with this error every 10-20 minutes:
"Virtualization is not available. Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding."
Windows virtualization is healthy (vmcompute is Running). The problem is the vm_bundles folder becoming stale.
The workaround
Delete the vm_bundles folder and relaunch Claude. On an MSIX install the folder is at:
%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles
This is not documented anywhere. The path commonly cited (%APPDATA%\Claude\vm_bundles) does not exist on MSIX installs.
Two requests
- Fix the underlying instability causing vm_bundles to go stale every 10-20 minutes
- Document the correct vm_bundles path for MSIX installations
Full writeup with reproduction steps and repair script here:
https://aeoseoengine.com/how-to-fix-claude-desktop-on-windows-when-virtual-machine-platform-error-happens/
Environment
The problem
After a clean MSIX install, Cowork launches correctly. Then, without any update or trigger, it breaks with this error every 10-20 minutes:
"Virtualization is not available. Claude's workspace requires Virtual Machine Platform, but the virtualization service isn't responding."
Windows virtualization is healthy (vmcompute is Running). The problem is the vm_bundles folder becoming stale.
The workaround
Delete the vm_bundles folder and relaunch Claude. On an MSIX install the folder is at:
%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles
This is not documented anywhere. The path commonly cited (%APPDATA%\Claude\vm_bundles) does not exist on MSIX installs.
Two requests
Full writeup with reproduction steps and repair script here:
https://aeoseoengine.com/how-to-fix-claude-desktop-on-windows-when-virtual-machine-platform-error-happens/