Fix ‘Software Updater Failed to Download Repository Information’ in Ubuntu

Few Ubuntu messages are more annoying than opening Software Updater and seeing a warning that it failed to download repository information. Your internet seems fine, your browser works, and yet updates stop. In most cases the problem is not your connection at all. It is usually one broken repository, an old third-party source, a changed server address, or a temporary mirror problem.

The good news is that you can almost always fix it yourself in a few minutes. This guide walks you through checking the full error message, finding the exact repository that failed, and repairing it without breaking the rest of your system.

Quick Answer

Open Software Updater, read the detailed error to find which repository failed, then open Software & Updates and untick or remove that broken source. Run sudo apt update in a terminal to confirm the error is gone. If the Ubuntu mirror itself is the problem, switch to the Main Server in Software & Updates and try again.

What This Error Actually Means

Ubuntu does not download software from one single place. It contacts a list of repositories, which are servers that hold packages and information about available versions. Software Updater first refreshes that package information. Only after that step succeeds can it show you real updates.

When one repository in the list cannot be reached, returns an error, or no longer matches your Ubuntu version, the whole refresh can be marked as failed. Ubuntu then shows the general message about repository information, even though all the other sources may be working perfectly.

Common Causes Behind the Message

• A third-party PPA was shut down, moved, or never updated for your Ubuntu release.
• A software vendor changed its download server address.
• The mirror server for your country is temporarily offline or very slow.
• Your system clock is wrong, so secure connections to repositories fail.
• An old repository entry still points to a previous Ubuntu codename.
• A proxy or VPN is blocking access to one specific server.

Because the cause is so specific, guessing rarely works. The fastest route is always to read the exact detail hidden behind the short warning.

Step 1: Read the Full Error Message

The short popup hides the most useful information. Follow these steps to see it clearly:

1. Open Software Updater and let it try to check for updates.
2. When the warning appears, look for a Details or Settings button and click it.
3. Read the lines carefully and note any web address that is mentioned.
4. Look for phrases such as Failed to fetch, 404 Not Found, or does not have a Release file.
5. Write down the domain name in that failing address. That is your problem source.

If the popup disappears too quickly, you can get the same information more reliably from the terminal in the next step.

Step 2: Find the Failing Repository in the Terminal

The terminal gives you a complete, line-by-line view of every repository Ubuntu contacts.

1. Press Ctrl + Alt + T to open a terminal.
2. Run the update command: sudo apt update
3. Enter your password when asked. Nothing will appear on screen as you type, which is normal.
4. Wait for the process to finish and scroll through the output.
5. Lines starting with Err or W: point to warnings and errors. The address on those lines is the failing source.

Healthy lines start with Hit or Get. Those repositories are fine and should be left alone. You only need to act on the failing address you found.

Step 3: Disable the Broken Repository

For most people, disabling the broken source in the graphical tool is the safest fix. You are not deleting any installed software. You are simply telling Ubuntu to stop asking that server for updates.

1. Open the Activities overview and search for Software & Updates.
2. Go to the Other Software tab.
3. Find the entry that matches the failing address from your terminal output.
4. Untick its checkbox to disable it, or select it and click Remove if you no longer use that software.
5. Close the window. Ubuntu will offer to reload package information. Accept it.
6. Run sudo apt update again to confirm the error no longer appears.

If the software that used that repository is still important to you, visit its official website later and follow its current installation instructions. Vendors often publish a new repository address when they move servers. Adding the fresh address is better than re-enabling a dead one.

Removing a Broken PPA With the Terminal

If the failing source was added as a PPA, you can remove it cleanly with one command. Replace the example name with the PPA you saw in the error:

sudo add-apt-repository --remove ppa:example/name

After that, refresh your package lists again:

sudo apt update

For a deeper walkthrough of keeping a healthy system, our guide on how to update Ubuntu safely from the terminal explains the update and upgrade commands in plain language.

Step 4: Switch Your Download Mirror

Sometimes the failing address belongs to Ubuntu itself, such as a country mirror like an archive address for your region. Mirrors are copies of the main Ubuntu server, and a single mirror can go offline or fall behind.

1. Open Software & Updates and stay on the Ubuntu Software tab.
2. Find the Download from dropdown.
3. Change it to Main Server.
4. Close the window and allow Ubuntu to reload the package information.
5. Run sudo apt update once more and check the result.

Using the main server can be slightly slower if you live far from it, but it is the most reliable option. Once your local mirror is healthy again, you can switch back if you wish. The official Ubuntu repositories documentation explains how mirrors and software sources work in more detail.

Step 5: Check Your Clock, Connection, and Proxies

If every repository fails, the problem is probably not a single source. Work through these quick checks:

Check the System Clock

Secure repository connections depend on the correct date and time. If your clock is hours or days wrong, certificates look invalid and downloads fail. Open Settings, go to Date & Time, and turn on Automatic Date & Time. Then try updating again.

Test Without a VPN or Proxy

Disconnect your VPN temporarily and try sudo apt update again. Some VPN servers block or cannot reach certain mirror addresses. Also open Settings, go to Network, and check that Network Proxy is set to Off unless your workplace or school requires one.

Restart and Try a Different Network

A simple restart clears stuck network states more often than people expect. If possible, test on another connection, such as a phone hotspot. If updates work there, your router or internet provider may be blocking or failing to resolve one server address.

Step 6: Clear a Corrupted Package List

Occasionally the downloaded repository information on your own computer becomes corrupted. Clearing it forces Ubuntu to download fresh copies.

1. Open a terminal.
2. Remove the cached lists: sudo rm -rf /var/lib/apt/lists/*
3. Download them again: sudo apt update
4. Watch the output. A clean run ends without errors and tells you how many packages can be upgraded.

This step is safe. It does not remove installed programs or your personal files. It only deletes temporary index files that Ubuntu recreates immediately.

Common Mistakes and Useful Tips

• Deleting random repository files: Do not delete files in the sources folders by guessing. One wrong deletion can remove your main Ubuntu sources. Disable entries through Software & Updates first.
• Ignoring the detail line: The short popup tells you almost nothing. Always read the full error or run sudo apt update to see exactly which address failed.
• Re-adding an old PPA: A PPA built for an older Ubuntu release can cause dependency problems. Only add sources that support your current release.
• Mixing release names: If you recently upgraded Ubuntu, check that no source still uses the previous codename. Old entries are a very common cause of this error after an upgrade.
• Assuming your internet is broken: If web browsing works, your connection is probably fine. Focus on the one failing repository instead of resetting your whole network.
• Tip — update weekly: Regular small updates are less likely to hit stale repositories than months of built-up changes. A quick weekly check keeps surprises away.

Conclusion

The “failed to download repository information” message sounds serious, but it usually means just one entry in your software sources list is broken. Read the detailed error, run sudo apt update to confirm which address fails, and disable or remove that source in Software & Updates. If the Ubuntu mirror is at fault, switch to the Main Server, and check your clock and VPN if everything fails at once. With the bad source out of the way, Software Updater should check and install updates normally again.

Frequently Asked Questions

Is it safe to disable a repository in Software & Updates?

Yes. Disabling a repository only stops Ubuntu from checking that server for new versions. Programs you already installed keep working, and you can re-enable the source later if the server comes back.

Why did this error appear right after I upgraded Ubuntu?

Upgrades disable most third-party sources, but old entries can remain or be re-enabled without support for the new release. Remove or update any source that still points to your previous Ubuntu version.

Can I still install security updates while one repository is broken?

Often the broken source blocks the whole refresh, so fix or disable it first. After a clean sudo apt update, run Software Updater again and install all offered updates, including security fixes.

What does “does not have a Release file” mean?

It means the server address exists, but it does not offer package information in the way Ubuntu expects. The source may be shut down, moved, or not built for your release. Disabling it is the correct fix in most cases.

Should I use the Main Server all the time?

You can, and it is very reliable. A local mirror may be faster for large downloads, so use the Main Server as a dependable fallback whenever your regional mirror causes trouble.