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

db0@lemmy.dbzer0.com

sunbrothersco@lemmy.dbzer0.com

dataprolet@lemmy.dbzer0.com

Flatworm7591@lemmy.dbzer0.com

RandomLegend@lemmy.dbzer0.com

qBittorrent install crashes at licence agreement (lemmy.world)

submitted 9 months ago by Mauntra@lemmy.world to c/piracy@lemmy.dbzer0.com

13 comments fedilink hide all child comments

I seem to be completely unable to install qBittorrent as it force closes with no error message when I try to accept the license agreement. So far I have tried turning off the firewall, making an exception for it in Windows defender, disabling reputation based protection, and of course reboots, but nothing works.

I've seen other posts of people with the same issue on other forums but none of them had any solutions. Has anyone experienced this? How does one actually install this program?

you are viewing a single comment's thread
view the rest of the comments

[–] Cinner@lemmy.world 2 points 9 months ago (1 children)

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.

[–] brickfrog@lemmy.dbzer0.com 4 points 9 months ago* (last edited 9 months ago)

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.