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

This error occurs because the Debian Package Manager (dpkg) keeps a "lock" on its database while it works. When the process is cut short, the database is left in an unstable state, preventing you from installing or removing any other software.

while an apt or dpkg command is running.

Run sudo apt-get update and try the configuration command one last time. Why did this happen? To prevent future occurrences, keep these tips in mind: This error occurs because the Debian Package Manager

The -f stands for "fix-broken." It attempts to repair a system with unmet dependencies. Step 5: The "Nuclear" Option (Use with caution)

If you were in the middle of installing a package or updating your system and your terminal froze, your internet cut out, or your computer lost power, you likely encountered this dreaded message: Run sudo apt-get update and try the configuration

If the command above finishes successfully, it’s a good idea to clean up any partially downloaded files that might be corrupted: sudo apt-get clean sudo apt-get update Use code with caution. Step 3: Handle the "Lock" Error (If Step 1 fails)

Sometimes, dpkg --configure -a will fail because the system thinks another process is still using the package database. You might see an error like: “Could not get lock /var/lib/dpkg/lock-frontend” Step 5: The "Nuclear" Option (Use with caution)

Fixing the "dpkg was interrupted" Error on Ubuntu and Debian