mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Bad downloads related to BitLocker. #3045
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#3045
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @noxiouscrow on GitHub (Sep 8, 2015).
Initiating a download to a path on a drive locked by BitLocker results in a bad download after unlocking the drive and resuming download. Tested on a Windows 10 Pro computer with two BitLocked disks. The qBittorent client is version 3.2.3.
To reproduce:
1- Set default download path to a BitLocked drive.
2- Click on a magnet link for video content to initiate download.
3- Start downloading. I/O error will appear.
4- Unlock the BitLocked drive.
5- Resume download.
6- After content is downloaded, try to run the video and it won't start at all.
Workaround for the issue:
Simply force recheck on the download and it should fix it.
@ngosang commented on GitHub (Sep 17, 2018):
We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.