Google Drive for Desktop Stuck on “Checking for updates”

When Google Drive for Desktop gets stuck on “Checking for updates,” the application cannot complete its startup handshake. This loop halts file synchronization, prevents new edits from uploading, and can freeze the local virtual drive mount. It typically indicates an interrupted update download, a corrupted local metadata cache, or network inspection blocking Google’s update servers.

Fast Fix

Quit Google Drive completely from the system tray or menu bar (Settings gear > Quit). Download the latest installer directly from Google (GoogleDriveSetup.exe on Windows or GoogleDrive.dmg on macOS) and run it over your current installation. An in-place reinstall updates the binaries and clears the update lock without deleting your local offline files or unlinking your account.

Diagnostic Snapshot

Parameter	Specification
Affected Applications	Google Drive for Desktop (Windows & macOS)
Primary Symptom	Tray icon displays animated sync/loading wheels indefinitely; status menu remains frozen at “Checking for updates”
Root Cause	Stalled Google Update service, corrupted DriveFS SQLite database, HTTPS deep packet inspection blocking update endpoints, or broken update lock files
Admin Access Required	No for manual cache resets and standard app restarts; Yes if modifying enterprise update policies or installing system-level packages

Forensic Decision Path

Use the following flowchart to isolate why the update check is hanging:

[Drive Stuck on “Checking for updates”]
│
├─► Can you open and sign in to drive.google.com in your web browser?
│ ├─► No ──► General network outage or corporate firewall block. See [INTERNAL LINK: S01C01.23 – Fix: “Can’t reach drive.google.com” on Corporate Networks].
│ └─► Yes ──► Network connection is live; issue is local client or update endpoint filtering.
│
├─► Is the Google Update Service / Keystone agent running and responsive?
│ ├─► Stalled / Disabled ──► Re-enable service in services.msc (Windows) or refresh LaunchAgents (macOS).
│ └─► Active / Running ────► Proceed to inspect the local DriveFS cache and lock files.
│
├─► Does the client throw an explicit version error after several minutes?
│ └─► See Troubleshooting “The version of Google Drive… is too old”.
│
└─► Does the loop persist across multiple reboots?
└─► Corrupted local application database or lingering lock files in %LOCALAPPDATA%\Google\DriveFS.

What This Means: System Mechanics

Whenever Google Drive for Desktop launches, it runs a two-stage initialization process before it begins syncing user data:

1. The Software Update Handshake: The client queries Google’s update servers (using GoogleUpdate.exe on Windows or the Omaha/Keystone framework on macOS) to check if the local executable is deprecated or if a patch is available.
2. Local Metadata Verification: The local sync engine opens the SQLite databases in your user profile to index changes between your local virtual filesystem and the cloud.

If the Google Update daemon cannot establish a socket connection to update.googleapis.com or dl.google.com, the client waits for a network response timeout. If a proxy drops the packets silently instead of rejecting them, the application can remain trapped in a timeout retry loop.

Similarly, if an abrupt shutdown left a temporary .lock file inside the local cache, the application will freeze while waiting for the lock to clear.

Common Causes

• Blocked Update Endpoints: Corporate firewalls, SSL inspection proxies, or third-party endpoint security software blocking traffic to tools.google.com, dl.google.com, or update.googleapis.com.
• Corrupted Local Application Cache: Damaged records in the local DriveFS database prevent the client from comparing local state against cloud timestamps.
• Hung Background Processes: A background updater process from a previous session remained running in an invalid state.
• Proxy Authentication Demands: If the network requires NTLM or Kerberos proxy authentication that the background update service cannot fulfill.
• Circular Reparse Points / Symlink Loops: An unresolvable local directory structure stalling the initial index scan.

Common Misdiagnoses

• Misdiagnosis: “The user’s Google Workspace account is suspended or out of storage.”
  • Distinction: Account suspension or quota limits return specific “Storage full” or “Account disconnected” notifications; they do not cause the software update check to freeze.
• Misdiagnosis: “The virtual drive letter has a conflict.”
  • Distinction: Drive letter collisions occur after initialization and display an explicit mount warning.
• Misdiagnosis: “The virtual drive has disappeared from File Explorer permanently.”
  • Distinction: While the drive will not show up while stuck in the update check, the missing drive is a symptom of the frozen startup phase, not a broken shell driver.

Resolution Steps

Step 1: Force Terminate and Relaunch

Lingering background processes frequently cause update locks:

1. Windows: Press Ctrl + Shift + Esc to open Task Manager. Under the Details tab, locate and end all instances of GoogleDriveFS.exe and GoogleUpdate.exe.
2. macOS: Open Activity Monitor, search for Google Drive, and force-quit all matching processes.
3. Relaunch Google Drive and check if the update cycle completes.

Step 2: Perform an In-Place Binary Reinstall

Running the installer over your current build replaces corrupted update scripts without wiping your local sync state:

1. Download the latest installer from Google’s official Workspace portal.
2. Run the installer (GoogleDriveSetup.exe or GoogleDrive.dmg).
3. Allow the installer to overwrite existing binaries.

Step 3: Rebuild the Local Cache Directory

If a corrupt SQLite database or stale lock file is freezing the client during the startup scan:

1. Quit Google Drive completely.
2. Open the file explorer to your local application data path:
   • Windows: Press Win + R, paste %LOCALAPPDATA%\Google, and press Enter.
   • macOS: In Finder, press Cmd + Shift + G, paste ~/Library/Application Support/Google, and press Enter.
3. Rename the DriveFS folder to DriveFS_Old.
4. Relaunch Google Drive. The app will create a clean configuration directory, re-authenticate your session, and stream metadata fresh from the cloud.

Local Application Path (%LOCALAPPDATA%\Google)
└── Rename: DriveFS ──► DriveFS_Old ──► Relaunch Google Drive (Generates fresh DriveFS)

Step 4: Verify Windows Firewall and Proxy Rules

Ensure local firewalls allow outbound Google Drive update communication:

1. Open Windows Defender Firewall or your third-party firewall console.
2. Verify that outbound connections for %ProgramFiles%\Google\Drive File Stream\[version]\GoogleDriveFS.exe and GoogleUpdate.exe are permitted across ports 80 and 443.

Admin & Advanced Checks

• Inspect Client Diagnostic Logs: Administrators can diagnose the exact socket or thread where the check stalls. Launch Drive in diagnostic mode to capture real-time execution logs.
• Group Policy Auto-Update Configuration: If your organization uses GPOs to govern updates, ensure the Google Update policy is not configured with contradictory rules:
  • Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update
  • Verify DisableAutoUpdateChecksCheckboxValue is set to 0 and UpdateDefault is not set to 0 (disabled).
• Verify TLS / SSL Inspection Exclusions: Ensure network appliances (such as Zscaler, Palo Alto, or Fortinet) exclude .google.com, .googleapis.com, and .gstatic.com from SSL decryption, as broken certificate chains during client handshakes will cause silent background connection timeouts.

Hard Stops

• Unsynced Offline Changes with Database Corruption: If you have files stored exclusively in local offline mode that have not synced to the cloud, do not delete the DriveFS folder. Renaming the folder preserves your data in DriveFS_Old\content_cache.