OneDrive not syncing files on Windows
Find whether OneDrive sync is paused, using the wrong account, blocked by storage or one file, or failing between this PC and the cloud.
- Updated
- September 17, 2026
- Reading time
- 4 min read
- Windows support
- Windows 11 · Windows 10
Quick diagnosis
Start by comparing one specific file on this PC with the same file in the intended OneDrive account on the web. A local file, a cloud-only placeholder, and the uploaded copy are different states. Protect unsynced edits before unlinking accounts or following any reset instructions.
Symptoms
- Files remain pending or show a sync error
- A recent edit exists locally but not on the web
- OneDrive reports paused, signed out, or storage full
Likely causes
- Sync is paused, the client is not running, or a different account is selected
- Cloud quota, local disk space, or a file-specific restriction blocks progress
- Connectivity, account access, or organization policy prevents synchronization
Quick reversible checks
- Open the OneDrive notification-area icon and read the actual status or error.
- Confirm the account and the file’s full local path, including whether it is inside that account’s synced folder.
- Copy any important locally available unsynced edits to a separate safe location and verify the copy.
Compare the right account and file
Open OneDrive on the web through your usual trusted Microsoft sign-in route and verify the account identity. Compare a known filename, folder, and modification you made. A personal account and a work account can contain similarly named folders without sharing their contents.
If the file never existed in the synced location, a reset will not upload it from an unrelated folder. If the web copy is current but this PC is not, investigate the download/client side. If the local edit is newer, protect it before changes that could replace or discard it.
Resolve an explicit paused or signed-out state
If OneDrive is paused, use its Resume syncing control when the connection and power situation allow. If it is closed, launch OneDrive from Start. When sign-in is requested, use the expected account rather than creating a new one.
Observe whether the status progresses or returns to the same error. Do not leave multiple troubleshooting actions running at once; one before-and-after comparison makes a recurring account or policy error easier to identify.
Separate one blocked file from all-file failure
Save and close the application editing the affected document. Read any file-specific error about its name, path, or permissions. Correct only the named problem on a backed-up copy, following the current OneDrive requirements rather than renaming whole folder trees.
Create a small harmless text file with a simple name in the same intended sync folder. If that uploads but the original does not, focus on the original file. If neither uploads, inspect account, storage, and connection status before editing documents.
Check both cloud and local storage
Review the OneDrive account’s storage status and the PC’s free disk space. More free space on this PC does not resolve a full cloud quota, and unused cloud storage does not guarantee space for a local download.
Do not delete synced files as a quick test: deletion can propagate to the cloud and other devices. A cloud-only placeholder is not an independent offline backup. Verify an actual readable copy of needed content before reorganizing or removing anything.
Use a controlled connection comparison
If many files fail and ordinary sites also fail, diagnose the network. If browser access to the intended OneDrive account works but the client does not, record that distinction and any client error.
For work or school storage, ask the administrator about service health, account access, and sync restrictions. Do not bypass those controls with a personal account. A client reset is an escalation step after data protection and error-specific guidance, not a first response to every pending icon.
Verification
- Confirm the harmless local test file appears and opens in the correct web account.
- Create a second harmless file on the web and confirm it becomes accessible on this PC to test the opposite direction.
- Check the original document’s expected contents, then remove diagnostic files only after confirming they contain nothing needed.
When to stop
Stop for conflicting versions you cannot safely reconcile, missing account access, unexplained mass deletions, or important unsynced data without a copy. Preserve both versions and the error details for support before unlinking, resetting, or reinstalling the client.
Review the safe troubleshooting workflow before any broader recovery step.