Cowork VM Service crash-loops after bash.exe Application Hang; repair fails while app is running

Environment

• OS: Windows 11 Pro 10.0.26200

-%20Git%20Bash%3A%202.55.0.3%0A%0AWhat%20happened%0A%0AWhile%20running%20Claude%20Code%20(Bash%20tool)%20inside%20the%20Cowork%20VM%20sandbox%2C%20%60bash.exe%60%20stopped%20responding%20to%20Windows%3A%0A%0A%3E%20Windows%20Event%20Log%2C%20Application%2C%20Event%20ID%201002%20(Application%20Hang)%3A%0A%3E%20%22bash.exe%20version%202.55.0.3%20stopped%20interacting%20with%20Windows%20and%20was%20closed.%22%0A%0AAt%20the%20same%20instant%2C%20the%20Cowork%20VM%20Windows%20service%20received%20a%20stop%20request%20and%20shut%20down%20mid-session%20(from%20%60C%3A%5CProgramData%5CClaude%5CLogs%5Ccowork-service.log%60)%3A%0A%60%60%60%0A17%3A59%3A32%20Service%20stop%20requested%0A17%3A59%3A32%20%5BServer%5D%20Stopping%20VM%20for%20session...%0A17%3A59%3A32%20Service%20stopped.%0A%60%60%60%0A%0AWith%20the%20service%20down%20but%20%60claude.exe%60%20still%20running%2C%20Windows%20Settings%20%3E%20Apps%20reported%20the%20Claude%20app%20as%20%22damaged%22%20and%20offered%20Repair%2FReset%20-%20but%20Repair%20failed%20every%20time%20with%20%22can't%20repair%20because%20the%20app%20is%20running.%22%20Over%20~3%20minutes%2C%20Windows'%20Service%20Control%20Manager%20logged%205%20repeated%20cycles%20of%20installing%20then%20auto-disabling%20the%20%60Claude%60%2F%60cowork-svc.exe%60%20service%20(Event%20IDs%207045%2F7040)%2C%20i.e.%20the%20self-repair%20loop%20never%20completed%20while%20the%20app%20process%20was%20alive.%0A%0AThe%20condition%20only%20cleared%20after%20manually%20ending%20a%20security%2Fcredential-isolation-related%20process%20in%20Task%20Manager%20(Windows%20System%20log%20shows%20a%20%22Secure%20Trustlet%22%20tied%20to%20the%20VM%20sandbox%20stopping%20around%20the%20same%20time).%20After%20that%2C%20the%20service%20log%20shows%20a%20clean%20restart%3A%0A%60%60%60%0A18%3A03%3A24%20Starting%20CoworkVMService%20as%20Windows%20service%0A18%3A03%3A24%20Claude%20VM%20Service%20starting...%0A18%3A04%3A13%20%5BServer%5D%20Client%20connected%20%20(claude.exe%20reconnects)%0A%60%60%60%0A%0AImpact%0A%0A-%20The%20running%20Claude%20Code%20session%20was%20silently%20killed%20with%20no%20error%20surfaced%20in%20the%20app%2FCLI%20itself%20-%20the%20only%20visible%20symptom%20was%20Windows%20saying%20the%20app%20was%20%22damaged.%22%0A-%20Recovery%20required%20manual%20intervention%20in%20Task%20Manager%3B%20there%20was%20no%20in-app%20recovery%20path.%0A%0AAsk%0A%0A-%20Investigate%20why%20a%20%60bash.exe%60%20hang%20cascades%20into%20killing%20the%20Cowork%20VM%20Windows%20service.%0A-%20Make%20the%20service's%20Windows-service%20%22Recovery%22%20(auto-restart)%20actually%20work%20-%20the%20log%20shows%20%60Warning%3A%20failed%20to%20open%20service%20for%20recovery%20config%3A%20Acceso%20denegado.%60%20(Access%20denied)%2C%20suggesting%20recovery%20actions%20aren't%20configured%2Fpermitted.%0A-%20Surface%20a%20clearer%20in-app%20error%20instead%20of%20leaving%20the%20user%20to%20interpret%20a%20generic%20Windows%20%22app%20is%20corrupted%22%20dialog.%0A