
To fix “Failed to install a dependency” on Kodi, identify the component that failed, then address its compatibility, repository, or installation problem. A dependency is a supporting component another add-on needs to work. The notification alone does not establish the cause. Follow the steps below to find it and choose a fix without unnecessarily removing your settings.
Find the Dependency That Failed
Open the affected add-on’s information page and inspect its dependency list, if available. Note any component marked unavailable or incompatible.
If the notification provides no useful detail, capture a debug log:
- Open Settings → System → Logging and enable debug logging.
- Exit Kodi normally and reopen it.
- Attempt the installation again.
- Open
kodi.logand search for the add-on name,dependency, orCAddonInstallJob.
Menu wording can vary by version and skin.
Read the entries immediately before the final failure. For example, an illustrative message such as CAddonInstallJob[plugin.video.example]: failed to install dependency script.module.example identifies the parent add-on and failed module, but an earlier entry may explain why that module failed.
If Kodi Logfile Uploader also fails to install, access the file directly. For a standard Windows installation, open %APPDATA%\Kodi\kodi.log. Portable, Microsoft Store, and other operating-system installations use different locations.
Check Whether One Add-on or All Installations Are Affected
After a normal restart, retry once. Then attempt to install a small, compatible add-on from the official Kodi repository.
If that succeeds, concentrate on the original add-on’s requirements and repository. If unrelated installations fail too, investigate shared repository access, connectivity, or local installation problems.
| What you observe | What to check next |
|---|---|
| Only one add-on fails | Its supported Kodi versions and dependencies |
| Several add-ons fail on the same module | That module’s availability and required version |
| Unrelated official add-ons also fail | Repository access and preceding download errors |
| The log reports copying or extraction failures | Available storage and file access |
This comparison narrows the investigation; it does not prove a cause.
Fix the Problem Identified in the Log
Missing, Outdated, or Disabled Dependencies
Open Settings → System → Add-ons → Manage dependencies. If the option is missing, change the settings level to Advanced. Find the named component and inspect its installed version and status.
Compare the installed version with the requirement shown in the error. Enable a disabled component if Kodi permits it and it is compatible.
In the add-on browser’s side menu, select Check for updates. Install an available compatible update, then retry the original add-on. If the dependency is absent, use the official repository or the developer’s documented source rather than an arbitrary ZIP download.
Kodi or Add-on Version Incompatibility
Check the developer’s documentation for supported Kodi versions. An installed dependency can still fail the add-on’s version requirements.
An error mentioning xbmc.python concerns Kodi’s Python add-on interface. Kodi 19 introduced Python 3, and older Python 2 add-ons require developer changes to work in that environment.
Use a compatible add-on release. Installing a separate Python application or editing the requirement in addon.xml does not convert incompatible code.
Repository or Download Failures
A repository is the source Kodi uses to discover and download add-ons. Confirm that the required repository is enabled and follows the developer’s current installation instructions.
Refresh updates, then inspect the log for download failures, unavailable URLs, or connection errors. Check whether your device can reach the internet and whether the developer reports an outage.
If a repository or mirror is temporarily unavailable, retry after service returns. Reinstalling Kodi cannot restore a remote server.
Avoid changing Update official add-ons from to Any repository indiscriminately. This changes where official add-on updates can originate.
Package, Storage, or File-access Failures
When the log points to downloading, unpacking, or copying files, check available storage and whether Kodi can write to its own data folders.
For a specifically identified invalid package, obtain a fresh copy from its legitimate source. Kodi distinguishes dependency-resolution failures from invalid archives and download failures.
Downloaded installation packages differ from playback cache. Clearing cache cannot supply an unavailable dependency or make an incompatible add-on compatible. Avoid deleting databases or clearing application data as an initial fix.
Confirm the Fix Worked
Retry installation of the original add-on, then open it. Confirm that installation completes and the dependency notification does not return.
If another dependency fails, inspect its error. A dependency can require further components, so the final notification may describe only part of the chain.
Turn off debug logging when troubleshooting is complete.
If Installation Still Fails
Send the relevant maintainer or support forum:
- Device and operating system.
- Kodi version.
- Add-on and repository versions.
- Failed dependency ID and required version.
- A fresh debug log and the steps that reproduce the failure.
Before testing a clean setup or resetting Kodi, back up your configuration. An abandoned add-on may need a maintained replacement.
The most reliable fix follows the evidence: identify the failed component, resolve its specific problem, and verify the original installation before making broader changes.
