Dpkg Was Interrupted, You Must Manually Run 'dpkg --configure -a' To Correct The Problem ((better)) May 2026

sudo dpkg --configure -a sudo apt install -f Run those two commands, and you'll be back to installing software in under a minute. Have a different package manager error? Let me know in the comments—I've probably seen it.

E: Could not get lock /var/lib/dpkg/lock-frontend Another package manager is running. Close the Software Center, Synaptic, or other terminal windows. Then try again.

Have you ever tried to install something on Ubuntu or Debian using apt install , only to be greeted by this wall of red text? sudo dpkg --configure -a sudo apt install -f

sudo dpkg --configure -a It tells dpkg to go back and finish configuring any partially installed packages.

You should now be able to install software normally. What If That Doesn't Work? In rare cases, you might see a different error after running dpkg --configure -a . Here are two common follow-up problems and their fixes. Case 1: "Unable to lock the administration directory" If you see: Have you ever tried to install something on

E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Don’t panic. Your system isn't broken, and you don't need to reinstall Linux. This error is simply Linux’s way of saying, "Hey, the last installation didn't finish cleanly. Please let me tidy up before we continue."

After running it, you'll see it process the interrupted package(s). Wait for it to finish—it may take 30 seconds to a few minutes depending on what was interrupted. If nothing else is open

If nothing else is open, force-remove the stale lock file (only if you're sure no package manager is running):