### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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 worked normally on this machine until version 1.21459.3.0. After the automatic update to 1.22209.0.0 (installed 2026-07-17), the app no lon

[BUG] Claude Desktop (MSIX) no longer launches after updating to 1.22209.0.0 — processes run but no window, on AD domain machine with OneDrive folder redirection

Status Open

Maintainer reply None cached

Activity 0 comments · opened Jul 18, 2026

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 worked normally on this machine until version 1.21459.3.0. After the automatic update to 1.22209.0.0 (installed 2026-07-17), the app no longer opens: background processes start (visible in Task Manager) but the main window never appears. No error dialog is shown.

The CoworkVMService log clearly shows the regression point: on every launch up to 1.21459.3.0, claude.exe connected to the service within seconds ("Client connected... signature verified"). Since 1.22209.0.0 (first start 2026-07-17 14:31), the service starts and listens, but no "Client connected" event ever appears again across all launch attempts on July 17–18. The service is healthy; the app process dies or hangs very early, before connecting to the service and before writing any of its own logs.

What Should Happen?

Claude Desktop should open its main window and be usable after launching from the Start menu, as it did on version 1.21459.3.0 and earlier on this same machine, user, and configuration (AD domain account with Desktop/Documents redirected to OneDrive). If the app cannot start due to the environment, it should at minimum show an error dialog and write a log entry indicating the failure reason, instead of exiting silently with background processes running and no window.

Error Messages/Logs

No error messages are produced anywhere — this is part of the problem:

- No error dialog is shown when launching the app
- No crash entries in Event Viewer (Windows Logs → Application, Microsoft-Windows-TWinUI/Operational, AppXDeploymentServer/Operational)
- The app never creates its own log: %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs remains empty
- Launching the inner binary directly with ELECTRON_ENABLE_LOGGING=1 and stdout/stderr redirected to a file prints nothing and creates no file — the process exits silently

The only log with content is the CoworkVMService log, which shows the regression point precisely. Last successful app-to-service connection, on 1.21459.3.0:


2026/07/16 15:13:56.288425 [Server] Client connected
2026/07/16 15:13:56.642340 [Server] Client signature verified: C:\Program Files\WindowsApps\Claude_1.21459.3.0_x64__pzs8sxrjxfjjc\app\claude.exe (subject: Anthropic, PBC)


Since the update to 1.22209.0.0 (first start 2026-07-17 14:31), the service starts and listens on every launch attempt, but claude.exe never connects again:


2026/07/17 14:31:22.720525 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/17 20:17:15.853433 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 16:43:25.917756 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 16:55:23.879566 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 17:20:40.088632 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 17:31:49.362982 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 17:40:47.052810 Service ready. Listening on \\.\pipe\cowork-vm-service


Full cowork-service.log attached.

Steps to Reproduce

Machine with AD domain user and Desktop/Documents redirected to OneDrive, running Claude Desktop 1.21459.3.0 normally.
App auto-updates to 1.22209.0.0.
Launch Claude Desktop from the Start menu.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.21459.3.0

Claude Code Version

1.22209.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Troubleshooting Already Attempted (none resolved the issue)

Killed all Claude/cowork processes and relaunched
Full uninstall (Remove-AppxPackage), deleted %LOCALAPPDATA%\Claude-3p, %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc, %APPDATA%\Claude, rebooted, reinstalled from claude.com/download (multiple times)
Removed orphaned CoworkVMService via registry (HKLM\SYSTEM\CurrentControlSet\Services\CoworkVMService) after sc.exe delete failed with Access is denied; verified with sc.exe query that the service no longer existed, rebooted, reinstalled — the new install registered its service correctly (service log confirms it runs fine), but the app still never opens
Deleted HKCU\SOFTWARE\Policies\Claude and HKLM\SOFTWARE\Policies\Claude
Launched the inner binary directly (...\app\claude.exe), with and without --disable-gpu, and with ELECTRON_ENABLE_LOGGING=1 redirecting output to a file: the process exits silently, prints nothing, creates no output file
Checked Event Viewer: Windows Logs → Application, and Applications and Services Logs → Microsoft → Windows → Apps (TWinUI/Operational) and AppXDeploymentServer/Operational — no errors logged around launch attempts
No main.log is ever created by the app (%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs is empty); the only log with content is the CoworkVMService log

Key Log Evidence (cowork-service.log)

Last successful app-to-service connection on 1.21459.3.0:

2026/07/16 15:13:56.288425 [Server] Client connected
2026/07/16 15:13:56.642340 [Server] Client signature verified: C:\Program Files\WindowsApps\Claude_1.21459.3.0_x64__pzs8sxrjxfjjc\app\claude.exe (subject: Anthropic, PBC)

First start of 1.22209.0.0 and all subsequent launch attempts — service ready, but the client never connects again:

2026/07/17 14:31:22.719217 [Server] Service: C:\Program Files\WindowsApps\Claude_1.22209.0.0_x64__pzs8sxrjxfjjc\app\resources\cowork-svc.exe
2026/07/17 14:31:22.720525 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/17 20:17:15.853433 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 16:43:25.917756 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 16:55:23.879566 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 17:20:40.088632 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 17:31:49.362982 Service ready. Listening on \\.\pipe\cowork-vm-service
2026/07/18 17:40:47.052810 Service ready. Listening on \\.\pipe\cowork-vm-service

View original on GitHub ↗