Sometimes, the command sudo dpkg --configure -a runs but the error persists, or the command produces a new error. Here are advanced steps to resolve stubborn cases.
The solution to this problem involves manually running dpkg in configure mode to try and fix any inconsistencies. Here’s how you can do it:
You included the word “top” at the end of your keyword: “dpkg was interrupted you must manually run sudo dpkg configure to correct the problem top.”
This likely comes from two possible sources:
If you meant the top command: after fixing dpkg, simply type top in the terminal. If top fails with “command not found,” install it via sudo apt install procps. If top shows high CPU usage, check if a stuck dpkg process lingers (use ps aux | grep dpkg and kill it with sudo kill -9 [PID]). Sometimes, the command sudo dpkg --configure -a runs
For the rest of this article, we’ll assume “top” refers to troubleshooting top-level solutions—including advanced fixes when the basic command fails.
dpkg maintains a status database for all installed packages. When a package operation is performed, dpkg updates the status of the relevant packages (e.g., from "Half-Installed" to "Installed"). If the process is terminated abruptly, the database reflects an incomplete state.
Because the package manager cannot verify the integrity of the previous operation, it initiates a fail-safe lock to prevent further damage or dependency conflicts.
If a particular package keeps failing (e.g., grub-pc, initramfs-tools), try: If you meant the top command: after fixing
sudo dpkg --configure -a --force-all
Or reconfigure the problematic package individually:
sudo dpkg --configure <package-name>
Scenario: You’re upgrading Ubuntu 22.04. The power goes out mid-upgrade. After rebooting, you run sudo apt upgrade and see:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Solution applied:
sudo dpkg --configure -a
# still fails with "cannot read status file"
sudo cp /var/backups/dpkg.status.0 /var/lib/dpkg/status
sudo dpkg --configure -a dpkg maintains a status database for all installed packages
Try these in order:
sudo apt clean
sudo apt autoclean
sudo apt autoremove
sudo dpkg --configure -a
sudo apt install --fix-broken
In very rare cases, you might need to force reconfigure all packages:
sudo dpkg --configure -a --force-all
Only remove locks if you confirmed no package process is active.
Broken packages / unmet dependencies
Corrupted package database (rare)
Out-of-space errors