PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
An Ubuntu release upgrade that appears frozen is usually waiting for input, unable to reach a package mirror, short of disk space, or blocked by third-party packages and broken dependencies. Do not switch off the computer immediately. First check for a hidden prompt, then make sure the current release is fully updated, a required reboot is complete, enough space is available, and incompatible repositories are disabled. Once apt is healthy, retry with sudo do-release-upgrade.
Determine whether the upgrade is really stuck
Ubuntu release upgrades are interactive. The upgrader can pause while it waits for a package-configuration decision, a configuration-file choice, permission to restart a service, or an answer to the “Foreign Packages Installed” question. A terminal window that shows no new progress is not proof that the process has failed.
Recommended Free Tools
Check every place the prompt could appear
- Bring the terminal running
do-release-upgradeto the foreground and read the last several lines. - Check for a graphical dialog behind other windows, including a package configuration or service-restart dialog.
- If you are connected remotely, check the original SSH, console, or multiplexer session rather than starting a second upgrader.
- Look for a question about keeping or replacing a configuration file, removing obsolete packages, or handling packages installed outside the Ubuntu archives.
Answer a prompt only when you understand what it changes. Keep the machine powered on while packages are being unpacked or configured. An abrupt shutdown can leave the package database incomplete and turn a waiting prompt into a repair job.
Distinguish a wait from a failed process
A continuously changing download or installation message indicates activity. A long period with the same message can indicate a slow mirror, a blocked network connection, or a package script waiting on input. If the terminal has returned to a shell prompt with an error, the upgrade has stopped and should be treated as a failed attempt, not restarted blindly.
#1 Best Overall
Note the exact last message before doing anything else. “Fetching” points toward network or mirror reachability; package names, dependency messages, or configuration errors point toward the local package state. A visible cursor or an unchanged percentage is not enough to distinguish these cases, so inspect the session that started the upgrade.
Prepare the current Ubuntu release before another attempt
Ubuntu’s supported recovery sequence starts with a backup and a completely updated source release. Do these checks from a normal shell, not from a second copy of the release upgrader. A clean preparation pass is safer than repeatedly launching the upgrader against an already inconsistent package database.
- Update package indexes. Run
sudo apt updateand wait for it to finish. Repository errors, authentication failures, or unreachable mirrors must be resolved before continuing. A successful-looking upgrade cannot compensate for indexes that were only partly downloaded. - Install every available update. Run
sudo apt dist-upgrade -o APT::Get::Always-Include-Phased-Updates=true. It should complete successfully and leave no remaining updates. The option includes phased updates so the source release is brought as current as the configured repositories allow. - Check for a required reboot. Run
test -e /run/reboot-required && echo "Reboot required". If the message appears, reboot and log in again before retrying the release upgrade. Continuing with a pending reboot can leave the upgrader working from an older kernel or service state. - Verify root storage. Run
df -h /. Release upgrades download hundreds of packages and can need several gigabytes for downloads, temporary files, and unpacking. The exact requirement varies with the source and target releases, architecture, installed software, and whether the system is a desktop or server. - Back up important data. Copy documents, application data, service configuration, and any other irreplaceable files to a separate, accessible location. Canonical’s upgrade guidance states: “It is extremely important that the data is safely copied to a backup location.” A backup on the same failing disk is not a useful recovery plan.
Free space conservatively. Remove only caches, old files, or applications you can identify with confidence; do not delete unknown files from system directories merely to reach a target number. If the root filesystem is full, package unpacking can fail even when a download appears to have completed. Remember that the free-space requirement is not a universal fixed threshold: the package set, architecture, desktop or server profile, and source/target pair all change the amount needed.
Read the preparation results, not just the exit screen
Both apt commands should finish without errors and should report that no further updates remain. If either command stops on a repository, package, or dependency error, stay on the current release and resolve that issue first. Starting the release upgrader while routine updates are failing makes it difficult to tell whether a new message is the original fault or a consequence of it.
Review PPAs and other third-party repositories
Personal Package Archives and other non-Ubuntu repositories are disabled during a release upgrade. Ubuntu identifies software installed from those sources as the most common cause of upgrade problems because the packages may depend on libraries, compiler versions, or package names that do not exist in the target release.
What to do before retrying
- Open Software & Updates and inspect the Other Software tab, or review the repository configuration used by the machine.
- Disable or remove sources that do not publish packages for the target Ubuntu release.
- Identify applications installed from those sources. Remove, downgrade, or replace them with versions available for the target release when they block dependency resolution.
- Do not re-enable a disabled source immediately after the upgrade. Wait until the system is running normally and the publisher confirms compatibility with the new release.
The upgrader has an --allow-third-party option, but using it permits additional repositories to influence dependency selection. It should be reserved for a repository known to support the exact target release; it is not a general fix for an upgrade that cannot calculate dependencies.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWhy foreign packages matter
A package can be present on the machine even when its repository is no longer reachable. During dependency calculation, the upgrader still has to decide whether that package can be replaced, removed, or kept. A foreign-package prompt is therefore a request for a deliberate choice, not an invitation to approve every removal. Record which application depends on a package before removing it, and prefer a target-release build from Ubuntu or a vendor that explicitly supports that release.
Retry with the supported release-upgrade command
After apt update and the full upgrade finish cleanly, any required reboot is complete, storage is adequate, and third-party sources have been reviewed, start the supported command-line workflow:
sudo do-release-upgradeRemain available for the entire run. The command can ask questions long after downloading has begun, and accepting defaults without reading them can alter services or configuration files. Canonical recommends this command for Server edition, cloud images, headless systems, and remote upgrades as well as for an interactive local terminal.
Run only one release upgrader at a time. A second invocation can compete for package-manager locks and make the original state harder to interpret. On a remote machine, use a stable console or a persistent terminal session so a dropped connection does not hide a prompt; the machine itself may continue running, but you must be able to reconnect and answer questions.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Choose the retry path by situation
A still-running process needs observation, not a second command. A process that returned an error needs package repair and preparation. A desktop user can inspect both graphical and terminal prompts; a server operator should plan console access and a maintenance window; a headless operator must arrange an interactive session before starting. The lowest-risk retry is always a backed-up, rebooted, fully updated system using repositories known to match the target release.
Match the symptom to the safest fix
| What you see | Likely cause | Action |
|---|---|---|
| No progress and a question is visible | Interactive package, configuration-file, service, or foreign-package prompt | Read the prompt, choose deliberately, and allow the current operation to finish. Do not power off. |
| Progress stops while fetching files | Unreachable, slow, or misconfigured mirror; local network interruption | Check network and mirror reachability. Select a reachable official mirror, then rerun sudo apt update before retrying. |
| “Could not calculate the upgrade” | Conflicting packages, disabled or incompatible third-party software, or an unhealthy package state | Review PPAs and foreign packages. Repair individual dependency issues with sudo apt-get -f install, then run sudo apt update and the full dist-upgrade again. Retry only after both complete without errors. |
| “Not enough free disk space” | Insufficient room on the filesystem used for downloads or unpacking | Check df -h /, free space you understand, and restart the preparation checks. Never remove unknown system files. |
| Foreign packages or a PPA warning | Packages came from outside the Ubuntu archives and may not exist for the target release | Find the supplying repository, then remove, downgrade, or replace the affected packages. Re-enable a source only after a compatible target-release version is available. |
| The command says no new release is available | The current release is not fully updated, the required reboot has not happened, or the release-upgrade policy does not match the desired track | Finish all updates, reboot when required, and check whether the policy is set for the intended LTS or interim-release path. Release availability and point-release timing change, so consult the target release’s notes. |
Mirror and network checks
When fetching is the point at which progress stops, first confirm that the machine still has network access and that the configured Ubuntu mirror responds. A mirror can be temporarily unavailable, misconfigured, or unreachable from a particular network. Switch to a reachable official mirror using the system’s repository settings, then run sudo apt update on its own. Do not interpret a mirror timeout as proof that package dependencies are broken.
Repair package state after an interrupted or failed attempt
If the process ended with an error, first record the last error text. Do not launch another release upgrade while ordinary package operations are failing. For an individual dependency problem, Ubuntu’s troubleshooting guidance documents:
sudo apt-get -f installLet that command finish, then run sudo apt update followed by:
sudo apt dist-upgrade -o APT::Get::Always-Include-Phased-Updates=trueBoth commands must complete successfully with no pending updates before you try sudo do-release-upgrade again. If the repair command itself reports a particular package, use that package name to investigate the relevant PPA, held package, or incomplete dependency rather than repeatedly running the upgrader.
If the computer was forcibly switched off during installation, allow extra time at the next boot and inspect the package-manager messages. A partially configured system is not equivalent to a cleanly failed download; the priority is to return apt to a consistent state, then repeat the preparation sequence. Do not delete package database files or manually remove libraries simply because an error names them.
When a repair is not yet complete
An apt-get -f install run that ends with another error is a signal to stop and investigate that named conflict. Check whether the package came from a PPA or other foreign source, whether the source is still enabled, and whether a target-release version exists. Only after the repair command, index refresh, and full upgrade all finish cleanly should the release-upgrade command be considered safe to rerun.
Desktop, server, and remote-upgrade considerations
Desktop systems
Keep both the terminal and graphical session visible. A graphical notification can be behind the terminal, while a terminal question can be hidden behind the desktop. Avoid starting software updates from a second graphical tool while do-release-upgrade is running; two package managers cannot safely modify the database at the same time.
Servers and cloud instances
Use a maintenance window, confirm console access, and verify that critical services have a recovery plan. The documented command-line method is sudo do-release-upgrade. A remote SSH session should be persistent enough to survive a brief network interruption, but never assume that a disconnected client means the upgrade has stopped. Reconnect to the original session or use the provider’s console before taking action. Make sure the backup is accessible independently of the server being upgraded.
Headless machines
Because the process is interactive, a headless system still needs an operator available to answer questions. If no one can monitor it, postpone the upgrade rather than starting it immediately before leaving the machine unattended. A lack of a graphical desktop changes where prompts appear, not whether prompts exist.
What to do after the release upgrade completes
Do not treat the disappearance of the upgrader window as the final check. Log in and confirm that the new release boots normally, network access works, and essential services start. Then perform a normal package-index refresh and look for any remaining package errors.
Rank #4
- Review disabled repositories and keep incompatible PPAs disabled.
- Re-enable only repositories that explicitly support the installed release, preferably one at a time so a new dependency problem can be identified.
- Reinstall or upgrade third-party applications using packages built for the new release instead of restoring old binaries blindly.
- Check service status, scheduled jobs, mounted storage, firewall rules, and application data relevant to the machine’s role.
- Keep the pre-upgrade backup until the system has operated normally long enough for you to trust the result.
For a server, verify that remote access and the services users depend on survive a reboot. For a desktop, verify the graphical session, network, sound, and applications that were installed from outside Ubuntu. These checks do not replace the package checks; they confirm that the upgraded system is usable.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →A low-risk decision path
Use the following order whenever an upgrade appears frozen:
- If a prompt is visible, answer it and wait. Never interrupt active package installation just because the screen is quiet.
- If the process has failed, stop using the release upgrader and make a backup.
- Run
sudo apt update, then the fulldist-upgradecommand with phased updates included. - Reboot if
/run/reboot-requiredexists. - Confirm several gigabytes of working space on
/and remove only understood, nonessential data. - Disable incompatible PPAs and third-party repositories; repair or replace packages supplied by them.
- Fix dependency errors with
sudo apt-get -f install, then repeat the update and full-upgrade checks. - Run one
sudo do-release-upgradeand monitor it until completion.
This sequence keeps the retry in the lowest-risk state: a backed-up, rebooted, fully updated system using repositories that are known to match the target release. It also separates reversible preparation work from the release change itself, making each new error easier to classify.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently asked questions
Why is my Ubuntu release upgrade stuck?
It may be waiting for an interactive answer, downloading from an unreachable mirror, running out of disk space, handling a PPA or other foreign package, or resolving broken dependencies. Inspect the original terminal and any graphical dialogs before interrupting it.
Can I safely restart an Ubuntu upgrade that stopped?
Do not restart it blindly. If it is still asking a question or installing packages, answer the prompt and wait. If it returned an error, repair the ordinary package state, complete apt update and dist-upgrade, and only then run sudo do-release-upgrade again.
What does “Could not calculate the upgrade” mean?
Usually the dependency solver found conflicting packages, foreign software, or an incomplete package state. Review PPAs, use sudo apt-get -f install for individual dependency issues, then repeat the update and full-upgrade checks without errors.
How much free space does an Ubuntu release upgrade need?
Ubuntu describes the requirement as several gigabytes because hundreds of packages are downloaded and unpacked. There is no single universal number; the needed space depends on releases, architecture, installed packages, and desktop or server profile. Check df -h / and leave room for temporary files.
Best Value
Should I enable --allow-third-party?
Only when a specific third-party repository is known to support the exact target release. Allowing such sources increases dependency risk and is not a general remedy for a failed calculation. In most cases, disable incompatible sources and re-enable them after the upgrade when compatible packages are available.
What if the upgrade is running over SSH?
Do not start a second upgrader after a disconnect. Reconnect to the original session or use the machine’s provider console, and look for a waiting prompt. Plan remote upgrades with a maintenance window, stable access, and a backup that is independent of the machine.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why does Ubuntu say no new release is available?
The current release may not be fully updated, a reboot may be pending, or the release-upgrade policy may target a different LTS or interim track. Complete updates, reboot when required, check the intended policy, and consult the target release notes because availability and point-release timing change.
Should I re-enable PPAs immediately after upgrading?
No. Keep them disabled until the new release is running normally and the publisher confirms a compatible repository. Re-enable sources one at a time and use packages built for the installed release so a new dependency problem can be isolated.
Frequently Asked Questions
What is the first thing to check when do-release-upgrade appears frozen?
Look for a hidden terminal or graphical prompt. Ubuntu upgrades can wait for configuration-file, service-restart, or foreign-package decisions, so do not power off while installation is active.
Is it safe to close the terminal during an upgrade?
Treat the terminal as the control point for an interactive process. Keep the session available, especially over SSH, and reconnect to the original session or console rather than starting another upgrader.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What commands must succeed before I retry?
Run sudo apt update and sudo apt dist-upgrade -o APT::Get::Always-Include-Phased-Updates=true. Both should finish without errors and leave no pending updates; reboot first if /run/reboot-required exists.
Can a mirror problem look like a dependency problem?
Yes. A fetch that stops can be caused by an unreachable or slow mirror. Check network and mirror reachability, select a reachable official mirror, and rerun sudo apt update before diagnosing dependencies.
What should I do with my backup after a successful upgrade?
Keep it until the new system has booted, networking and essential services work, package checks are clean, and you have operated normally long enough to trust the result.
The Bottom Line
Do not force a reboot just because the Ubuntu release-upgrade screen is quiet. Check for a prompt, then restore a clean starting point: back up your data, finish apt update and the full phased dist-upgrade, reboot when required, verify several gigabytes of free space, and disable incompatible PPAs. Repair dependency errors before running one monitored sudo do-release-upgrade. Afterward, verify the new system and re-enable only repositories that support it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
