Fixing “Can’t sync [Filename]: Access denied” Local Errors

The error “Can’t sync [Filename]: Access denied” occurs when Google Drive for Desktop is blocked from reading, modifying, or uploading a specific file on your computer. This error halts synchronization for the affected item. It indicates an operating system-level lock, such as another application holding the file open, restrictive local NTFS or macOS file permissions, or security software blocking read access, rather than a cloud account suspension.

Fast Fix

Close any application (such as Excel, Word, or Adobe Acrobat) currently using the file. If the file is already closed, check local permissions: right-click the file or folder, select Properties > Security, and verify your user account has Full control or Modify access. Relaunch Google Drive for Desktop to retry the sync.

Diagnostic Snapshot

Parameter	Specification
Affected Applications	Google Drive for Desktop (Windows & macOS)
Primary Symptom	Sync error banner stating “Can’t sync [Filename]: Access denied” with a red warning badge
Failure Layer	Local Operating System (NTFS permissions, POSIX permissions, file handle locks, Antivirus/DLP hooks)
Data Risk	Low to Moderate: Cloud version remains untouched, but local edits will not upload until the lock is released
Admin Access Required	No for personal file locks; Yes if modifying inherited administrative folder permissions or endpoint security policies

Forensic Decision Path

Use the following diagnostic path to isolate why Google Drive is receiving an “Access Denied” response from your operating system:

[Error: "Can't sync [Filename]: Access denied"]
  │
  ├─► Is the file currently open in an application (Office, CAD, PDF reader)?
  │     ├─► Yes ──► Exclusive lock held by app. Save and close application.
  │     └─► No  ──► Check background processes in Task Manager / Activity Monitor.
  │
  ├─► Is the error affecting an Excel or Office file with hidden temporary lock files (~$filename)?
  │     └─► Yes ──► Temporary lock file conflict. See [Fixing "Excel file is locked for editing" in Shared Folders](<http://www.workspaceforensics.com/google-drive-manual/drive-sync-connection-errors/fix-excel-file-locked-editing-google-drive>).
  │
  ├─► Is this occurring on macOS?
  │     ├─► Check macOS System Settings > Privacy & Security > Full Disk Access.
  │     └─► If missing permissions ──► See [How to Grant Full Disk Access to Google Drive (macOS)](<http://www.workspaceforensics.com/google-drive-manual/drive-sync-connection-errors/google-drive-full-disk-access-macos>).
  │
  └─► Is the file located in a local folder with restricted Windows NTFS permissions?
        └─► Check File Properties > Security tab > Advance ownership and user ACLs.

What This Means: System Mechanics

Google Drive for Desktop synchronizes local changes by registering a filesystem hook through its background process (GoogleDriveFS.exe on Windows or Google Drive.app on macOS).

When you edit, save, or mirror a file:

1. Google Drive requests a read handle from the operating system to hash the file chunks and prepare the payload.
2. The operating system checks the Access Control List (ACL) of the user running the Google Drive process.
3. If the file is marked read-only, owned by another local account, or locked exclusively by another application via FILE_SHARE_READ restrictions, the OS denies the read request with an ERROR_ACCESS_DENIED (Windows) or EACCES / EPERM (macOS) system code.
4. Google Drive catches this failure and reports “Can’t sync [Filename]: Access denied” to prevent uploading partially written or corrupted data.

Common Causes

• Exclusive Application File Locks: Applications like Microsoft Excel, Word, AutoCAD, and specialized database engines place an exclusive lock on open files. While locked, background services cannot read the file stream.
• Insufficient Local NTFS Permissions (Windows): If a file was created by an elevated process or copied from another user profile, your current Windows user account may lack Read, Write, or Modify permissions.
• Missing macOS Full Disk Access: On macOS 12 and newer, strict sandboxing prevents Google Drive from accessing user directories (such as Documents, Desktop, or external volumes) unless explicitly granted permission.
• Security Software / DLP Interception: Endpoint Detection and Response (EDR), Antivirus, or Data Loss Prevention (DLP) tools can temporarily lock files during scanning or isolate them if flagged as suspicious.
• Read-Only File Attribute: Files marked with the Windows Read-only attribute or POSIX 444 flags prevent the sync engine from clearing temporary staging data.

Common Misdiagnoses

• Misdiagnosis: “The user lacks permissions on the Google Shared Drive in the cloud.”
  • Distinction: If you lack cloud permissions, Google Drive displays “You do not have permission to edit this file” or “insufficient permissions” generated by the Workspace API. An “Access denied” error referencing a specific local filename almost always indicates an OS-level file system block. If your issue is confirmed to be on the cloud side of a Shared Drive, see Fix: “Access Denied” on Shared Drive (Even for Managers).
• Misdiagnosis: “Google Drive cache is corrupted and needs full deletion.”
  • Distinction: Rebuilding the entire local cache is unnecessary when only one or two specific files report access denial. Wiping the cache while a file has unsynced changes can cause data loss. For safe cache handling procedures, see How to Clear Google Drive Local Cached Files Safely.

Resolution Steps

Step 1: Close Conflicting Applications and Background Processes

1. Save your progress and close any application using the affected file.
2. If the file appears closed, open Task Manager (Ctrl + Shift + Esc) on Windows or Activity Monitor on macOS.
3. Check for lingering background processes (such as EXCEL.EXE, WINWORD.EXE, or Acrobat.exe) and end them.
4. Click the Google Drive icon in the system tray/menu bar, go to the sync error list, and click Retry.

Step 2: Remove Read-Only Attributes (Windows)

1. In File Explorer, navigate to the affected file or folder.
2. Right-click the file and select Properties.
3. In the General tab, look at the Attributes section at the bottom.
4. Uncheck Read-only if it is selected.
5. Click Apply > OK.

Step 3: Take Ownership and Reset NTFS Permissions (Windows)

If your user profile lacks permission to access the local file:

1. Right-click the file or its parent folder and select Properties.
2. Switch to the Security tab and click Advanced.
3. Check the Owner listed at the top. If it is not your user account, click Change, type your Windows username, click Check Names, and select OK.
4. Check the box labeled “Replace owner on subcontainers and objects” and click Apply.
5. In the Permissions tab, verify that your user account has Full control or Modify. If not, click Add, select your principal account, check Full control, and click OK.
6. Check “Replace all child object permission entries with inheritable permission entries from this object” and click Apply.

File Properties > Security > Advanced
├── Owner: [Your User Account] (Check: Replace on subcontainers)
└── Permission Entries:
    └── [Your User Account] ──► Full Control ──► Applies to: This folder, subfolders, and files

Step 4: Grant Full Disk Access (macOS)

If running macOS and syncing local mirrored folders:

1. Open System Settings > Privacy & Security.
2. Select Full Disk Access.
3. Ensure the toggle next to Google Drive is enabled.
4. If prompted, restart Google Drive. For complete step-by-step guidance on macOS permissions, refer to How to Grant Full Disk Access to Google Drive (macOS).

Step 5: Check Antivirus Exclusions

If your antivirus or endpoint protection software locks active files during background scans:

1. Temporarily pause real-time protection to test if sync resumes immediately.
2. If sync succeeds while paused, add the Google Drive streaming cache path (%LOCALAPPDATA%\Google\DriveFS) and the virtual drive letter to your security software’s scan exclusion list.

Admin & Advanced Checks

• Handle Lock Inspection via Sysinternals: Administrators troubleshooting persistent locks can use Sysinternals Handle or Process Explorer:
  1. Open Process Explorer as Administrator.
  2. Press Ctrl + F and search for the exact filename.
  3. Identify the process ID (PID) holding the file handle and evaluate whether that process is essential or orphaned.
• Audit File System Filter Drivers: Security tools (such as DLP agents) install mini-filter drivers in the Windows storage stack. Run fltmc in an elevated Command Prompt to inspect active filter drivers if access errors occur across all users on a managed endpoint.
• General Error Reference: For a complete catalog of related sync engine status codes, consult The Master List of Google Drive for Desktop Error Codes.

Hard Stops

• Encrypted or Quarantined Files: If endpoint security software has quarantined the file due to a security alert or ransomware heuristic detection, do not force permission changes or modify ownership. Preserve the file in place and escalate to your organization’s security operations team for analysis.