Log in

RetroArch Online Updater not working — core list empty or download fails

High4 solutions

RetroArch's Online Updater is how most users install and update cores (the individual emulator plugins). When it shows an empty list, a connection error, or downloads that silently fail, you cannot install any emulator — making RetroArch appear broken on first launch.

Common symptoms that bring users here:

  • "Core Updater list is empty" — Online Updater opens but no cores appear. Scrolling shows nothing.
  • "Failed to connect to server" or timeout error — RetroArch cannot reach the buildbot server that hosts cores.
  • "Core downloaded but won't load" or checksum mismatch — The download completed but the file is corrupted or partial.
  • "No cores found" after a fresh install — RetroArch was installed without any bundled cores (common on PC, normal on many platforms).

The most frequent root cause on Windows is using an outdated RetroArch installation. In 2023, the buildbot URL scheme changed, and versions older than approximately 1.16 point to dead paths that return empty results. This looks identical to a network error but is fixed by simply updating RetroArch.

Last updated 1 week ago0 users reported this issue9
Sign in to interact

Solutions

solution #1525

update-retroarch-to-current-version (sortOrder=1, isMostHelpful)

The most common cause of an empty core list or "failed to connect" is an outdated RetroArch version pointing to a changed buildbot URL. Updating RetroArch fixes this in most cases.

  1. Check your current version. Open RetroArch → Main Menu → Information → System Information. Note the version number shown next to "RetroArch Version."
  2. Download the current release. Go to retroarch.com/index.php/download on your PC's browser and download the latest Windows installer or the 7-zip package. The current version is shown on the download page. As of mid-2026, versions below 1.16 are known to hit dead buildbot paths.
  3. Install over the existing copy. Run the installer and point it to the same folder as your existing RetroArch. Your configuration, saves, and any already-installed cores will be preserved. If you used the 7-zip package, extract it into the same folder and overwrite the files.
  4. Reopen RetroArch and try the Online Updater. Go to Online Updater → Core Updater. The core list should now populate. If it does not, proceed to Solution 2.

If you installed RetroArch through Steam, update it via the Steam library like any other game — Steam handles the version automatically.

Jul 30, 2026
Was this helpful?0

solution #1526

install-cores-manually-from-the-libretro-buildbot (sortOrder=2)

If the Online Updater still fails after updating, you can download cores directly from the libretro buildbot website and drop them into RetroArch's cores folder. This bypasses the in-app updater entirely.

  1. Find your RetroArch cores folder. Open RetroArch → Settings → Directory → Cores. Note the path shown. On Windows it is typically C:\RetroArch-Win64\cores\ or %APPDATA%\RetroArch\cores\ depending on how you installed it.
  2. Open the buildbot in your browser. Go to buildbot.libretro.com/nightly/windows/x86_64/latest/ for 64-bit Windows (adjust the path for your platform — Mac, Linux, and ARM paths are listed at the top of the buildbot index). You will see a list of .zip files, one per core.
  3. Download the core you need. Each file is named after the core, for example snes9x_libretro.dll.zip for SNES9x or dolphin_libretro.dll.zip for Dolphin. Download the ZIP for the core you want.
  4. Extract the DLL into the cores folder. Open the ZIP and copy the .dll file (Windows) or .so (Linux) into the RetroArch cores folder you found in step 1. The next time you open RetroArch, the core will appear under Load Core and in Core Updater for future updates.

For RetroArch on Android, the process is the same but the cores are .so files stored at the path shown under Settings → Directory → Cores on your device.

Jul 30, 2026
Was this helpful?0

solution #1527

whitelist-retroarch-in-antivirus-and-firewall (sortOrder=3)

Windows Defender and third-party antivirus products frequently block RetroArch's updater from reaching the internet, or quarantine downloaded core files before they can be saved. This produces the same "failed to connect" or silent-fail symptoms as a network problem.

  1. Check Windows Security quarantine. Open Windows Security → Virus and threat protection → Protection history. If you see RetroArch-related files listed as blocked or quarantined, restore them and mark them as allowed.
  2. Add a Windows Defender exclusion for the RetroArch folder. Go to Windows Security → Virus and threat protection → Virus and threat protection settings → Add or remove exclusions. Add the entire RetroArch installation folder (e.g., C:\RetroArch-Win64\) as a folder exclusion. This prevents Defender from scanning or quarantining freshly downloaded core files.
  3. Allow RetroArch through Windows Firewall. Open Control Panel → System and Security → Windows Defender Firewall → Allow an app or feature through Windows Defender Firewall. Click Change settings → Allow another app and browse to retroarch.exe. Enable both Private and Public network access.
  4. Retry the Online Updater. After adding the exclusions, reopen RetroArch and try Online Updater → Core Updater again. If you use a third-party antivirus (Malwarebytes, Kaspersky, etc.), add an equivalent exclusion in that product's settings.
Jul 30, 2026
Was this helpful?0

solution #1528

fix-date-and-time-to-resolve-ssl-certificate-errors (sortOrder=4)

If your PC's system clock is wrong by more than a few minutes, RetroArch's HTTPS connection to the buildbot will fail SSL certificate validation — producing a "failed to connect" error that has nothing to do with your network.

  1. Check your system clock. Look at the clock in the Windows taskbar and compare it to a known-good time source (your phone, for example). Even being off by a few minutes can break SSL on strict servers.
  2. Sync the clock automatically. Right-click the taskbar clock → Adjust date/time → toggle Set time automatically off then on again, and click Sync now. Windows will contact its NTP server and correct the time.
  3. If automatic sync fails, open Command Prompt as Administrator and run:
    w32tm /resync /force
    This forces an immediate NTP sync. If the Windows Time service is stopped, first run net start w32tm.
  4. Retry the Online Updater. After syncing the clock, reopen RetroArch and try Online Updater → Core Updater. If the SSL error was the cause, the core list will now load.

Wrong system clocks are particularly common on dual-boot systems (Windows + Linux can disagree on UTC vs local time) and on older hardware where the CMOS battery is failing.

Jul 30, 2026
Was this helpful?0
Experiencing a different problem?Report a new issue to help the community find solutions.

Comments (0)

No other comments yet. Be the first to share your thoughts.

Sign in to_leave_comment

On This Page