IssueRaiser

Claude Desktop (Windows): provide a way to disable the bundled Cowork background service (CoworkVMService) for users who don't use Cowork

### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement On Windows, Claude Desktop bundles a packaged Win32 service called `CoworkVMService` (running `app\resources\cowork-svc.exe` as `localSystem`) inside its MSIX package. The service is registered with `StartupType="auto"` and starts on every system boot — even when the user has never opened Cowork or has decided not to use it. I'm primarily a Claude Code user. I tried Cowork once early on, decided Claude Code suits my workflow better, and haven't used Cowork since. But `cowork-svc.exe` still spins up on every boot, takes RAM, and there is no way to turn it off: - **No in-app toggle** in Claude Desktop to disable Cowork or its background service. - **Standard Windows methods are blocked** because it's an MSIX-packaged service: - `sc.exe config CoworkVMService start= disabled` returns `OpenService FAILED 5: Access is denied`, even from an elevated Administrator PowerShell. - `Set-Service -StartupType Disabled` has the same problem. - **The package manifest hardcodes** `<desktop6:Service Name="CoworkVMService" StartupType="auto" StartAccount="localSystem">`, so even a clean reinstall would re-register it identically. Uninstalling Claude Desktop is not an option for me — I use it daily. - **The only

Posted by itutar on May 8, 2026, 6:24 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (SaaS)

Claude Desktop (Windows): provide a way to disable the bundled Cowork background service (CoworkVMService) for users who don't use Cowork

itutarMay 8, 2026, 6:24 PM

### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement On Windows, Claude Desktop bundles a packaged Win32 service called `CoworkVMService` (running `app\resources\cowork-svc.exe` as `localSystem`) inside its MSIX package. The service is registered with `StartupType="auto"` and starts on every system boot — even when the user has never opened Cowork or has decided not to use it. I'm primarily a Claude Code user. I tried Cowork once early on, decided Claude Code suits my workflow better, and haven't used Cowork since. But `cowork-svc.exe` still spins up on every boot, takes RAM, and there is no way to turn it off: - **No in-app toggle** in Claude Desktop to disable Cowork or its background service. - **Standard Windows methods are blocked** because it's an MSIX-packaged service: - `sc.exe config CoworkVMService start= disabled` returns `OpenService FAILED 5: Access is denied`, even from an elevated Administrator PowerShell. - `Set-Service -StartupType Disabled` has the same problem. - **The package manifest hardcodes** `<desktop6:Service Name="CoworkVMService" StartupType="auto" StartAccount="localSystem">`, so even a clean reinstall would re-register it identically. Uninstalling Claude Desktop is not an option for me — I use it daily. - **The only

Comments (0)

No comments yet. Start the discussion.

Comment on this issue