It was a Thursday afternoon and one of our sales guys pinged me on Cliq saying his WorkDrive folder on his laptop was "empty." Not partially synced. Empty. He had 4GB of files in there the day before. TrueSync was running in the system tray, showing no errors, just quietly doing absolutely nothing. That little icon looked perfectly fine. Totally useless.

I spent about two hours on that one. Checked the Zoho status page, nothing. Restarted TrueSync, nothing. Reinstalled it, still nothing. What finally fixed it was buried in a combination of Windows credential issues and a workspace permission flag that had silently reset. And I found exactly zero documentation that connected those two things together. So here's what I wish I'd had that day.

TrueSync is genuinely useful when it works. The on-demand sync model means you're not clogging up disk space, and for teams sharing large project folders it's a solid solution. But it's also one of those tools that fails quietly, which makes it way more frustrating than something that throws a loud obvious error. Sound familiar? Good. Let's get into it.

Table of Contents

• What TrueSync Actually Does (and Where It Goes Wrong)
• Fix 1: Re-authenticate and Clear Stored Credentials
• Fix 2: Check Workspace and Team Folder Permissions
• Fix 3: Reset TrueSync Config Without Losing Files
• Fix 4: Windows and macOS Specific Issues
• Common Mistakes People Make

What TrueSync Actually Does (and Where It Goes Wrong)

TrueSync is Zoho WorkDrive's desktop sync client. Unlike old-school sync tools that download everything locally, TrueSync uses placeholder files. You see the folder structure and file names, but the actual data only downloads when you open the file. Smart idea. The problem is this architecture has more failure points than a basic sync client does.

Here's the thing: TrueSync can break at several different layers. Authentication can expire silently. Folder permissions on the WorkDrive web side can change without the desktop client noticing. The local sync database can get corrupted. Or Windows credential manager holds a stale token that TrueSync keeps trying to use. Each of these looks identical from the outside: files missing, sync stuck, icon showing green when nothing is actually happening.

The most common scenarios I've seen are: files not appearing after a fresh install, sync stopping after a password change, specific team folders not showing up even though the user has access on the web, and the dreaded "partial sync" where some files appear but entire sub-folders are just gone.

Fix 1: Re-authenticate and Clear Stored Credentials

Start here. Always. Half the time this is it.

On Windows, go to Control Panel > Credential Manager > Windows Credentials. Look for any entries with "Zoho" in the name. Delete all of them. Then open TrueSync from the system tray, click your profile icon, and sign out completely. Don't just close it. Sign out.

On Mac, open Keychain Access, search for "Zoho", and remove any stored entries related to WorkDrive or TrueSync. Then sign out from the TrueSync menu bar icon.

After clearing credentials, relaunch TrueSync and sign in fresh. Watch the sync icon for about 60 seconds. If it starts spinning and then settles, you're probably sorted. If you just changed your Zoho account password recently and didn't do this step, that's almost certainly your problem.

Fix 2: Check Workspace and Team Folder Permissions

This one catches people off guard. TrueSync only syncs folders that are explicitly shared to the user with at least "View" access inside WorkDrive. If someone on the admin side reorganized folders, moved files between Team Folders, or changed a sharing setting, TrueSync won't automatically adjust. It just silently stops showing that folder.

Log into WorkDrive on the web > My Teams > [your team] > Team Folders. Check every folder the user is supposed to access. Click the folder, then go to Members on the right panel. Confirm the user is listed with a role. If they got removed during a reorganization, that's your answer.

Also check this: go to WorkDrive Admin Panel > Reports > Audit Log and filter by the affected user. You can sometimes see permission change events that happened right around the time sync broke. That's how I nailed the issue I mentioned at the start. A team admin had accidentally changed a folder from "Everyone in team" to "Specific members" and just didn't add the sales guy back.

Fix 3: Reset TrueSync Config Without Losing Files

If auth and permissions check out, the local sync database might be corrupted. This sounds scary but it doesn't delete your actual cloud files. It just resets what TrueSync knows about local state.

On Windows, close TrueSync completely from the system tray. Then navigate to:

Rename the entire TrueSync folder to something like TrueSync_backup_old. Don't delete it yet. Relaunch TrueSync, sign back in, and let it rebuild from scratch. It'll re-create that folder and re-sync everything. On most setups this takes 5-15 minutes depending on how many folders you have.

On Mac, the equivalent path is:

Same process. Rename, relaunch, re-authenticate. I've done this probably a dozen times across different machines and it's never caused data loss, but rename instead of delete just to be safe. Especially on a user's machine where they've saved things locally that you don't know about.

Fix 4: Windows and macOS Specific Issues

Windows 11 specifically has an issue where the Files On-Demand integration can conflict with TrueSync if OneDrive is also installed. Both want to handle placeholder files at the OS level. If you have both running, try disabling OneDrive's Files On-Demand under OneDrive Settings > Sync and Backup > Advanced Settings and see if TrueSync starts behaving.

On Mac, after any macOS update, TrueSync sometimes loses its Full Disk Access permission. Go to System Settings > Privacy and Security > Full Disk Access and make sure TrueSync is in the list and toggled on. This one is easy to miss and it will cause partial syncs where some folders work but protected directories don't.

Also on Mac: if you're on an M1 or M2 chip and installed an older version of TrueSync, make sure you have the Apple Silicon native build. The Rosetta version works but it's slower and occasionally hiccups. Download the latest from the WorkDrive desktop apps page in your Zoho account.

Common Mistakes People Make

Reinstalling TrueSync without clearing credentials first. This is probably the most common one. The reinstall keeps your saved auth tokens and you end up right back where you started. Clear credentials first, then reinstall if needed.

Assuming the problem is server-side. I've done this. Spent 20 minutes on the Zoho status page when the issue was entirely local. Check your own machine first before blaming the cloud.

Not giving TrueSync enough time after sign-in. On first sync or after a reset, it takes a few minutes to pull the folder structure. People see nothing immediately and start poking around, restarting it again, which just restarts the clock. Give it five minutes minimum.

Running TrueSync as a standard user on a machine that needs admin rights for certain paths. If the WorkDrive folder location is set to somewhere like C:\Company Files\ instead of the user's home directory, you might need TrueSync running with elevated permissions or just move the sync folder somewhere the user owns.

Ignoring the TrueSync logs. They're actually readable. On Windows find them at C:\Users\[Username]\AppData\Local\Zoho\TrueSync\Logs. On Mac at ~/Library/Logs/Zoho/TrueSync. Open the most recent log file and search for "error" or "failed". You'll usually find something useful in there that the UI never shows you.

Honestly, TrueSync is much better than it was two years ago. But it's still the kind of tool where you need to know these internals because the surface-level troubleshooting gets you nowhere fast. Hope this saves you the two hours it cost me that Thursday. If you're an admin managing this across multiple machines, I'd also recommend setting up a quick checklist for new installs that covers credentials, permissions, and Full Disk Access before the user even touches it. Way easier than troubleshooting after the fact.