Claude Code Cowork (Windows): stuck process after auto-update requires full reboot to relaunch

Description

After Claude Code Cowork auto-updates on Windows, it closes but leaves orphan processes (cowork-svc.exe, chrome-native-host) that prevent the app from reopening. The only reliable workaround is a full system reboot.

This has happened at least 10 times, including on the most recent update (v1.569.0.0). It is extremely frustrating and time-consuming.

Steps to reproduce

1. Have Claude Code Cowork open on Windows 11
2. An auto-update triggers
3. The app closes itself to apply the update
4. Try to reopen the app — it won't launch

What we tried (none of these work)

1. taskkill /F /IM "Claude.exe" /T — process not found (the app runs as cowork-svc.exe under WindowsApps)
2. Stop-Process -Name "cowork-svc" -Force — kills the process, but it respawns immediately because its parent is services.exe (Windows SCM, PID 1796)
3. Stop-Service -Name "CoworkVMService" -Force — the service shows as Stopped, but cowork-svc.exe keeps respawning anyway
4. Killing process by PID repeatedly — it respawns with a new PID every time
5. Stop-Process -Id <PID> -Force; Start-Process "shell:AppsFolder\Claude_pzs8sxrjxfjjc!Claude" — kills process but app still won't open
6. Killing parent + child processes in sequence — parent is services.exe, access denied

Process tree observed

services.exe (PID 1796) — Windows SCM, cannot be killed
  └── cowork-svc.exe (respawns indefinitely)
        └── chrome-native-host (also orphaned)

Relevant paths

• C:\Program Files\WindowsApps\Claude_1.569.0.0_x64__pzs8sxrjxfjjc\app\resources\cowork-svc.exe
• C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\Chrome...

Expected behavior

The app should cleanly restart after auto-updating without leaving zombie processes or requiring a full system reboot.

Environment

• OS: Windows 11 Pro 10.0.26200
• App: Claude Code Cowork (Microsoft Store), v1.569.0.0
• Frequency: At least 10 times, every auto-update

Impact

Every time the app updates, the user loses ~5-10 minutes waiting for process kills that don't work, eventually having to reboot. This significantly disrupts workflow.