If you are seeing this on your device, record one reproducible example. Drive for desktop shows Preparing to sync indefinitely after a large folder was moved locally. The comparison below helps identify whether the issue is local, account-specific or service-side.
Symptoms and boundaries
Observed behavior: Drive for desktop shows Preparing to sync indefinitely after a large folder was moved locally. Record the exact app or device build, affected account or file, and the first time this happened. A screenshot of the error state or a short log excerpt is useful when it contains no sensitive information.
Control comparison: Check Drive’s activity panel, local disk free space and whether a newly created small file syncs normally. Keep the account, file, network and hardware unchanged wherever the comparison permits. If the control works, the difference between the two paths is your most useful clue.
- Does this reproduce every attempt, or only after a reboot, resume, update or account switch?
- Can the affected action complete through another supported route without changing the original data?
- Is the problem limited to one file, one profile, one device or every user of the service?
Diagnostic clues
A Google Drive item can be visible but not writable. Check role and ownership of the exact shared folder before considering an account-wide issue.
Focused investigation: Compare mirrored vs streamed file modes, path length and inaccessible moved items; isolate a locked database or unauthorized directory. Treat this as a way to test a cause, not proof that the cause has already been established.
| What you observe | What to check next |
|---|---|
| The controlled comparison succeeds | Compare the settings, permissions or content specific to the failing path. |
| Both original and control fail | Check the shared device, account, network or service dependencies before changing the application. |
| It works only after a fresh start | Inspect background processes, cache state, session expiry or a reconnect sequence. |
Safeguards before repair
Verify the active account and sharing scope before changing cloud settings. Use a harmless test file or message rather than a sensitive document.
Save the current configuration, note its values, and use a harmless test item where possible. Avoid combining this repair with unrelated updates. In particular, Do not uninstall Drive or delete its cache before confirming all local unsynced files are backed up.
Choose Beginner for reversible checks or Advanced for targeted diagnostics. Drive for desktop shows Preparing to sync indefinitely after a large folder was moved locally. Confirm the affected product, user account, file or device, then record the time and a screenshot without private account information. This is the baseline; do not change settings yet. Check Drive's activity panel, local disk free space and whether a newly created small file syncs normally. Perform the comparison with one harmless test item. Write down both the successful and failing paths so that the next action targets the actual difference. Pause competing file operations, wait for the initial inventory to finish and restart Drive without deleting the local folder. Change one setting or workflow at a time. Preserve an easy route back to the previous configuration and allow any synchronization, indexing or activation step to complete before retesting. The moved folder finishes indexing and a new text file appears in the expected cloud location. Test the original failing situation rather than an unrelated feature. If it passes, repeat after one normal restart or reconnect; if it fails, restore temporary diagnostic settings and use the Advanced track. Compare mirrored vs streamed file modes, path length and inaccessible moved items; isolate a locked database or unauthorized directory. Note which component provides the first observable failure. Avoid logging secrets, account recovery keys, authentication cookies or the contents of private documents. Use the least invasive diagnostic appropriate to Google Drive for Desktop Stays on Preparing to Sync After a Folder Move. Compare the result with the supported control path: Check Drive's activity panel, local disk free space and whether a newly created small file syncs normally. If there are policy restrictions, involve the administrator rather than bypassing them. Pause competing file operations, wait for the initial inventory to finish and restart Drive without deleting the local folder. Tie any configuration change to a specific observation. If the result is ambiguous, collect additional evidence instead of layering new resets onto an unexplained problem. The moved folder finishes indexing and a new text file appears in the expected cloud location. If this does not pass, reverse temporary changes. Safety limit: Do not uninstall Drive or delete its cache before confirming all local unsynced files are backed up. Provide support with the error text, environment version and reproducible comparison; do not submit private tokens or user data.Step-by-Step Troubleshooting
Capture the exact symptom
Use a supported comparison
Apply the narrow repair
Test the original workflow
Establish the failing boundary
Collect focused diagnostics
Validate the likely cause
Restore and escalate safely
Solution Checklist
Pitfalls
- Do not uninstall Drive or delete its cache before confirming all local unsynced files are backed up.
- Do not treat a successful unrelated feature as evidence that the failing action is fixed; run the original comparison again.
- Do not erase logs, synced files or working credentials before you know which layer was responsible.
Test the result
Pass condition: The moved folder finishes indexing and a new text file appears in the expected cloud location. Repeat the same test using the original account, document, peripheral or network path; a passing test on a substitute is useful evidence but is not the final result.
For intermittent problems, repeat the operation after a normal application restart and again after the state change that originally triggered it, such as reconnecting a dock, signing in, or resuming from sleep. Check for new errors in the same location as the original symptom.
Escalation and rollback
If the controlled test still fails, return temporary settings to their earlier state and collect the minimum relevant evidence. Next diagnostic: Compare mirrored vs streamed file modes, path length and inaccessible moved items; isolate a locked database or unauthorized directory. Note exactly which comparison failed and what changed after the attempted repair.
For managed devices, privacy-sensitive files, damaged storage or account security concerns, escalate to the responsible administrator or vendor with timestamps and non-sensitive logs rather than attempting a broad reset.
Prevent the same failure
Use least-privilege sharing, stable time zones and a small test change when migrating accounts or modifying synchronization rules.
When the system is stable, record the specific working change: Pause competing file operations, wait for the initial inventory to finish and restart Drive without deleting the local folder. Keep this as a reversible troubleshooting record so a later upgrade does not require repeating unrelated repair attempts.
Official Resources
For product-specific procedures and limitations, consult Google Drive Help — Fix problems in Drive for desktop.