Jump to content

Tim_01

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by Tim_01

  1. Dear Marcos and Eset,

    I have few questions and i am not cleared with postings from you in this thread and other threads.

    Our Machines - Windows 10 and ACS not Supported.

    (we go one by one)

    Does ESET Internet Security disable upgrade version 16 to 17 permanently on NON ACS Supported Windows 10 systems 

     

    1. Switching to pre release update channel does ESET will upgrade version 16 to 17?

    2. In upcoming days, weeks, months does On automatic/regular channel upgrade version 16 to 17?

    3. If manual update/forced update "check for the updates" does it upgrade to version 16 to 17?

     

  2. Dear Eset customer care team and @Marcos, PLEASE SEND THIS THREAD/ MESSAGE FOR DEVELOPERS.

    AS I HAVE MENTIONED WE HAVE SEVERAL PCS WITH WINDOWS 10 EARLIER VERSIONS OF WINDOWS 10, DOES NOT SUPPORT ACS (AZURE CODE SIGNING). WE ARE HAPPY TO GO WITH ESET 16.2.15.0 UNTIL PRODUCT LIFE GOING TO END AND STOP UPDATING MODULES/SIGNATURES.

    Example: LAST YEAR WINDOWS XP STOPPED updating and couple of our machines used ESET 9 until signature and modules stopped updating its databases.

     

    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. 

    IT SHOULD ALSO APPLY  IF A USER   MANUALLY UPDATING (CHECK FOR UPDATES - OTHERWISE ISSUE WILL REOCCUR).

    PLEASE SEND THIS TO THE DEVELOPERS SOON AS POSSIBLE.

    THANK YOU,

  3. 8 minutes ago, Marcos said:

    In order to download v16, use the link https://download.eset.com/com/eset/apps/home/eis/windows/v16/latest/eis_nt64.exe, not the one from the KB.

    NOW IT IS WORKING, INSTALLATION IN PROGRESS . AS I HAVE PREVIOUSLY MENTIONED DO I NEED DISABLE APPLICATION UPDATE, BECAUSE I AM SCARED IT WILL AGAIN UPDATED TO VERSION 17?

    I KNOW THAT WITHOUT ACS SUPPORT I CAN'T UPDATE TO VERSION 17, NO ISSUE I CAN STAY WITH VERSION 16 UNTIL END OF THE SUPPORT.

  4. 5 minutes ago, itman said:

    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.

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

  5. 4 minutes ago, Marcos said:

    If you choose to uninstall v17, it's possible to export the configuration also on non-ACS systems:

    image.png

    EIS v16 can be downloaded from https://download.eset.com/com/eset/apps/home/eis/windows/v15/latest/eis_nt64.exe.

     I have exported settings when i am uninstalling version, i have downloaded from your link it shows product version 15.2.17.0? download and see.  I need latest version of 16 please??

  6. 2 minutes ago, Marcos said:

    We haven't released automatic update; it was downloaded only for those who ran update manually. Currently it is stopped except the pre-release update channel.

    We are currently trying to come up with a solution for you so if it's important to keep the configuration and rules, please wait a bit. If it's not important and you can create the rules from scratch, you can go ahead and uninstall v17 and install v16.2.

    Rules are important for me is there are any solution without uninstalling the product and installing again?

    Do i need to stop application update on my other pcs (with Win 10 older versions) because they are also not ACS supported and does it auto updated to 17?

  7. 3 minutes ago, Marcos said:

    If you don't have any custom rules or other settings, uninstall v17 and install v16.2. Otherwise export the settings and import them into 16.2.

    Please note that after December 8 it will not be possible to install ESET on systems without ACS support or at least not without temporarily shifting the system date backwards. This is because Microsoft deprecated cross-signing program: https://support.microsoft.com/en-au/topic/kb5022661-windows-support-for-the-azure-code-signing-program-4b505a31-fa1e-4ea6-85dd-6630229e8ef4.

    in this scenario i do have custom rules but how can i export them because Eset is not opening on my machine?? any suggestions?

    by the way please inform developers to stop this update until the issue been solve, otherwise many pcs will effect from this like mine.

  8. 3 minutes ago, Marcos said:

    Thank you for the heads-up. We have found out that a condition for installation on non-ACS systems was not enabled. We are working on a fix. It should not be possible to install v17 on an outdated operating system unless it supports Azure Code Signing.

    SO PLEASE tell me what should i do now, please go through the topic and replies and guided me sooner.

    as @itman mentioned developers should go it thoroughly before releasing the newer version and indepth scan issue also not fixed yet, more than a month. From my understanding if a new version released basic elements like indepth scan issues should be fixed for a user to test the new product with the scan.

  9. 15 minutes ago, itman said:

    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

    Thank you very much for taking your time and helping me, appreciated. so is it the only option i am having uninstall the product and install it again, is there is a workaround?

    I AM SCARED THAT SAME ISSUE WILL OCCUR AFTER FRESH INSTALL OF VER 16. By the way i can't export  my existing Eset settings because i don't have access to the product.

×
×
  • Create New...