MarcFL

10.1.219 Released Info and Change Log: hxxp://support.eset.com/news6510/

10.1.219 is now an official release. Info and Change log: hxxp://support.eset.com/news6510/

The update to Pre-Release 10.1.219.0 seems to have resolved the issue.

It's intermittent and random. The freeze happens when opening Firefox and Outlook 2016. Seems to happen more with https but I'm not certain yet. I already tried disabling https protocol filtering. I just installed the Pre-Release 10.1.219.0. I'll let you know if the issue is resolved over the next couple of days. Thanks.

Thanks for info. We're already using OpenDNS (now part of Cisco). Found this at OpenDNS - might be related (we're in Florida). Miami (MIA) re-routed Miami – Re-routed Jul 17, 2017 09:06 AM UTC We will perform scheduled maintenance at our Miami (MIA) data centre. Users will be automatically re-directed to the next closest site without loss of service. https://system.opendns.com/

Eset NOD32 v.10.1.210 is causing random freezing / hanging of applications such as Firefox and Outlook 2016 for up 1 minute. Reinstalling did not help. Disabling Eset helped. I want to downgrade to NOD32 v.10.0.390. Does anyone have a link to NOD32 Version 10.0.390 (64-bit Windows). Update: Eset Tech Support provided the file. Thanks. In the meantime, I'll try Pre-Release 10.1.219.0.

Solution: They only work using UNC. Example: \\SERVER\FOLDER1\*.*

RE: NOD32 9.0.381 Issue: When Scan Network Drives is ON under Real Time Protection, Exclusions under Real Time Exclusions of Mapped Folders does NOT work. Example: The following is added to Setup, Computer Protection, Real Time, Edit Exclusions: F:\FOLDER1\*.* Result: Running an Eicar.com file on the workstation at this location results in an Antivirus detection and deletion. Summary: When Scan Network Drives is On, exclusions of mapped drives or folders does not work! The only way to exclude network shares is to uncheck "Scan Network Drives". Exclusions do not override this as expected. I consider this a bug or at least a warning should be present in exclusions that you can not exclude network drives or folders with exclusions. Thank You.

Undocumented Serious Error 0x1106 and cannot update the virus signature database. This is happening on all of our 15 computers at different locations throughout the USA. Eset Servers are malfunctioning. Please Fix.

The exclusion of file extensions can be placed in 2 locations. In one location, mentioned above, it's easy to overlook the context change when "Scan all files" setting is checked/unchecked. The rep's name was not in the email. Thanks.

My mistake, you can exclude file extensions from any source in Advanced Settings -> Computer -> Antivirus and antispyware -> Real-time file system protection -> Threatsense engine parameter setup -> Setup -> Extensions. Please add desired extensions there that will not be scanned for threats. An ESET Customer Care Representative has updated this case with the following information: Our previous solution does not require that you disable the scan of all files. Please note the difference in wording when the "Scan all files" setting is checked/unchecked: Enabled -> Files with the extensions listed below WILL NOT BE scanned for threats Disabled -> Files with the extensions listed below WILL BE scanned for threats Our recommendation is still add the extensions you want to exclude from scanning (e.g. VHD) to that list while the "Scan all files" setting is enabled. Thank you for using ESET security products, ESET Customer Care North America

Note: This was posted in the home section here by mistake and again posted in the business section here https://forum.eset.com/topic/3861-server-2012-r2-backup-and-eset-nod32-failure-compacting-virtual-hard-disk/ , but the replies occurred here. Note: My original issue with Windows Backup had nothing to do with Eset after all. I am using ESET File Security for Microsoft Windows Server - a product designed for servers: hxxp://www.eset.com/us/business/products/file-windows/ In this product, if you select to exclude *.vhd it automatically adds the drive letter when you click OK: C:\*.vhd D:\*.vhd This strongly implies that if a new drive, say E, is added it will not exclude *.vhd on that new drive. I have not tested this by adding a new drive and going back to exclusions to check if it is added automatically. This should be corrected by Eset, if not just the exclusion section which should technically be listed just as entered by the user: *.vhd --- Exclude any file with an extension of .vhd on any drive, anywhere, any time. NOT: C:\*.vhd D:\*.vhd

Update: This reduced the frequency of the issue, but it still occurs. Not happy with Server 2012R2 Backup.

Solution for Error: There was a failure while compacting the virtual hard disk on the backup location. A device attached to the system is not functioning. Windows Server 2012R2 Backup fails. Solution: You must change real time scan from all extensions to only scan infectable extensions. This should resolve the issue. Note: Excluding the destination backup drive is not effective as a virtual drive is created during Backup. Since NOD32 does not allow exclusions without a specified drive letter, I had to change the following setting in NOD32: Real Time File System Protection, Setup, Extensions. Uncheck "Scan All Files". If Eset would allow blanket exclusions for certian file types, regardless of location, I could have excluded .vhd and .vhdx extensions. Unfortunately, this is not an option in NOD32. Somewhat related Issue that may be of interest: compacting the virtual hard disk(s) may take a long time hxxp://support.microsoft.com/kb/2524602