You copy, move, or open a file — and Windows File Explorer stops you cold with: “The source and destination file names are the same.” No copy happens. No file opens. Just a dialog box asking you to Skip, Cancel, or try again.
This error shows up when the source and destination resolve to the same file path — in simple terms, Windows thinks you’re trying to copy, move, or replace a file with itself. It’s not a corruption warning. It’s a path collision.
It hits across several environments, and the fix depends on which one you’re in:
- OneDrive desktop sync client (Windows 10 and 11)
- SharePoint Document Libraries, synced via OneDrive
- Windows File Explorer during local copy/move operations
- Files On-Demand placeholder files marked “Available when online”
This guide walks through every fix, organized from fastest to most advanced, so you can resolve the error in the next two minutes — or dig into the root cause if it keeps coming back.
Table of Contents
Quick Fix Checklist (30-Second Workarounds)
Before troubleshooting deeper, run through this checklist. One of these resolves the error in most cases:
- Verify the path — confirm source and destination folders aren’t the same folder
- Rename the file — add a suffix (-copy, -v2) before moving it
- Pause and resume OneDrive sync — right-click the OneDrive icon in the system tray
- Refresh File Explorer — press F5 or close and reopen the window
- Restart OneDrive.exe — close it from the taskbar and relaunch from the Start menu
If none of these work, move to the scenario matrix below to find your specific fix path.
Before You Start: Identify Your Scenario
Not every instance of this error has the same root cause. Use this table to jump straight to the relevant fix section.
| Scenario | Primary Root Cause | Jump To Fix |
| Copying/Moving in Explorer | Identical source and target directory | Windows Explorer Fixes (Fix 1–2) |
| OneDrive Syncing Error | Files On-Demand cloud placeholder lock | OneDrive Fixes (Fix 3–6) |
| SharePoint Document Library | Mapped drive or broken sync relationship | SharePoint Fixes (Fix 7) |
Check OneDrive Sync Status Before Troubleshooting
Before running any fix, glance at the OneDrive icon overlay on the file or folder — it tells you exactly what state the file is in:
| Icon | Meaning |
| ☁️ Blue cloud | Online-only — file exists in the cloud, not downloaded locally |
| ✅ Green check | Available locally — fully downloaded and safe to move, copy, or open |
| 🔄 Circular arrows | Currently syncing — wait for this to finish before retrying |
| ❌ Red X | Sync error — the specific file or folder has a conflict that needs resolving |
If you see the circular arrows or a blue cloud icon on the file involved, that’s very likely the root of your error — skip straight to Fix 3 below.
What Does “The Source and Destination File Names Are the Same” Mean?
Windows displays the “The source and destination file names are the same” error when the source and destination resolve to the same file path. In other words, Windows believes you’re trying to copy, move, or replace a file with itself. This commonly occurs during OneDrive synchronization, SharePoint document library operations, or while a file is still downloading as a cloud placeholder.
Behind the scenes, Windows compares the complete source and destination paths before performing a file operation. If both paths resolve to the same location—for example, because OneDrive is still syncing, indexing, or resolving the file in the cloud—Windows treats the source and destination as identical. Since a file cannot be copied or moved onto itself, Windows stops the operation and displays the error:
“The source and destination file names are the same.”
Importantly, the file doesn’t have to be an actual duplicate. During synchronization, OneDrive’s sync engine and the Windows file system can temporarily interpret a cloud-hosted file and its local placeholder as the same object. This temporary path conflict is enough to trigger the error, even when no duplicate file exists.
Why Does This Error Occur? (Comparison Matrix)
| Root Cause | OneDrive | SharePoint | Windows Explorer (Local) |
| Same folder selected / dragged into itself | Occasional | Occasional | Most common cause |
| Duplicate file names in source and target | Common | Common | Common |
| Existing cloud copy sync lock | Most common cause | Common | Rare |
| Files On-Demand placeholder (“Available when online”) | Very common | Common | N/A |
| Corrupted sync metadata / cache | Common | Very common | Rare |
| Symbolic links / junction points | Rare | Rare | Occasional |
Understanding which column applies to you determines which fix set to run first.
Step-by-Step Fixes (Organized by Depth)
Basic Resolutions
Fix 1: Verify Folder Paths and Prevent Nested Folder Dragging
This is the single most common Windows Explorer cause. Dragging a folder into a subfolder of itself, or dropping a file into the exact directory it already lives in, triggers this error immediately.
- Open both source and destination in separate Explorer windows
- Confirm the full path strings differ (check the address bar, not just the folder name)
- If moving folders, never drag a parent folder into its own child directory
Fix 2: Rename the File or Change the File Extension
If the file name is genuinely duplicated at the destination:
- Right-click the source file and select Rename
- Add a version suffix, e.g., Invoice-March.xlsx → Invoice-March-v2.xlsx
- Retry the copy or move operation
This sidesteps the naming collision entirely and is the fastest fix when you don’t need to preserve the original file name immediately.
Fix 3: Resolve “Available When Online” (Files On-Demand) Status
OneDrive’s Files On-Demand feature creates cloud placeholders that appear as normal files in File Explorer, even before their content has downloaded. If the sync client can’t correctly resolve the local and cloud versions of a file, Windows may report a source and destination conflict.
- Right-click the file in File Explorer
- Select Always keep on this device
- Wait for the green checkmark to confirm the file has downloaded fully
- Retry the operation
Fix 4: Pause and Resume Sync / Restart OneDrive
A stalled sync cycle often leaves a phantom lock on a file reference.
- Click the OneDrive cloud icon in the system tray
- Select Pause syncing → choose 2 hours
- Wait 30 seconds, then click Resume syncing
- If the error persists, close OneDrive entirely (right-click icon → Close OneDrive) and relaunch it from the Start menu
Advanced System Resolutions
Fix 5: Reset OneDrive
Resetting clears OneDrive’s local sync cache without deleting your files — everything re-syncs from the cloud.
- Press Win + R
- Enter: onedrive.exe /reset
- Press Enter and wait — no confirmation dialog will appear. If OneDrive doesn’t restart automatically within a few minutes, open the Start Menu and launch OneDrive manually.
- Relaunch OneDrive manually from the Start menu after 1–2 minutes, if needed
Pro Tip: Running onedrive.exe /reset won’t delete your local or cloud files — it only rebuilds the sync index. Don’t worry if OneDrive temporarily disappears from your taskbar.
Fix 6: Unlink and Relink Your OneDrive Account
If resetting doesn’t help, a full unlink clears deeper metadata corruption.
- Open OneDrive settings (gear icon → Settings)
- Go to the Account tab → Unlink this PC
- Sign back in with your Microsoft or work/school account
- Choose which folders to re-sync
Fix 7: Fix SharePoint Library Sync Relationships and Clear Office Cache
SharePoint-specific syncing issues often stem from a broken sync relationship rather than a simple file lock. Part of what makes this tricky is understanding the difference between SharePoint and OneDrive in the first place — they share a sync engine but handle permissions and library structure very differently.
- Stop syncing the library: OneDrive icon → Manage → Stop syncing for the affected SharePoint library
- If the issue involves Office files stored in SharePoint specifically, clearing the Office Document Cache may help resolve stale sync metadata: navigate to %localappdata%\Microsoft\Office\16.0\OfficeFileCache and delete its contents. This isn’t a universal fix for every case, but it’s worth trying when Word, Excel, or PowerPoint files are involved.
- Re-sync the library from the SharePoint site: Sync button on the document library page
- Retry the file operation
“Source & Destination Same” vs. “Destination Has Files With the Same Names”
These two messages look similar but require different responses.
| “Source and Destination File Names Are the Same” | “Destination Has Files With the Same Names” | |
| Meaning | Windows sees source and target as the identical path/object | Windows sees two different files sharing a name |
| Typical Trigger | Sync lock, placeholder file, self-nested folder move | Genuine duplicate during copy/move |
| Correct Action | Rename, resync, or reset OneDrive | Choose Skip, Replace, or Keep Both |
| Data Risk | Low — usually a sync-state issue | Moderate — replacing can overwrite data |
Fixing the Error in SharePoint Libraries
SharePoint document libraries add an extra layer of complexity because sync relationships depend on both the local OneDrive client and the SharePoint site’s permission structure.
Common SharePoint-specific triggers include:
- Broken sync relationships after a site was renamed, restructured, or migrated
- Permission changes mid-sync, where a file becomes read-locked
- Mapped network drives pointing to the same SharePoint library through two different paths (e.g., a mapped drive letter and a synced OneDrive folder)
If the error appears specifically in a shared team library, confirm with your Microsoft 365 admin whether the library was recently migrated or restructured — this is one of the most frequent causes of persistent sync locks in enterprise environments.
Windows 10 vs. Windows 11 Differences
| Area | Windows 10 | Windows 11 |
| Context menu | Full right-click menu with OneDrive options inline | Condensed menu — OneDrive options may be under “Show more options” |
| File Explorer layout | Ribbon-based command bar | Simplified top action bar with icons |
| OneDrive app | Classic settings dialog | Modernized UI, same underlying reset commands |
| Reset command | onedrive.exe /reset (same) | onedrive.exe /reset (same) |
The underlying fixes are identical across both versions — only the click path to reach OneDrive options in the right-click menu changes.
Skip, Cancel, or Replace: Which Should You Choose?
| Choice | When to Use | Outcome |
| Skip | You’re batch-copying many files and this one isn’t urgent | File is left out of the current operation; retry it individually later |
| Cancel | You suspect a folder-nesting mistake or wrong destination | Operation stops entirely; re-verify paths before retrying |
| Replace | You’ve confirmed the destination file is outdated or a true duplicate | Destination file is overwritten — irreversible |
Warning: Never choose Replace unless you’ve manually confirmed the destination file’s content and modified date — replacing overwrites the existing file permanently, and this can’t be undone.
Real-World Troubleshooting Scenarios
Scenario A: Moving Files from Desktop to OneDrive Folder
A user drags a batch of files from the Desktop into their OneDrive folder. Windows throws the error on one specific file. Cause: that file already existed in the OneDrive folder from an earlier auto-backup. Fix: rename the incoming file (Fix 2) or confirm and replace only that file.
Scenario B: Opening a PDF File Causing Temporary Cache Locks
A user double-clicks a PDF stored in OneDrive and gets the error instead of the file opening. Cause: the PDF was still a Files On-Demand placeholder mid-download when a background sync cycle tried to write to the same path. Fix: right-click → Always keep on this device (Fix 3), then reopen.
Scenario C: SharePoint Folder Sync Across Multiple Team Members
A shared SharePoint folder was renamed by an admin while three team members had it actively synced locally. Every team member starts seeing the error. Cause: broken sync relationship following the rename. Fix: each user stops syncing the old library reference and re-syncs from the updated SharePoint URL (Fix 7).
How to Prevent This Error in the Future
- Set frequently used files to Always keep on this device to avoid placeholder lock conflicts
- Avoid renaming SharePoint libraries or folders while team members have them actively syncing
- Don’t drag folders into their own subdirectories — check the destination path before dropping
- Periodically clear the Office Document Cache if you work across multiple shared libraries
- Keep OneDrive client updated to the latest build to avoid known sync-index bugs
- If you’re moving large amounts of OneDrive data as part of a broader IT project, plan the transfer during low-sync-activity hours to reduce the odds of conflicts like this one appearing mid-migration, particularly during Microsoft 365 migrations where multiple libraries sync simultaneously
Frequently Asked Questions
What does “the source and destination file names are the same” mean? It means Windows has identified the file you’re copying, moving, or opening as sharing an identical path or file pointer with a file already at the destination, often due to a sync-state conflict rather than a true duplicate.
Why does this error happen when opening a PDF file? It typically occurs when the PDF is still a Files On-Demand cloud placeholder and a background OneDrive sync cycle tries to write to the same file path simultaneously. Downloading the file fully before opening it resolves this.
Does resetting OneDrive delete my local files? No. Running onedrive.exe /reset only clears the local sync cache and metadata index. Your files remain intact both locally and in the cloud, and OneDrive re-syncs everything after relaunch.
Why does this occur with “Available when online” files? These files are placeholders that haven’t fully downloaded. Any operation that requires reading or writing the actual file content can collide with the ongoing sync process, producing this error until the file is fully downloaded.
Is this error related to disc burning software? Some legacy ISO or disc-burning programs display a visually similar “source and destination” message, but that error refers to burn-buffer conflicts and is unrelated to OneDrive or SharePoint cloud sync. If you saw this message while burning a disc rather than during a Windows/OneDrive file operation, the fixes in this guide won’t apply — check your burning software’s documentation instead.
Conclusion & Migration Support
This error is almost always a sync-state or path-collision issue, not a sign of file corruption. Working through the checklist, then the OneDrive or SharePoint-specific fixes, resolves it in nearly every case — and the prevention steps above keep it from resurfacing during routine work.
Sync locks and file-naming conflicts like this tend to multiply during larger-scale operations — like migrating an entire team’s SharePoint libraries or consolidating multiple OneDrive accounts. In those situations, manual troubleshooting file-by-file isn’t practical.
If your organization is dealing with repeated sync conflicts during a Microsoft 365 migration, using a migration platform with built-in conflict detection can cut down on manual troubleshooting significantly. SkyMigrate’s SharePoint migration and OneDrive migration tools are built with exactly this kind of large-scale conflict handling in mind.
