Have you ever opened qBittorrent and found torrents you finished weeks ago showing Checking again?
Sometimes that happens once after a crash and then stops. For other users, it happens every time qBittorrent starts, and a big library can keep the disk busy for hours.
So why does qBittorrent keep rechecking torrents? It usually happens because the app cannot trust what it saved about them. Resume data may be missing or unsaved, the files may not be where qBittorrent expects them, or the drive may not be ready when the app starts.
In this guide, we’ll explain why qBittorrent keeps rechecking torrents, how to tell a full hash check from a quick resume-data check, and how to stop the loop. We’ll cover unexpected shutdowns, external drives, NAS shares, Docker paths, and the settings that trigger extra checks.
If you want to know what happens when you click Force Recheck yourself, read our guide on why a torrent rechecks files. This article focuses on rechecks that keep coming back.
Is qBittorrent Really Rechecking, or Only Checking Resume Data?
The word Checking can describe two different jobs.
- Checking resume data: qBittorrent loads the information it saved about each torrent. This is usually quick, even with many torrents.
- Checking files (hash verification): qBittorrent reads your files from the disk and compares them with the torrent’s piece hashes. This is slow and creates heavy disk activity.
One user on the qBittorrent forum found that all of their completed torrents were only checking resume data. Their Status column was too narrow to show the full label, so it looked like a full recheck.
Before you change anything, widen the Status column and watch the disk. A true recheck reads a lot of data. A resume-data check usually finishes quickly.
Why Does qBittorrent Keep Rechecking Torrents?
Rechecks that keep coming back usually have one of the causes below.
1. Resume data is not being saved
qBittorrent stores a record of each torrent’s progress so it can resume without reading every file. If it cannot save that record, it has to verify the data again at the next start.
Common reasons include a read-only profile folder, a full system drive, antivirus software blocking writes, or a portable installation running from a protected location.
2. qBittorrent closes unexpectedly
A crash, a power cut, or a forced shutdown can leave the saved state behind what is actually on the disk. On the next start, qBittorrent may verify torrents it was working on.
Not every unclean shutdown triggers a full check, but repeated crashes make it more likely.
3. The drive is not ready at startup
If your downloads live on an external USB drive, a second internal drive, or a NAS share, that storage may mount after qBittorrent has already started.
qBittorrent then sees missing files, and the torrents may be checked again once the drive appears. This is one of the most common causes on systems that start qBittorrent automatically at login.
4. The save path changed
A different drive letter, a renamed folder, or a moved download directory makes qBittorrent look in the wrong place. If you moved files in File Explorer instead of using qBittorrent’s Set Location option, the torrent still points to the old path.
An extra folder level is a classic example. A torrent expecting a file at one path cannot find it when the folder name is repeated inside itself.
5. Another program changes the files
Cloud sync tools, backup software, antivirus scans, media managers, and tag editors can modify, lock, or quarantine files that qBittorrent is still sharing.
Even a small change inside a file makes at least one piece fail verification. The torrent then drops below 100%, and qBittorrent may start downloading the damaged piece again.
6. Recheck on completion is turned on
qBittorrent has an option that verifies torrents again after they finish downloading. It adds another pass of disk reading for every completed torrent.
It can be useful on unreliable storage, but it also explains why a torrent seems to check itself right after it finishes.
7. Several torrents share the same files
Cross-seeding the same source files under more than one torrent can cause trouble. After an interruption, one torrent may check fine while another reports missing files.
If you use this setup, make sure each torrent points to the correct folder and that the shared files are not renamed or moved.
8. Docker or NAS path mappings changed
Inside a Docker container, qBittorrent sees paths such as /downloads, which map to a real folder on the host. If a volume mapping, user ID, or mount point changes, the same torrents suddenly look empty.
On a NAS, a share that disconnects, a permissions change, or a different mount path has the same effect. Our guide on running a torrent client on a NAS covers this kind of setup.
How to Stop qBittorrent From Rechecking Torrents
Work through these steps in order. Most users find the cause in the first four.
Step 1: Read the Execution Log
Open View, then Log, to see the Execution Log. Look for messages about missing files, I/O errors, permission problems, or failed attempts to save resume data.
The log often names the exact torrent and the path that caused the problem.
Step 2: Confirm the save path
Select a torrent that keeps checking and open the General tab at the bottom. Compare the Save Path with the real folder on your drive.
If the files moved, right-click the torrent, choose Set Location, and point it to the right folder. Then run one recheck.
Step 3: Make sure storage is ready before qBittorrent starts
If your downloads are on an external drive or a network share, start qBittorrent only after the storage is available.
On Windows, you can remove qBittorrent from automatic startup and open it manually after the drive appears. You can also use Task Scheduler to start it with a delay after login.
Step 4: Close qBittorrent normally
Use File, then Exit, instead of ending the process or shutting down the computer while the app is busy. A normal exit gives qBittorrent time to save its state.
If you shut down often, close qBittorrent first and wait until its window disappears.
Step 5: Check free space and profile permissions
Make sure the drive that holds qBittorrent’s profile has free space. Also make sure your user account can write to the profile folder.
On Windows, the settings usually live in your AppData folders. On Linux, they are usually under your home directory in .config and .local/share.
Step 6: Turn off recheck on completion if you do not need it
Open Tools, then Options, then Advanced, and look for the option that rechecks torrents on completion. The exact location can change between versions, and the official qBittorrent options guide explains each setting.
If you do not need the extra verification, turn it off. For important downloads, our guide on verifying downloaded files with hashes and checksums shows a more targeted way to confirm integrity.
Step 7: Recheck once and let it finish
After fixing the path or the storage problem, run one Force Recheck on the affected torrent and wait for it to finish. Avoid moving or editing the files while it runs.
Resume the torrent only after the check ends. If the percentage drops, qBittorrent will download the missing pieces.
Step 8: Back up the profile before big changes
Before reinstalling qBittorrent, switching versions, or moving to a new PC, copy the whole profile folder.
The folder holds your torrent list and resume information. Without it, qBittorrent has to rebuild everything by reading your files.
What Should You Do If Checking Never Finishes?
A large torrent on a slow hard drive can take a long time to verify, so a slow progress bar does not always mean a problem.
Open Task Manager and look at the disk. If the disk is busy and the percentage is moving, the check is working. If the disk is idle and nothing moves, make sure the drive is connected and no other program is locking the files.
If the whole system becomes slow while checking, our guide on fixing qBittorrent disk overload explains how to reduce the load.
Can You Stop qBittorrent From Rechecking at Startup?
As far as we know, qBittorrent has no setting that skips startup checks completely. Users with very large libraries have asked for one.
The practical answer is to remove the reason for the check. Keep paths stable, keep storage available at startup, close the app cleanly, and make sure resume data can be saved.
When Does Rechecking Point to a Hardware Problem?
Sometimes the cause is not qBittorrent at all.
- A drive that disconnects during heavy use can make files vanish for a moment.
- A failing disk can return read errors during verification.
- A loose USB cable or weak power supply on an external drive can cause repeated drops.
If the same torrents fail every time, test the drive with a health tool from the manufacturer and check the cable and port. Keep a backup of anything important.
Frequently Asked Questions (FAQs)
Why does qBittorrent recheck torrents every time I restart?
Usually because resume data was not saved, the files were not found at the saved path, or the drive was not ready at startup. The Execution Log normally shows which one applies.
Does rechecking redownload my files?
No. Rechecking reads the files you already have and compares them with the torrent’s hashes. Only missing or invalid pieces are downloaded afterward.
Is rechecking bad for my hard drive?
Rechecking mostly reads data. It keeps the drive busy, especially a mechanical hard drive, but it is not a heavy write workload. Repeated checks on a failing drive can still expose existing problems.
Why do all my torrents show Checking after a crash?
After an unexpected shutdown, qBittorrent cannot be sure the saved state matches the files on disk. It may verify torrents again to be safe.
Why did my torrent recheck after I moved the files?
qBittorrent still expected the files at the old path. Use Set Location to point the torrent to the new folder, then run a recheck.
Can I pause a recheck?
You may be able to pause or stop the torrent, but the check will usually be needed again later. It is better to let it finish when the drive is healthy.
Does Force Recheck affect my ratio?
The local check does not upload or download data. Private trackers calculate ratio by their own rules, and a short check normally does not change it.
Why does a recheck show less than 100%?
Some pieces failed verification because files were edited, deleted, or damaged, or the path points to an incomplete copy. Fix the path first, then let qBittorrent download any missing pieces.
Does a NAS or Docker setup cause more rechecks?
It can. Changed mount paths, user IDs, or volume mappings make the same files look missing to qBittorrent.
Why is my torrent stuck at 99% after a recheck?
A few pieces probably failed verification and no reachable peer has them. Our guide on why a torrent gets stuck at 99 percent explains what to check next.
Final Thoughts
When qBittorrent keeps rechecking torrents, it is usually protecting you from data it cannot trust. The cause is often simple: a path that changed, a drive that was not ready, or resume data that never got saved.
Start with the Execution Log, then check the save path and the storage. Close qBittorrent normally, and turn off extra checks you do not need.
If rechecks continue after you fix the setup, look at the drive itself. Repeated disconnects and read errors are worth fixing before they cost you data.
Once the paths stay stable and the storage is ready at startup, most users find that the constant checking stops.
