[BUG] Claude Desktop crashes/restarts when Google Drive virtual drive unmounts during file-index scan

Status Open
Reported on v2.1.209
Maintainer reply None cached
Activity 0 comments · opened Jul 17, 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 periodically loses its current state and returns to the home screen with no warning or error dialog. This happens repeatedly (8 times in one overnight session) with no corresponding Windows crash-dump, WER report, or Application Error event — the process tree is simply killed and relaunched.

Root cause found in %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\main.log: the background file-index worker walks local drives, including Google Drive's virtual streaming drive (G:). When that virtual drive unmounts (Google Drive's own "keepalive close" event, a normal occurrence during brief network hiccups), the file-index worker is terminated by the OS instead of failing gracefully, and this cascades into a full app crash + relaunch.

What Should Happen?

The file-index worker should catch filesystem errors (e.g. device-removed/ENOENT) when a watched path disappears mid-scan, skip that volume, and retry later — without taking down the whole app. Ideally, virtual/network drives (Google Drive, OneDrive, Dropbox streaming mounts, mapped drives) shouldn't be indexed by default, or should be configurable.

Error Messages/Logs

02:01:05 [file-index] worker exited (1073807364); will refork on next request
02:01:05 [error] Sentry caught: { eventId: 'ded3ac8dfb0d410f9302de46685f6555', type: 'Unknown', value: "'Utility' process exited with 'killed'" }

Same second, Windows System event log (googledrivefs31931 provider):
02:01:05  Unmounting due to keepalive close.
02:01:05  Link deleted: "\DosDevices\G:"

App relaunches at 02:13:14 ("Starting app").

Second occurrence:
02:25:30  googledrivefs: Unmounting due to keepalive close. Link deleted "\DosDevices\G:"
02:26:12  [main.log] Starting app { appVersion: '1.22209.0', ... }

Steps to Reproduce

  1. Install Google Drive for desktop, set to "Stream files" mode (virtual drive, e.g. G:).
  2. Use Claude Desktop normally while the network connection is imperfect enough that Google Drive periodically drops and remounts its virtual drive (logged by Google Drive as "Unmounting due to keepalive close").
  3. When the unmount happens while Claude's file-index worker is walking/watching that drive, the worker is killed and the whole app crashes/restarts to the home screen.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.209 (Claude Code) (Claude Desktop app version: 1.22209.0.0)

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

  • Claude Desktop installed via direct MSIX sideload from claude.ai (SignatureKind: Developer, Publisher: Anthropic, PBC) — not Microsoft Store
  • Google Drive for desktop v128.0.0.0
  • Related but not duplicate issues: #12600 (crash reading file modified by external process), #67839 (Utility process crash on Windows, different root cause — extension install regression)

View original on GitHub ↗