planet

From your screenshot it looks like the bundled Ask Toolbar is detected as a Potentially Unsafe Application instead of a Potentially Unwanted Application and that could be the reason why it's not activated, unless it is an actual UI bug - Is there difference between unsafe and unwanted @Marcos for the options to be available (since the options aren't available for this unsafe detection)?

Same question posted a day or two ago: https://forum.eset.com/topic/6299-eset-mac-ui/ I've also found this default setting change in the recent release to be unwanted as there is no point for having it open and active in the dock in the first place because of the icon in the menu bar. It's similar to constantly having an minimised window on Windows sitting in the task bar all the time even though it's in the system tray already. Unfortunately this has also come into the home products (ECS/ECSP) too now. Yes it's simple to change, but it would be convenient not to have it turned on in the first place, especially for endpoints who now need to figure out how to turn this off. Please ESET, reconsider leaving 'Present Application in Dock' unchecked in default installations/preferences for EEA, EES, ECS and ECSP like you did in previous releases.

Thank you for reporting the seperate launch, I also got it working automatically now by uninstalling Chrome (keeping user data) and installing it again. Took a restart or two (without restart there was no green frame around the window, after first restart the banking protection message was showing 'Opening window' but never did, but then after the second restart everything was functional with the green frame and I was able to automatically redirect and open Chrome windows in one session) and now everything is working as it should.

You are using build 10565 which is currently an Insider preview build and isn't fully compatible with HIPS. You need to be using the regular stable releases of Windows 10 (currently build 10240) for HIPS to work. Please see this pinned topic regarding HIPS and Insider builds: https://forum.eset.com/topic/6282-windows-10-insider-preview-builds-not-fully-supported-hips-is-inactive/ P.S: You posted in the Beta topic but ESS and NOD32 are now released to the public - visit the relevant section in the forums to see more info.

Right now, Chrome is at version 46.0.2490.71m - just the regular stable releases which auto update as expected. Tried with no extensions and still doesn't work. Tested with Internet Explorer and Edge - auto detection is working for both. Chrome - No (after first time) IE - Yes Edge - Yes

I'm having an issue with ESS v9 (great release by the way, congrats) and Windows 10 where banking protection is automatically detecting a banking website in Google Chrome, and I can successfully launch the special window... but after closing that first window I'm never able to make the automatic detection work again in Chrome as the browser just loads the website normally. Checked settings and that banking website was set to automatically launch banking protection, but even after removing the rule and turning the protection off and on, restarting the computer, etc. automatic detection for any banking/payment website is no longer working for me in Chrome. It also doesn't work if I manually enter a website for ESS and set it to ask me or automatically launch, Chrome just loads the website normally. I am able to manually launch banking protection at any time which opens an IE window, but I was hoping to be able to use the automatic detection in Chrome and am not sure why it no longer works. Any help would be appreciated.

One thing I've noticed is trying to edit a recognised network - if you try to do it from the main window there are no 'OK' and 'Cancel buttons so nothing you edit can be saved (pressing enter doesn't work either). But in the Advanced section, the 'OK' and 'Cancel' buttons appear so you can save changes that way.

I decided to give it a go anyway and it seems that iCloud Drive is able to work in El Capitan without needing to exclude the folders anymore.

I've been able to keep using devices with previous versions that use a Username and Password whilst using the new converted key on another device with no issue (with a multi-device license), so no there should be no problems as long as you stick with the number of devices allowed.

Updating this thread to mention that ESET Cyber Security Pro (from version 6.1.12.0) will automatically assign the 'Work' profile of the Firewall to an active VPN connection, making it easier to manage rules/connections if using a VPN (So for the OP's question - you only allow enough rules to establish the VPN connection in 'Public' and block the rest as it will then use 'Work' whilst connected to a VPN). Thanks ESET!

Does the width that we set stay that way after rebooting or reopening the window though? It seems a little inconvenient having to keep adjusting the column every single time. It doesn't remember in Cyber Security, does it remember in Smart Security 9 (Beta)?

You can test Anti-Theft by visiting my.eset.com and logging into Anti-Theft management. Select the device and click 'Run a Test'.

Yes, I would also like to know what to do in this situation for Windows 10 and ESET Smart Security. Windows Update doesn't let us update the updates/drivers that ESET notifies us about even if we have enabled to receive all updates.

Slightly off topic but the same annoyance - ESET Cyber Security Pro for Mac also has the exact same thing in the firewall editor and it's very hard to see what the actual rule is for, manually editing each rule to remove 'Allow communication for' or 'Deny communication for'. Same issues with remembering window size - no point resizing as it goes back to default including column width. Would be great to do something about this for both Smart Security's (and Cyber Security Pro's) Firewall.

Version 4.0.81.0 was announced on this forum (still pinned on the top of the linux section) back in 12 October 2013, almost two years ago.

Had no idea esets_scan would allow you to do this, great find When typing, you can start typing the first few letters of a folder and press Tab - terminal will automatically do the rest of the folder name (useful for getting the ESET name right, you just type ESET and press tab). You can alternatively visit the MacOS folder in Finder and simply drag 'esets_scan' into the terminal window and it will automatically fill in the whole path for you.

I constantly edit the first post of this topic as much as possible with what's been fixed, new issues I've noticed and more - along with when it was last updated and versions of OS X and ECSP.

El Capitan improved the way Mail & iCloud is done, and the user can now disable and enable Mail in iCloud Preferences with ECS or ECSP installed without an issue. Tested with OS X 10.11 and ESCP 6.1.12.0.

In the KB article: "Can I use my ESET for Mac products with OS X Yosemite (10.10)?" there was an issue with iCloud Drive and real-time protection of ECS and ECSP, requiring exclusions to be set manually. Because El Capitan encourages us to sign into iCloud when setting it up or using it for the first time, iCloud Drive is usually turned on already. Do we still need to set exclusions manually with this new OS X version, or has the recent release of ECS/ECSP 6.1.12.0 automatically resolved this conflict?

Please try downloading the newest release of ECP or ECSP (version 6.1.12.0) and see if this issue continues to occur.

, the new release for ECS and ECSP is here and is version 6.1.12.0, which already supports OS X El Capitan as well. This version has the Shutdown issue fixed, and the unprotected issue is also fixed, along with many other improvements I mentioned earlier in this topic.

This is a similar issue mentioned in an earlier topic here: https://forum.eset.com/topic/3552-random-freezes-and-crashes-by-esets-daemon/ Was experiencing the same issues. Still checking with version 6.1.12.0 if it has been resolved.

Shutdown issue now resolved with version 6.1.12.0 of ECS and ECSP. https://forum.eset.com/topic/3341-os-x-shutdown-delay/page-3#entry33792

Happy to say that version 6.1.12.0 of ECS and ECSP improved the way updates are done and also resolved this CPU issue whilst updating. (Now only about 10% CPU for the first large VSD update).

Shutdown issue now resolved with version 6.1.12.0 of ECS and ECSP. https://forum.eset.com/topic/3341-os-x-shutdown-delay/?p=33792