Fix Google Drive Desktop Cannot Connect Error

Quick Answer

Clear your cached OAuth tokens by signing out of Drive for Desktop, deleting the tokens folder, then signing back in. Nine times out of ten, that's it.

Why This Happens

Google Drive Desktop (the app formerly known as Backup and Sync) holds onto authentication tokens in a local file. When those tokens get stale — usually after a password change, a forced logout from Google, or a network disruption that leaves a half-baked token — the app refuses to connect. Itll sit there with a spinning wheel or a red 'Cannot Connect' message. Restarting the app or your PC rarely fixes it because the bad token is still cached.

I've seen this on hundreds of machines. Windows 10, Windows 11, macOS Ventura, Sonoma — makes no difference. The pattern is the same: user changes their Google password, or Google rolls out a security policy update, and Drive stops dead. The fix is always the same.

Step-by-Step Fix

Quit Drive for Desktop completely. On Windows, right-click the Drive icon in the system tray and select 'Quit Drive for Desktop'. On Mac, right-click the menu bar icon and choose 'Quit'. Don't just close the window — the process stays running.
Delete the cached token folder.
On Windows:
```
%USERPROFILE%\AppData\Local\Google\DriveFS
```
Open File Explorer, paste that path, and delete everything inside the DriveFS folder. Don't delete the folder itself — just its contents.
On Mac:
```
~/Library/Application Support/Google/DriveFS
```
Open Finder, hit Cmd+Shift+G, paste that path, and delete everything inside the DriveFS folder.
Restart Drive for Desktop. Launch it from Start (Windows) or Applications (Mac). It'll ask you to sign in again. Do it with your Google account.
Wait a minute. It'll resync. If you have a lot of files, be patient — it's rebuilding the local database, not re-downloading everything. Give it 2–3 minutes.

Alternative Fixes If That Doesn't Work

If the main fix didn't do it (rare, but happens), try these in order:

1. Check for a VPN or proxy conflict

Google Drive hates VPNs that force traffic through a non-standard route. Turn off your VPN entirely, then restart Drive. If it connects, add an exception for drive.google.com and *.googleusercontent.com in your VPN config.

2. Reinstall Drive for Desktop

Uninstall it, reboot, then download the latest version from https://www.google.com/drive/download/. Install and sign in. This is nuclear, but it clears every possible cached piece of cruft.

3. Check your date and time

I know it sounds stupid, but I've had three calls this year alone where a PC with the wrong system time couldn't authenticate. Sync your clock with time.windows.com (Windows) or time.apple.com (Mac).

4. Use a different network

Switch from Wi-Fi to a mobile hotspot or a coffee shop's network. If it works there, your office firewall is blocking Google's sync servers. Talk to your network admin about whitelisting *.googleapis.com and accounts.google.com.

Prevention Tip

This won't happen nearly as often if you never change your Google password without first signing out of Drive for Desktop on every machine. Before you reset that password, open Drive, click the gear icon, choose 'Preferences', then 'Disconnect account'. Change the password, then connect again. That bypasses the whole stale-token mess.

Also — keep the app updated. Old versions of Drive for Desktop (pre-2022) had a bug where tokens expired after 28 days with no warning. Current versions handle that better, but they still choke on bad tokens.