Fix a Custom Add-In That Will Not Load in Microsoft Word
Question details
Resolve a custom add-in loading error in Microsoft Word.

- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- The user is trying to start a custom Word add-in.
- Observed behavior
- Word displays: “We couldn't get the information needed to start this add-in.” The add-in manifest or cached local storage may be involved.
Check whether you are using Word on Windows, Mac, or the web, and whether the add-in was deployed by your organization or loaded for development. The cache-clearing path below applies to Windows; keep the original manifest file or deployment source available so the add-in can be loaded again.
Clear the Word Add-In Cache on Windows
Remove locally cached add-in files so Word can retrieve the manifest again.
Save your work, then close Word and any other open Microsoft Office apps.
Press Windows + R, enter %LOCALAPPDATA%\Microsoft\Office\16.0\Wef\, and select OK. If the folder does not exist, skip this method and try reloading the add-in.
In the Wef folder, delete its contents. Do not delete the original manifest file from your development or deployment location.
Reopen Word and use Insert > My Add-ins to open the custom add-in again. If it was sideloaded, load it again from its original manifest or deployment source.

Reload the Add-In and Check Its Deployment
Use this approach if clearing the cache does not help or the Windows cache path does not apply.
Edit Word Documents with WPS Writer
WPS Office is a free, lightweight alternative with a familiar interface and support for Microsoft Office formats, making it easy to move everyday document work to WPS Writer. It does not fix Microsoft Word add-in loading errors.

Frequently Asked Questions
Why does Word say it cannot get the information needed to start my add-in?
A stale add-in cache or a problem with the manifest or its referenced resources may prevent the add-in from loading. Clear the cache on Windows, then ask the add-in developer or administrator to check its deployment if the error continues.
Where is the Office add-in cache on Windows?
Close Office apps, press Windows + R, and enter %LOCALAPPDATA%\Microsoft\Office\16.0\Wef\. If the folder exists, you can delete its contents and reopen Word.
Should I delete the original add-in manifest?
No. Clear the locally cached files, but keep the original manifest or deployment source so you can sideload or deploy the add-in again.
What if my organization manages the custom add-in?
If Word does not offer a Remove option under Insert > My Add-ins, contact your administrator. Provide the exact error and your Word version so they can check the deployment.
How do I find my Word version for troubleshooting?
On Windows, open File > Account > About Word. On Mac, open Word > About Microsoft Word, then share the version information with the add-in developer or administrator.




