geosoft

I still say that ESET needs a touch friendlier user interface thanks to proliferations of ultrabooks with touch screens.

The last number in the version format is wave releases. Typically for new language translations. There isn't bug fixes in wave releases. There isn't much point in worrying about that version number.

This is true. I have 4 computers, 3 on Windows and 1 on Mac. The only problem I'm having is a known issue with the Mac 6.0 where a product upgrade will be coming soon. As for the updates, this is what I have while running Pre-Release update server. Virus signature database: 9739P (20140429) Rapid Response module: 4031 (20140429) Update module: 1051 (20140409) Antivirus and antispyware scanner module: 1425 (20140402) Advanced heuristics module: 1148 (20140407) Archive support module: 1198 (20140422) Cleaner module: 1087 (20140317) Anti-Stealth support module: 1058 (20140130) Personal firewall module: 1197 (20140411) Antispam module: 1027 (20131119) ESET SysInspector module: 1240 (20131202) Real-time file system protection module: 1009 (20130301) Translation support module: 1145 (20131121) HIPS support module: 1125 (20140410) Internet protection module: 1113 (20140312) Web content filter module: 1033 (20140219) Advanced antispam module: 1697P (20140428) Database module: 1058 (20140319)

Really? Not for me. Only the first 2 Modules. All others are outdated. Some Modules are Updated last 2013. Whats wrong with my Setup? Signaturdatenbank: 9737 (20140429) Soforteinsatz-Modul: 4029 (20140429) Updates: 1047 (20131023) Viren- und Spyware-Schutz: 1425 (20140402) Advanced Heuristik: 1148 (20140407) Archivunterstützung: 1195 (20140402) Säuberungstechnologie: 1087 (20140317) Anti-Stealth-Unterstützung: 1058 (20140130) ESET SysInspector: 1240 (20131202) Echtzeit-Dateischutz: 1006 (20110921) Lokalisierungsunterstützung: 1145 (20131121) HIPS-Unterstützung: 1125 (20140410) Internet-Schutz: 1113 (20140312) Datenbank: 1057 (20140312) Not all modules needs to be updated. The updates are for performance improvements, enhanced detection, or fixes to the modules itself. For example, take the Updates module. It hasn't been updated since 2013, but that doesn't mean there's something wrong with it. The module itself is working properly and as expected. Why fix something that isn't broken? Also, modules sometimes go through an internal testing procedure before being released to the general public or the pre-release update server. This is just to ensure the fixes or performance improvements are working properly before being released. This typically means that the module will have the date that the module was created, not released to general public. So to see these updates, take a copy of these modules and then wait a week and compare the release versions to see if there has been changes. Finally, there are several ESET modules hidden in the background that gets updated that are not displayed on the "About ESET" box. The Rapid Response module was one of those modules that was hidden once upon a time, but was recently displayed in the about box so people can see the version updates. Typically used for troubleshooting.

As far as I know, ESET makes use of the certificate store within Windows to manage/detect SSL traffic, therefore wouldn't be affected to heartbleed.

I haven't had a kernel panic while running on version 6, but just have problems with the esets_proxy service. The process seems to stutter and takes long time to render web pages over time to the point where the service just locks up and no longer processes data. This does not block me from viewing webpages with any web browser, but the proxy service is clearly no longer filtering data anymore. I can 90% guarantee that the service will crash after waking up from sleep mode. If I manually kill the esets_proxy, it's able to revive and start processing again. It's more of an annoyance.

I would also suggest disabling HIPS and restarting first as well.

I think Uninstall is under New Task, not Upgrade. Check that tree in the context menu.

I have also fell back to 5.0.115 because of the issues with 6.0.9.1

The computers should be listed in the Remote Install tab, despite having ESET installed or not.

Since Endpoint Antivirus and Endpoint Smart Security are two completely different product streams, the best method would be to push an uninstall to the client, and then push an install to the client. I don't think you can upgrade antivirus to smart security. Maybe if they were on two different product versions, but I don't think that's recommended.

You should probably call support, and also submit a sample of that virus to samples@eset.com hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN141

I tried reinstalling CyberSecurity, but the problem returned.

I installed 6.0.9.1 on my mid 2010 macbook pro and noticed that the ESET proxy server stops recording statistics after waking the laptop from sleep. The only way to make it work again is to restart. Running OS X Mavericks.

Yes, I was able to find the setting. My mistake thinking it was enabled by default.

Looks like I'm having multiple issues with this beta. Just noticed that the web scanner isn't working for me either. 12/17/2013, 7:52:03 PM Protoscan Proxy Agent Daemon closed connection 12/17/2013, 7:52:03 PM ESET Daemon Child process esets_daemon[488] terminated with return code 1, restart in 0 seconds 12/17/2013, 7:51:25 PM ESET Daemon Child process mac[489] terminated with return code 69, restart in 60 seconds 12/17/2013, 7:51:25 PM Media access control Cannot connect to /tmp/esets.sock: Connection refused 12/17/2013, 7:51:25 PM ESET Daemon Child process esets_daemon[124] terminated with return code 1, restart in 0 seconds 12/17/2013, 7:51:25 PM Protoscan Proxy Agent Daemon closed connection 12/17/2013, 7:48:15 PM ESET Daemon Module not compatible 12/17/2013, 7:48:08 PM ESET Daemon Module not compatible 12/17/2013, 7:47:54 PM ESET Daemon Module not compatible 12/17/2013, 7:47:54 PM ESET Daemon Module not compatible 12/17/2013, 7:47:36 PM ESET Daemon Module not compatible 12/17/2013, 7:47:24 PM ESET Daemon Invalid value of parameter url_cat I might try a reinstall later, unless you guys want me to run a data collecting tool to find out what's going on.

Just did a fresh install of Mavericks, with a new install of ESET CyberSecurity Pro 6 and noticed that there is no context menu for ESET in finder. Did I miss something?

I figured I document this here as well in case someone else has this issue, but someone noticed that Steam was being blocked by the firewall. I have posted a plausible solution in that thread: Unable to use Steam or any Steam Game with Cyber Security Pro

Is it just me or is ESET CS Pro not logging the standard events such as updates and submitting statistics? My event log window is completely empty.

Did the following to solve the problem: Added new firewall in rule thusly: Created rule name Allow Steam, and loaded the location of the Steam app Action: Allow, Direction: In Protocol: UDP, Ports: Remote, Remote Port: All Destination: Entire Internet Not too sure if I can be more exact than this. Edit: for some reason the first attempt to login, the subsequent login attempt works.

Confirmed. Having the same issue with CyberSecurity Pro Beta. Steam allows me to login, but then shows "NO CONNECTION" on the bottom of the app. Firewall block shows this: 12/12/2013, 7:33:08 PM No usable rule found 72.165.61.176:27018 0.0.0.0:62986 UDP /Applications/Steam.app/Contents/MacOS/osx32/steam

Well, here are the excludes we have set, but just remember that this may be unique to what others may need for their development platform. C:\Windows\assembly\*.* C:\Windows\Microsoft.NET\*.* C:\Users\*\AppData\Local\Temp\_CL_* C:\Users\*\AppData\Local\Temp\Process?\_CL_* C:\Windows\Prefetch\*.* C:\Program Files (x86)\MSBuild\*.* C:\Program Files (x86)\Microsoft SDKs\*.* C:\Program Files (x86)\Reference Assemblies\*.* C:\Program Files (x86)\Windows Kits\*.* C:\Program Files\Microsoft Visual Studio 12.0\*.* C:\Program Files (x86)\Microsoft Visual Studio 12.0\*.* We have others that are unique to our builds as well, which include excluding Phython as well as our build directories and application directories.

I think Arakasi is right about the web filtering. I would go into Protocol Filtering in Advanced Settings and exclude the vmnat.exe from protocol application filtering.

Oh, I wasn't aware that CyberSecurity Pro had antitheft as they don't mention it anywhere on their sales or download cliff notes. That's why I brought it up. I'm just the owner of CyberSecurity.

Just out of curiosity, are you guys installing x64 version of Office 2013 or x86? Maybe it's a bitwise issue? I haven't seen the issue in our office, but our deployment of Office 2013 is currently limited, and we are only using x86 of the office install as recommended by Microsoft. I'll keep my eyes peeled for this.