How to Fix ‘Google Drive File Stream Has Encountered a Problem’

Working with cloud-mirrored files in Windows 11 only for the desktop sync client to suddenly crash with the notification: “Drive File Stream has encountered a problem and needs to stop” or “Google Drive for desktop needs to restart” interrupts collaborative file access. In the Google Drive for desktop client architecture, the software establishes a virtual local disk drive (typically mounted as G:) using a kernel-level file system driver (Dokan or WinFsp). When internal SQLite metadata databases become desynchronised, local content cache folders exceed disk quotas, or conflicting backup software locks virtual file handles, the GoogleDriveFS.exe supervisor process halts execution to prevent cloud file corruption. This guide walks you through purging corrupted local cache databases, fixing drive letter conflicts, and restoring Google Drive desktop sync.

Underlying Factors Behind Google Drive Desktop Crashes

The desktop client continuously streams remote Google Drive metadata while caching offline files locally. Common failure points include:

• Corrupted Local DriveFS Cache (DriveFS Directory): Damaged transaction journals in %LOCALAPPDATA%\Google\DriveFS preventing the client from reconciling local changes with Google Cloud storage.
• Virtual Drive Letter Collisions: Another connected network share, USB flash drive, or card reader seizing the drive letter (e.g. G:) designated for Google Drive.
• Outdated or Corrupted Virtual File System Drivers: The underlying WinFsp/Dokan file system bridge failing to initialise due to Windows Security kernel isolation rules.
• Conflicting Antivirus Real-Time File Locks: Security shields locking virtual sparse files while the sync client writes streaming metadata headers.
• Account OAuth Token Invalidation: Expired security tokens requiring complete re-authentication through your web browser.

Method 1: Clear the Corrupted DriveFS Cache Folder

Purging the local application cache forces Google Drive for desktop to download fresh metadata without affecting files safely stored in the cloud.

1. Right-click the Google Drive icon in the system tray and click the Settings (gear) icon, then select Quit.
2. Press Windows Key + R to open the Run dialogue box.
3. Type the following path and press Enter:

   %LOCALAPPDATA%Google

4. Locate the folder named DriveFS.
5. Rename this folder to DriveFS.old (or delete it if you do not have un-synced offline files stored locally).
6. Relaunch Google Drive from the Start Menu.
7. The application will create a fresh, clean DriveFS directory and synchronise your cloud files without errors.

Method 2: Change the Assigned Virtual Drive Letter

If another peripheral claimed Google Drive’s default mount letter, assigning a high, unused letter eliminates bus conflicts.

1. Click the Google Drive icon in your Windows taskbar.
2. Click the Settings (gear) icon and select Preferences.
3. Click the Settings (gear) icon again in the top-right corner of the Preferences window.
4. Scroll down to the Google Drive streaming location section.
5. Under Drive letter, click the dropdown menu and select an unused letter near the end of the alphabet, such as S: or X:.
6. Click Save and confirm restarting the application.

Method 3: Whitelist DriveFS in Windows Security / Antivirus

Aggressive heuristic scanning often mistakes Google Drive’s virtual file mounting for ransomware activity.

1. Open Windows Security by clicking the shield icon in the system tray.
2. Navigate to Virus & threat protection > Manage settings.
3. Scroll down to Exclusions and click Add or remove exclusions.
4. Click Add an exclusion and choose Folder.
5. Select your %LOCALAPPDATA%GoogleDriveFS folder.
6. Click Add an exclusion again, select Process, and type GoogleDriveFS.exe.

Method 4: Disconnect and Re-authenticate Your Account

Renewing your OAuth2 session re-establishes a clean cloud handshake if credentials have expired.

1. In Google Drive Preferences > Settings, locate your account at the top.
2. Click Disconnect account and confirm.
3. Restart your PC.
4. Launch Google Drive and click Sign in with browser to authenticate and regenerate fresh tokens.