How to Use the Google Drive “Diagnostic Mode”

Google Drive for Desktop includes a hidden Diagnostic Mode designed to help administrators and power users troubleshoot complex sync stalls, silent crashes, authentication loops, and filesystem mount errors. When standard error dialogs fail to explain why synchronization is blocked, Diagnostic Mode allows you to generate diagnostic packages, enable verbose debug logging, simulate crash states, and inspect low-level client-server transactions in real time.

Fast Fix

To access Diagnostic Mode on Windows, hold down the Shift key and click the Google Drive icon in the system tray, then click the Settings gear and select Diagnostic Mode (or press Ctrl + Shift + D inside Preferences). On macOS, hold Option, click the menu bar icon, click Settings, and select Diagnostic Mode.

Diagnostic Snapshot

Parameter	Specification
Supported Platforms	Google Drive for Desktop (Windows 10/11, macOS 12+)
Primary Use Cases	Intermittent sync drops, unhandled exceptions, proxy negotiation hangs, deep inspection of local SQLite database state
Key Artifact Generated	drive_fs.log, diagnostic_report.zip, and active process memory dumps
Admin Access Required	No for accessing user diagnostic menus; Yes for extracting system-wide proxy traces and registry debugging flags

How to Access and Use Diagnostic Tools

Method 1: Accessing the GUI Diagnostic Menu

On Windows:

1. Locate the Google Drive icon in the system tray (bottom-right taskbar).
2. Hold down the Shift key on your keyboard and left-click the Drive icon.
3. While still holding Shift, click the Settings gear icon.
4. You will see new hidden options in the dropdown:
   • Diagnostic Mode
   • Generate Diagnostic Report
   • Open Logs Folder
5. Alternatively, open Preferences, press Ctrl + Shift + D, and the Diagnostic Mode overlay will appear.

On macOS:

1. Locate the Google Drive icon in the top menu bar.
2. Hold down the Option (or Alt) key and click the Drive icon.
3. Click the Settings gear icon.
4. Select Diagnostic Mode or choose Generate Diagnostic Report.

System Tray / Menu Bar Icon
└── [Hold Shift / Option] + Click Icon
    └── Settings (Gear)
        ├── Generate Diagnostic Report
        ├── Open Logs Folder
        └── Diagnostic Mode (Debug Overlays)

Method 2: Enabling Verbose Debug Logging via Registry or Command Line

If the application crashes too quickly to access the graphical menu, you can force verbose logging before startup.

On Windows (Registry):

1. Press Win + R, type regedit, and press Enter.
2. Navigate to HKEY_LOCAL_MACHINE\Software\Google\DriveFS (or create it).
3. Create a new String (REG_SZ) value named LogLevel.
4. Set its data to VERBOSE.
5. Restart Google Drive.

On macOS (Terminal):

1. Open Terminal.
2. Run:Bash defaults write com.google.drivefs.settings LogLevel -string "VERBOSE"
3. Restart Google Drive.

Locating and Reading Local Diagnostic Logs

Once you reproduce the issue with verbose logging enabled, retrieve the generated log files:

• Windows Log Path: %LOCALAPPDATA%\Google\DriveFS\Logs
• macOS Log Path: ~/Library/Application Support/Google/DriveFS/Logs

Key Files to Inspect

• drive_fs.log: The primary operational log file. Contains real-time timestamps, cloud synchronization queues, mount point operations, and error traces.
• drive_fs_startup.log: Captures driver registration (WinFsp), authentication tokens, and virtual mount sequences during the first 10 seconds of boot.
• crash_dumps/: Contains .dmp minidumps generated during unhandled thread exceptions.

Hard Stops

• Disable Verbose Logging After Diagnosis: Do not leave LogLevel set to VERBOSE permanently. Verbose logging writes massive volumes of plain-text data to your storage drive continuously, which can cause local disk storage exhaustion over several weeks. If your drive runs low on space. Once your diagnostic investigation is complete, delete the LogLevel registry/defaults key or set it back to INFO.