Why Kali Linux updates stop working
If you are trying to figure out how to fix Kali Linux update not working, the issue usually comes down to repository configuration, broken package metadata, or network and DNS problems.
The good news is that most update failures can be traced, diagnosed, and repaired with a few standard apt and system checks.
Kali Linux is based on Debian and uses the Advanced Package Tool (apt), so updates depend on a healthy package index, correct mirrors, valid signing keys, and a stable network path.
When one part of that chain breaks, apt update and apt full-upgrade can fail in predictable ways.
Check the exact error message first
Before changing anything, read the terminal output carefully.
The message usually points to the root cause.
- 404 Not Found: the repository URL is wrong or outdated.
- Release file expired: the mirror metadata is stale or unavailable.
- NO_PUBKEY: the repository signing key is missing.
- Temporary failure resolving: DNS or network connectivity is failing.
- Held broken packages: dependency conflicts are blocking upgrades.
Run the update command again and capture the exact line that fails:
sudo apt updateVerify your Kali repository configuration
The most common reason Kali Linux updates do not work is an incorrect entry in /etc/apt/sources.list or a conflicting file in /etc/apt/sources.list.d/.
Kali should generally use the rolling repository rather than mixed Debian or third-party sources.
Open the main sources file and check for a clean Kali entry:
sudo nano /etc/apt/sources.listA typical correct line is:
deb http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmwareRemove or comment out lines that point to:
- Debian stable or testing repositories
- Old Kali release names
- Third-party mirrors that are no longer maintained
- Duplicate entries with the same repository
After editing, refresh package metadata:
sudo apt clean
sudo apt updateFix missing or expired signing keys
Kali packages are signed, and apt rejects metadata when the key is missing or outdated.
This often shows up as NO_PUBKEY or signature verification errors.
First, confirm that you are using the official Kali archive keyring package:
sudo apt install --reinstall kali-archive-keyringIf apt cannot complete because of the key problem, manually refresh the keyring package from a trusted Kali source after verifying your repository list.
Avoid random key import commands from forums unless they come from Kali documentation.
Refresh package lists and clear corrupted cache
Sometimes the update fails because local package metadata is damaged or incomplete.
In those cases, clearing cached lists usually helps.
sudo rm -rf /var/lib/apt/lists/*
sudo apt clean
sudo apt updateThis removes stale metadata and forces apt to download fresh package indexes from the mirror.
If you get partial download errors, the cache reset is often enough to restore normal behavior.
Check network connectivity and DNS resolution
A working repository configuration still fails if Kali cannot reach the internet or resolve hostnames.
Test connectivity in layers, starting with the local network and then DNS.
ping -c 3 8.8.8.8
ping -c 3 http.kali.org
resolvectl statusIf IP connectivity works but domain names fail, the issue is likely DNS.
Update your resolver settings through NetworkManager, your router, or /etc/resolv.conf depending on your setup.
On laptops and virtual machines, switching networks or renewing the DHCP lease can also solve update failures.
Use a different Kali mirror if the default one is slow
Mirror problems can make it look like Kali Linux update is not working even when your system is fine.
If the main mirror is slow, overloaded, or blocked by your network, apt may time out or repeatedly fail downloads.
Try a different mirror from the official Kali mirror list, then replace the repository URL in /etc/apt/sources.list.
After that, run:
sudo apt updateIf the update succeeds on another mirror, the problem was likely mirror latency or regional routing rather than your local system.
Resolve broken packages and dependency conflicts
When package installation is interrupted, apt can enter a broken state where updates no longer proceed cleanly.
This is common after a crash, forced shutdown, or partially completed upgrade.
Run these repair commands in order:
sudo dpkg --configure -a
sudo apt --fix-broken install
sudo apt full-upgradeThe first command finishes incomplete package configuration.
The second repairs dependency issues.
The third performs a full upgrade and resolves package transitions that a simple upgrade may not handle.
Remove package holds that block upgrades
Packages can be marked as held, which prevents apt from upgrading them even when updates are available.
This can cause dependency chains to stall.
List held packages with:
apt-mark showholdIf a package should no longer be pinned, unhold it:
sudo apt-mark unhold package-nameThen rerun the update and upgrade commands.
This is especially useful when troubleshooting kernel packages, desktop environments, or tools from third-party repositories.
Check disk space before retrying the update
Low disk space can cause package downloads and unpacking to fail.
Kali updates may appear to break randomly when the root partition is nearly full.
Inspect available space with:
df -hPay attention to /, /var, and /boot.
If space is tight, remove unused package caches, old kernels, or unnecessary tools.
A crowded /boot partition is a common cause of kernel upgrade failures.
Repair apt lock and permission issues
If another package manager process is running, apt may refuse to update.
This usually happens when a graphical updater is open or a previous apt process crashed.
Look for active package processes:
ps aux | grep -E 'apt|dpkg'If a legitimate process is still running, wait for it to finish.
If a stale lock remains after a crash, avoid deleting lock files blindly unless you are certain no package process is active.
It is safer to repair the interrupted state with dpkg --configure -a than to force-remove locks.
Restore the correct update sequence
Once the repository, network, and package state are fixed, use a clean update sequence.
This reduces the chance of partial upgrades and keeps Kali aligned with the rolling branch.
sudo apt update
sudo apt full-upgrade -y
sudo apt autoremove -yIn Kali Linux, full-upgrade is often the better choice than upgrade because it allows apt to remove or replace packages when dependencies change.
That matters in a rolling distribution where security tools, kernels, and libraries move quickly.
When to check Kali documentation and package sources
If the problem continues after these fixes, the issue may be specific to your installation, virtual machine provider, proxy, or security policy.
Review the Kali Linux documentation, confirm your version of apt, and inspect any custom repository files in /etc/apt/sources.list.d/.
Also check whether a proxy, VPN, captive portal, or firewall is intercepting package downloads.
In enterprise environments, TLS inspection or repository filtering can cause update failures that look like broken Kali configuration.
- Confirm the system date and time are correct.
- Check whether a proxy is set in environment variables or apt config.
- Inspect third-party repository files for Debian or Ubuntu entries.
- Reinstall
kali-archive-keyringif signatures fail. - Use the official Kali rolling repository only unless you have a specific reason not to.
By working through repository settings, keys, connectivity, cache cleanup, and package repair in that order, you can usually restore updates without reinstalling Kali Linux.