Synology NAS Error Code 65: How to Fix It

Medium 20-60 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
65
Brand
Synology
Product Type
nas
Severity
Medium
DIY Difficulty
Medium
Estimated Fix Time
20-60 minutes
Synology NAS Error Code 65 indicates a sync conflict within the Synology Drive client, meaning two or more versions of the same file exist and the system cannot automatically determine which version to keep. This typically happens when the same file is edited on multiple devices before syncing completes, or when a connection interruption leaves sync tasks in an inconsistent state. The error is medium severity — your data is not lost, but you must resolve the conflict manually to resume normal syncing.
Ad

Tools You'll Need

How to Fix Error Code 65

  1. Back Up All Affected Files Immediately

    Do not delete or overwrite any file until you have confirmed your backup is complete. Syncing conflicts can sometimes result in data loss if the wrong version is chosen.

  2. Identify the Conflicted Files in Synology Drive Admin Console

  3. Check for Conflict Copies on All Client Devices

  4. Resolve Each Conflict by Keeping the Correct Version

    Deleting a conflict copy is permanent. Confirm you have reviewed both file versions before discarding either one.

  5. Pause and Resume Sync on the Synology Drive Desktop Client

  6. Restart the Synology Drive Server Package on DSM

    Stopping the Synology Drive Server will temporarily disconnect all active Drive clients. Inform other users before doing this in a shared environment.

  7. Check DSM and Synology Drive Client for Updates

    Back up your NAS configuration before applying DSM updates. Go to Control Panel > Update & Restore > Configuration Backup to save your settings.

  8. Re-link the Sync Task If the Error Persists

    When re-linking, ensure the local folder and NAS folder both contain the latest versions of your files before starting the new sync task to avoid recreating conflicts.
Ad

When to Call a Professional

Contact Synology technical support if error code 65 returns repeatedly after following all steps, if the conflict involves a large number of files across multiple users, if you suspect file system corruption on the NAS drives, or if critical business data is at risk and you are not confident determining which file version is authoritative. Synology offers official support through their Help Center at help.synology.com, and a qualified NAS administrator or IT professional should be engaged for production or enterprise environments.

Frequently Asked Questions

What causes Synology error code 65?
Error code 65 is caused by a sync conflict in the Synology Drive client. This usually happens when the same file is modified on two different devices before either change is uploaded and synced to the NAS. It can also occur after a network interruption that leaves a sync task in an incomplete state, causing the server and client to disagree on which version of a file is current.
Will error code 65 cause me to lose any files?
Not automatically. When Synology Drive detects a conflict, it typically preserves both versions — the original and the conflict copy — by renaming one of them. However, if you manually delete the wrong version while resolving the conflict, that data will be lost. Always back up both versions of a conflicted file before deciding which one to keep.
How do I find conflict copies created by Synology Drive?
Synology Drive names conflict copies with a suffix that includes the device name and the date of the conflict, such as 'filename (Device conflicted copy YYYY-MM-DD).ext'. Open your local sync folder in File Explorer (Windows) or Finder (Mac) and search for files containing the word 'conflicted' to find all conflict copies quickly.
How can I prevent Synology error code 65 from happening again?
To minimize future sync conflicts, always ensure the Synology Drive client has fully synced before closing your laptop or shutting down a device. Avoid editing the same file simultaneously on multiple devices. Keep DSM and the Drive client updated, as newer versions often include improved conflict detection and resolution logic. For team environments, consider using Synology Drive's versioning feature so you can recover previous file versions if a conflict resolution goes wrong.
Is it safe to restart the Synology Drive Server package?
Yes, restarting the Synology Drive Server package is safe and does not delete any data. It temporarily disconnects all Drive clients, so they will show as offline until the server restarts — usually within 30 to 60 seconds. Any files in the process of uploading or downloading at that moment will resume or retry automatically once the server comes back online.

Related Error Codes