[BUG] [BUG] Claude Desktop (Windows) unusable: orphaned CoworkVMService blocks MSIX registration repair — deadlock between 0x80073CF9 / 0x80070002 / 0x80073D02

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?

Claude Desktop cannot be launched, repaired, reinstalled, or fully removed. The machine is stuck in a self-sustaining deadlock caused by an orphaned packaged service (CoworkVMService / cowork-svc.exe) that survives package uninstall, cannot be deleted even by an elevated administrator, and auto-starts on every boot.

Launching the app produces the Windows dialog:

无法打开这个应用 — Claude 有问题。请从其原始安装位置重新安装应用程序，或与管理员联系。 ("This app can't open — There's a problem with Claude. Reinstall the app from its original install location, or contact your administrator.")

What Should Happen?

Expected Behavior
Uninstalling the package should remove its packaged service, or the installer should be able to force-remove it.
When the packaged service blocks deployment, the installer should terminate it (ForceApplicationShutdown / ForceTargetApplicationShutdown) rather than aborting.
The installer should not silently fall back to in-place update after a failed removal, since that is what produces the wedged state.
The error dialog should not claim "administrator access is required" when the log shows the process is already elevated; it should surface the underlying OpenService error.
A documented recovery path should exist for machines already in this state.

Error Messages/Logs

The Deadlock
The MSIX package registration is corrupt → the app refuses to launch.
Windows attempts an automatic registration repair (RegisterByPackageFullName with RepairAppRegistrationOption).
The repair is aborted because CoworkVMService is running — Windows treats the package as "in use" and returns 0x80073D02 (app must be closed).
Registration therefore stays corrupt → back to step 1.
The service is auto-start, so rebooting does not break the loop — it restores it.

The service also cannot be removed to break the cycle manually (see below), and a clean install path is unavailable because the installer's data-preserving removal is rejected without developer mode.

Steps to Reproduce

Have a previously installed Claude Desktop MSIX on Windows 10 Home (19045), developer mode off.
Run the current Claude Setup.exe to upgrade.
Installer logs WARNING: CoworkVMService already exists (potential conflict).
Installer fails to remove the conflicting service: Access is denied.
Installer's data-preserving removal is rejected: 0x80073CFA, requires developer mode; it falls back to in-place update.
AddPackage fails with 0x80073CF9.
The app is now in a state where it launches to the "can't open this app" dialog, and every subsequent repair/reinstall attempt fails

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude_1.24012.1.0_x64__pzs8sxrjxfjjc

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

Elevation type: Full
Is elevated: true
WARNING: CoworkVMService already exists (potential conflict)
Removing conflicting CoworkVMService...
WARNING: failed to remove conflicting service: could not open CoworkVMService: Access is denied.
Removing: Claude_1.24012.1.0_x64__pzs8sxrjxfjjc
Windows rejected data-preserving removal for Claude_1.24012.1.0_x64__pzs8sxrjxfjjc
(0x80073CFA, requires developer mode); relying on in-place update
Installing via AddPackage (current-user)...
MSIX installation failed: AddPackage failed: AddPackage failed with HRESULT 0x80073CF9
ERROR dialog (with log path): Administrator access is required to install Claude with full features.