Dpkg Was Interrupted You Must Manually Run Sudo Dpkg Configure To Correct The Problem Top !!hot!! Jun 2026

In this article, we will explain why this error happens and walk you through the steps to resolve it.

Remove old kernels (carefully – keep at least one working kernel):

dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

If you are certain no process is running, manually remove the lock files: In this article, we will explain why this

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.

– While not typical, a severe network glitch during package download (when combined with certain dpkg hooks) could theoretically cause a disruption.

If you are using Ubuntu, Debian, or any Linux distribution based on them, you will eventually encounter package manager errors. One of the most common and alarming errors is: When a package operation is performed, dpkg updates

Sometimes, a corrupted archive file ( .deb ) sitting in your local cache keeps re-triggering the interruption whenever dpkg tries to process it. Clear out the cached installer files and pull fresh copies: sudo apt clean sudo apt update Use code with caution.

sudo apt-get -o Dpkg::Options::="--force-overwrite" install -f Use code with caution. Best Practices to Prevent Future Interuptions

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. If you are using Ubuntu, Debian, or any

If a package (e.g., grub-pc or mysql-server ) keeps failing, purge it:

E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

Stuck or locked dpkg/apt (lock file errors)

Navigate to /var/lib/dpkg/info/ . You’ll find files like package.postinst , package.prerm , etc. You can temporarily move these aside so dpkg thinks the package has no configuration scripts:

Here’s a quick cheat sheet of all the commands mentioned: