Skip to content
kaspersky beta

beta

  • Register

  • Login

  • Categories
  • KForum
  • KClub
  1. Home
  2. ENGLISH USER FORUM
  3. Home
  4. Kaspersky
  5. Archive
  6. 2021 MR15
  7. Application Control (HIPS, SW, Firewall, IDS, TAM)
  8. Bug with Howard Email

Bug with Howard Email

Scheduled Pinned Locked Moved Application Control (HIPS, SW, Firewall, IDS, TAM)
5 Posts 2 Posters 704 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    tistou
    wrote on last edited by Jarvis
    #1

    <p><strong>Reproduction steps: If Kaspersky is stopped and restarted, by clicking on the Howard Email icon in the systray,, the web page takes more than 1 minute to open, The bug had been reference 6396955 with previous versions and had been resolved with an update of the 21.14</strong></p>
    <p><span></span></p>
    <p><strong>Actual result: The bug reappeared, the web page takes 1 minute to open</strong></p>
    <p><span></span></p>
    <p><strong>Expected Result: The web page should open immediately with Kaspersky re launched</strong></p>
    <p><strong></strong></p>
    <p><strong><a href="https://the-sz.com/products/howard/" target="_blank" rel="noopener">Howard - Outlook.com / GMail / Yahoo / mail.ru / orange.fr / Lotus Notes Email Notifier - the sz development (the-sz.com)</a></strong></p>
    <p><span></span></p>

    1 Reply Last reply
    0
    • JarvisJ Offline
      JarvisJ Offline
      Jarvis
      wrote on last edited by
      #2

      Hello! Bug 6396955 is still open, so there is no need to open another one - it will be closed as duplicate.
      Although, as you say, problem disappeared in 21.14, the fix wasn't made or included in any version.
      I've added new info to 6396955.

      T 2 Replies Last reply
      0
      • T Offline
        T Offline
        tistou
        wrote on last edited by tistou
        #3

        <p>Hello</p>
        <p>Ok, I thought the developers had fixed the problem but support forgot to notify me ('ticket' opened at the start of the year)</p>
        <p>I confirm that the problem was resolved with an update (of the components I suppose) with 21.14</p>
        <p>I went back with 21.14 while waiting</p>
        <p>Thanks</p>

        1 Reply Last reply
        0
        • JarvisJ Jarvis

          Hello! Bug 6396955 is still open, so there is no need to open another one - it will be closed as duplicate.
          Although, as you say, problem disappeared in 21.14, the fix wasn't made or included in any version.
          I've added new info to 6396955.

          T Offline
          T Offline
          tistou
          wrote on last edited by tistou
          #4

          <p>Hello @jarvis</p>
          <p>After some tests, I found where the bug in 21.15 comes from</p>
          <p>If the "Application updates schedule setting" option (in "Performance settings") is disabled, the bug appears, if the option is enabled, it's OK</p>
          <p>If your developers can do what is necessary</p>
          <p>Thanks in advance</p>
          <p>EDIT : and for info, I tested the <span>21.16.0.182 build and the problem is not present by disabling this option</span></p>

          1 Reply Last reply
          0
          • JarvisJ Jarvis

            Hello! Bug 6396955 is still open, so there is no need to open another one - it will be closed as duplicate.
            Although, as you say, problem disappeared in 21.14, the fix wasn't made or included in any version.
            I've added new info to 6396955.

            T Offline
            T Offline
            tistou
            wrote on last edited by tistou
            #5

            <p>@jarvis <a href="/user/dmitriy-pisarets" target="_blank" rel="noopener">@dmitriy-pisarets</a></p>
            <p></p>
            <p>Hello</p>
            <p>Could you do what is necessary or "report" the cause of the bug to the appropriate department?</p>
            <p>Customer service tells me that this bug is still under investigation (for 10 months now)</p>
            <p>I informed them of the cause of the bug (easily reproducible) which I found in 48 hours and they responded to me with an email automatically I think, that it is still the subject of an investigation</p>
            <p>Thanks in advance</p>
            <p></p>

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            © 2025 АО «Лаборатория Касперского»
            • First post
              Last post
            0
            • Categories
            • KForum
            • KClub