It was a Monday morning. One of our department heads messages me saying her WorkDrive folder is just sitting there, completely static, not syncing anything. The TrueSync icon in the system tray had that little warning badge on it. She had a client presentation in two hours and needed the latest version of a deck someone else had updated over the weekend.

I logged into the admin console expecting some obvious error. Nothing. Everything looked fine on Zoho's end. The desktop app, though, was stuck in what I can only describe as a silent failure state. No useful error message. Just... not working. Sound familiar?

That incident sent me down a two-hour rabbit hole. I've since dealt with TrueSync failures maybe a dozen times across different machines — Windows and Mac both — and I've figured out what actually causes this and what actually fixes it. Not the generic "reinstall the app" advice you get from support tickets. Real fixes.

Table of Contents

• What TrueSync Is Actually Doing (And Why It Breaks)
• Fix 1: Force Sign Out and Re-authenticate
• Fix 2: Clear the TrueSync Cache Properly
• Fix 3: Check Proxy and Firewall Settings
• Fix 4: Clean Uninstall and Reinstall
• Common Mistakes People Make
• Closing Thoughts

What TrueSync Is Actually Doing (And Why It Breaks)

TrueSync is WorkDrive's desktop sync client. Unlike the older WorkDrive Genie (which physically downloaded everything to your machine), TrueSync works more like a virtual drive. Files appear on your desktop but they're pulled on demand from the cloud. That's clever in theory. In practice it means there are more moving parts that can go wrong.

The most common failure modes I've seen are: expired OAuth tokens (happens after a password change or a security policy refresh), corrupted local cache that gets the app confused about what's synced, proxy or firewall rules blocking TrueSync's outbound connections, and bad installs where an update didn't complete cleanly. The tricky part is TrueSync doesn't always tell you which one it is. You get a vague "sync paused" or "unable to connect" message and that's it.

Here's the thing — most people jump straight to reinstalling. Sometimes that works. But half the time it doesn't because the reinstall leaves behind old cache files that poison the fresh install anyway. So let's go in order.

Fix 1: Force Sign Out and Re-authenticate

This fixes the problem probably 40% of the time. If your company recently enforced a password policy change, or if someone's Zoho account got a security refresh, the OAuth token TrueSync is holding onto is stale. The app doesn't always catch this gracefully.

1. Click the TrueSync icon in your system tray (Windows) or menu bar (Mac).
2. Click the three-dot menu or gear icon depending on your version.
3. Select Sign Out. Not quit. Sign out.
4. Wait about 30 seconds after it signs out before signing back in.
5. Sign in again with your Zoho credentials and go through the auth flow completely.

After you sign back in, give it two or three minutes. Watch the tray icon. If you see it start showing sync activity, you're done. If it just sits there again, move to Fix 2.

Fix 2: Clear the TrueSync Cache Properly

This one is where most guides fail you. They say "clear the cache" but don't tell you where it actually lives.

On Windows, quit TrueSync completely first. Then navigate to:

C:\Users\[YourUsername]\AppData\Local\ZohoWorkDrive

Delete everything inside that folder. Not the folder itself — the contents. There'll be folders named things like Cache, Logs, Sync. Wipe them all.

On Mac, the path is:

~/Library/Application Support/ZohoWorkDrive

Same deal. Clear the contents. Then relaunch TrueSync and sign in fresh. I've seen this fix cases where the app was looping on a corrupted sync record for a file that had already been deleted from WorkDrive weeks ago. The app just couldn't move past it.

Fix 3: Check Proxy and Firewall Settings

This is the fix that trips up Indian IT admins specifically, in my experience. A lot of offices here route traffic through proxies or have stricter firewall rules, and TrueSync needs outbound access to a few specific Zoho domains.

Make sure these are whitelisted in your firewall or proxy config:

workdrive.zoho.com
accounts.zoho.com
*.zohoapis.com
downloads.zohocdn.com

TrueSync uses HTTPS on port 443. But I've also seen setups where the proxy was doing SSL inspection and that broke TrueSync's certificate validation completely. If you're running SSL inspection, you'll need to add TrueSync as an exception. The app doesn't handle SSL interception well at all — honestly that's a real weakness in how it's built.

To test quickly, try temporarily connecting the problem machine to a mobile hotspot and see if TrueSync syncs. If it does, your network config is the culprit.

Fix 4: Clean Uninstall and Reinstall

If nothing above worked, you need to do this properly. A regular uninstall leaves residual files and that's why a naive reinstall often doesn't fix anything.

On Windows:

1. Uninstall TrueSync from Add or Remove Programs.
2. Manually delete C:\Users\[YourUsername]\AppData\Local\ZohoWorkDrive entirely this time.
3. Also check C:\Users\[YourUsername]\AppData\Roaming\ZohoWorkDrive and delete that too if it exists.
4. Restart the machine.
5. Download a fresh installer from workdrive.zoho.com/truesync — don't reuse an old installer file.
6. Install and sign in.

On Mac, use the uninstaller that comes with the TrueSync app package. Don't just drag it to trash. The bundled uninstaller actually removes the helper processes and launch agents that a trash-drag won't touch.

Common Mistakes People Make

Reinstalling without clearing cache first. Already covered this but it's worth repeating because it's the most common one.

Checking the wrong account. If your company uses multiple Zoho orgs, make sure TrueSync is authenticated against the right one. I've seen people spend 45 minutes troubleshooting before realizing TrueSync was connected to a personal free account instead of the company org.

Ignoring Windows Controlled Folder Access. If you're on Windows 10 or 11 with Controlled Folder Access turned on in Windows Security, it can silently block TrueSync from writing to the virtual drive location. Go to Windows Security, Virus and Threat Protection, Manage Ransomware Protection, and either disable Controlled Folder Access or add TrueSync as an allowed app.

Running an outdated version. TrueSync updates quietly and sometimes a bug in an older version just gets fixed in a newer one. Check your current version by clicking the tray icon and going to About. Then compare it with whatever's listed on the WorkDrive download page.

Closing Thoughts

TrueSync is genuinely useful when it works. The on-demand sync model saves a ton of disk space compared to Genie, and for teams sharing large files it's a big deal. But it's also a bit fragile and Zoho's own documentation for troubleshooting it is honestly pretty thin. You end up figuring this out through trial and error or by bugging their support chat.

Hope this saves you a couple of hours on a morning when you really didn't need this problem. If none of these fixes worked for you, drop the exact error message you're seeing into a support ticket — sometimes there are backend sync issues on Zoho's end that only their team can see. But try these first. Nine times out of ten, one of them is your answer.