Word freezes opening files from SharePoint – real fixes

1. Corrupted Office Document Cache (the most common cause)

What's actually happening here is that Word caches a local copy of the SharePoint file in %localappdata%\Microsoft\Office\16.0\OfficeFileCache. Over time, that cache gets stale – permissions change, the file gets updated, but the cache doesn't refresh. The result: Word tries to open the cached version, can't verify it against the server, and hangs indefinitely.

The fix is to nuke the cache entirely. Don't bother with the Office Upload Center UI – it's flaky. Do it manually.

1. Close all Office apps – Word, Excel, Outlook, everything. Even OneDrive sync.
2. Open File Explorer and paste this into the address bar:
   %localappdata%\Microsoft\Office\16.0\OfficeFileCache
3. Delete everything inside that folder. Yes, all of it.
4. Empty your Recycle Bin just to be safe.
5. Restart Word, then try opening the SharePoint document again.

The reason step 3 works is that Word regenerates the cache from scratch next time you open a file. It'll be slightly slower for the first file – maybe 2 seconds – but after that, it's back to normal. If you're on Office 2019 or 365, the folder path might be 15.0 instead of 16.0 – adjust accordingly.

Real-world trigger: You're editing a shared project plan in a SharePoint team site. You close Word, come back an hour later, open the same file, and it hangs. Your coworker updated the file while you were away. The cache has the old version, and Word can't reconcile the mismatch.

2. Conflicting Add-ins (especially Adobe Acrobat PDF Maker)

Word add-ins hook into the document open event. If an add-in tries to scan or process the SharePoint file before Word finishes loading it, you get a deadlock. The worst offender is Adobe Acrobat's PDFMaker add-in – it's known to cause exactly this freeze when the file comes from a SharePoint URL rather than a local path.

Don't bother disabling add-ins one by one through the UI – that's tedious and unreliable. Use safe mode to test first.

1. Hold the Ctrl key and double-click the Word icon. Click Yes when asked to start in safe mode.
2. In safe mode, open the SharePoint document. If it works, you've confirmed an add-in conflict.
3. Close Word, start normally, then go to File > Options > Add-ins.
4. At the bottom, next to Manage, select COM Add-ins and click Go.
5. Uncheck everything except maybe Microsoft's own add-ins (like OneNote or Teams).
6. Click OK, restart Word, test again. If it works, re-enable add-ins one at a time until you find the culprit.

The reason safe mode bypasses add-ins is that Word skips the Add-inLoadBehavior registry keys entirely. It's the fastest way to isolate the problem without guessing. If you see Adobe PDFMaker in the list, that's almost certainly it – disable it permanently unless you actually use it to create PDFs from within Word (which you probably don't).

Real-world trigger: You install Adobe Acrobat Reader for a one-time PDF merge, and suddenly Word freezes every time you open a .docx from your company's SharePoint. Acrobat's add-in registers itself without asking, and it doesn't handle SharePoint file streams correctly.

3. Sync Center or OneDrive conflict with SharePoint files

Here's the subtle one. If you have a SharePoint library synced to your local machine via OneDrive (or the older Windows Sync Center), Word gets confused when you open the file through the browser while a sync is in progress. What's happening is that both SharePoint and the local sync process claim ownership of the file lock. Word opens the file from the cache, but the sync engine holds a read lock on the local copy, so Word's attempt to read the file times out.

The fix depends on whether you need the sync or not.

If you don't need synced folders: Stop syncing that SharePoint library entirely.

1. Right-click the OneDrive icon in the system tray and select Settings.
2. Go to the Account tab, click Choose folders, and uncheck the troublesome library.
3. Click OK and wait for the sync to stop.

If you need the sync but want to avoid the freeze: Open the file from the synced local folder instead of the SharePoint web URL. That sounds obvious, but most people click the link from the browser. Instead, open File Explorer, navigate to the synced folder (under C:\Users\YourName\SharePoint), and double-click the file there. Word can then use the local file directly without the SharePoint cache layer.

The reason this works is that Word opens local files using the standard Windows file system API, which handles read locks gracefully. When opened from SharePoint, Word uses a different protocol (WebDAV or the Office cache), which doesn't handle sync locks well at all.

Real-world trigger: Your IT department set up automatic sync for the "Marketing" SharePoint library. You click a link in an email to open the latest brochure draft, Word freezes. But if you navigate to the synced folder and open it from there, it works fine. The conflict only happens when the file is opened via the SharePoint URL while the sync engine is actively syncing.

Quick-reference summary table

Start with the cache clear – it's the fastest fix and the most common cause. If that doesn't work, test safe mode. The sync conflict is rare but easy to diagnose once you know the pattern. Skip any registry edits or reinstall suggestions you see online – they're overkill for this problem.