A Google Drive desktop Can’t locate folder message often needs a folder-location check, not a reinstall. If the local sync folder was renamed or moved, use the app’s supported Locate action and confirm its contents before reconnecting it.
Find the actual local folder
Record the path Drive expected and inspect where the folder now exists. Check whether a disk or removable device is disconnected. Distinguish the original folder from an empty replacement or an old inactive mirror.
Preserve local changes and avoid creating another same-name folder merely to satisfy the message. An empty new folder does not prove that the original synchronized data is safe.
Use the supported reconnection
Google’s troubleshooting instructions describe selecting Locate in the notification, choosing the renamed or moved folder, and allowing Drive to reconnect. Confirm that the selected folder belongs to the intended account and workflow.
If the folder was actually deleted or you no longer want it synchronized, inspect the current official stop-syncing instructions instead. Do not pretend a deleted directory can be located by choosing an unrelated one.
Verify after reconnection
Allow time for synchronization and inspect errors. Compare important local contents with the correct cloud account, particularly if changes occurred while the folder was disconnected. A mode transition can leave an old mirror that no longer syncs, so check the active configuration. Keep source material until the resulting relationship is clear. On newer macOS File Provider setups, the streaming location is controlled by macOS; manually moving that internal location is not the same as locating an ordinary user-chosen mirror folder.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.