Fix 'dpkg was interrupted' Error: Run dpkg --configure -a

Linux & Unix Intermediate 👁 0 views 📅 May 25, 2026

When dpkg is interrupted during package installation or update, it locks the package manager. This guide shows how to safely reconfigure and complete pending package operations.

Symptoms

When running apt-get, apt, or dpkg commands, you may encounter an error similar to:

E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

This error prevents any package installation, removal, or update operations. The system may also show partial upgrades or broken package states. Attempts to install new software fail immediately.

Root Causes

The error occurs when a dpkg operation (such as package installation, removal, or upgrade) is terminated before completion. Common causes include:

  • Power failure or system crash during package installation
  • User manually killed the apt or dpkg process (Ctrl+C)
  • Network interruption during package download
  • Running multiple package manager instances simultaneously
  • Disk space exhaustion during installation

dpkg maintains a database of package states. An interrupted operation leaves the database in an inconsistent state, requiring manual intervention to complete or roll back the pending changes.

Step-by-Step Fix

Step 1: Run dpkg --configure -a

Open a terminal and execute:

sudo dpkg --configure -a

This command reconfigures all unpacked but not yet configured packages. It will attempt to complete any pending package setup scripts.

Step 2: Wait for Completion

The process may take several minutes. Do not interrupt it. Watch for any error messages. If successful, you'll see output like:

Setting up package-name (version) ...

Step 3: Verify Package Status

After completion, check for any remaining broken packages:

sudo apt-get check

If no errors are reported, proceed.

Step 4: Fix Broken Dependencies

If the previous step shows broken packages, run:

sudo apt-get install -f

This attempts to fix broken dependencies automatically.

Step 5: Update Package Cache

Finally, update the package list and upgrade:

sudo apt-get update
sudo apt-get upgrade

Alternative Fixes

If dpkg --configure -a Fails

Try forcing configuration:

sudo dpkg --configure -a --force-depends

Manual Package Removal

If a specific package is problematic, remove it manually:

sudo dpkg --remove --force-remove-reinstreq package-name

Then clean up:

sudo apt-get clean
sudo apt-get autoclean

Reconfigure dpkg Database

In rare cases, rebuild the dpkg database:

sudo rm /var/lib/dpkg/lock-frontend
sudo rm /var/lib/dpkg/lock
sudo dpkg --configure -a

Caution: Only remove lock files if you are certain no other dpkg process is running.

Prevention

  • Always allow package operations to complete fully before closing the terminal or shutting down the system.
  • Use a UPS (Uninterruptible Power Supply) to prevent power loss during updates.
  • Avoid running multiple package manager instances (e.g., apt and Synaptic simultaneously).
  • Ensure sufficient disk space before starting large installations.
  • Use screen or tmux when performing remote updates to avoid session interruptions.
  • Regularly run sudo apt-get check to verify package consistency.

By following these steps, you can safely recover from a dpkg interruption and restore your package manager to normal operation. The key is patience and avoiding further interruptions during the recovery process.

Was this solution helpful?