Fix Google Drive Error: File Ownership Error

Encountering a File Ownership Error or “Cannot transfer ownership of this file” in Google Drive occurs when you attempt to reassign the primary owner of a file or folder but the action is blocked by organization policies, domain mismatches, or target folder structures.

This guide outlines Google’s ownership rules, details how to bypass cross-domain transfers, and explains how to force permission sync on desktop clients.

What Causes Google Drive File Ownership Errors?

Google enforces strict boundaries around who can own data:

1. Cross-Domain Ownership Blocks (Highly Common): You cannot transfer ownership of a file from a corporate Google Workspace account (user@company.com) to a personal account (user@gmail.com) or a different organization.
2. Target User Sharing Status: You cannot transfer ownership to a user unless they have already been added to the file’s share list and accepted editor permissions.
3. Shared Drive Rules: Files located inside a Shared Drive are owned by the organization/Shared Drive entity itself, not by individuals. You cannot transfer individual ownership of these files.
4. Desktop Sync Cached Permissions: The desktop file system driver (DriveFS) uses cached security descriptors that mismatch the web interface, blocking file movement.

Detailed Steps to Resolve File Ownership Errors

Follow these steps to re-allocate file ownership.

Step 1: Add User as Editor Before Transferring Ownership

You cannot make someone an owner unless they are already an active editor on the file.

1. Right-click the file in Google Drive and select Share.
2. Type the recipient’s email address, set their role to Editor, and click Send.
3. Once they are added, open the Share menu again.
4. Click the dropdown next to the recipient’s name and select Transfer Ownership.
5. Click Send Invitation. The recipient must accept the invitation to complete the transfer.

Step 2: Bypass Cross-Domain Ownership Transfers (The Copy Workaround)

If the transfer is blocked because the target user is outside your organization domain, the target user must duplicate the files to establish ownership.

Web Workaround:

1. Share the folder/file containing the files with the external target user as an Editor.
2. The external user must log into their Google Drive, go to Shared with me, and select the shared files.
3. The external user must right-click the files and select Make a copy.
4. The copied files will belong to the external user’s account. The original owner can then safely delete their source files.

CLI Workaround (Using rclone for bulk transfers):

If you have a massive directory structure, the external user can pull the files using rclone to automatically generate new file copies owned by their account:

• Windows Command Prompt:

  rclone copy "SourceRemote:SharedFolder" "TargetRemote:MyLocalCopy" --drive-shared-with-me

• macOS Terminal:

  rclone copy "SourceRemote:SharedFolder" "TargetRemote:MyLocalCopy" --drive-shared-with-me

Step 3: Resolve Shared Drive Ownership Constraints

If you need to move files into a Shared Drive:

• Moving Files In: You must have Editor access to the file and be a Contributor or Manager of the target Shared Drive. Once moved, the file’s owner changes from your personal account to the Shared Drive.
• Moving Folders In: Moving folders into a Shared Drive is restricted to Workspace Administrators. Regular users must create folders directly inside the Shared Drive and move files individually.

Step 4: Flush Cached Permissions on Google Drive for Desktop

If your desktop client is throwing permission or ownership errors when modifying files, reset the local permissions database.

:: Kill the desktop sync client processes
taskkill /F /IM GoogleDriveFS.exe

:: Clear the local SQLite metadata caches that store file descriptors
cd /d "%USERPROFILE%\AppData\Local\Google\DriveFS"
del /F /S /Q *metadata*

:: Restart Google Drive
start "" "C:\Program Files\Google\Drive File Stream\bin\GoogleDriveFS.exe"

# Force quit the Google Drive app
killall "Google Drive"

# Delete the permission metadata files
find ~/Library/Application\ Support/Google/DriveFS -name "*metadata*" -delete

# Restart Google Drive
open -a "Google Drive"

Summary Checklist

• Share the file as an Editor first before attempting to transfer ownership.
• For cross-domain transfers, have the recipient Make a copy of the file to claim ownership.
• If migrating files to a Shared Drive, verify you have the Manager or Contributor role.
• Remember that whole folders cannot be moved into Shared Drives by non-admin accounts.
• Clear metadata caches on desktop clients using the scripts above if sync permission errors persist.