Downloading

My download failed or will not finish

Quick answer: It depends on the method: Usenet downloads with missing articles can usually be repaired with PAR2 files, torrents stuck at 99% need a seeder with the last pieces, and file host errors normally mean a limit or a removed link. If one option keeps failing, try another option in the download box.

A download that stops, errors or will not finish is frustrating, especially on a big build. The good news: most failures have a clear cause and a fix. Find your method below.

Usenet (NZB): missing articles and PAR2 repair

On Usenet, a build is stored as thousands of small posts called articles. Occasionally some are missing from your provider’s servers, so your client reports “missing articles” or a percentage of the download as missing.

That is what PAR2 files are for. They are recovery files posted alongside the build, and your client uses them to rebuild missing or damaged pieces. Think of them as spare parts. Good clients (NZB Grab, SABnzbd, NZBGet) fetch the PAR2 files only when needed and repair automatically.

  1. Check the status message. “Repaired” or “Verified” means all is well. “Repair failed” or “not enough repair blocks” means too much is missing for the PAR2 files to fix.
  2. Retry it. Most clients have a Retry option in the history. Temporary server hiccups do happen.
  3. Check your connection settings. Use host news.newshosting.com, port 563 and SSL on. Wrong details show up as failures too.
  4. Check your account is active. An expired subscription makes every download fail.
  5. Try another option in the download box if repair still fails.

If you do not have a Usenet account yet, Newshosting’s Arcade Punks deal is 70% off plus 3 free months, and it is what we test with. More on the basics: Usenet and NZB for beginners.

Torrents: stuck at 99%

A torrent that sits at 99% (or any number) forever is waiting for pieces that nobody connected to you has. No seeders with the full build means no last pieces.

  1. Leave it running. A seeder may come online later, often in the evening.
  2. Force a recheck. In Tixati, right click the transfer and run a check of the files. This can find pieces that are actually fine and fix a stuck count.
  3. Check your disk space. A full drive stalls a torrent near the end.
  4. Check your antivirus has not quarantined part of the download. See antivirus false positives.
  5. Use another option to finish the job.

More in torrents for beginners.

File hosts: errors and dead links

  • “File not found”, “removed” or “deleted”: the link has gone. Try another option and report it with the Missing / Broken File option on our contact page. Tell us the build name and which host failed.
  • Quota or limit messages: you have hit a free user limit. See MEGA and Google Drive quota exceeded.
  • Download stops part way: free browser downloads often cannot resume. A premium account (such as RapidGator premium), the host’s own app, or a download manager like JDownloader will resume instead of starting again.
  • “Network error” in the browser: try again, try another browser, and make sure your download folder has space.

More in RapidGator and file hosts.

It downloaded, but it will not extract

If the download finished but WinRAR or 7-Zip shows CRC errors or “unexpected end of archive”, one of the parts is damaged or missing. You often only need to re-download that one part, not the whole build. See extraction errors.

The golden rule: try another option

Every method has bad days. If one keeps failing, the same build is usually waiting under another icon in the download box. Not every build has every option, but most have several.

Still stuck? Leave a comment on the build’s post saying which method failed and the exact error, or ask in our Discord.

Did this help?