-
Posts
36,489 -
Joined
-
Last visited
-
Days Won
1,452
Posts posted by Marcos
-
-
There are 2 problems:
1, You didn't uninstall ESET NOD32 Antivirus and install ESET Internet Security (a trial version). Only EIS and ESSP can create diagnostic firewall logs that can reveal the root cause of the issue.2, No diagnostic logs were included in the package. Prior to running ELC, with EIS installed make sure that you:
- Enable advanced logging under Help and support -> Details for technical support.
- Reboot the system.
- Disable advanced logging. -
Just now, itman said:
I just upgraded to ver. 12.1.34. This module is still missing on my Win 10 x(64) 1809 build. Is this by design?
I can only repeat what I have recently said: The module will be added in the list through a module update soon.
-
I'm sorry but I'm afraid I don't get what you mean. Please clarify and possibly provide a screen shot or two for illustration, if needed.
-
12 minutes ago, howardagoldberg said:
This module is still not listed on the Windows 7 system. Is this expected behavior (12.1.34.0)?
It has nothing to do with the version of the program. It will be added through a module update soon.
-
I think this should be possible only via a scheduled on-demand scan task:
-
Probably you enabled detection of covert channel data in ICMP. We do not recommend enabling this detection since some legitimate applications may trigger the detection. Please disable it:
-
19 minutes ago, Purpleroses said:
So if I don't make any changes to rules etc. Is it alright just to leave it blocking unknown devices? My computer is not at risk with this continuing to block unknown devices? I will just have tons of logs in my network protection.
Not sure what you mean by blocking unknown devices. Do you have advanced logging turned off and logging verbosity set to informative (default) and not to "diagnostic"? What kind of records are being created in your firewall log?
-
Please post one or more screen shots to show us how you created the agent Live installer. Nevertheless, we strongly recommend upgrading to the latest ERA v6.5 since v6.1 is already very old and unsupported.
Also attach the Live installer that was generated.
-
Most likely the person responsible for posting announcements is currently on his way to the US. An announcement about the availability of the new version of Endpoint 7.1 will be posted as soon as possible.
-
Try to generate a fresh Live installer. The paths inside the script should be as follows:
eraa_installer_url="http://repository.eset.com/v1/com/eset/apps/business/era/agent/v7/7.0.471.0/agent_linux_i386.sh"
eraa_installer_url="http://repository.eset.com/v1/com/eset/apps/business/era/agent/v7/7.0.471.0/agent_linux_x86_64.sh"Also I'd recommend upgrading ERA to ESMC or at least to the latest version of ERA 6.5 as soon as possible.
-
Quote
A threat (HTML/ScrInject.B) was found in a file that Microsoft Windows Search Protocol Host tried to access.
There's nothing like that in the logs you provided. The only detections were:
Win32/Bundled.Toolbar.Ask.G pot. unsafe app.
HTML/Refresh.BC -
Please somebody provide network protection advanced log as I requested earlier in this topic.
-
If you use a proxy server, make sure that epns.eset.com can be accessed directly. Connection through a proxy is not possible (https://help.eset.com/esmc_admin/70/en-US/epns.html).
-
I don't need the operation log generated by ELC but the whole archive that was generated.
-
Please carry on as follows:
- download and launch ESET Log Collector
- also select "Quarantined files" in the list
- gather logs and other files
- post the generated archive here. -
1 hour ago, ram1220 said:
People were having issues updating Windows 10 and Eset blamed the customer. After a bit of a heated debate for a while Eset finally admitted their problem and patched the program which fixed the issue.
I was able to find only the following topics concerning issues with Windows updates, however, none of them turned out to be caused by ESET. Therefore I will appreciate if you post links to the issues you were referring to.
https://forum.eset.com/topic/15238-windows-updates-not-installing-using-eset/
https://forum.eset.com/topic/15309-win-update-4093118repeating/
To my best knowledge, we never blamed customers or other companies for issues without a proof and I haven't done so recently either. We are open to constructive discussion and troubleshooting various issues, however, this cannot be done without the help of users who experience issues.
-
I'm not aware of any issues with WSL except the one in the linked topic. The best course of action would be to contact customer care so that the issue is investigated, tracked and possibly fixed if confirmed.
Support for WSL was added 1 or 2 years ago if I remember correctly.
-
Please provide logs gathered with ELC (the whole archive). For an unknown reason there were no pcapng logs in your diagnostics folder (or at least they were not supplied).
-
Here is how to enable advanced logging:
-
I'd start off by:
- gathering and providing ELC logs
- generating and providing a Procmon log from time when the issue occurs
- generating and providing a complete memory dump when the system freezes (https://support.eset.com/kb380)
- raising a support ticket for customer care so that the case is properly tracked. -
If possible, please provide logs generated as follows. Until then we cannot carry on and check what is causing the error:
- enable advanced logging under Help and support -> Details for technical support
- reboot Windows
- reproduce the error
- stop logging
- gather logs with ESET Log Collector and provide the generated archive. -
Please carry on as follows:
1, Temporarily uninstall ESET NOD32 Antivirus and install ESET Internet Security. Activate a 30-day trial version.
2, After updating modules, enable advanced logging under Help and support -> Details for technical support.
3, Reboot the system.
4, Disable advanced logging.
5, Gather logs with ESET Log Collector and post the generated archive here. Also raise a support ticket for customer care so that the case is tracked properly and provide them with the ELC logs as well.After the issue has been sorted, you will downgrade to EAV.
-
-
Please read https://help.eset.com/esmc_admin/70/en-US/support_vdi.html for more information about cloning.
ParentalControl can be uninstalled from children's device without entering PIN
in ESET Products for Mobile Devices
Posted
First of all, please make sure that you have the latest version of Parental Control installed (2.4.22.0). You will find this information in the About section. Here you can also find a handful of screen shots with hints how to improve protection on Xiaomi phones.