Google Drive Sync Stuck on 'Processing Changes' — Real Fix

You open Google Drive for desktop and see that spinning circle next to 'Processing changes…' It's been like that for an hour. Or a day. Your files won't sync, and restarting the app does nothing.

What's actually happening here is Google Drive's local cache — a database file called drive_fs.db — got corrupted. This file tracks which files you have locally and what's changed. When it breaks, the app can't figure out what to process, so it just spins forever. This usually happens after a forced shutdown, a full hard drive, or a bad network disconnect.

The fix is simple: delete that database file and let Google Drive rebuild it. Here's how.

What This Fix Does

You're not losing any files. drive_fs.db is just a local index. Google Drive will re-scan your cloud files and rebuild it fresh. That takes 2-5 minutes on a normal account.

Step-by-Step Fix

Quit Google Drive completely. Right-click the Drive icon in your system tray (Windows) or menu bar (macOS) and select 'Quit'. Wait 10 seconds. Make sure the process isn't running in Task Manager or Activity Monitor. If it shows up, end it manually.
Open the cache folder. The path depends on your OS:
Windows 10/11:
```
%LOCALAPPDATA%\Google\DriveFS
```
macOS (Ventura, Sonoma, Sequoia):
```
~/Library/Application Support/Google/DriveFS
```
Just paste that into File Explorer (Windows) or Finder > Go > Go to Folder (macOS).
Find and delete the right file. Inside the DriveFS folder, you'll see a subfolder with a long random name (like f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5). Open that. Look for a file called drive_fs.db. Delete it. Don't delete anything else — especially not any .sqlite files or folders named Cache or Logs.
Restart Google Drive. Launch the app from your Start menu or Applications folder. It will show 'Setting up…' for a minute, then 'Syncing…'.
Wait 5 minutes. Your files will start syncing again. If you have a huge Drive (500+ GB), it might take 10 minutes max.

Why Step 3 Works

The drive_fs.db file is a SQLite database. Google Drive uses it to match local file versions with cloud ones. When it gets corrupted — say from a power loss while the app was writing to it — the app can't parse it, so it sits in a loop trying. Deleting it forces a clean rebuild from Google's servers. The reason you don't delete the whole folder is that the Cache folder inside holds thumbnail previews and temporary download data. Deleting that would make the app re-download everything, which takes way longer.

Check These If It Still Fails

Is your hard drive full? Google Drive needs at least 500 MB free to rebuild the cache. Free up space if needed.
Are you offline? Check your network. Google Drive won't process changes without internet. Run a ping test: ping google.com in the terminal. If it fails, fix your connection first.
Is the app updated? Go to Google Drive settings > About. Version 70.0 or newer works best. Old versions (below 60) have a known bug where the cache corrupts more often. Update from here for Windows or here for macOS.
Did you delete the wrong folder? If you deleted the whole DriveFS folder, Google Drive will treat your computer as a new device and re-download everything. That's not broken, just slow. Let it finish.
Are you using Windows with BitLocker? Sometimes BitLocker encrypts the cache while the app is writing, causing corruption. Pause BitLocker temporarily, apply the fix, then re-enable it.

I've seen this issue on Windows 11 with 64GB drives and on macOS Ventura with 1TB accounts. The fix is the same every time. The real solution is that one file. Skip reinstalling Google Drive — that just wastes time.