How to Resolve “Disk Full” Errors with Plenty of Space

The error “Disk full” or “Not enough disk space” in Google Drive for Desktop appears when the client cannot write cached chunks or sync files, even though Windows File Explorer or macOS Finder shows tens or hundreds of gigabytes of free physical hard drive capacity. This false positive occurs because Google Drive for Desktop evaluates free space thresholds across multiple discrete locations: the host OS partition hosting the cache database, internal safety margin thresholds, or cloud account storage quotas rather than the primary disk’s raw total capacity.

Fast Fix

Quit Google Drive completely. Free up space on your primary boot drive (C:\ or macOS startup volume) where the hidden %LOCALAPPDATA%\Google\DriveFS cache folder resides, rather than your secondary or virtual storage volumes. If your boot drive has ample room, open the registry or terminal and lower the ContentCacheMinFreeDiskSpaceKbytes safety buffer threshold.

Diagnostic Snapshot

Parameter	Specification
Affected Applications	Google Drive for Desktop (Windows & macOS)
Primary Symptom	“Can’t sync: Disk full” notification or write failure when opening/saving files via the virtual drive
Root Conflict	Discrepancy between virtual drive capacity (G:\), cloud account quota, and physical boot drive hosting %LOCALAPPDATA%
Admin Access Required	No for cache relocation and manual file cleanup; Yes for modifying system-wide registry buffer policies

Forensic Decision Path

Use the following diagnostic flowchart to isolate which layer is triggering the “Disk full” block:

["Disk Full" Error Displayed]
  │
  ├─► Check Google Workspace Cloud Quota at drive.google.com/drive/quota:
  │     └─► Cloud storage is full / exceeded ──► Root cause: Cloud quota exhaustion (not local drive).
  │
  ├─► Check Primary OS Boot Volume (C:\ or macOS System Volume):
  │     ├─► Boot volume has < 10% or < 10–20 GB free space?
  │     │     └─► Root cause: Drive cache lives on C:\ by default. Move cache path or free C:\ drive space.
  │     │
  │     └─► Boot volume has ample space (> 50 GB free)?
  │           ├─► Check for NTFS volume quotas or localized folder compression limits.
  │           └─► Check registry key `ContentCacheMinFreeDiskSpaceKbytes` setting a strict hard stop.
  │
  └─► Attempting to sync a single file larger than remaining contiguous cache space?
        └─► Root cause: Drive for Desktop requires staging space equal to the total size of the streaming payload.

What This Means: System Mechanics

Google Drive for Desktop presents your cloud files through a virtual drive letter (such as G:\ on Windows) or a Finder File Provider location. While this virtual volume may visually report the total size of your Google Workspace storage pool, the application processes read and write actions through a physical local cache on your computer:

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

When you open, stream, or copy a file to the virtual drive:

1. Google Drive allocates local disk space on your primary boot drive to stage the file before uploading or rendering.
2. The client checks if writing the staged file will cause the host physical drive to breach the minimum free disk space threshold (configured by default to safeguard the OS from crashing).
3. If the host boot volume lacks enough contiguous free space to stage the file plus the safety buffer—or if your Google Workspace cloud quota is full—the client halts the operation with a “Disk full” error.

Common Causes

• Default Boot Drive Cache Placement: You may have installed software or stored large media on a secondary drive (D:\), but Google Drive’s DriveFS cache folder remains anchored to your nearly full C:\ drive.
• Exceeded Cloud Storage Quota: When your Google Workspace account hits its cloud storage limit, the desktop sync engine reports local write failures as disk allocation errors. If your cloud storage reporting appears inconsistent with actual files, see [INTERNAL LINK: S01C04.01 – Fix: Drive says “Storage Full” but I deleted everything].
• Aggressive Safety Buffer Thresholds: Google Drive enforces a minimum disk space reserve (often 10–20 GB) to prevent the OS from locking up. If the drive drops below this margin, all sync activity ceases immediately.
• Staged Sync File Size Mismatch: Copying an uncompressed 40 GB archive onto a virtual drive when the host physical drive only has 35 GB of free space will instantly trigger a “Disk full” error, even if you have 2 TB of cloud space available.
• Corrupted Cache Database: In rare instances, SQLite database index corruption within the cache folder miscalculates remaining allocations and blocks incoming write handles.

Common Misdiagnoses

• Misdiagnosis: “The virtual Google Drive (G:) partition needs to be expanded in Disk Management.”
  • Distinction: The G: volume is a virtual filesystem generated dynamically by WinFsp or the Mac File Provider API. It has no physical partition table in Disk Management and cannot be resized using partition tools.
• Misdiagnosis: “The file is locked or permissions are restricted.”
  • Distinction: Permission blocks return explicit “Access denied” alerts, not storage exhaustion errors.
• Misdiagnosis: “The desktop application requires a complete reinstallation.”
  • Distinction: Reinstalling the client without moving the cache or clearing the host boot drive will simply recreate the cache in the same full partition, reproducing the error immediately.

Resolution Steps

Step 1: Verify Google Workspace Cloud Quota

1. Open your web browser and navigate to https://drive.google.com/drive/quota.
2. Verify that your total storage usage is below the maximum allowed account threshold.
3. If your cloud quota is full, empty the Trash ([drive.google.com/drive/trash](<https://drive.google.com/drive/trash>)) and remove unnecessary large files in the cloud.

Step 2: Relocate the Local Content Cache to a Larger Drive

If your primary C:\ drive is low on space but you have a larger secondary partition (D:\ or external high-speed SSD):

1. Click the Google Drive icon in the system tray or menu bar.
2. Click the Settings gear > Preferences.
3. Click the inner Settings gear (top-right corner).
4. Scroll down to Local cached files directory.
5. Click Browse and select a folder on your drive with ample free space (e.g., D:\GoogleDriveCache).
6. Click Save and confirm the prompt to Restart now.

Google Drive Preferences
└── Settings (Gear Icon)
    └── Local cached files directory ──► Browse ──► D:\GoogleDriveCache ──► Save & Restart

Step 3: Rebuild and Safely Purge Stale Cache Data

If the local cache has accumulated obsolete file blocks:

1. Quit Google Drive (Settings gear > Quit).
2. Open Windows Run (Win + R), type %LOCALAPPDATA%\Google, and press Enter.
3. Rename the DriveFS directory to DriveFS_Old.
4. Relaunch Google Drive from the Start menu. The client will rebuild a clean database.

Step 4: Adjust Safety Buffer Thresholds (Windows Registry)

If your primary disk has enough space (e.g., 8 GB free) for your working tasks but Google Drive halts due to conservative defaults:

1. Press Win + R, type regedit, and press Enter.
2. Navigate to HKEY_LOCAL_MACHINE\Software\Google\DriveFS (create the key if missing).
3. Right-click in the right pane, select New > DWORD (32-bit) Value, and name it ContentCacheMinFreeDiskSpaceKbytes.
4. Set the value to a lower safety floor in kilobytes (for example, 2097152 for 2 GB).
5. Restart Google Drive for Desktop.

Admin & Advanced Checks

• Multi-User / VDI Storage Allocation: In non-persistent VDI environments (Citrix, VMware Horizon, AVD), user profile disks (such as FSLogix containers) often have strict default sizes (e.g., 30 GB). Ensure FSLogix container sizes accommodate active local caching, or redirect the cache path to persistent scratch disks.
• Enforce Central Cache Limits: Administrators can prevent users from filling endpoints by deploying the ContentCacheMaxKbytes registry policy via Group Policy or Intune, setting an enforced ceiling on how much disk space Drive for Desktop is allowed to consume.

Hard Stops

• Boot Drive Exhaustion Below 1 GB: If the physical operating system drive drops below 1 GB of free space, immediately stop sync tasks and avoid force-clearing registry thresholds. Operating systems require working disk space for virtual memory paging and system stability; forcing Drive to write under extreme storage depletion can lead to OS crashes or filesystem corruption.