Dpkg Was Interrupted You Must Manually Run Sudo Dpkg Configure To Correct The Problem (2025)

Sometimes, simply running the configure command isn't enough, especially if a specific package is "stuck" or the lock files are still active. If the command above hangs or throws another error, follow these steps in order: 1. Clear the Lock Files

In 99% of cases, is the only command you need. It safely resumes the interrupted process and fixes the database. If you see this error, don't panic—your system isn't broken; it's just waiting for your permission to finish the job.

Are you running into a or a package name that refuses to clear after running these commands? It safely resumes the interrupted process and fixes

To prevent this error in the future, avoid the following during an update:

To ensure everything is synced up, finish with a clean-up and a full upgrade: sudo apt autoremove sudo apt upgrade Use code with caution. Why did this happen? To prevent this error in the future, avoid

Never close the window while a process is running.

If the system thinks another process is still using the package manager, it will block you. Remove the manual locks with: don't panic—your system isn't broken

--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

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