Most of the time, sudo dpkg --configure -a alone solves it. Try that first, then follow the other steps only if needed.
How to Fix "dpkg was interrupted, you must manually run sudo dpkg --configure -a"
In very rare cases, you might need to force reconfigure all packages: Most of the time, sudo dpkg --configure -a alone solves it
Broken packages / unmet dependencies
A: No. It only completes pending package configurations. It does not remove user data or system configuration files (except in rare cases where a package’s post‑install script performs deletions – but that’s part of the intended package behavior). It only completes pending package configurations
Panic sets in. What did you do?! How do you fix this?! Fear not, dear reader, for we're about to embark on a journey to understand the what, why, and how of this pesky problem.
– dpkg needs space for temporary files and configuration. Monitor usage with df -h . Aim for at least 5‑10% free. What did you do
If dpkg --configure -a still fails with a specific error message, try these deeper fixes: Clear the "Partial" Folder Sometimes a corrupted download file is the culprit. : sudo rm -rf /var/lib/apt/lists/partial/* Force Overwrite (The Nuclear Option)
sudo dpkg --configure -a
Sometimes, an interrupted process leaves behind a "lock file." Lock files are safety mechanisms that prevent two programs from modifying the package database at the same time. If the previous process crashed, the lock file remains, blocking even sudo dpkg --configure -a from running.
If a specific package is corrupt and blocking the dpkg --configure -a command from completing, you can force the installation system to overwrite it. Replace package_name with the exact name of the problematic software shown in your error terminal.