qBittorrent 4.2.1 crashes on launch (Windows 10).

[zero5zero6zero7]

qBittorrent version and Operating System

qBittorrent 4.2.1 under Windows 10 (1809)

What is the problem

When I launch the app, it doesn't open (it was opening initially). I get following error in Event Log:

Faulting application name: qbittorrent.exe, version: 4.2.1.0, time stamp: 0x5df96484

Faulting module name: qbittorrent.exe, version: 4.2.1.0, time stamp: 0x5df96484

Exception code: 0xc0000005

Fault offset: 0x000000000087f393

Faulting process id: 0x1494

Faulting application start time: 0x01d5b6589a3ee849

Faulting application path: E:\Torrents\qBittorrent\qbittorrent.exe

Faulting module path: E:\Torrents\qBittorrent\qbittorrent.exe

Report Id: 06d5c240-53df-4a68-a11c-7cdd5372ebca

What is the expected behavior

Should launch.

Steps to reproduce

No idea.

Extra info(if any)

Thought this crash was because of Comodo 12.1.0.6914, I downgraded to Comodo 12.0.0.6882 and this issue persists. I've been using previous qB versions just fine with Comodo so not sure if this is because of Comodo or not.

[Chaython]

Why comodo? Anyways I'm unsure of 1809, I'm currently on 1909, no issue. 0xc0000005 is usually AV related. Completely disable comodo see if it works.

[zero5zero6zero7]

Cause Comodo is the best Firewall/AV combo I've ever used. Have been using it for more than 8 years now.

Anyway, tested it with Comodo 6882, had same issues. Went back to qB 4.20 for now and the problem seems to have gone. Seems to be an issue with 4.2.1 only.

[Chaython]

Does comodo have a feature to block applications from launching? Like kaspersky's application control? Or something that checks signature etc? Did comodo report anything? Anyways I had false positives w/ qbittorent and malwarebytes before. Because the certificate/hash[i forget] had changed from what mwb expected... it was fixed by MWB after reporting that the update had the new certificate/hash[i forget]

[zero5zero6zero7]

Comodo blocks apps when they are detected as malware/virus/spywayre, but you can unblock and let them be.

It doesn't detect the new qB version as any of those. Anyway, went back a version and things have been fine. Can launch app without any issues, it doesn't crash, no Event Log message.

It could've been the new Comodo version issue, but I went back a version and problem persisted with new qB release. So I don't think it was Comodo.

[radoborisov]

Hello, Using qbittorent since 2 years. 2 weeks ago put it on A newly installed pc with windows 10 pro 64 bit Intel g4900, 16 gb ddr4 kingstone hyperX, m.2 ssd 128 gb lite on, 5 x 4 tb seagate iron wolf using them in raid 5 like a storage pool created in windows, nvidia 1030 silentfx.

No problems until yesterday. After try to install 1030 gpu, the board didnt recognized it /Asrock z370m-ITX/ac/ so made a bios update, but noticed that after 10 min of working qbittorrent exit itself with no notification at all. This happened on 4.2.0 and managed to update it to 4.2.1, but with no success. Still exits from nothing. There are 167 torrents seeding with capacity of 2 tb. The biggest one is around 120 gb.

Please, it looses all the info about the newly added torrents and start them from the beginning every time.

Thanks in advance!

[radoborisov]

So... I noticed that it don't start with system start, beside that the mark is checked. Unchecked, restarted pc, checked, restarted pc. Now working for 3 hours with no problem :)

[zero5zero6zero7]

qB losing all progress info for torrents is a constant issue for me no matter which release. If you Google it, you'll find that the issue with finished torrents being rechecked from start has been a issue for years. Weird.

[washere]

Basically Comodo blocks qBittorrent. Just spent an hour to trace the issue.

Exiting Comodo will not help as it enters it's list into Windows or it's firewall settings.

Entering qBittorent as an ALLOWED APPLICATION (Settings: Firewall: Application Rules) as either Ruleset/Custom_Ruleset as Fully Allowed (TCP/UDP both ways i/o) will not help either.

To get it working, set:

Settings: Firewall: Firewall Settings to Training Mode (most users are in Safe Mode)

Then qBT will launch and show up

Unfortunately it will not train (show dialog_Box pop-up to ask if qBT is ok or not for future setting)

So you got to keep Comodo in Training_Mode.

Been using Comodo for nearly two decades. qBT is the best, and even better now with dark themes. Was using qBT dark fork (qBittorrent-installer by suratovvlad) until recently. This is a bug that either qBT team or Comodo team has to fix. Shame.

[FranciscoPombal]

Closing as not an issue with qBittorrent - we can't do or guarantee anything about other software that tries to manipulate qBittorrent in ways it shouldn't.

[radoborisov]

Thanks.

On 4.4.2020 г. 02:28 ч., washere wrote:

Basically Comodo blocks qBittorrent. Just spent an hour to trace the issue.

Exiting Comodo will not help as it enters it's list into Windows or it's firewall settings.

Entering qBittorent as an ALLOWED APPLICATION (Settings: Firewall: Application Rules) as either Ruleset/Custom_Ruleset as Fully Allowed (TCP/UDP both ways i/o) will not help either.

To get it working, set:

Settings: Firewall: Firewall Settings to Training Mode (most users are in Safe Mode)

Then qBT will launch and show up

Unfortunately it will not train (show dialog_Box pop-up to ask if qBT is ok or not for future setting)

So you got to keep Comodo in Training_Mode.

Been using Comodo for nearly two decades. qBT is the best, and even better now with dark themes. Was using qBT dark fork (qBittorrent-installer) until recently. This is a bug that either qBT team or Comodo team has to fix. Shame.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/11707#issuecomment-608811316, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOC7FA2HFNTPFS4BTIE3ESLRKZWJNANCNFSM4J5CUPYQ.