Jump to content

Marcos

Administrators
  • Posts

    36,137
  • Joined

  • Last visited

  • Days Won

    1,439

Posts posted by Marcos

  1. 10 hours ago, QuickSilverST250 said:

    I have some apk files i want to check but to exceeds the limit so will email a wetransfer link for them

    Is it detected by other vendors or it exhibited suspicious behavior when you installed the application? It is not that an arbitrary file can be submitted and it will be analyzed by humans. We need to know what makes the file suspicious to you. Moreover, if only a link is submitted the file cannot be pre-processed automatically for analysts.

  2. Just now, Zardoc said:

    Why is this taking so long? Even if this is not a serious issue it just makes Eset loose credibility on a lagging issue.

    I have around 40 licences circulating and my customers don't like problems especially with their anti virus.

    That's because it's somehow related to the recent certificate change (SHA2->ACS) and it requires cooperation with Microsoft to figure out the root cause.

  3. We've checked all the files you've supplied. There was only one trivial JavaScript downloaded that has been added: JS/TrojanDownloader.Agent.AAOS trojan.  Nevertheless, the payload () has been detected as PowerShell/TrojanDownloader.Agent.HLI trojan since February 12.

    The other files are not subject to detection.

  4. Is ESET correctly registered in the Security Center? There are error like these in the system application log

    The Windows Security Center Service was unable to load instances of AntiVirusProduct from datastore., 08/02/2024 12:00:24
    The Windows Security Center Service was unable to load instances of FirewallProduct from datastore., 08/02/2024 12:00:24

    Message, Date
    Faulting application name: wmiprvse.exe, version: 10.0.19041.3636, time stamp: 0x71c3372a
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0x80131623
    Fault offset: 0x00007fff9252200f
    Faulting process ID: 0x2f00
    Faulting application start time: 0x01da5a88c604f1c1
    Faulting application path: C:\WINDOWS\system32\wbem\wmiprvse.exe
    Faulting module path: unknown
    Report ID: c08a42dc-4259-4926-b81c-e9e550a4252f
    Faulting package full name:
    Faulting package-relative application ID:, 08/02/2024 12:17:25

    Could you try to rebuild the WMI repository to make sure that those errors do not occur and wmiprvse.exe doesn't crash?

    https://techcommunity.microsoft.com/t5/ask-the-performance-team/wmi-rebuilding-the-wmi-repository/ba-p/373846

  5. We use Windows Installer msi packages which means that if an important related registry value has been removed in the mean time, standard uninstallation by Windows Installer may fail. This doesn't happen normally, especially not on home systems that are not in a domain where installation was not done via GPO. One could hardly find a report of a failed uninstallation from other users in this forum. If there's a problem uninstalling ESET for whatever reason, we have the ESET Uninstall tool for use in safe mode.

    If the problems with network occurred after running the ESET Uninstall tool, we'd like to bring this notice to your attention:

    https://support.eset.com/en/kb2289

    Back up network adapter settings

    After using the ESET Uninstaller tool, you may be required to reinstall your network adapter drivers. Follow the steps below to back up your network adapter settings and restore them after uninstallation is finished:

    1. Before running the Uninstaller Tool: Open an administrative command prompt and type the following command to back up your network adapter settings:
      • netsh -c interface dump > C:\NetworkSettings.txt
    2. After uninstallation is complete: Reinstall your network adapter drivers if necessary and then open an administrative command prompt and type the following command to restore your network adapter settings:
      • netsh -f C:\NetworkSettings.txt
×
×
  • Create New...