hash checking on relaunch after authenticating bitlocker

[ghost]

qBittorrent & operating system versions

latest w64

What is the problem?

hash checking on relaunch after authenticating bitlocker

1. it cant see the torrents because of bitlocker
2. bitlocker is unlocked but now it wants to recheck them all

It should not recheck the torrents this is a waste of time.

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

No response

[glassez]

2. bitlocker is unlocked but now it wants to recheck them all

Really? Aren't they in the "missing files" state? What do you mean, "it wants to recheck them all"?

[ghost]

A simple restart would make them available again without requiring a recheck. Maybe you should start qBt after unlocking the drive or auto unlock the drive at boot time.

[ghost]

The simple restart does nothing of the sort, apparently it saves a f-ed state for the torrents and they appear f-ed after drive unlock and restarting the app. They appear 0% Checking ...

[ghost]

Please provide steps to reproduce. Because if files are missing at startup it shouldn’t auto recheck.

[ghost]

Reproduce:
1 save the torrent on a BL drive
2 exit app and lock the BL drive
3 run app - on the torrent state will be something of the sort drive is locked
4 exit app and unlock the BL drive
5 run app - it will want to recheck the torrent that was on the BL drive

[glassez]

run app - on the torrent state will be something of the sort drive is locked

What does Log say?

[ghost]

The logs say..

3/5/2022 8:01 AM - File error alert. Torrent: "Ubuntu". File: "E:\Ubuntu.iso". Reason: Ubuntu file_stat (E:\Ubuntu.iso) error: This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel

When qbt start rechecking, after unlock - the logs do not say anything about that.

#16240 seems same

[ghost]

fixed by #17064 and latest libtorrent(2.0.7).