A Microsoft file hosting and synchronization service.
Use OneDrive’s error details and then narrow down by common sync blockers.
- Check OneDrive’s action center
- Select the OneDrive cloud icon in the notification area.
- In the panel that opens, look for any files listed with errors or warnings. OneDrive often shows the exact files it is trying to upload and why they fail (name restrictions, size, permissions, etc.).
- Look for files that never finish syncing
Continuous “uploading” usually means one or more files hit a restriction or limitation:
- Too many items in a folder
- File too large
- Invalid characters in the name
- Path too long
- Broken links inside Office files
- Use the “move out, sync, move back” method to isolate bad files
- Pause syncing from the OneDrive menu.
- In File Explorer, move a subset of files (for example, half of the suspected folder) out of the OneDrive folder to a temporary location (like Desktop).
- Resume syncing and watch the OneDrive icon:
- If the upload count drops or completes, the problematic files are likely in the group that was moved out.
- If it still hangs, repeat with a different subset until the problematic group is isolated.
- Once narrowed down, move files back in smaller batches until the exact files that cause the stall are identified.
- Check for hidden or temporary files
Some hidden or temporary files can show as “syncing” indefinitely:
- Enable viewing hidden files in File Explorer.
- In the OneDrive folder, remove hidden or temporary files that are not needed.
- For Office files, close all Office apps and clear the Office document cache as described in the context, then try syncing again.
- Verify there is enough local disk space Lack of local disk space can prevent OneDrive from finishing uploads. Ensure there is sufficient free space on the drive hosting the OneDrive folder.
- If still stuck, repair or re‑establish sync If the same 93 files remain blocked after checking the above, stop syncing the affected library/folder and set it up again so OneDrive creates a fresh local folder, then copy content into it in batches to see which files fail.
References: