Jump to content

tistou77

Members
  • Posts

    171
  • Joined

  • Last visited

Posts posted by tistou77

  1. Hello

    I had changed the settings for the VPN in the Microsoft Edge options
    Now that the problem is resolved, I wanted to return to the default settings, but Kaspersky always puts a custom setting (blue icon)

    Capture.thumb.PNG.c0d37c49a0ffa233710e2542aa620ff1.PNG

    Even when deleting the app, it comes back with the blue icon (and no more settings)

    Capture2.thumb.PNG.76799588e9da6a0ea31075b92782f423.PNG

    How to have the default settings ?

    Thanks

  2. 2 minutes ago, Cyanide said:

      

     

    Any updates on this? My Kaspersky got updated to 21.17 few days ago and it started blocking all browser vpn connections, chrome, firefox, edge and brave. Its not conducive for me to keep disabling Kaspersky everytime so I may access the internt through my vpn.

    No updates 2 days ago when I tested, you have to be patient 😉

    • Sad 1
  3. 7 minutes ago, Dmitriy Pisarets said:

    hello! 

    Sorry, but I cannot answer this particular question. I know only that it's not "unnecessary", and it was added on purpose. I don't know which feature or fix caused it. 

    Ok thanks

  4. 13 minutes ago, Dmitriy Pisarets said:

    Hello! Due to difference between service and exe in windows you may see two rows. Yes, they are connected with one exe file, but has different nature: first launcher is exe process, and second is service. Colleagues says, it's correctly.

    Hello

    Thanks for your reply and your help,

    But until version 21.16, there was only 1 "launcher" process, with 21.17, there are 2
    If there is no difference with 21.17 about processes, strange that there is an additional process with 21.17

    21.15 (screen of 21.15 but same thing with 21.16) K21_16.PNG.317212d80b64a5a24aafb1362c60a2c6.PNG

     

    21.17 K21_17.PNG.6274a7fdabf666d6f1572ee15a2808ea.PNG

    What we noticed, when K does an update, scan, etc... a new Launcher process opens and closes at the end of the operation until version 21.16
    With 21.17, this process is still present (no additional process during an update, scan, etc.)
    Those who have the VPN, the VPN processes are still present even when the VPN is closed

    Example with scan

    Scan.thumb.PNG.1140f9e544374e0c496e99c4c66658b6.PNG  

     

    and without scan :

    WoScan.thumb.PNG.3827cab9f3e20fac0a61a39da6160e4e.PNG

     

    And those who use the VPN for example have 3 or 4 more processes even if it is closed
    Until version 21.16, the process was only launched when it was "necessary"
    No need to have processes “unnecessarily” launched 🙂

    So, why did K adopt this “behavior” with 21.17 ?

    Thanks 

    • Like 1
  5. Bonjour

    Ok, avec la version 21.17 de Kaspersky (AV) il y a un bug avec les VPN des navigateurs, etc...
    Peut-être le cas avec VPN Secure aussi

    il faut désactiver l'analyse du traffic chiffré de l'application dans les paramètres de Kaspersky
    Emule dans votre cas (moi je l'ai fais pour Microsoft Edge en attendant le bugfix)

    Si vous pouvez faire des réglages dans l'application, regardez de ce côté là
    Je ne connais pas VPN Secure

    • Like 1
  6. 5 minutes ago, Berny said:

    From an unofficial source 🤔

     

    Indeed, if I did a scan, update, etc..., a new process appeared and disappeared when it was finished (until 21.16)
    With 21.17 the process is present all the time and during a scan, etc... there is no new one

    The best is to have the process launched when requested via scanning, etc... But not all the time

    For 3 or 4 (related to the VPN it seems), probably the processes which are not closed when the VPN is closed
    Unnecessary use of resources I think

    If it's related, of course

    If a developer comes by here to explain this behavior to us 🙂

    • Like 1
  7. 1 minute ago, Xzz123 said:

    that is not correct

    I have not meet such interesting thing

    highly likely to be a bug

    I will install K back tonight than try reproduce

    You don't have this additional process with 21.17 ?

    Afterwards, it doesn't matter in itself, if it corresponds to a new feature (which one ?)
    Or if it's a "bug" and has been fixed

×
×
  • Create New...