starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

.!qB files: Not detecting completion. Force Recheck fails. #8482

New issue

Closed

opened 2026-02-21 19:38:27 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-21 19:38:27 -05:00

Owner

Originally created by @a-raccoon on GitHub (Mar 23, 2019).

This bug only applies if you have the option [x] Append .!qB extension to incomplete files.

If you disrupt a torrent's download folder by moving in completed file(s) ...
Or if you move out completed file(s), restart qBittorrent or Recheck the torrent, and then move the completed file(s) back to its proper location again ...
Or if you first move a torrent's file(s) to another location via your operating system, and then you try Setting Location of the torrent to the new location of the file(s) ...

qBittorrent will never show the torrent as being complete, even when you attempt to Force a Recheck. I discovered, this is because qBittorrent is only looking for files ending in .!qB, and is not expecting the files to be actually completed. Even when qBittorrent does know the torrent was completed and does show a completion time.

Work-around: Add the .!qB extension to your file(s) and then Force a Recheck. It will then discover the files and recognize them as completed, and then remove the .!qB extension for you.

Fix Solution: Upon qBittorrent startup and for any (Force) Recheck, check first for the presence of files without .!qB, and (failing that) then check for those same files with the .!qB extension.

This solution should be agnostic to the aforementioned [x] Append .!qB extension to incomplete files setting, since this setting may be turned on or off during the course of a torrent's lifetime, and so .!qB files may or may not be present regardless.

Originally created by @a-raccoon on GitHub (Mar 23, 2019). This bug only applies if you have the option `[x] Append .!qB extension to incomplete files`. If you disrupt a torrent's download folder by moving in completed file(s) ... Or if you move out completed file(s), restart qBittorrent or Recheck the torrent, and then move the completed file(s) back to its proper location again ... Or if you first move a torrent's file(s) to another location via your operating system, and then you try Setting Location of the torrent to the new location of the file(s) ... qBittorrent will never show the torrent as being complete, even when you attempt to Force a Recheck. I discovered, this is because qBittorrent is only looking for files ending in `.!qB`, and is not expecting the files to be **actually** completed. Even when qBittorrent does know the torrent was completed and does show a completion time. Work-around: Add the `.!qB` extension to your file(s) and then Force a Recheck. It will then discover the files and recognize them as completed, and then remove the `.!qB` extension for you. **Fix Solution: Upon qBittorrent startup and for any (Force) Recheck, check first for the presence of files without `.!qB`, and (failing that) then check for those same files with the `.!qB` extension.** This solution should be agnostic to the aforementioned `[x] Append .!qB extension to incomplete files` setting, since this setting may be turned on or off during the course of a torrent's lifetime, and so `.!qB` files may or may not be present regardless.

deekerman

2026-02-21 19:38:27 -05:00

closed this issue
added the
Core
label

deekerman commented

2026-02-21 19:38:34 -05:00

Author

Owner

@tp0 commented on GitHub (Jun 4, 2019):

I found a developer explanation from 2015: https://github.com/qbittorrent/qBittorrent/issues/3890#issuecomment-155138761. Relates to libtorrent and apparently not as easy to fix as it sounds like.

I also reported this 3 years ago #5460 with an easy repro case.

@tp0 commented on GitHub (Jun 4, 2019): I found a developer explanation from 2015: https://github.com/qbittorrent/qBittorrent/issues/3890#issuecomment-155138761. Relates to libtorrent and apparently not as easy to fix as it sounds like. I also reported this 3 years ago #5460 with an easy repro case.

deekerman commented

2026-02-21 19:38:34 -05:00

Author

Owner

@a-raccoon commented on GitHub (Jun 11, 2019):

This problem also presents itself when some files complete within a torrent and then there is a power outage. You will return with an Errored torrent with the status Missing Files. You have to rename the completed files that indicate as incomplete in the Content tab, to include the .!qB extension, and then you have to Force Recheck the torrent. Twice. The first recheck will show a lower % of completeness, and the second recheck will show the accurate completeness(!!!).

@a-raccoon commented on GitHub (Jun 11, 2019): This problem also presents itself when some files complete within a torrent and then there is a power outage. You will return with an Errored torrent with the status `Missing Files`. You have to rename the completed files that indicate as incomplete in the Content tab, to include the `.!qB` extension, and then you have to Force Recheck the torrent. **Twice.** The first recheck will show a lower % of completeness, and the second recheck will show the accurate completeness(!!!).

deekerman commented

2026-02-21 19:38:34 -05:00

Author

Owner

@tp0 commented on GitHub (Oct 31, 2020):

I can no longer repro this on 4.3.0.

Sounds like this might have been the fix in 4.3.0:

BUGFIX: Improve detecting completed files when adding, rechecking or moving a torrent (glassez)

@tp0 commented on GitHub (Oct 31, 2020): I can no longer repro this on 4.3.0. Sounds like this might have been the fix in 4.3.0: > BUGFIX: Improve detecting completed files when adding, rechecking or moving a torrent (glassez)

deekerman commented

2026-02-21 19:38:34 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Oct 31, 2020):

@a-raccoon Can you confirm as well?

@FranciscoPombal commented on GitHub (Oct 31, 2020): @a-raccoon Can you confirm as well?

deekerman commented

2026-02-21 19:38:35 -05:00

Author

Owner

@a-raccoon commented on GitHub (Nov 10, 2020):

I haven't migrated to 4.3 yet, so the best I could do is set up a test scenario like anyone else can. It will be a moment before updating to 4.3.x

@a-raccoon commented on GitHub (Nov 10, 2020): I haven't migrated to 4.3 yet, so the best I could do is set up a test scenario like anyone else can. It will be a moment before updating to 4.3.x

deekerman commented

2026-02-21 19:38:35 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Feb 9, 2021):

@a-raccoon Have you upgraded to 4.3.3? Is this fixed?

@xavier2k6 commented on GitHub (Feb 9, 2021): @a-raccoon Have you upgraded to **4.3.3**? Is this fixed?

deekerman commented

2026-02-21 19:38:35 -05:00

Author

Owner

@ghost commented on GitHub (Jul 30, 2022):

I'm closing this as fixed as OP failed to respond in a timely manner and this issue most likely got fixed in 4.3.0 as I haven't seen any new tickets recently. However if you can still reproduce it with latest version then please comment to re-open the thread.

@ghost commented on GitHub (Jul 30, 2022): I'm closing this as fixed as OP failed to respond in a timely manner and this issue most likely got fixed in 4.3.0 as I haven't seen any new tickets recently. However if you can still reproduce it with latest version then please comment to re-open the thread.