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

How to Fix "dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem"

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.

Many users instinctively press Ctrl+C when an installation seems stuck. However, interrupting dpkg at the wrong moment (e.g., while it’s writing to the database) will trigger this error. Always let package operations complete, or use sudo apt-get install --fix-missing instead of killing them.

In rare cases where a post-install script fails, one can:

After removing these locks, tell the package manager to re-evaluate its state: sudo dpkg --configure -a Use code with caution. Step 2: Repair Broken Dependencies with APT How to Fix "dpkg was interrupted, you must

If the error no longer appears, you have successfully resolved the issue.

The error is a safeguard. It prevents you from starting a new package operation while the database is in an inconsistent state. The --configure -a flag tells dpkg to reconfigure all unpacked but not yet configured packages, finishing any pending operations.

sudo dpkg --configure -a

dpkg maintains each package in one of several states: not-installed , config-files , half-installed , unpacked , half-configured , triggers-awaited , triggers-pending , installed . The critical states for this error are: However, interrupting dpkg at the wrong moment (e

The Linux package management system uses a strict locking mechanism to prevent system corruption. If an installation process terminates unexpectedly, the package database is left in an unstable, incomplete state. Common triggers include:

before initiating large system upgrades. If your system is still throwing errors, let me know:

: Even if a progress bar appears stuck at 99%, look at your storage indicator or system monitor. Configuration scripts can sometimes take several minutes to compile or configure services in the background.

Sometimes an interrupted installation leaves dependencies broken. After running --configure -a , try: Step 2: Repair Broken Dependencies with APT If

A. System Administrator Affiliation: Journal of Linux Systems Management Date: April 21, 2026

In this comprehensive guide, we’ll explain what causes this error, how to fix it step by step, how to prevent it from recurring, and what to do if the basic fix doesn’t work.

Fixing the "dpkg was interrupted" Error in Linux If you’ve been managing a Debian-based system like Ubuntu, Linux Mint, or Kali, you’ve likely encountered this daunting terminal message:

Understanding the context can help you prevent the problem. Here are typical situations where you might see "dpkg was interrupted":

: If you see an error like "Could not get lock," another process might be using the package manager. Close other installers (like Synaptic or Update Manager) or manually remove the locks as suggested on BigBearTechWorld sudo rm /var/lib/dpkg/lock Remove Pending Updates