If Google Drive for Desktop (File Stream) is not showing up in Windows File Explorer or Mac Finder, or crashes on startup: on Windows, kill the process in Task Manager, restart as Administrator, and ensure a unique virtual drive letter (e.g. G:) is assigned in Drive Preferences. On macOS (Sonoma/Sequoia), grant Full Disk Access in System Settings and check the Finder sidebar under Locations (Apple FileProvider migration). If syncing continues to fail, use SaveInDrive (https://saveindrive.com) to transfer and access files directly in the cloud without local desktop software.
Google Drive for Desktop (formerly known as Drive File Stream) is the official bridge that allows Windows and Mac users to stream cloud files locally without consuming hard drive space. It mounts your Google Drive as a virtual hard drive (such as G: on Windows or a CloudStorage volume in macOS Finder), making files feel like local documents.
However, after recent operating system updates (Windows 11 23H2/24H2 and macOS Sonoma/Sequoia), millions of users report that Google Drive for Desktop either:
- Disappears completely from File Explorer or Finder.
- Crashes silently a few seconds after launching with an error: "Google Drive encountered an error and has stopped."
- Stucks at "Syncing 1 of 4,000 files..." forever without making progress.
- Shows gray cloud icons with an exclamation mark on every file.
In this comprehensive troubleshooting guide, we walk through the exact steps to diagnose and repair Google Drive for Desktop on both Windows and Mac operating systems.
Fix 1: Windows Virtual Drive Letter Conflict (Windows 10/11)
On Windows, Google Drive mounts as a virtual partition, traditionally defaulting to the drive letter G:. If you insert a USB thumb drive, connect a network mapped drive, or have external hard drives that claim G: first, Google Drive fails silently without mounting:
Open Google Drive Preferences
Click the Google Drive icon in your Windows system tray (bottom-right near the clock). Click the Gear icon (Settings) and select Preferences.
Change the Virtual Drive Letter
In the Preferences window, click the Gear icon in the top-right corner to open advanced settings. Scroll down to Google Drive streaming location. Change the drive letter from G: to an unused letter toward the end of the alphabet, such as X:, Y:, or Z:. Click Save and restart your PC.
Fix 2: macOS FileProvider & Full Disk Access Permissions (macOS Sonoma & Sequoia)
Starting with macOS 12.3 and continuing through macOS Sonoma and Sequoia, Apple deprecated legacy kernel extensions (KEXTs) and forced all cloud storage providers to adopt Apple's native FileProvider API. As a result, Google Drive no longer mounts at /Volumes/GoogleDrive; it mounts under ~/Library/CloudStorage/GoogleDrive-user@gmail.com:
Check Finder Sidebar Locations
Open Finder. Look in the left sidebar under the Locations header. If Google Drive is not visible, go to Finder > Settings (Cmd+,) > Sidebar, and ensure that "Cloud Storage" or "Removable Media" is checked.
Grant Full Disk Access to Google Drive
Open System Settings > Privacy & Security > Full Disk Access. Locate Google Drive in the application list and toggle the switch to ON. You will be prompted to enter your Mac password and restart Google Drive.
Fix 3: Clear Corrupted Local Drive Cache Files
When Google Drive for Desktop crashes on startup or hangs during synchronization, the culprit is almost always a corrupted SQLite cache database stored locally on your SSD. Purging this temporary cache forces Drive to rebuild a fresh, clean index from Google's servers:
On Windows:
- Press
Ctrl + Shift + Escto open Task Manager. End all tasks named GoogleDriveFS.exe. - Press
Win + Rto open the Run dialog. Paste the following path and press Enter:%LOCALAPPDATA%\Google\DriveFS - Inside this folder, you will see subfolders named with long numerical IDs (your cached profiles). Select all files and folders inside
DriveFSand delete them. - Restart Google Drive from your Start Menu. Sign back in; Drive will re-index your files cleanly.
On macOS:
- Quit Google Drive from the top menu bar icon.
- Open Terminal (or Finder > Go > Go to Folder) and navigate to:
~/Library/Application Support/Google/DriveFS - Delete the contents of the
DriveFSdirectory. - Relaunch Google Drive.
If you only need Google Drive for Desktop to move files between cloud services (like transferring from Dropbox, MEGA, or TeraBox) or to download large archives without browser timeouts, you do not need desktop software at all! SaveInDrive handles cloud-to-cloud transfers directly server-to-server. Zero desktop software installed, zero virtual drive bugs, and zero local hard drive clutter.
Troubleshooting Matrix: Common Symptoms & Resolutions
| Observed Symptom | Underlying Cause | Verified Solution |
|---|---|---|
| Virtual Drive missing in Explorer | Drive letter conflict (G: already taken) | Change drive letter to X: or Z: in Preferences |
| Crashes immediately on startup | Corrupted local SQLite metadata cache | Delete contents of %LOCALAPPDATA%\Google\DriveFS |
| Missing in Mac Finder sidebar | macOS FileProvider migration & sidebar settings | Enable Cloud Storage in Finder Settings |
| Files show gray sync icon indefinitely | Antivirus firewall blocking background daemon | Add GoogleDriveFS.exe to Antivirus Exclusion list |
| "Error 403: Rate Limit Exceeded" | Exceeded 750GB daily desktop upload cap | Wait 24 hours or use SaveInDrive Service Accounts |
Frequently Asked Questions (FAQ)
Will clearing the DriveFS cache delete my files stored in Google Drive?
No! The DriveFS folder contains only cached thumbnails, temporary streaming chunks, and index pointers. Your actual files are safely stored in Google's cloud data centers and will automatically re-populate once the app restarts.
Should I choose "Stream files" or "Mirror files" in Google Drive for Desktop?
For most users, "Stream files" is strongly recommended. Streaming keeps all files stored strictly in the cloud and only downloads data temporarily into RAM when you open a file, saving your computer's SSD storage. "Mirror files" downloads a full duplicate copy of every cloud file to your local hard drive, which can quickly fill up smaller drives.
Why does Google Drive for Desktop consume high CPU and RAM on Mac?
When the app performs an initial sync or after a major macOS update, the background process (Google Drive File Stream) reads file hashes across tens of thousands of items. If CPU usage remains above 80% for several hours, clearing the local cache (Fix 3) stops the indexing loop.
Can I run Google Drive for Desktop with multiple Google accounts simultaneously?
Yes. Google Drive for Desktop supports connecting up to 4 Google accounts at once. Click the menu bar / system tray icon, click your profile picture, and select "Add another account". Each account mounts as its own distinct folder or drive letter.
Conclusion
Google Drive for Desktop issues can disrupt your workday, but fixing them is straightforward once you know whether the problem stems from drive letter conflicts, macOS permissions, or a corrupted local cache. Apply these fixes to restore seamless desktop synchronization, or switch to lightweight web solutions like SaveInDrive for hassle-free cloud transfers.
📚 Recommended In-Depth Cloud Guides:
- Google Drive Upload Failed or Server Error? 8 Proven Fixes (2026) — Google Drive (8 min read)
- How to Download Large Files When Google Drive Can't Scan for Viruses — Google Drive (8 min read)
- Google Drive 750 GB Daily Upload Limit: How It Works & How to Bypass It — Google Drive (11 min read)
- Why Is Google Drive Download So Slow? 9 Fixes to Get Maximum Speed (2026) — Google Drive (11 min read)
