Jump to content

itman

Most Valued Members
  • Posts

    12,195
  • Joined

  • Last visited

  • Days Won

    320

Posts posted by itman

  1. 11 minutes ago, Pete12 said:

     5. Import Eset settings if previously exported." ...........have only the settings of the 17-version , can we use them on the new installed 16-version also ?

    Should not be a problem as far as I am aware of. At least one poster has done so: https://forum.eset.com/topic/38725-eset-internet-security-not-working-after-17015/?do=findComment&comment=175524 .

  2. 41 minutes ago, Pete12 said:

    Can you , please, tell me how(?) to roll back to previous ESET Internet Security 16.2.15 ?

    You can't "rollback" to ver. 16.2.25.

    1. Export existing Eset 17.0.15 settings if customization made from Eset default settings.

    2. Download ver. 16.2.15 from here: https://support.eset.com/en/kb2885-download-and-install-eset-offline-or-install-older-versions-of-eset-products . Scroll down to this web page section, Earlier versions of ESET Windows home products, and select ver. 16.x for the Eset product you have installed.

    3. Uninstall Eset ver. 17.0.15. Reboot necessary after uninstall.

    4. Install Eset ver. 16 previously downloaded.

    5. Import Eset settings if previously exported.

     

  3. 17 minutes ago, Pete12 said:

    Windows 11 ( 23H2 , Dutch ) ..?? 

    This does clarify the problem might only be related to Win 11.

    Another posting of note: https://answers.microsoft.com/en-us/windows/forum/all/receiving-event-id-18-19-and-error-with-thumbprint/c34478a9-c7e5-4631-b9a5-37eacb8b0d36?page=1

    Quote

    The Windows Security Center Service was unable to load instances of AntiVirusProduct from datastore.
    The Windows Security Center Service was unable to load instances of FirewallProduct from datastore.

    The only way this poster was able to resolve the issue was to revert back to Win 10.

  4. 19 minutes ago, Tim_01 said:

    AS FAR WINDOWS 10 GOES WITH MISSING SUPPORT FOR ACS WE WOULD LIKE TO SUGGEST DEVELOPERS  NOT TO AUTO UPDATE TO VERSION 17, 17+ VERSIONS WHEN UPDATING THE PRODUCT SIGNATURES/MODULES OF ESET VERSION 16. BECAUSE YOU HAVE SEEN WHAT HAS HAPPENED TO ONE OF MY MACHINES. 

    This has already been acknowledged here: https://forum.eset.com/topic/38725-eset-internet-security-not-working-after-17015/?do=findComment&comment=175486

  5. Assume Eset has temporarily suspended ver. 17.0.15 upgrades by all in-product methods until recently posted issues have been resolved.

    Appears however you can still download here: https://support.eset.com/en/kb2885-download-and-install-eset-offline-or-install-older-versions-of-eset-products?ref=esf . Do so at your own risk.

    -EDIT- Looks like off-load download link is also down.

     

  6. 14 minutes ago, Tim_01 said:

    I have done couple of times please download Eset Internet Security 16. after downloading see properties of the file. no luck

    You are indeed correct. The web site is downloading ver. 17.0.15;

    Eset_Download.png.e9e07d7f1a45cb9411dc28c377de1403.png

    Looks like Eset can't do anything right lately.

    Problem might be the download is coming from the Eset International web site which doesn't seem right.

     

  7. 8 minutes ago, Tim_01 said:

    as i have stated previously version 16 is wrong.

    Open this link: https://support.eset.com/en/kb2885-download-and-install-eset-offline-or-install-older-versions-of-eset-products?ref=esf .

    Scroll down in the web page to the section named, "Earlier versions of ESET Windows home products." Select ver. 16 there for the Eset product you have installed.

  8. On your other Win 10 Pro devices, you can block Eset auto upgrading to ver. 17 per below screen shot.

    On the device with Win Device Manager issue, your only option is;

    1. Export your existing Eset settings if modifications from defaults settings made.

    2. Uninstall ver. 17.

    3. Download and install ver. 16 from here: https://support.eset.com/en/kb2885-download-and-install-eset-offline-or-install-older-versions-of-eset-products .

    4. If previous Eset settings exported, import those settings into ver. 16.

    Eset_Product.thumb.png.b45a6c90548122cb6435669ef9e57ff6.png

  9. This is a strange one.

    According to Microsoft, Device Guard is only now being used in HVCI - memory integrity processing: https://learn.microsoft.com/en-us/windows/security/application-security/application-control/introduction-to-device-guard-virtualization-based-security-and-windows-defender-application-control . Otherwise, WDAC in Win 10 Pro handles everything.

    I don't have WDAC enabled on my Win 10 Pro x(64) 22H2 build. This might be the explanation why I didn't encounter the issue in my previous testing of ESSP ver. 17.0.13. However at the end of that testing, I was getting system lockup after system startup as describe here: https://forum.eset.com/topic/38669-ver-1703-secure-search-issue/?do=findComment&comment=175389 . Hence, my recommendation not to release ver. 17 to production which Eset ignored.

  10. 17 hours ago, eornate said:

    Currently in my case, my customer paid for license ESET and still now he can not install Eset product on his server with problem update the KB5006728 ( although i tried update all KB on this guide October 12, 2021—KB5006728 (Security-only update) - Microsoft Support ,)

    As noted in this long thread on the issue: https://forum.eset.com/topic/38667-can-not-install-kb5006728-on-win-2008-r2-sp1/ unless the Win Server 2008 R2 customer has ESU, it will not be possible to apply KB5006728 to it.

×
×
  • Create New...