# Troubleshooting extension corruption errors

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.

### Incorrect Citrix/Roaming Profile Settings

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](/enterprise-it-setup/browser-extension-installation-and-configuration/browser-extension-installation-policy/citrix-profile-configuration.md) for more information.

### Antivirus and Security Settings

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.

```
%LocalAppData%\Google\Chrome\User Data
%LocalAppData%\Microsoft\Edge\User Data
```

### Verify Browser Version

If your browser is managed by your organization, verify that your browser is up-to-date:

* Chrome: `chrome://settings/help` (also available from Help > About Google Chrome)
* Edge: `edge://settings/help` (also available from Help and Feedback > About Microsoft Edge)

If you see an error that your browser has failed to install automatic updates due to a corrupted update, ensure your browser is up-to-date before proceeding to troubleshoot the extension.

### Chromium Bugs

Chromium has some known/open bugs ([Chromium Bug Tracker](https://issues.chromium.org/issues?q=corrupted%20status:open%20type:bug)) 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 <support@pixiebrix.com>.

### Manually Deleting the Extension Folder

{% hint style="info" %}
Only delete the extension folder if the extension is force installed (cannot be removed in the Chrome extension interface) and restarting Chrome does not repair the extension.
{% endhint %}

1. Open version information:
   1. `chrome://version/`
   2. `edge://version/`
2. Copy the value from Profile Path
3. In Windows Explorer / Finder, open the Profile Path
4. Open the `Extensions` folder
5. Close Chrome completely (to release file locks)
6. Delete the folder corresponding to the extension id
7. Open Chrome


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pixiebrix.com/how-to/troubleshooting/troubleshooting-extension-corruption-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.