Desktop app hang leaves orphaned processes/service, blocking reinstall
Status Closed — duplicate
Maintainer reply None cached
Activity 1 comment · opened Aug 20, 2026 · closed Aug 25, 2026
Description
The Claude desktop app hung and was force-closed by Windows. Afterward, the app icon vanished from the taskbar and relaunching gave an error requiring reinstall. The reinstall itself would not proceed until Claude-related processes were killed manually via Task Manager first.
Environment
- Windows 10 Pro 10.0.19045
- Claude desktop app version 1.32352.1.0
- Package:
Claude_1.32352.1.0_x64__pzs8sxrjxfjjc
Relevant Event Viewer entries
[Application Hang, Event ID 1002]
The program claude.exe version 1.32352.1.0 stopped interacting with Windows
and was closed.
Process ID: 4750
Faulting package full name: Claude_1.32352.1.0_x64__pzs8sxrjxfjjc
[Windows Error Reporting, Event ID 1001]
Fault bucket type 5, Event Name: MoAppHang
P1: Claude_1.32352.1.0_x64__pzs8sxrjxfjjc
P2: praid:Claude
[CoworkVMService, Warning]
Claude VM Service: failed to disarm SCM recovery actions for this stop;
if the stop overruns, the service may be auto-restarted during package
servicing: open service: Access is denied.
Claude VM Service: failed to configure SCM recovery actions; if the
service crashes it will not restart until the machine reboots:
open service: Access is denied.
Observed behavior
- App hangs, Windows force-closes it.
- App no longer launches / disappears from taskbar; UI reports reinstall is required.
- Reinstall fails/won't proceed until leftover Claude processes are killed manually in Task Manager.
- CoworkVMService logs repeated "Access is denied" errors when trying to (re)configure its own SCM recovery actions around the hang/restart.
Expected behavior
An app hang should not leave orphaned processes that block reinstallation, and the background service should be able to manage its own recovery actions without a permissions error.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗