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

sudo dpkg --force-all --configure broken-package The file /var/lib/dpkg/status holds the state of every package on your system. If it's corrupted, you can rename the old one and create a new one from the backups:

sudo dpkg --configure -a sudo apt-get update If the package database is more severely corrupted, run an audit and force a reconfigure of all packages:

sudo dpkg --configure -a | grep -oP "Package: \K.*" If you identify a package (e.g., broken-package ), try:

First, find the problematic package:

| Scenario | Command | | :--- | :--- | | | sudo dpkg --configure -a | | Fix broken dependencies after | sudo apt-get install -f | | Remove lock files manually | sudo rm /var/lib/dpkg/lock-frontend /var/lib/dpkg/lock | | Reconfigure pending packages only | sudo dpkg --configure --pending | | Audit the package database | sudo dpkg --audit | | Force remove a problematic package | sudo dpkg --force-depends --remove <package-name> | | Restore dpkg status from backup | sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status | Conclusion The message "dpkg was interrupted – you must manually run sudo dpkg --configure -a" is one of the most common errors on Debian-based systems, but it is also one of the easiest to fix. In most cases, simply running the suggested command resolves everything in under ten seconds.