Jump to content

shocked

Most Valued Members
  • Posts

    485
  • Joined

  • Last visited

  • Days Won

    9

Posts posted by shocked

  1. my guess is that the in-product update (if i'm saying it correctly) updates only the files in the Program Files folder, it doesn't recompile the msi file that is stored in C > Windows > Installer, that's why the repair option was missing after the auto update, and it came back after a clean install.

     

    if that's the case then it might be expected behaviour unless the dev team finds a way to recompile the msi file after a successful in-product update.

  2. 2 hours ago, Marcos said:

    It is not possible to install the same version of the product over an already installed version

    so it's by design. thanks.
    any plans to change that behaviour? completely removing the product in order to repair (if the repair option from the uninstaller/control panel  doesn't help) it is somewhat of time consuming.

     

    @itman after the auto-update i had the same options as your image and from my test by removing/reinstalling it, the "repair" button was returned by doing a complete removal using the safe mode uninstaller.

    and your MSI log entry perhaps is incorrect, mine reports the correct version. i cleared all temp files and started the uninstall just for the window to appear and then i closed it. it reported the correct version.

    Capture.thumb.PNG.a5d79a35119e09a99381cf6a5a102409.PNG

     

     

  3. i downloaded and installed v14.1. everything went fine.
    after running the installer again i noticed that the option to repair the installation doesn't exist, it never existed even on v13 and the previous v14 release.

    is it by design that the installer doesn't have that option and i must perform the repair from the control panel > add/remove programs?

    my local support insisted that this option does exist.

    https://youtu.be/3Y44Q7xY5Z0

     

  4. 10 hours ago, MacLean said:

    Could this be another hack of ESET?

    what do you mean with this statement? Eset doesn't hack people if that's what you mean. if your internet/email provider was hacked, that has to do with their own security programs and protection tactics.

    having an AV installed on your pc can protect your pc/files only, not your internet provider.

  5. i don't think MichalJ was being suspicious, maybe curious as to why need a picture when you could have installed the program. as for the images in the help pages, even most of the pages for EIS don't have images. i suppose it all comes down to if there is a real need for images on all pages.

    21 minutes ago, Serial.com said:

    People are curious to know what they are buying without having to download or install any product first.

    as for this statement, people buy a product for the level of protection it offers, not if it looks pretty or not. personally i liked the UI of v8 and older but i don't mind the new makeover. i bought it for it's protection.
     

  6. On 12/16/2020 at 3:28 PM, shocked said:

    on latest FF when clicking on image attachments on posts to view them, they open in a full screen like mode with no visible X to close them other than clicking the "back" button on the browser to go one page back.

    on latest MS Edge this seem to work as intended. both tests were done with no addons that block scripts or adverts etc.
    the bottom picture is from FF, the image from the post i clicked doesn't "float" like on Edge does.
    after an image is clicked, it will momentarily appear "floating" then it will go to "full-screen mode".

    i can create a video if needed.

     

    1290689922_Screenshot(42).thumb.png.6cc91f4d007741399e9c5fa0732ed44a.png

    -



    426356352_Screenshot(43).thumb.png.02f38aefe136eef803fab1707b715c8c.png



    i return to my post. for the last 2-3 weeks, whenever i click an image from a post, it opens it in the whole tab as if i clicked "open link in new tab". Edge opens it in a floating state with an X to close the image viewer.
    i've cleared the FF history recently.
    as it seems, that bug returned.
    https://youtu.be/evtRhmDemvo
     

  7. today is the first time i've seen ekrn at around 60mb. ever since september when i bought the product it has been steadily at 200mb (some times above or below). 200+- is my everyday normal.

    i started a quick scan and ended it after a couple of minutes, the memory upped to 80-90+ and had stayed there for more than 10-15 minutes.

    i strongly believe there's a memory leak here and it's so random the devs have difficulty finding it.

  8. Marcos will verify that after checking it, but if you didn't buy the key from a legitimate source, it may have been resold to countless other users and eset blacklisted it. that's usually why many users write about it here, you'll find many posts.

    if the key is legitimate and it serves it's purpose as indented, then further info will be required by the dev team.

×
×
  • Create New...