When you edit a Word document stored in OneDrive for Business, the file may duplicate with “Upload Failed” or “Upload Failed Copy” in the filename. This happens because Word and OneDrive lose sync during the save process, often due to network interruptions or file lock conflicts. The issue is not permanent file corruption, but a failed sync handshake that creates a renamed copy. This article explains why the copies appear and provides the exact steps to stop them from happening again.
Key Takeaways: Stop Word From Creating Upload Failed Copies
- File > Options > Save > AutoSave files stored in the Cloud by default in Word: Enabling this forces Word to use the OneDrive save pipeline, reducing sync conflicts
- OneDrive settings > Sync and backup > Advanced settings > Files On-Demand: Disabling Files On-Demand can prevent file lock issues that trigger duplicate copies
- Task Manager > Microsoft OneDrive > End task > Restart OneDrive: A clean restart clears stale file locks and resets the sync connection
Why Word Creates Upload Failed Copies in OneDrive
When you edit a Word document that is synced through OneDrive, the file is temporarily locked by the Office application during the save operation. OneDrive detects the lock and waits for the file to be released. If the network connection drops, OneDrive times out, or the save takes longer than expected, OneDrive marks the file as “Upload Failed” and creates a duplicate with that label. The original file remains intact, but the duplicate causes confusion and clutter.
The root cause is a mismatch between Word’s local save process and OneDrive’s sync cycle. Word saves to a temporary file, then replaces the original. OneDrive sees the deletion and creation as separate events. If the creation event is delayed or interrupted, OneDrive treats the new file as a failed upload and appends the error text to the filename. This behavior is more common when Files On-Demand is enabled because the file may not be fully downloaded before Word tries to edit it.
Steps to Fix Word Upload Failed Copies
Follow these steps in order. Each step addresses a different layer of the issue. Test after each step by editing a Word document and saving it.
- Enable AutoSave in Word
Open Word. Go to File > Options > Save. Check the box labeled “AutoSave files stored in the Cloud by default in Word.” Click OK. AutoSave forces Word to use the OneDrive save API instead of the local temp file method. This prevents the file replacement cycle that triggers duplicates. - Disable Files On-Demand temporarily
Right-click the OneDrive icon in the system tray. Select Settings. Go to the Sync and backup tab. Click Advanced settings. Under Files On-Demand, uncheck “Save space and download files as you use them.” Click OK. Restart File Explorer. With Files On-Demand off, Word edits the fully downloaded file, reducing lock conflicts. - Restart OneDrive sync
Press Ctrl+Shift+Esc to open Task Manager. Find Microsoft OneDrive in the list. Select it and click End task. Open the Start menu, type OneDrive, and press Enter. Sign in if prompted. This clears any stale file handles and resets the sync state. - Delete the duplicate files
In File Explorer, locate the Word documents with “Upload Failed” or “Upload Failed Copy” in the name. Select them and press Delete. Empty the Recycle Bin. The original file is still intact. Deleting the duplicates prevents confusion and forces OneDrive to sync the original cleanly. - Check for Office updates
Open Word. Go to File > Account > Update Options > Update Now. Install any pending updates. Microsoft has released patches that improve the sync handshake between Word and OneDrive. After updating, restart your computer.
If Word Still Creates Upload Failed Copies
Word document is checked out by another user
If the file is shared and someone else has it open, Word cannot save the changes directly. The file gets locked by the other user’s session. OneDrive creates a duplicate to avoid overwriting the locked version. Ask the other user to close the document. Use the web version of Word to see who has the file open by checking the document status bar.
Network proxy or VPN blocks sync
Corporate networks with strict proxy rules or VPN connections can interrupt the sync process. OneDrive uses HTTPS on port 443. If the proxy or VPN drops the connection during a save, Word’s temp file replacement fails. Contact your IT team to ensure OneDrive endpoints are allowed through the proxy. You can test by disconnecting the VPN and saving a file on a local network.
Antivirus software locks the file
Some antivirus programs scan Office files during save operations. This can delay the file release long enough for OneDrive to time out. Add the OneDrive folder to your antivirus exclusion list. The exact steps depend on your antivirus software. After adding the exclusion, restart the computer and test.
AutoSave vs Manual Save: Behavior Differences
| Item | AutoSave Enabled | Manual Save (Ctrl+S) |
|---|---|---|
| Save method | Word writes directly to OneDrive via API | Word writes to a local temp file, then replaces the original |
| File lock duration | Milliseconds — lock is released immediately after write | Seconds to minutes — lock persists until temp file is moved |
| Duplicate copy risk | Very low — no temp file replacement cycle | High — network interruption during replacement triggers “Upload Failed” |
| OneDrive sync trigger | Real-time push via API | File system change detection |
AutoSave is available only for files stored in OneDrive or SharePoint. It requires an active internet connection. If you need to work offline, disable AutoSave temporarily, but be aware that manual saves carry the duplicate copy risk. When you reconnect, save manually and wait for the OneDrive icon to show a green check before closing the file.
You can now prevent Word from creating Upload Failed copies by enabling AutoSave, disabling Files On-Demand, and keeping OneDrive updated. Next time you edit a shared document, use the web version of Word for real-time co-authoring — it eliminates the temp file issue entirely. As an advanced tip, set the Windows registry key HKCU\Software\Microsoft\Office\16.0\Word\Options\fUseNewSavePipeline to 1 to force Word to use the improved save pipeline on older builds.