Jump to content

MarcFL

Members
  • Posts

    170
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by MarcFL

  1. More reports: https://www.ghacks.net/2022/04/14/browsers-are-crashing-with-error-code-0xc0000022-after-installing-the-april-2022-windows-updates/
  2. It's been reported that the April 12 Windows updates are causing issues with browsers with Eset installed: See: https://www.world-today-news.com/windows-update-is-preventing-some-browsers-from-opening/ Also See: https://www.askwoody.com/
  3. Correction: The pages are NOT being blocked. However, Eset is generating numerous warnings when visiting the two example pages: "Address has been blocked": Time;URL;Status;Detection;Application;User;IP address;Hash 2/7/2022 8:46:29 PM; https://dp8hsntg6do36.cloudfront.net; Blocked; Internal blacklist; C:\Program Files\Mozilla Firefox\firefox.exe; Computer\user; 65.8.181.47; 80ED756A35A9A476EB64B7F5C9028F1266FB1D52
  4. "Internal blacklist" blocking arstechnica.com Example 1: https://arstechnica.com/cars/2022/02/nissan-is-ending-engine-development-except-for-us-bound-vehicles Example 2: https://arstechnica.com/tech-policy/2020/02/facebook-google-would-have-to-share-more-data-under-new-eu-plan/
  5. Maybe Eset should fix this? This is the only way right now to upgrade your license from say NOD32 to Smart Security Premium or Internet Security: Login to : https://login.eset.com Select your license and open it Click on the icon with the two up arrows (upper right corner)) and select Upgrade. Upgrade and pay for your license. NOW you can assign the upgraded license either online or by following these instructions in the Eset application (Change products after installation): https://support.eset.com/en/kb6584-change-your-eset-windows-home-product#after
  6. "Marcos posted a couple of days ago that ver. 14.2.23 was pulled from the Eset update servers due to a technical issue." THANK YOU. "How did you verify this download was indeed ver. 14,2.23?" I ran it, and in the lower left corner of the splash screen was the version number.
  7. NewbyUser, No that's version 14.2.19. However, this mislabeled 14.2.10 offline installer is actually 14.2.23: https://support.eset.com/en/kb2885-download-and-install-eset-offline-or-install-older-versions-of-eset-products
  8. Eset NOD32 version 14.2.19 will NOT update to the latest version 14.2.23, even after clearing the update cache, on several Windows 8.1 machines. This is an Eset bug that needs to be addressed. Manual download and install is also NOT possible, because the newest installer is STILL version 4.2.19 or older. Please address. Thank You. https://support.eset.com/en/kb2476-upgrade-your-eset-windows-home-product-to-the-latest-version#download https://support.eset.com/en/kb2885-download-and-install-eset-offline-or-install-older-versions-of-eset-products
  9. Thanks, I realized that after I posted. I guess I was being annoyed with notifications about startup item changes, which can be disabled separately. I appreciate your help.
  10. Thanks Marcos. That's a bummer. I guess it's a feature request or perhaps a design flaw. Our goal: Not be annoyed by informative popups, such as definition updates, BUT be notified when a custom HIPS rule blocks something.
  11. It would be a very good idea for you to report the bug as well. The more they get, the more likely they will fix it. You can report the bug in two ways: 1. Through Eset: Just open Eset NOD32 and click on Help & Support, Submit Support Request; or 2. At this website: https://www.eset.com/int/support/contact/ Thanks.
  12. Thanks for your reply. The notifications should display when minimum verbosity is set to Warning as I explained. I have no desire to set it to Diagnostic or Informative as a workaround. I hope Eset fixes it.
  13. Reported this bug to Eset: BUG REPORT Details: My custom HIPS rules are set to "Notify User" and Logging Severity set to Warning. Under Desktop Notifications, Minimum Verbosity of events to display - It is also Set to "Warning". Bug: No desktop notifications appear when a HIPS rule is triggered. But they should appear because "Desktop Notifications, Minimum Verbosity" is set to Warning AND the HIPS rule is also set to Warning. Note: If Desktop Notifications, Minimum Verbosity is set to Informative, HIPS notifications appear. See Attached Screenshots and Forum post with all the details of this bug: https://forum.eset.com/topic/28730-hips-notify-user-not-working/
  14. Found the Bug! Desktop Notifications, Minimum Verbosity of events to display: If Set to Warning, no notifications appear. If set to Informative, notifications appear. HOWEVER, if you look at my HIPS rules above, they are set to Warning. Therefore, if Minimum Verbosity is set to Warning, notifications should display - but they don't. This is bug.
  15. Here are some screenshots. The rules work fine, just no Eset Notifications. I've tested this on a few different systems with NOD32 - same results - no Eset notification. Bug or am I missing something? Thanks for your input.
  16. When a HIPS Deny rule is created, and "Notify User" is turned on, a display a notification does NOT appear when the rule is triggered. Bug? Thanks. See: https://help.eset.com/eav/14/en-US/idh_hips_editor_single_rule.html?idh_hips_editor_single_rule.html
  17. Agreed. Poor decision. But it's done.
  18. Updating Eset NOD32 to the new version 14.1.19 fixes this issue. You will be prompted to login to your license manager account by Eset NOD32 in Windows after the update is installed and you reboot.
  19. Thanks. I tried it on one my accounts and stills says "not connected". Eset NOD32 v.14.1.19 update was just released and is prompting to install. The release notes say: Added: support for device association with myESET Hopefully it will be fixed once I update.
  20. I don't have anti-theft. I have several online accounts and they all have the same bug. The new license manager is broken and needs repair. It should never have been rolled out without proper testing. I submitted a ticket. The reply was: Please be assured that your comments have been shared with the appropriate parties and formally noted for further review.
  21. BUG in new license manager online: my.eset.com/licenses The new license manager does not work properly! When you open a license and view the devices they now ALL say: Not active for more than 2 weeks Not connected Not active Before your change in the license manager, this worked properly. Please report this bug so it can be fixed. Thank You.
  22. I sent you a private message. Thank You Marcos.
  23. Same Here. I purchased Eset DIRECTLY from Eset. Thanks for looking into this Marcos. In my case, the setting "Display Marketing Messages" was set to a question mark "?" (center of slider).
×
×
  • Create New...