Jump to content
Comet Forums


  • Content Count

  • Joined

Community Reputation

0 Neutral

About george2018

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. this bug finally fixed in new 1.56 build, all the private trackers working again after exiting bitcomet except teamhd.org which banned bitcomet client Core Bugfix: after all trackers in private torrent been replaced, no tracker will be connected when task downloading
  2. this bug is still there in 1.54 new bitcomet build, i tried every combination but download doesn't work after i restart bitcomet client, problem is with dht ipv6 network ulr, i already checked with 1.51 version if you have dht ipv6 network ulr private tracker tasks doesn't work, when i removed it from any private torrent download works again, i altredy checked around 5-6 private trackers not 1-2, my friends have same problem with newer builds, by the way all the standard torrent tasks without private flag are working fine with 1.52-1.54 builds
  3. well no more false trojan warnings in new 1.54 build but 1.52 bug with private trackers remains, i don't know about other users but with ipv4 connection i cannot continue to download any private torrent task after i restart bitcomet client, i checked many torrent trackers and none is working with private flag, 1.51 version works fine as well as older ones, can you at least add option to remove dht ipv6 network url from private trackers, otherwise it won't download anything and i'm stack with 1.51 build as well as many other users who still use ipv4 protocol and private trackers with bitcomet client
  4. well after fresh windows 10 1809 installation i installed 1.51 and then installed KIS 2019 with D patch, so far no more false trojan warnings, i don't use 1.53 version because it has some problem with private trackers, 1.52 has same problem https://www.cometforums.com/topic/12800244-152-torrents-corruption/ i think it's something to do with dht ipv6 network url which introduced from 1.52 build
  5. yes KIS 2019 treats bitcomet.exe as trojan and deletes it after some time even after adding it in threats and exclusions i rather stay at 1.45 version, it's working fine and there's no false trojan warnings, i check again 1.51 version in KIS 2020 when they release final version, maybe they fixed it
  6. no it keeps deleting some files: since 1.46 version it deletes even installation exe file, last version is 1.45 that installs fine without deleting anything, so KIS 2019 and maybe some other antiviruses changed something in their latest virus definitions that prevents using bitcomet 1.46-1.53 builds, even it is false positive and there's no actual virus or trojan
  7. well KIS 2019 started deleting bitcomet.exe file even after adding it in threats and exclusions (using 1.51 version) , i think i switch to 1.45 version as well, there's no such problem, well it treats 1.46-1.53 versions as adaware and doesn't like fusion.dll file in those versions, i even cannot install those version when KIS 2019 is running, i think they changed this recently, because i was using 1.46-1.51 since they were released and never had any problems with them using KIS maybe it's something to do with the installer, i will try zipped version as well and report back
  8. well it has only avast advertisement on start page, i just removed start page tab and it disappeared, maybe some antiviruses treat it as adaware, in past they had different advertisement on start tab
  9. in C:\Users\username\AppData\Roaming\BitComet\torrents folder
  10. yes i had same problem, just false positive, you should add bitcomet.exe in threats and exclusions not only kaspersky some other antivirus programs treat it as virus, i think this happened after i installed 1.53 update, before that it was working fine, i tried older builds and they doesn't have this problem, 1.45 was fine
  11. i had same problem, KIS 2019 deleted bitcomet.exe after installing 1.51 build, adding it in threats and exclusions helped, then i changed some tab settings and removed threats and exclusions rule and warning message disappeared, it was some kind of adaware not-a-virus, i think just false positive, before that i never had any problems using 1.51 build
  12. i have same bug since 1.52 version, well when i run any torrent from private trackers at first it's working fine, after i quit bitcomet and enter again there's no connection, this happens with any private torrent, i think DHT IPV6 network URL is the problem, when i installed 1.51 version and removed DHT IPV6 network URL private torrent download is working again, so at the moment i cannot use latest bitcomet version for private trackers, all the torrents without private tracker flag is working fine with 1.52-1.53 builds, i know that some private trackers block bitcomet client but this is not the case, every private torrent working fine using 1.51 build, torrent trackers that i used so far: rutracker.org (with some older torrents with private flags) https://bluebird-hd.org https://www.torrentleech.org https://www.torrentday.com/ port is green and at first it's working fine, but there's some problem after quiting bitcomet and resuming downloading i never had any problem before using private trackers in older bitcomet builds, this bug started only after IPv6 DHT Tracker support added in 1.52 build i have already uploaded screenshots in this topic
  13. well when i turned on bitcomet 1.51 today green light returned again, i haven't changed anything, you don't need to download anything port opens without downloading now, yesterday i update java runtime, but maybe internet provider changed some settings, well problem started after i installed 1.52 build, before that i never had any problems and port always stayed green
  14. lol, green light returned again using bitcomet 1.51 build, but problem with private trackers remeins on 1.52 build
  • Create New...