Troubleshooting extension corruption errors
Troubleshooting "The extension may have been corrupted" errors
Last updated
Was this helpful?
Troubleshooting "The extension may have been corrupted" errors
Last updated
Was this helpful?
Chromium browsers automatically disable browser extensions if the browser detects that the extension's files have been tampered with or are otherwise corrupted (i.e., they fail a signature/integrity check).
You can check the extension's status by opening Extensions > Manage Extensions, or directly navigating to your browser's extensions page:
Chrome: chrome://extensions
Edge: edge://extensions
If you manually installed the browser extension from the Chrome Web Store, you can click "Repair" to try to repair the extension installation.
If the browser extension is force installed (managed by your organization), the browser will automatically attempt to re-download/repair the extension. Or, try closing and reopening the browser profile.
If your Citrix or Windows Roaming Profile Settings include the extension directory, during profile transfer, the browser extension's files may be in an inconsistent state.
See Citrix Profile Configuration for more information.
Antivirus and security software might mis-categorize the extension's files and quarantine and/or otherwise modify the file. Add the browser extension's directory to your Antivirus's ignore-list/allowlist.
Chromium has some known/open bugs () causing the browser to incorrectly flag extensions as corrupted.
If you have checked your VDI/Windows profile and Antivirus settings and continue to experience extension corruption errors, contact .