A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
Hi, I'm Mite and here to help.
Since the same account works correctly in Excel for the web, this does not look like a general account or add-in permission issue. It points more toward the Excel Desktop environment on this device.
Please try the following checks:
- In Excel Desktop, go to File > Account > Account Privacy > Manage Settings and make sure connected experiences are enabled. Office Add-ins may fail to load if Office is not allowed to connect to online services.
- Check the Windows date, time, and time zone. Close Office, then go to Windows Settings > Time & language > Date & time and make sure the date, time, and time zone are correct. Microsoft’s Office Add-ins troubleshooting documentation notes that incorrect system time can cause add-in manifest verification problems.
- Test Excel in Safe Mode. Press Windows + R, type excel /safe, and try Insert > Add-ins again. If it works in Safe Mode, disable unnecessary COM add-ins under File > Options > Add-ins.
- Update Office from File > Account > Update Options > Update Now. If this started after a recent Office update, also consider testing a rollback to a previous stable build, especially if this is managed by an organization.
- Clear the Office Web Add-in cache again by closing all Office apps and deleting the contents of: %LOCALAPPDATA%\Microsoft\Office\16.0\Wef
- If this is a work or school account, ask your Microsoft 365 admin to check whether Office Store add-ins, integrated apps, or user-owned apps are restricted by policy.
- Check whether firewall, proxy, VPN, SSL inspection, or security software is blocking Excel Desktop from reaching Office Add-ins/Microsoft Store endpoints.
- Create a new Windows user profile on the same device and test Excel add-ins there. If add-ins work in the new profile, the issue is likely with the original Windows/Office user profile.
Because add-ins work in Excel for the web, the focus should be on the desktop Office environment, connected experiences, local Office cache, WebView2/WEF cache, security policy, or the Windows user profile.