this post was submitted on 09 Feb 2024
29 points (93.9% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54716 readers
229 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What version of Windows? Is this a normal install of Windows or did you do anything different/custom?
Assuming Windows 10/11 try disabling Real-time protection (Virus & Threat Protection / Manage Settings / Real-time protection) at least temporarily during the install.
Also disable any other anti-virus/malware type software you have.
With all of that disabled re-download qBittorrent from the normal download sources https://www.qbittorrent.org/download
When you attempt to run the setup make sure to run it as administrator so it is elevated (do a shift right-click on the setup.exe file & select Run as administrator).
If the install finally works, before you re-enable Real-time protection you should add the installed qbittorrent.exe in the Windows Defender Exclusions and Controlled folder access (Virus & Threat Protection / Manage Settings / add or remove exclusions) and (Virus & Threat Protection / Manage ransomware protection / Allow an app through Controlled folder access). The installed qbittorrent is probably in C:\Program Files\qBittorrent\qbittorrent.exe or wherever your programs are normally installed.
If none of that worked then I'd go with the other commenters, run RAM and hard drive diagnostics & make sure that's all working correctly.
Or maybe your Windows OS install is broken somehow, I'd run sfc and dism in those cases (a bit outside of scope of this community but you can search around for that).
I'd almost put money on it being AV. But I'd also think the installer wouldn't just crash on locked file. That was my first thought too though since I don't believe the qbt executable is signed.
Yup you are correct, another reason that anti-virus/malware type software will mess with the download or execution of the installer.
Based on the current info that's kind of my initial hunch. The installer could crash if the user's anti-virus/malware messed with it. We also don't know if there is other software installed on the system doing things like that..
Otherwise, ruling out other things could be just that Windows itself is possibly borked. The sfc / dism method may fix that. Installers definitely crash when something is wrong with the Windows OS.