Marcos

Although ESET shouldn't be affected by the infamous problem with mouse lags on Windows 8.1, you might want to try installing this hotfix: hxxp://support.microsoft.com/kb/2908279

These tests have been discussed numerous times. If you want to prevent injections, you can create your own HIPS rules but we cannot block them generally for all users in any environment.

Do you mean that if you leave your computer turned on for more than an hour and there's a newer signature database available, your ESS will not update automatically? Or is it that ESS doesn't update automatically after Windows starts?

Unfortunately, we don't plan to provide Persian version and couldn't find any competitive products in Persian either.

It does what it says. If enabled, the timestamp of files won't be modified due to being accessed and scanned by ESET.

I confirm that the website is blocked with v7, too, after adding 777888p.com* to the list of blocked addresses. Since nothing has changed between v6 and v7 with regard to this, I assume you must have entered the address incorrectly.

Do you have this problem when opening the page in Internet Exporer?

Hello, did you add "*" at the end of the address? Ie. "http//777888p.com/*".

Business edition for OS X Mavericks is going to be released within a couple of days.

ESET doesn't search for Windows updates, it receives a list of available updates from Windows Management Instrumentation.

If you consider the size of all binaries and help files except modules and the engine, they can easily reach ~20MB.

Hello, svchose.exe is not a system process, it sounds fishy. The legit system process is svchost.exe (C:\Windows\System32\svchost.exe) but maybe you made a typo. As for the increased memory consumption by svchost.exe, I don't think that signature updates would cause this, I assume it's rather Windows update which utilizes svchost.exe As for the smart scan, it should be relatively quick. If you don't want to scan inside archives, you can perform scans even quicker. However, since startup scans are run upon every computer start and after every update, I'd consider running on-demand scans on a frequent basis unnecessary. Regarding the statistics, real-time protection scans all files that are accessed by the operating system or 3rd party applications so it's normal that files are continually being scanned. Actually I'd be worried if no files were shown as being scanned : )

There's an option "Log all blocked operations" in the advanced HIPS setup. However, we don't recommend enabling it unless you need to troubleshoot an issue caused by HIPS, otherwise large logs could be generated which would have adverse effect on the overall system performance.

Would it be possible for you to change the password, create a log for us and then change the password back for security reasons? I'd provide you with instructions how to create logs we'll need to troubleshoot the issue.

I'm able to open Google websites as well as other https websites in Firefox 25 and SSL scanning enabled fine. Could you post a screen shot of the warning you're getting?

Outpost firewall didn't work with v7 HIPS on Windows XP due to a bug which was fixed in Windows Vista and newer: We've made a workaround for this in the Anti-Stealth module, however. Please enable pre-release updates and run update manually. Make sure the Anti-Stealth module has updated to version 1055 prior to installing Outpost firewall.

ESET's products support Windows 8.1; support was added some time ago by updating the HIPS and Anti-Stealth modules. You wrote that "The network problems disappeared after disabling: Resident Shield and Web filter". By web filter, do you mean disabling web protection via gui or protocol / http filtering in the advanced setup?

Each HIPS rule has an option "Notify user". When enabled, a notification will pop up whenever a rule is applied.

I wouldn't recommend leaving logging of all operations blocked by HIPS enabled; it serves for troubleshooting purposes when HIPS causes an issue with certain software.

CryptoLocker is a name used by some other vendors, ESET calls it Win32/Filecoder.BQ.

Please download and run the Uninstall tool in safe mode, then install v7 from scratch.

Maybe their server doesn't communicate properly via http. We'll try to reproduce the issue and check the http communication.

Detection for the toolbar (PUA) has been added recently.

We still don't know what exactly was detected. Please post the complete record from your threat log here. Note that ESET didn't detect the file RegSvcs.exe but malware which is injected in this process. File with sha1 2F8ED26EB714B4EFBE5D7A3167E33ADE82C51FD8 cannot be detected because it's been whitelisted for a long time.

1st cleaned object - script.au3 2nd cleaned object - f734d0219... .exe