How to fix dpkg: package is in a very bad inconsistent state - you should reinstall it before attempting configuration in APT

APTINTERMEDIATEHIGHUpdated Oct 10, 2026· 207 views

The 'dpkg: package is in a very bad inconsistent state' error indicates that a package's installation was interrupted or corrupted, leaving the system in an inconsistent state. This commonly occurs after failed installations, network interruptions, or system crashes during package management operations.

Quick fix

Fixes dpkg: package is in a very bad inconsistent state - you should reinstall it before attempting configuration

sudo dpkg -C
  1. Identify which packages are in an inconsistent state
  2. Attempt automatic dpkg configuration
  3. Fix broken dependencies with apt
  4. Manually remove the problematic package (if needed)
apt — error
sudo dpkg -C
dpkg: package is in a very bad inconsistent state - you should reinstall it before attempting configuration

What this error means

The "dpkg: package is in a very bad inconsistent state" error means that the Debian Package Manager (dpkg) has detected that one or more packages are not properly configured or installed. This typically happens when: - A package installation or removal was interrupted (system crash, power loss, or manual termination) - The package manager was forcefully closed or killed during an operation - Network issues caused a download to fail mid-installation - Conflicting packages were removed or installed incompletely - The dpkg database (/var/lib/dpkg) became corrupted When dpkg detects this, it marks the package as needing reinstallation before it can be configured. This error prevents further apt operations until the inconsistency is resolved.

Typical symptoms

  • Error appears when running apt upgrade, apt install, or apt remove commands
  • Package manager operations hang or fail immediately
  • Cannot install or remove any packages until the inconsistent package is fixed
  • Running apt commands repeatedly shows the same error
  • System cannot proceed with security updates or new installations
  • Error message specifies which package is in an inconsistent state

Common causes

  1. Installation or removal of a package was interrupted by system shutdown or reboot
  2. The apt or dpkg process was forcefully terminated (kill -9)
  3. Network connection dropped during package download or installation
  4. Disk space ran out while extracting package files
  5. Another package manager (Snap, YUM, etc.) was used concurrently on Debian-based system
  6. Corrupted dpkg database or missing package configuration files
  7. Previous failed update left packages in unconfigured state

How to fix "dpkg: package is in a very bad inconsistent state - you should reinstall it before attempting configuration"

1Identify which packages are in an inconsistent state

First, check which packages are problematic:

bash
sudo dpkg -C

This command lists all packages with configuration problems. The output will show you exactly which package(s) need attention:

bash
The following packages are in a broken state:
 package-name : Depends: dependency-package (>= 1.0) but it is not going to be installed

Make note of the package name(s) shown in this list.

2Attempt automatic dpkg configuration

First, try the automatic repair which reconfigures all unconfigured packages:

bash
sudo dpkg --configure -a

This command tells dpkg to:
- Reconfigure all packages that are in 'half-configured' state
- Retry interrupted installations
- Fix dependency issues

If this succeeds, you're done! Your package manager should return to normal. Verify with:

bash
sudo apt update
3Fix broken dependencies with apt

If dpkg --configure -a doesn't fully resolve the issue, use apt's dependency fixing:

bash
sudo apt --fix-broken install

Or the more aggressive variant:

bash
sudo apt -f install

These commands:
- Install missing dependencies
- Remove conflicting packages
- Complete interrupted installations
- Fix dependency conflicts

After running, check if the system is repaired:

bash
sudo dpkg -C

If no packages are listed, the issue is resolved.

4Manually remove the problematic package (if needed)

If the automatic methods don't work, you may need to force-remove the problematic package. Use caution with this approach:

bash
# First, check which package dpkg identifies
sudo dpkg -l | grep -E '^[^i]'

# Force remove the specific problematic package
# (replace 'package-name' with the actual package)
sudo dpkg --remove --force-remove-reinstreq package-name

The --force-remove-reinstreq flag tells dpkg:
- Remove the package even if it's marked as needing reinstallation
- Ignore warnings about dependencies

Then reinstall it cleanly:

bash
sudo apt update
sudo apt install package-name

Warning: This can break dependencies if the package is required by others. Always check what depends on it first:

bash
sudo apt-cache depends package-name
5Clean up package files and metadata

After resolving the inconsistent state, clean up stale package files and metadata:

bash
# Remove cached package files
sudo apt clean

# Remove only partial packages (incomplete downloads)
sudo apt autoclean

# Remove packages that are no longer needed
sudo apt autoremove

Then verify the system is fully clean:

bash
# Check for any remaining issues
sudo dpkg -C

# Check apt can run without errors
sudo apt update

No output from dpkg -C means all inconsistencies are resolved.

6Verify the fix by running package operations

Finally, confirm that the package manager is fully operational:

bash
# Update package lists
sudo apt update

# Check for available upgrades
apt list --upgradable

# Perform an upgrade to verify everything works
sudo apt upgrade

# Or install a test package
sudo apt install curl

If all commands complete without errors, the inconsistent state has been fixed.

For future prevention, ensure you:
- Never force-kill apt or dpkg processes
- Avoid interrupting package operations
- Monitor disk space before apt operations
- Use uninterruptible power supplies (UPS) for servers

Advanced notes

Understanding dpkg Status States

The dpkg database tracks each package in several states:

| State | Meaning |
|-------|---------|
| ii | Package is installed and configured |
| rc | Package is removed but configuration files remain |
| iH | Package is on hold (will not be upgraded) |
| iU | Package is unpacked but not configured |
| iW | Package is waiting to be configured |

The "very bad inconsistent state" occurs when dpkg cannot determine the correct state for a package, usually due to interrupted operations.

dpkg Database Location

The package state database is stored in:
- /var/lib/dpkg/status - Main package status file
- /var/lib/dpkg/status.d/ - Status directory (newer systems)
- /var/lib/dpkg/info/ - Individual package information files

If corruption occurs, these files may become unreadable. Backups are kept at:
- /var/lib/dpkg/status.old - Previous backup
- /var/lib/dpkg/status-old - Alternative backup location

Force Flags Explanation

When using dpkg --force-* options, understand what each does:

- --force-remove-reinstreq - Ignore packages marked for reinstallation
- --force-depends - Ignore dependency problems (dangerous)
- --force-depends-version - Ignore version constraints
- --force-all - Force all checks to be overridden (extremely dangerous)

Only use these when necessary, as they can break the system if dependencies are actually needed.

Difference Between apt and dpkg

- dpkg - Low-level tool that manages individual .deb files. Operates on packages directly.
- apt - High-level package manager that uses dpkg. Handles dependencies automatically.

When dpkg has issues, apt cannot function because it relies on dpkg's database. This is why you must fix dpkg issues before apt will work.

Preventing Inconsistent States

To avoid this error in the future:

1. Never interrupt package operations - Let apt/dpkg complete, even if it seems slow
2. Use stable power - Install UPS for servers, avoid running on laptop battery for critical updates
3. Monitor disk space - Ensure /var/lib/dpkg has at least 100MB free before operations
4. Check dpkg locks - Before forcing operations, check if dpkg is already running:

bash
sudo lsof | grep dpkg

5. Use apt-listchanges - Preview package changes before applying them
6. Keep backups - Backup /var/lib/dpkg/status before major operations

Emergency Recovery

If the standard fixes don't work, you have more drastic options:

bash
# Restore dpkg database from backup
sudo cp /var/lib/dpkg/status.old /var/lib/dpkg/status

# Or start with an empty status and rebuild (dangerous!)
sudo mv /var/lib/dpkg/status /var/lib/dpkg/status.broken
sudo touch /var/lib/dpkg/status

# Then try to reconfigure
sudo dpkg --configure -a

These should only be done as a last resort, as they can cause data loss.

CI/CD Considerations

If you encounter this error in automated deployments:

1. Set a timeout - Add timeout wrapper to apt commands
2. Enable retry logic - Wrap apt in scripts that retry on failure
3. Use apt-get -y - Auto-answer yes to prompts to prevent hanging
4. Monitor logs - Check /var/log/apt/ for detailed operation logs
5. Pre-allocate space - Ensure container images have sufficient /var space

Example safe wrapper:

bash
#!/bin/bash
set -e

for attempt in {1..3}; do
  echo "Attempt $attempt of apt upgrade..."
  if sudo apt update && sudo apt upgrade -y; then
    echo "Success!"
    break
  fi
  if [ $attempt -lt 3 ]; then
    echo "Attempt $attempt failed, retrying..."
    sleep 5
  fi
done

Frequently asked questions

What does "dpkg: package is in a very bad inconsistent state - you should reinsta" mean?
The "dpkg: package is in a very bad inconsistent state" error means that the Debian Package Manager (dpkg) has detected that one or more packages are not properly configured or installed. This typically happens when: - A package installation or removal was interrupted (system crash, power loss, or manual termination) - The package manager was forcefully closed or killed during an operation - Network issues caused a download to fail mid-installation - Conflicting packages were removed or installed incompletely - The dpkg database (/var/lib/dpkg) became corrupted When dpkg detects this, it marks the package as needing reinstallation before it can be configured. This error prevents further apt operations until the inconsistency is resolved.
How do I fix "dpkg: package is in a very bad inconsistent state - you should reinsta"?
The 'dpkg: package is in a very bad inconsistent state' error indicates that a package's installation was interrupted or corrupted, leaving the system in an inconsistent state. This commonly occurs after failed installations, network interruptions, or system crashes during package management operations.
What causes "dpkg: package is in a very bad inconsistent state - you should reinsta"?
Installation or removal of a package was interrupted by system shutdown or reboot The apt or dpkg process was forcefully terminated (kill -9) Network connection dropped during package download or installation
Is the "dpkg: package is in a very bad inconsistent state - you should reinsta" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading