xxJackxx

Thanks for the link. I iwll likely give it a try in automatic mode as the interactive is a bit tedious. It is especially painful in the middle of a full screen 3D app.

I would like to know how everyone else is using the firewall. I have been installing in learning mode and then switching to interactive mode at the end of learning mode. It has been many years since I have tried automatic mode and at that time I found it to block too many things. How is it with version 7? I realize I can test it myself but I would like a bigger sample of information from others. Thanks.

I have been renewing from betterantivirus.com for several years. I would not think that an issue.

That has been my previous experience, but not this time. Was there a policy change or am I just having a technical issue?

Misfortunate if that is the case. You used to be able to use it for a lessor product.

I have a 3 user license for Smart Security. Are we no longer allowed to use the ESS licenses to activate NOD32? I wanted to give it a test run and it says invalid license. It does not expire for 3 more months.

I test a lot of software and have licenses for several security suites, but ESET Smart Security 7 is the only new release this year that has not given me any problems. I assume it's probably best I don't name any names, but some of the supposed top tier solutions have causes me BSODs, false positives, left me unable to send email, caused browser crashes, etc. My praise to the staff of ESET for delivering a solid product. I have spent too many hours recently installing and testing other products with promises from their support that issues have been fixed that have not been. I now have ESS on all of my machines and will be keeping it that way for the foreseeable future. Thanks to all that make it a great product and give some of the best support in the business.

Would it not be necessary to have some 32 bit components to protect from 32 bit malware, which would likley be most of it?

From a discussion over at Wilders I was asked to post here the things I found left behind after an uninstall of ESS. This list includes folders left on the hard drive, not including any subfolders, and the registry keys were exported and the contents of each exported key copied and pasted here. This is from a 64 bit Windows 8.1 machine with Office 2013 and a copy of ESS 7 and is after an uninstall and then running the ESET Uninstaller in safe mode. These are this things I was able to find searching for the exact string "ESET" and the string "ESET Smart Security". Folders: C:\Users\(Username)\AppData\Local C:\Users\(Username)\AppData\Roaming C:\Windows\SysWOW64\config\systemprofile\AppData\Local Registry: [HKEY_CLASSES_ROOT\CLSID\{F43F5136-AA90-4005-9368-F91F5C120D69}] [HKEY_CLASSES_ROOT\CLSID\{F43F5136-AA90-4005-9368-F91F5C120D69}\InprocServer32] @="C:\\Program Files\\ESET\\ESET Smart Security\\eplgOutlook.dll" "ThreadingModel"="Apartment" [HKEY_CLASSES_ROOT\CLSID\{F43F5136-AA90-4005-9368-F91F5C120D69}\ProgID] @="ESET.OutlookAddin" --------------------------------------------------------------------- [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{F43F5136-AA90-4005-9368-F91F5C120D69}] [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{F43F5136-AA90-4005-9368-F91F5C120D69}\InprocServer32] @="C:\\Program Files\\ESET\\ESET Smart Security\\x86\\eplgOutlook.dll" "ThreadingModel"="Apartment" [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{F43F5136-AA90-4005-9368-F91F5C120D69}\ProgID] @="ESET.OutlookAddin" ------------------------------------- [HKEY_CURRENT_USER\Software\ESET] [HKEY_CURRENT_USER\Software\ESET\Setup] ------------------------------------------ [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ESET] [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ESET\ESET Security] [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ESET\ESET Security\CurrentVersion] [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ESET\ESET Security\CurrentVersion\Plugins] [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ESET\ESET Security\CurrentVersion\Plugins\01000E00] [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ESET\ESET Security\CurrentVersion\Plugins\01000E00\Profiles] ---------------------------------------- [HKEY_USERS\.DEFAULT\Software\ESET] -------------------------------------- [HKEY_USERS\S-1-5-19\Software\ESET] ----------------------------------------- [HKEY_USERS\S-1-5-20\Software\ESET] -------------------------------------- [HKEY_CLASSES_ROOT\ESET.OutlookAddin] [HKEY_CLASSES_ROOT\ESET.OutlookAddin\CLSID] @="{F43F5136-AA90-4005-9368-F91F5C120D69}" -------------------------------------------- [HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\CustomUIValidationCache] "ESET.OutlookAddin.Microsoft.Outlook.Explorer"=dword:f1662ae4 ------------------------------------------------- [HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AddInLoadTimes] "ESET.OutlookAddin"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00 --------------------------------------------------- [HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Addins\ESET.OutlookAddin] "1"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00 "4"=hex:01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00 ---------------------------------------------------------- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\ESET.OutlookAddin] "FriendlyName"="ESET Outlook Add-in" "LoadBehavior"=dword:00000003

Thanks to everyone that looked at it. I did not suspect it was anything that was dangerous.

File sent. ESS was still trying to delete it. Uploaded to virustotal with a 0/49 rate. Not even detected by NOD32, for whatever reasoon.

C:\Windows\WinSxS\amd64_windows-defender-service_31bf3856ad364e35_6.2.9200.16513_none_1eba7d28e058e749\MsMpEng.exe - probably unknown STEALTH.CRYPT.TSR.DRIVER virus [7] - action selection postponed until scan completion

I reinstalled the current beta of ESS this evening and upon install it warned of a potential conflict with Windows Defender and recommended I uninstall it (Windows 8, not an option). Then after it ran its first scan it detected the executable for Windows Defender as malicious and wanted to delete it. Probably something that should be looked into.

No date set yet for the final release afaik, keep in mind though that an RC "release candidate" hasn't been released yet, so it will take a while longer. In the past ESET have released only one beta then gone straight to production product. I assume their answer for release is when its ready. Based on my previous experience with testing I am still expecting an RC release. I don't expect a final for at least a couple of months if not longer.

If you don't mind my asking, I have been getting this message repeatedly for years and would love to know if it is known how to prevent or fix this. It is usually this very thing that causes me to uninstall ESS.

Uninstalled until the release of the next build. I understand it is beta but the response on this has been too slow.

Same here. Would it not be better to have it fail than to have it stuck running in a loop that does not end and cannot be cancelled?

I hope so. Don't dumb it down and don't mess it up.

Ok, I found one. If you set the firewall to learning mode it does not seem to expire.

I must say I still can't find anythingwrong with it. This is the most troublefree ESET product I have run since the days of 2.x. Can't wait for the final.

It does and that is the default.

Keen observation I've edited my initial post and included download links for both products. Great! I have been using the 7.0.104 build on 2 machines since it was released and can't find anything wrong with it. I'll report back if that changes.

The download link appears to only go to NOD32 and not the suite. I found it anyway, but not from that page.

The new icon is fine. If we were going to go backwards I would like to see something that looks more like the good old 2.x days.

The version 7 beta does not seem to support high DPI settings. 6 did not either so this is not specific to the beta. My laptop screen is high resolution and Windows sets it to Medium (125%) by default. This makes the ESS UI a little hard to read as everything is small. Are there any plans to support higher than normal DPI?