Google Drive not syncing means files you expect to be available everywhere are stuck on one device. But “not syncing” can mean several different things that need different approaches — so the fastest fix depends on what’s actually happening. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The quickest check: click the Drive for Desktop icon in the system tray (bottom right). Does it show a spinning sync animation, an error icon, or a “paused” indicator? Each tells you something different.
- Spinning/syncing icon that never completes — A specific file is stuck or the queue is too large. Click the icon to see which file is causing the hold-up.
- Red error icon — Authentication failure or a specific file error. Click to see the error message.
- Pause icon — Sync was manually paused. Click → Resume sync. This is embarrassingly common.
- Icon shows “Up to date” but files are missing — Selective sync excluded the folder, or the files are Files On-Demand (placeholders, not downloaded).
Fix 1: Restart and Sign Out/In
Google Drive for Desktop runs as a background application that occasionally gets into a stuck state — particularly after a Windows sleep/wake cycle, after a network interruption, or after a Drive update that didn’t restart the service cleanly. Restarting it takes 30 seconds.
System tray → Drive for Desktop icon → gear icon → Quit Google Drive. Wait 15 seconds. Reopen Drive for Desktop from Start or from your Applications folder. Sign out and back in if restarting alone doesn’t work: gear icon → Preferences → your account → Sign out. After signing back in, Drive rechecks all files and queues any that fell out of sync during the outage.
Fix 2: Authentication and Account Issues
Drive stops syncing when the authentication token expires — which happens after a Google account password change, after a security policy update, or occasionally just as the token ages. The application shows a “sign in” or “authentication failed” error in the system tray.
Click the error notification → sign in again with your Google account. The fresh authentication establishes a new valid token and sync resumes. If your Google account uses two-factor authentication, complete the 2FA step during the sign-in. After re-authenticating, watch the sync queue for a few minutes — it should begin clearing files that accumulated during the authentication failure.
Fix 3: Check What’s Actually Queued
Drive for Desktop shows the sync queue in its popup. Click the tray icon → click on the sync status text to expand the queue view. This shows which files are currently being processed, which are waiting, and which have errors. A single large video file being uploaded at 5 Mbps will occupy the queue and prevent everything else from being marked as synced — not because anything is broken, but because the queue is working sequentially.
If a specific file shows “Error” next to it rather than progress: hover over it to see the specific error. Common file-level errors:
- File name contains unsupported characters — Characters like : * ? ” < > | can’t sync. Rename the file.
- File path too long — Windows has a 260-character maximum path. Move the file to a less deeply nested folder.
- File locked by another application — The file is open in another app. Close the app using it, or wait for Drive to retry.
- Insufficient storage — Your Google account is out of space. Check storage at drive.google.com/settings.
Fix 4: Selective Sync and Missing Folders
Drive for Desktop allows choosing which Google Drive folders sync to the local machine. If a folder visible in Google Drive on the web doesn’t appear in your local Drive folder, it may be excluded from selective sync rather than failing to sync.
Check: Drive for Desktop tray → gear → Preferences → Google Drive tab → My Drive syncing options → confirm the folders you need are included. If they’re not, add them and save. Also check whether the sync mode is “Mirror files” (keeps a local copy of everything) or “Stream files” (Files On-Demand — shows placeholders). Stream mode is why files might show in File Explorer but appear as cloud-only icons that need to be clicked to download.
Fix 5: Files On-Demand vs Downloaded Files
With Files On-Demand (Stream mode), Drive shows files as placeholders in File Explorer — you see the file name and can click it to download, but it’s not stored locally until accessed. This looks like “Drive is not syncing” when it’s actually working as designed.
Identify Files On-Demand files by the cloud icon next to them in File Explorer. A white cloud = online only (not downloaded). A green tick = available locally. To download files permanently: right-click a file or folder → Google Drive → Download now (or “Available offline” depending on Drive version). To switch the entire account to keeping everything local: Preferences → Google Drive → My Drive syncing options → change from Stream to Mirror. Mirror downloads everything to the local machine, which requires sufficient disk space.
Fix 6: Firewall and Network Blocking Drive
Google Drive for Desktop communicates over HTTPS (port 443) to Google’s servers. When a firewall — Windows Defender Firewall, a corporate proxy, or third-party security software — blocks these connections, Drive shows “Sync paused” or “Unable to connect” rather than a more descriptive error.
Test: temporarily disable Windows Firewall (Settings → Windows Security → Firewall → your active network → toggle off) and see if sync resumes. If it does, Drive needs to be added as an allowed app: “Allow an app through Windows Firewall” → Add Drive for Desktop.
On corporate networks: Drive sync may be intentionally blocked by IT policy. Check with IT whether Google Drive for Desktop is permitted on your network before spending time on technical fixes — some organisations block all personal cloud storage applications and this is a policy decision rather than a configuration error.
Fix 7: Reinstall Drive for Desktop
A corrupted Drive for Desktop installation causes sync failures that don’t respond to sign-out/sign-in or preference changes. Reinstalling clears the corrupted local state:
Settings → Apps → Google Drive → Uninstall. After uninstalling, check whether the application data folder at %localappdata%GoogleDriveFS remains — delete it if so. Download the latest Drive for Desktop installer from drive.google.com/drive/download. Install fresh and sign in. The first sync after reinstalling may take time as Drive verifies all files.
Google Workspace Admin Restrictions
For Google Workspace (work/school) accounts, some Drive sync features are controlled by the administrator. The Google Workspace admin can disable Drive for Desktop entirely for the organisation, restrict which file types sync, prevent sharing to personal accounts, or limit storage. If Drive sync fails specifically on a work or school account while personal Google accounts work fine, admin restrictions may be the cause.
Signs of admin restriction: Drive for Desktop installs and authenticates but sync doesn’t start, or specific actions (uploading certain file types, sharing outside the organisation) produce specific error messages. Contact your IT administrator to confirm what Google Workspace policies are in effect for your account.
Our guide on OneDrive not syncing covers parallel cloud sync issues — the authentication token expiry and selective sync configuration problems are nearly identical between Drive and OneDrive. For the Windows 260-character path length limitation affecting file names, our guide on Windows 11 file management covers enabling long path support via Group Policy. Google’s Drive support documentation covers the Drive for Desktop diagnostic tool and the sync error log location for detailed per-file error investigation beyond what the application popup shows.
Shared Drives Require Explicit Sync Setup
Shared Drives (previously called Team Drives) in Google Workspace behave differently from personal My Drive folders. They don’t automatically sync to local machines even when you have full access to them in the browser. Each Shared Drive must be explicitly added to Drive for Desktop’s sync configuration.
In Drive for Desktop Preferences → Google Drive, there’s a separate section for “Shared drives.” Any Shared Drive you want available locally needs to be checked in this list. If a team folder shows in the browser at drive.google.com but isn’t appearing locally on the machine, check this list first — the folder probably just wasn’t added to the desktop sync configuration. Checking it and saving starts sync immediately.
Drive Version Mismatches Between Devices
Google Drive for Desktop updates automatically, but machines that are rarely restarted or that have background updates blocked sometimes fall behind. A significantly outdated Drive for Desktop client occasionally causes sync issues with newer Google Drive APIs that the old version doesn’t support correctly.
Check the version: Drive for Desktop tray icon → gear → About Google Drive. The version number appears there. If it’s significantly behind the current release (check drive.google.com for the latest version number), the auto-update may have gotten stuck. Manually download and install the latest version from google.com/drive/download. The installer updates the existing installation and doesn’t require signing in again.
Conflicting Drive Installations
Google Drive has gone through several versions over the years: the original “Google Drive” sync client, then “Backup and Sync,” and now “Drive for Desktop” (also called “Google Drive for Desktop”). On machines that have been in use for several years and upgraded through these versions, remnants of older installations sometimes conflict with the current version.
Check for multiple Google Drive entries in Settings → Apps. If “Google Drive” (the old sync client) and “Google Drive for Desktop” both appear, they may conflict. Uninstall the older one and check whether sync improves. The migration from Backup and Sync to Drive for Desktop in 2021 was supposed to be seamless, but machines that were upgraded gradually sometimes retained both.
Bandwidth and Large Upload Queues
Drive for Desktop has a bandwidth throttle setting that controls how much of the network connection it uses for uploads and downloads. On connections where Drive was configured to limit bandwidth (useful when the connection was slow), that limit persists even as connection speeds improve, causing sync to appear stuck when it’s actually just slowly working through the queue.
Check: Drive for Desktop → gear → Preferences → Network settings → Bandwidth. If “Upload rate” or “Download rate” shows a specific limit rather than “Don’t limit,” remove the limit. Drive then uses the full available connection speed for sync operations. For home connections that are now faster than when Drive was first set up, this change can dramatically reduce sync completion time.
When Sync Gets Genuinely Stuck
If Drive shows syncing but the progress percentage or file count doesn’t change over many hours — not because a large file is uploading slowly, but because nothing is actually moving — the sync process has genuinely stalled. A complete disconnect and reconnect of the account is the most reliable reset:
Drive for Desktop → gear → Preferences → your Google account → Disconnect account. This unlinks the account from the local machine but doesn’t delete local files or cloud data. After disconnecting, reconnect: click “Add account” in Drive for Desktop preferences → sign in again. Drive performs a fresh inventory of all files and restarts sync from a clean state. Files that were queued but not synced will re-enter the queue and typically upload correctly this time.
This is more thorough than sign-out/sign-in (Fix 1) because it also clears the local sync database that tracks which files have been processed — useful when the database itself has become corrupted and is causing the stall.
Sync Activity Log for Detailed Error Investigation
Drive for Desktop maintains a detailed sync log that goes beyond what the system tray popup shows. The log records every file operation, every error, and every retry with timestamps and specific error codes. For persistent sync failures where the tray popup isn’t giving enough information, the log provides the detail needed to identify exactly which files are failing and why.
Find the log: Drive for Desktop → gear → Preferences → About → click “View sync diagnostics” or navigate to the log folder. On Windows, logs are typically at %localappdata%GoogleDriveFS in the logs subfolder. The log files are text files that open in Notepad. Look for lines containing “ERROR” or “FAILED” and note the file paths and error codes mentioned. Google’s support documentation cross-references these error codes to their specific causes, which often reveals that a specific file type or a specific folder has a configuration issue causing the repeated failures.
One practical note: Drive for Desktop and Google Chrome sometimes conflict when both are running on a machine that’s also signed into a Google account in the browser. Chrome has its own Google account session management, and when the Chrome account session and the Drive for Desktop account session fall out of sync — after a Chrome sign-out, for example — Drive occasionally shows authentication errors even though the account credentials haven’t changed. Signing out of the Google account in Chrome and signing back in, then restarting Drive for Desktop, often resolves this conflict without needing to go through the full disconnect-reconnect process. See also Google Drive Not Syncing on Windows 11 for a related case.
