Update available – doclinc for Outlook
Update available

Your add-in needs a quick refresh.

doclinc detected a new version but couldn't load it automatically. This is caused by Outlook's local cache — not your computer or account. Follow the steps below for your version of Outlook.

Which version of Outlook are you using?

Select yours to see the exact steps.

1

Try force-reloading first

Click anywhere inside the doclinc panel, then press Shift + F5. This forces a hard reload of the add-in and often resolves the issue in seconds.

⚡ Fastest option — try this before anything else.
2

Close Outlook completely and reopen

Close the Outlook window. Then right-click the Outlook icon in the system tray (bottom-right corner of your screen) and choose Quit or Exit.

Reopen Outlook. doclinc will load the latest version.

⚠️ Simply closing the window is not enough — Outlook must fully stop running.
3

Clear the add-in cache folder manually

If the above didn't work, you can clear Outlook's local add-in cache. Close Outlook first, then:

Press Windows + R, paste this path, and press Enter:

%LOCALAPPDATA%\Microsoft\Office\16.0\Wef

Select all files inside (Ctrl + A), then delete them. Reopen Outlook.

🔒 This only removes cached add-in data — not your emails or settings.
4

Also clear the HubAppFileCache folder

If step 3 alone didn't help, repeat the same process for this second cache folder:

%USERPROFILE%\AppData\Local\Microsoft\Outlook\HubAppFileCache

Delete all contents, then reopen Outlook.

1

Close and reopen New Outlook

Close New Outlook completely, then reopen it. Because New Outlook is web-based, a fresh start often loads the updated version automatically.

⚡ This is often enough for New Outlook users.
2

Clear the browser cache via DevTools

If the update still doesn't appear, run the following command in the Windows Run dialog (Windows + R):

olk.exe --devtools

This opens New Outlook alongside Microsoft Edge DevTools. In DevTools:

Go to the Network tab → right-click anywhere in the table → select Clear browser cache.

Close DevTools and restart New Outlook.

💡 You can also simply clear your browser cache if you use Outlook on the web at outlook.office.com.
1

Hard-refresh the page

With Outlook on the Web open in your browser, press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to force a full reload, bypassing the browser cache.

⚡ This resolves the issue in most cases for web users.
2

Clear your browser cache

If the hard refresh didn't work, clear the cache for outlook.office.com specifically:

Open your browser settings → Privacy & Security → Clear browsing data → select Cached images and files → Clear data.

Then reload Outlook on the Web.

3

Try a different browser

If the issue persists in one browser (e.g. Chrome), try opening Outlook on the Web in another browser such as Microsoft Edge or Firefox. Each browser maintains its own cache.

1

Try force-reloading first

Click anywhere inside the doclinc panel in Outlook, then press Shift + Cmd + R. This forces the add-in to reload ignoring its cached copy.

⚡ Try this first — it's often enough.
2

Quit Outlook and reopen

Go to Outlook → Quit Outlook from the menu bar (or press Cmd + Q). Make sure Outlook is no longer running in the Dock, then reopen it.

3

Clear the Wef cache folder (Mac)

Close Outlook first. Then open Finder, press Cmd + Shift + G, and navigate to:

~/Library/Containers/com.microsoft.Outlook/Data/Documents/wef

Delete all contents of that folder. Reopen Outlook.

💡 To show hidden folders in Finder, press Cmd + Shift + . (period).
4

Also clear the OsfWebHost cache

If step 3 alone didn't help, also delete the contents of this folder:

~/Library/Containers/com.Microsoft.OsfWebHost/Data/

Reopen Outlook after clearing.

Outlook stores a local copy of the add-in on your computer to speed up loading. When doclinc releases an update, Outlook doesn't always detect it immediately — it continues serving the older cached version instead.

This is a known limitation of how Outlook handles add-in updates, and is unrelated to your account or computer. The steps above clear that local copy so Outlook fetches the latest version fresh from our servers on the next launch.

For IT administrators

If multiple users in your organization are affected, these options allow you to resolve the issue centrally.

PowerShell script — clear cache for one user

Run this script locally on the affected machine (Outlook must be closed):

  • Closes all Office processes automatically
  • Clears both the Wef and HubAppFileCache folders
  • Safe — does not affect emails or account settings

Contact support@doclinc.io and we will send you the script.

Group Policy — deploy fix to all machines

If the issue is widespread, the same PowerShell script can be deployed silently via Group Policy Object (GPO) to run at user login.

  • Clears cache on every affected workstation automatically
  • No user interaction required
  • Can be scoped to a specific AD security group

Contact support@doclinc.io — we will guide your team through the deployment.

Remove and redeploy the add-in

As a last resort, the add-in can be removed and reinstalled from the Microsoft 365 Admin Center. This resets the cached manifest and forces a clean install for all users.

  • Go to Microsoft 365 Admin Center → Settings → Integrated apps
  • Find the doclinc add-in and remove it
  • Redeploy from the same location
  • Users may need to restart Outlook once

What doclinc cannot fix remotely

The add-in cache lives entirely on users' local machines. doclinc's servers cannot clear it remotely — all fixes are client-side. What we can do:

  • Provide and guide the PowerShell script
  • Assist with GPO deployment
  • Support your IT team through the process
  • Confirm the latest version is correctly deployed on our end

None of the steps worked?

Contact doclinc support — we'll identify exactly which cache is causing the issue and walk you or your IT team through the resolution.

Contact support Go to doclinc.io

doclinc for Outlook — secure document sharing, directly from your inbox.