Marcos
-
Content Count
22,168 -
Joined
-
Last visited
-
Days Won
945
Posts posted by Marcos
-
-
In order to determine the serial number of a device, connect the device, open the Device Control rule editor and click Populate. Alternatively you can determine it from ESET PROTECT reports after setting the warning severity for particular Device Control blocking rules.
-
I was able to find only a trial license registered with your forum email address. If you have paid for ESET, please provide the public license ID in the form of XXX-XXX-XXX as well as the website through which your purchased the license.
-
Please collect logs as per https://support.eset.com/en/kb6159 and open a support ticket with your local ESET distributor.
-
46 minutes ago, henrik_admiral said:
So basically this means that ESET will always require installation on a clean computer, otherwise it cannot guarantee finding viruses that are not even that new?
That's true for any antivirus, not only specifically for ESET.
-
Several exclusions are not entered correctly. I'd suggest removing all exclusions and adding folders/files by browsing after clicking "..." in the Path field, e.g.
For me it worked and the crack or whatever it was was not detected.
-
Please provide a screen shot of the error as well as logs collected with ESET Log Collector.
-
Please provide logs collected with ESET Log Collector for perusal.
-
22 hours ago, Er1kS said:
@Marcos, See above post. May you help me with this?
Please check your personal messages.
-
Please create 2 advanced oper. system logs and adv. network protection logs, one with protocol filtering enabled and the other with PF disabled. Use the same url/file to test the download speed. To enable adv. OS logging, navigate to Tools -> Diagnostics in the adv. setup.
The esetperf.etl logs will be generated in C:\ProgramData\ESET\ESET Security\Diagnostics. After generating each log and disabling adv. OS logging, rename the file so that it's clear if it was generated with PF on or off. Finally collect logs with ESET Log Collector, upload the generated archive to a safe location and drop me a personal message with a download link.
Note: in order to enable adv. network filtering logging, temporarily uninstall EAV, install ESET Internet Security and activate a 30-day trial version.
-
The license was sold to a person from Afghanistan with the email address r........n@yahoo.com. It expires in 5 days.
What website did you purchase the renewal from?
-
42 minutes ago, henrik_admiral said:
ESET really dissapointed me with this one tho, why do i need to use other anti viruses to delete this virus when i purchased ESET? either way thanks everyone for their help!
ESET actually protected you from getting infected by the malware. Once AV protection is disabled and malware is run, it may be very difficult to remove it and specialized tools must be used.
-
Release date: January 8, 2021
ESET Security for Microsoft SharePoint Server version 7.3.15000.0 has been released and is available to download.
Changelog
Version 7.3.15000.0
- Added: Internal technology improvements
- Added: Compatibility with future Windows Server operating systems
- Added: eShell option to pause computer and hyper-v scan for user defined period
- Fixed: Various eShell fixes and improvements
- Fixed: When the main product view shows "functional" and under Setup/Computer RTP shows "non-functional" (under specific conditions)
- Fixed: Various localization and functional bugs
- Fixed: On-demand DB scan - sites using Host Header are not displayed correctly
- Fixed: On-demand DB scan – scan may fail when a FileNotFound error is returned for a file
- Fixed: On-demand DB scan – Only main sites are displayed in scan dialog when "Direct SQL database access" is enabled
- Removed: Support for Windows Server 2008 due to missing new OS features
Support Resources
Online Help (user guide):
For more information and to download the product, visit the ESET Security for Microsoft SharePoint Server download page or contact your local reseller, distributor or ESET office.
-
If the issue occurs with the latest version of ECS, please collect logs as per https://support.eset.com/en/kb3404 and open a support ticket with your local ESET distributor.
-
Release date: January 8, 2021
ESET Mail Security for IBM Domino version 7.3.14001.0 has been released and is available to download.
Changelog
Version 7.3.14001
- Added: Internal technology improvements
- Added: Compatibility with future Windows Server operating systems
- Added: eShell option to pause computer and hyper-v scan for user defined period
- Fixed: Various eShell fixes and improvements
- Fixed: The main product view shows "functional" and under Setup/Computer RTP shows "non-functional"
- Fixed: Various localization and functional bugs
- Removed: Support for Windows Server 2008 due to missing new OS features
Support Resources
Online Help (user guide):
For more information and to download the product, visit the ESET Mail Security for IBM Lotus Domino download page or contact your local reseller, distributor or ESET office.
-
It's UpdaterService.exe from ESMC v7 which is affected. From what I understood, the file from ESET PROTECT is not affected so upgrade to any future version should work alright.
-
Please provide ELC logs from the machine so that we can check the HIPS rules. Temporarily disabling self-defense and rebooting the machine will work around the issue but it's important to pinpoint it and fix possibly troublesome rules, if there are any.
-
Please switch to pre-release updates to get the latest HIPS module 1403.1 (should be released on standard update servers today)
Should the issue occur with the above HIPS module, carry on as follows:
- create an ekrn dump via adv. setup -> tools -> diagnostics -> click Create
- collect logs with ESET Log Collector and provide us with the generated archive. -
OOBE did not complete. I assume that HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\State does not contain the value IMAGE_STATE_COMPLETE.
We can only recommend installing the OS from scratch.
After installing EFSW I would also recommend:
1, enabling detection of pot. unsafe applications (to detect legit tools that could stop ESET)
2, enable password protection to prevent setting from being modified by unauthorized persons
3, enforce default real-time protection settings via a policy
4, enable SSL filtering
5, consider applying the extra HIPS rules as per https://support.eset.com/en/kb6119 -
You should restore MBR as per https://neosmart.net/wiki/fix-mbr/.
-
If possible, create a bootable SysRescue medium and run a disk scan from there.
-
1 hour ago, edwindb76 said:
I found the Advanced setup, thanks! I send you a link with the files.
Where did you download ELC from? The logs were collected with an old version 3.2 which is not compatible with latest ESET products. The latest version of ELC is 4.1.
Anyways, the problem is that OOBE has completed yet. How was the OS installed? Was it created from an image generlized using Sysprep? Unfortunately we cannot help as it's a problem with the OS and we can only recommend installing the OS from scratch and complete OOBE at the end of installation.
-
9 minutes ago, edwindb76 said:
We are using ESET File Security for Windows Server to protect our servers.
It doesn't matter, just the label is different:
-
-
1 hour ago, edwindb76 said:
I have the same problem on all of our RDS servers (WinSRV2019), any updates about this error?
Please follow my instructions above.
how to unlock USB sticks while using media control policy
in Remote Management
Posted
You must open the Device Control rule editor in Endpoint, not in the ESET PROTECT web console.