How to Fix Claude Desktop Cowork on Windows When Virtual Machine Platform Error Happens
The MSIX link Anthropic buried, and why Microsoft’s AI had to walk me through finding it
Is This Your Problem?
There are several ways Cowork can break on Windows, and the fix depends entirely on which one you have. This post covers one specific scenario.
You installed Claude Desktop using the standard .exe from claude.com/download. When you open the Cowork tab, you see: “Virtual Machine Platform required” or “Virtualization is not enabled.” You’ve uninstalled and reinstalled. Nothing changed.
If that’s your situation, keep reading. The fix is straightforward once you know what’s actually broken.
If Cowork installed but is failing with API unreachable errors, NAT conflicts, or networking issues, that’s a different family of problems. This post won’t fix those. The GitHub issue tracker for Claude Code has active threads on all of them.
Update: April 5, 2026
The MSIX fix below still works for the original installation problem. But there’s more to the story.
After getting Cowork running cleanly, I found it breaking on its own every 10-20 minutes with a different error: “Virtualization is not available. The virtualization service isn’t responding.” No update triggered it. It just happens.
There’s a fix, and it works. But the frequency makes Cowork impractical for sustained use right now. Read the full update at the bottom of this post before you invest time in the install.
The Complete Fix, In Order
The EXE installer leaves behind two app data folders that corrupt any reinstall attempt. You have to clean those out first. Do these steps in exact order and don’t skip any of them.
Step 1: Uninstall Claude Desktop
Go to Windows Settings, then Apps, find Claude, and uninstall it the normal way. Wait for it to finish completely before moving on.
Step 2: Delete the two leftover app data folders
Open File Explorer. Paste each of these paths into the address bar one at a time and delete the Claude folder at each location:
%LOCALAPPDATA%\Claude
%APPDATA%\ClaudeThe EXE installed Claude using an older packaging format called Squirrel. When Windows tries to install the MSIX package over it, the two formats conflict and the install silently fails. Deleting these folders removes the leftover Squirrel data so the MSIX can register cleanly.
Step 3: Download the MSIX installer
Do not go back to claude.com/download. That’s the EXE again. Use this URL:
https://claude.ai/api/desktop/win32/x64/msix/latest/redirect
That URL always redirects to the current version. Save the file to your Downloads folder. More on why this link is buried where nobody finds it in a moment.
Step 4: Install via PowerShell
Open PowerShell as administrator and run these two commands:
cd $env:USERPROFILE\Downloads
Add-AppxPackage -Path ".\Claude.msix"When it finishes, PowerShell will return nothing. No confirmation. No “installation complete.” Just a blinking cursor and a return to the prompt.
That’s the success message. Silence equals done.
Step 5: Restart your machine
Not optional. Cowork checks virtualization services on first launch and needs a clean boot to initialize them correctly. Two minutes now saves another round of troubleshooting later.
Step 6: Launch Claude and open Cowork
Open Claude Desktop. Wait about ten seconds for background services to spin up. Then open the Cowork tab. The virtualization error should be gone.
Why the Standard Installer Breaks Cowork
The download at claude.com/download gives you a .exe installer. I ran it. Claude installed. Cowork didn’t work. I uninstalled, reinstalled. Same result.
What I eventually learned is that the EXE installer has a known issue on Windows: the app installs, but the virtualization components Cowork depends on don’t register correctly. The MSIX package handles that registration properly. The EXE doesn’t. This isn’t a configuration problem on your end. It’s a packaging problem on Anthropic’s end.
The Link Anthropic Doesn’t Surface (But Should)
The MSIX installer is official. It’s on Anthropic’s servers. It just isn’t on the main download page. It lives in enterprise deployment documentation written for IT departments doing fleet installs, not for someone who just wants Cowork to work on their laptop.
Here’s how buried it is: I asked Claude directly where to find the MSIX package. Claude had to search the web to locate it. The AI that makes the product couldn’t pull the link from memory because it isn’t surfaced anywhere a normal user would land.
That’s not a knock on Claude. That’s a documentation problem. And it’s exactly why people hit this wall and assume they did something wrong when they didn’t.
The Part Where Microsoft’s AI Fixed Anthropic’s AI
Before I had any of this figured out, I spent time in a Copilot session walking through the diagnosis step by step. Copilot identified the broken EXE installer issue. Copilot pointed me toward the MSIX path. Copilot walked me through the PowerShell commands.
It worked. Cowork launched clean on the first try after the MSIX install.
I’m not telling you this to needle Anthropic. Claude is the tool I use every day and I’m not switching. But the irony deserves acknowledgment: on the day I finally got Claude’s most powerful feature working, the credit goes to a competitor’s AI. That’s where we are in 2026. The ecosystem is genuinely useful, genuinely rough around the edges, and occasionally you need one AI to debug another.
One More Thing Before You Update
Cowork on Windows is still a research preview, and several users have reported it breaking again after Claude Desktop auto-updates. I’m not telling you to freeze your installation forever. Security patches matter and a frozen install creates its own problems. But it’s worth letting updates sit for a day or two before applying them. Let the early adopters take the shrapnel first.
Side Note: If you’re using Cloudflare and haven’t checked your AI crawler settings, that’s a separate problem worth fixing. I covered it here.
If this saved you an afternoon, good. If you hit a different wall along the way, reply and tell me what it was. I’m collecting real-world results, not feature lists.
When Cowork Breaks After It’s Already Working
If you followed the steps above and Cowork was working, then suddenly wasn’t, this is a different problem. The vm_bundles folder that Cowork uses to run its local VM becomes stale and needs to be deleted so Claude can rebuild it clean.
The vm_bundles folder on an MSIX install is not where most guides will tell you to look. It’s here:
%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundlesClose Claude Desktop completely. Open PowerShell as Administrator and run:
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles"Relaunch Claude. Cowork should open without the error.
To make this repeatable, save this as a PowerShell script and run it from an Administrator PowerShell session when the error appears:
# Fix-Claude-Cowork.ps1
Get-Process -Name "Claude*" -ErrorAction SilentlyContinue | Stop-Process -Force
Start-Sleep -Seconds 3
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\vm_bundles" -ErrorAction SilentlyContinue
Start-Process "explorer.exe" "shell:AppsFolder\Claude_pzs8sxrjxfjjc!Claude"The honest assessment: In my testing, this error returns every 10-20 minutes on its own. The script fixes it reliably, but that frequency makes Cowork impractical for sustained work. Cowork is still a research preview on Windows, and right now it shows. I’ll update this post when the stability picture changes.
