OneDrive Admin Checklist: Word AutoSave creates conflicts for desktop Office users

Desktop Office users report that Word AutoSave causes file conflict errors, duplicate documents, and version mismatches when saving to OneDrive. The conflict occurs because AutoSave attempts to write changes every few seconds, while OneDrive syncs those changes to the cloud simultaneously. This article explains the technical cause of these conflicts and provides an admin checklist to prevent them across your organization.

Why Word AutoSave Conflicts Occur with OneDrive Sync

Word AutoSave saves changes to a temporary file in the same folder as the original document every 3 to 10 seconds while the user is typing. OneDrive monitors that folder for changes and uploads each new version to the cloud. When two devices or two Office processes save at nearly the same time, OneDrive detects a version mismatch and creates a conflict copy — typically named with a suffix like “_conflict (User’s laptop).”

The root cause is a timing collision between AutoSave’s local save cycle and OneDrive’s sync cycle. AutoSave does not wait for OneDrive to confirm that the previous upload finished. If the user opens the same file on a second device while the first device is still syncing, OneDrive sees two different local versions and cannot merge them. The result is duplicate files, lost edits, and user confusion.

Additional factors include:

• Network latency: Slower upload speeds increase the window for collisions.
• Large file size: Files over 10 MB take longer to sync, raising conflict risk.
• Known Folder Move: Redirecting Desktop, Documents, and Pictures to OneDrive can cause AutoSave to trigger on files that are still being synced from other locations.

Admin Checklist to Prevent Word AutoSave Conflicts

Use the following steps to configure your Microsoft 365 tenant and client machines. Each step targets a specific cause of the conflict.

1. Disable AutoSave by default using Group Policy
   Download the Office Administrative Template files from Microsoft. In Group Policy Management Editor, navigate to User Configuration > Policies > Administrative Templates > Microsoft Word 2016 > Word Options > Save. Enable the policy “Do not allow AutoSave” and set it to Enabled. This turns off AutoSave for all Word documents saved to OneDrive. Users can still manually save with Ctrl+S.
2. Set OneDrive sync app to always keep Office files on the device
   In the OneDrive sync app settings, go to Sync and backup > Advanced settings > Files On-Demand. Check the box “Always keep on this device” for the folder containing shared Office documents. This prevents OneDrive from marking files as online-only, which can cause AutoSave to write to a placeholder instead of the actual file.
3. Update OneDrive sync app to the latest build
   Require all clients to run OneDrive sync app version 22.022 or later. This build introduced a 2-second debounce timer that delays AutoSave writes until OneDrive confirms the previous sync cycle completed. To enforce updates, use the “Update ring” setting in the OneDrive admin center under Health > Sync app update.
4. Enable version history and conflict resolution settings
   In the Microsoft 365 admin center, go to Settings > Org settings > OneDrive > Sync. Enable “Show conflict resolution dialog” so users see a prompt when a conflict is detected instead of a silent duplicate. Also enable “Keep the last 500 versions” to allow recovery of overwritten content.
5. Limit the number of concurrent editors on a single file
   Use SharePoint site collection settings to restrict co-authoring to 10 simultaneous editors. In SharePoint admin center, go to Settings > Co-authoring and set “Maximum number of co-authors” to 10. Fewer editors reduce the chance of multiple AutoSave triggers colliding.
6. Train users to close files when not editing
   Instruct users to close Word documents after they finish typing. An open file with AutoSave enabled continues to save every few seconds even when the user is not actively typing. Closing the file stops the save cycle and eliminates conflict risk.

If Conflicts Still Occur After Applying the Checklist

Users see a conflict file named “_conflict” every day

Check the OneDrive sync app logs on the affected machine. Open the OneDrive icon in the system tray, select Help & Settings > Settings > Sync and backup > Advanced settings > Open logs. Search for entries containing “CONFLICT” or “MERGE_FAILED.” If the logs show a recurring pattern where two devices save within 1 second of each other, increase the AutoSave interval using a registry key. Set HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options to add a DWORD value “AutoSaveInterval” with a decimal value of 60000 (60 seconds). This reduces the save frequency from 3 seconds to 60 seconds.

OneDrive creates a duplicate copy of the file

This happens when AutoSave writes to a file that OneDrive has already marked as “uploaded” but the cloud version is still processing. The fix is to enable the “OneDrive sync client – Delay upload on save” policy. In Group Policy, navigate to Computer Configuration > Policies > Administrative Templates > OneDrive > Sync. Enable “Delay upload on save” and set the delay to 5000 milliseconds. This forces OneDrive to wait 5 seconds after a local save before starting the upload, allowing AutoSave to finish its write cycle completely.

AutoSave creates a new file with a GUID name

A GUID-named file indicates that OneDrive could not match the local file to any cloud file. This occurs when the file was moved or renamed while AutoSave was running. Instruct users to never move or rename a file that has AutoSave enabled. If the problem persists, disable AutoSave for that specific document by clicking the AutoSave toggle in the top-left corner of Word and setting it to Off.

AutoSave On vs AutoSave Off: Impact on OneDrive Sync

Item	AutoSave On	AutoSave Off
Save frequency	Every 3–10 seconds	Only when user presses Ctrl+S or clicks Save
Conflict risk	High – multiple writes per minute increase collision windows	Low – single manual save gives OneDrive time to sync
File version history	Many automatic versions, some may be incomplete	Fewer versions, each representing a deliberate save
User awareness	Changes saved without user confirmation	User must explicitly save, reducing accidental overwrites

After applying the checklist, users will see fewer conflict files and duplicate documents. Test the configuration on a small pilot group first, then deploy to all users. For ongoing monitoring, use the OneDrive admin center’s Sync health dashboard to review conflict rates and adjust the AutoSave interval or sync delay as needed. One advanced tip: enable the “Require users to sign in with a work or school account” policy in OneDrive settings to prevent personal Microsoft accounts from syncing corporate files, which bypasses your conflict prevention rules.