Dpkg Was Interrupted You Must Manually Run Sudo Dpkg Configure To Correct The Problem Top

Run the command:

sudo rm /var/lib/dpkg/lock-frontend sudo rm /var/lib/dpkg/lock sudo rm /var/cache/apt/archives/lock Use code with caution.

sudo dpkg --configure -a

dpkg -l | grep ^un

Remember:

Below are the methods to resolve this issue, ordered from the simplest and most common fix to advanced troubleshooting steps.

If that fails, restore from backup:

Sometimes a stale lock file prevents dpkg from running. Lock files are located in /var/lib/dpkg/ and /var/lib/apt/lists/ .

. Common causes include sudden power loss, manual interruption of a terminal process (like pressing ), or background Unattended Upgrades being interrupted by a system reboot. Step 1: Run the Suggested Repair Command

Fix broken dependencies:

: If the above step doesn’t solve the problem, you might need to reinstall dpkg :

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

This completes any pending package configuration. Run the command: sudo rm /var/lib/dpkg/lock-frontend sudo rm

If you use Debian, Ubuntu, Linux Mint, or any other Debian-based distribution, you may have encountered a frustrating error message while trying to install, update, or remove software using apt or dpkg . The error typically looks like this: