Dpkg Was Interrupted You Must Manually Run Sudo Dpkg | Configure To Correct The Problem [updated]
Dpkg Was Interrupted You Must Manually Run Sudo Dpkg | Configure To Correct The Problem [updated]
Sometimes, running the command above results in another error, such as "Could not get lock." This happens because another process (like the Software Updater or an unattended upgrade) is still running in the background. Step A: Remove the Lock Files
sudo kill -9 PID
dpkg maintains each package in one of several states: not-installed , config-files , half-installed , unpacked , half-configured , triggers-awaited , triggers-pending , installed . The critical states for this error are: Sometimes, running the command above results in another
while an apt upgrade or apt install command is running.
When this happens, dpkg leaves itself in a locked or unfinished state. Instead of risking corruption, it refuses to run new commands until you clean up the previous one. When this happens, dpkg leaves itself in a
sudo dpkg --configure -a --force-all
If you’re a Linux user—specifically on Debian-based systems like Ubuntu, Linux Mint, or Kali—you’ve likely encountered the dreaded "dpkg was interrupted" error. This usually happens when a system update or software installation is cut short by a power failure, a lost internet connection, or a forced restart. This usually happens when a system update or
If dpkg finished configuring but some software is still acting "broken," use the apt fix-broken tool: sudo apt install -f Use code with caution. 4. Clean up and Upgrade
The "dpkg was interrupted" error typically occurs when a package installation or update process is interrupted, causing the package database to become inconsistent. Some common causes of this error include:
If you must stop a process, use Ctrl+C in the terminal to allow it to stop safely, rather than killing the terminal window.
Sometimes, the local package cache is outdated or corrupted during an interruption. Update it to ensure the system knows which version of the software to install. sudo apt update Use code with caution. Solution 4: Removing the Locked Package