Dpkg Was Interrupted You Must Manually Run Sudo Dpkg Configure To Correct The Problem Jun 2026

Sometimes an interrupted installation corrupts package dependencies. Tell the Advanced Package Tool ( apt ) to look for missing pieces and force a repair: sudo apt update --fix-missing sudo apt install -f Use code with caution.

--configure -a : Tells the system to look for all packages that were unpacked but not yet fully configured and finish the job. What to do if the Quick Fix fails

If you're a Linux user, you may have encountered the frustrating error message: "dpkg was interrupted. You must manually run sudo dpkg --configure -a to correct the problem." This error can occur due to various reasons, including interrupted package installations, corrupted package databases, or issues with dependencies. In this article, we'll walk you through the causes, consequences, and most importantly, the solutions to resolve this error.

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

and internet stability before kicking off large distribution upgrades ( dist-upgrade ). What to do if the Quick Fix fails

Sometimes the command itself throws an error. Common failures include:

After running that, you should be able to use apt normally again.

In 90% of cases, running the exact command suggested by the system will resolve the issue. Open your terminal and run: sudo dpkg --configure -a Use code with caution.

The error states that dpkg was "interrupted." This means that during a previous operation (installing, upgrading, or removing a package), the process was forcibly stopped before it could finish. Common causes include: This public link is valid for 7 days

After removing the locks, clear the cache and re-attempt the configuration: sudo apt clean sudo dpkg --configure -a Use code with caution. Step 3: Fix Broken Dependencies

Then, once that completes successfully, clean up any remaining issues with:

Yes, but only after ensuring no dpkg or apt process is actually running. Use ps aux | grep -E "dpkg|apt" to check. Removing locks is safe as long as no process is writing to the database.

The "dpkg was interrupted" error typically occurs when the package manager's database becomes inconsistent or corrupted. This can happen due to: If you share with third parties

Delete the entire block of text corresponding to that package (from the line starting with Package: [name] up to the blank line before the next package). Save and exit ( Ctrl + O , then Ctrl + X ). Run the update sequence again: sudo apt-get update Use code with caution. How to Prevent Future Interruptions

The after running sudo dpkg --configure -a