planet

I reported the issue and provided logs about this shortly after 6.1.12.0's release last month and also reflected these issues in 'Issues, Ideas & Feedback for ESET Cyber Security (and Pro)'. Still waiting for a solution, but they are looking into it.

I've never got it working. Not sure if it's because ECS doesn't support secure connections (IMAPS, POPS) or it isn't compatible with the Mail app.

Figured it out - for some reason an older ESET Certificate was still installed even after uninstalling ESS and using the Uninstall Tool, so after removing it manually and reinstalling ESS, emails are working now with SSL/IMAPS turned on.

Did you restart Yosemite after setting exclusions for changes to take affect? Tried Disabling Real-time Protection and seeing if that temporarily helps as the cause? Have you considered upgrading to El Capitan which no longer needs the exclusions and has better integration with iCloud?

Just visited both and it looks like it's working okay. Is it working for you now too?

Oh But the Chrome website also provides a link to the 64-bit version and that's what I got on most PCs. Guess I need to uninstall and go back to the 32-bit version of Chrome.

Hi femtobeam, I didn't see this post highlighted for some reason so I'm sorry for the lateness. Time Machine is a pretty interesting thing as I mentioned in my earlier post, for example it can create multiple 'ghost copies' of one file instead of replicating actual files, but is actually only the one (explains why future backups will only take seconds, but it's able to somehow immediately create another 'full copy' of your Mac in another folder on your drive. So in other words, this is expected and is why I mentioned in my earlier post not to scan the Time Machine drive as ESET would have scanned 3/4 of the files on drive 40 times, which is unnecessary. Possibly both the current backup and future backups (especially if you try to do a full restore), due to the complexity of Time Machine. It may be best to reformat the Seagate drive and perform a fresh Time Machine backup once your Mac is clean. Delete the files from Quarantine if you don't need them as well. Pressing 'Options' in Time Machine's Preferences allow you to specify exclusions - in this case you can browse to your user folder, then Library > Mail > V3 (if El Capitan, otherwise V2), select a folder (each one is for a different account), and select Junk.mbox to exclude it (up to you what you want to exclude, you could exclude the whole Mail folder if you only use IMAP for example as everything is already synced with Gmail anyway). It wouldn't hurt to perform an "In-depth Scan" from the Scan section of ECSP, either with the Seagate drive unplugged and/or with the exclusion set in ECSP. Follow the KB link in my earlier post and create the exclusions for Time Machine and your Seagate drive, otherwise you should be okay. Hopefully in the future ECSP will automatically play nice with Time Machine drives, but setting an exclusion is ideal for now.

Also not working for me since the update, doesn't work anymore for any browser (Chrome, IE, Edge). Reinstalled/repaired and nothing works, can't manually launch it either.

Since the Windows 10 November Update, I cannot get Thunderbird to connect to any IMAPS (Gmail, Outlook) server when SSL is turned on in ESS (Thunderbird says it cannot connect to the server). As soon as I turn it off, communication works fine. Issue wasn't present before the Windows update, and I've tried removing/reinstalling both ESS and Thunderbird. I see the ESET Certificate in Thunderbird too, so I'm not too sure what is happening. I've turned off SSL (Edit: I found that leaving on SSL but specifically turning off 'IMAPS checking' also allows Thunderbird to keep working) for now in ESS, but it would be nice to have it working again.

You tried to download CCleaner Pro using Firefox, but ESET let you know that the installer contains the Google Toolbar/Chrome bundled with it. You can either click Déconnecter to stop the download from continuing, or click Ignorer to let the download complete (but be careful during installation to uncheck the boxes that try to install the Google Toolbar/Chrome and you should be okay) if you want to use CCleaner Pro on your computer.

One fast option is to visit/search the ESET Knowledge Base, which has the article "Which ESET product do I have and is it the latest version? (Home Users)" that shows the latest version available. -- Otherwise, depending on the particular ESET website relevant to your location, most will display the version just as you download the program (if you choose the offline installer, not the Live Installer). So for NOD32 at the moment on the 'International' site for the English 64-bit variant, the latest version is 9.0.318.0. (hxxp://www.eset.com/int/download//home/detail/family/2?installer=offline#offline,249,ENU,,,) Go to eset.com > select your location > click Download (For Home) > next to NOD32, click 'More options' > Select operating system > Select language > Information appears below the Download button. The new ESET site for the US however only displays 'Version 9.0' regardless, so this option is only valid for the older style websites in other locations.

We shutdown/restart pretty regularly, so it just started working again the next day after restarting (Although the green frame still never works). Nothing else running in the background, this particular Win 10 PC doesn't have much (if any) software on it other than the basics (Chrome and Thunderbird, plus ESS 9).

unless you joke about it. congratulations! you just infected your computer with whatever was in that program. NEVER download anything from non official sites. www.eset.com always from the officials. Luckily, the URL mentioned here is simply a direct download link to the 32-bit and 64-bit variants of NOD32 v9 from the official ESET website (download.eset.com). Although, it is always a good practice to download from the official website, as pavilion_alex said... which is simply by visiting hxxp://www.eset.com/.

The issue just came back, after the first automatic window all future instances just loaded normally in the Chrome window and didn't redirect to the ESET page and open the protected window anymore. Is this something to do with Chrome's automatic updates? Launching it manually continues to work (opens an IE window), although no green frame appears still (no answer from my last post). Edit: And the issue is resolved again... So confusing at the moment

Great to hear! :-)

That is understandable, hopefully it's not too long. If you'd like, I can PM you when the next version is publicly released and I've confirmed the issues are resolved. What files are left behind after a uninstall? This is getting off topic, but quite a few things are left behind... (make sure to restart as well so other files not listed here are removed as well) /private/etc/pam.d/esets /Library/Application Support/ESET /Users/<user>/.esets /Users/<user>/Library/Preferences/com.eset.ecsp.6.plist /Users/<user>/Library/Caches/com.apple.helpd/SDMHelpData/Other/English/HelpSDMIndexFile/com.eset.ecsp.6.help This is common, even when removing apps downloaded from the OS X App Store (caches, preferences are left behind). I noticed that it's likely intentional so some of your preferences and info (last scan, GUI options) can remain for future installs.

Is this still occurring after updating El Capitan to 10.11.1 (Should be available as an update in the App Store)? If so, try creating a test user account and use Safari logged in to that account to see if you are experiencing the issues there (Don't forget to delete the test account after trying it out).

Followed the steps and I was able to recreate the blinking in Windows 10.

I'm able to connect to new Wi-Fi networks as well as my iPhone's hotspot just fine with ECSP installed (regular updates). It also prompts for zones immediately after connecting. In this case it may be best to get specialised help with this from Tomas if you are willing to reinstall it for a moment to collect the log files, or continue to wait until a number of issues are fixed which may help with yours (in particular the issues with esets_pfw). I would also maybe try using ECS in the mean time (your license will still work).

My guess is the ESET program will automatically run that file to make it work with Windows 10 if you upgraded from Windows 7/8.1 with NOD32 installed.

It is still the same issue overall - the names are currently too long to see (and making them short isn't an easy solution when you have a large number of them, but is the only solution for the short term right now). Making the column bigger isn't a permanent solution as resizing will be required every single time. So, having the rules set without 'allow communication for' and 'deny communication for' in future releases would be the first fix, plus having ESET's programs remember the column width would be the second fix. Both would be beneficial to have.

Hello, You can simply uninstall ESET Smart Security 9 for any reason just by going to Add/Remove Programs in Control Panel (or by going to your installed Applications in Settings), selecting the ESET product and clicking 'Uninstall'. If you do have issues with uninstalling, you can then use the tool mentioned which is a great backup plan that should definitely work in removing ESS. Don't forget to go into Safe Mode with Networking to run the tool. Can also confirm the tool worked for me with v9 (& Win 10). Enjoy the trial!

Especially when there is a large number of them. It's also what I've been doing. @TomasP, does this include EES (Business) & ECSP (Home) for OS X users?

Hi Roger, if that is what you have decided, that is okay. Thomas just mentioned above your post that they will eventually offer version 9 to everyone within the program after they feel that it went well enough for those who manually installed version 9, so sooner or later you will be notified to update which will benefit for all supported versions of Windows (including Windows 7 SP1). Users do things in different ways, some upgrade immediately (or let the program do it itself), others like to wait until they are told to upgrade, and some trust to do things in particular ways that they know works for them. In the end, everyone will be notified to upgrade to version 9 no matter the Windows version, the preferred method of upgrading and their personal preferences by the user (we were notified via the forums, others will via ESET's social media, but mostly everyone else eventually via the in-product updater soon). It isn't so bad if Roger (and a lot of other users who aren't browsing the forum, don't check the ESET website or otherwise) wishes to wait for ESET to notify him within the program, it will be ESET's decision of when to do so about version 9 eventually. For this, I would be very concerned if you were being notified to upgrade within the program and you were personally choosing to ignore it. That is when it would begin to be a problem. When you do receive a notification to upgrade soon, I hope you enjoy the new version and continue to let it protect you with the latest and greatest ESET has to offer you with NOD32 v9. I would then encourage you to accept future updates offered to you in NOD32 (via the in-product updater/when you get a notification to update) as they always serve a purpose to help you remain protected as new types of threats emerge and help the program itself remain in the best condition possible. It is better for the program to prevent issues in the first place than to wait for a problem to occur to release an update after. Trust the ESET team behind your product, if they are offering an update of their product to you on your laptop, it is for a reason. It would be difficult to list every single improvement and change between builds in detail every single time. Note: I did edit this post a few times to make sure what I was trying to say made sense, so this post might look different in the email notification you got for this. (Personally, when it is mentioned in the release notes that there is an update available for 'internal product security hardening against targeted attacks', it is important for me to update the program to 8.0.319.0 as it further protects me from possible issues. Yes it's not a big noticeable change, but internally that is an important thing I would want an improvement for from 8.0.312.0 and will only take about ten minutes of my time to update.)

One thing I've noticed is the green frame isn't showing every time around the Chrome window when banking & payment protection is launched - is this something to be concerned about or am I still protected even if I can't see the green frame (but still launches the special window)? Edit: Found that if I launch banking & payment protection manually first, the green frame is then shown around the automatic protected Chrome window, but if I never manually launch it or restart Windows, I don't get the green frame until I manually launch it again.