Jump to content

puff-m-d

ESET Insiders
  • Posts

    269
  • Joined

  • Last visited

  • Days Won

    17

puff-m-d last won the day on February 5

puff-m-d had the most liked content!

About puff-m-d

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Male
  • Location
    USA

Recent Profile Visitors

1,919 profile views
  1. Hello @SlashRose, Thanks for reporting. I just enabled B&PP again to test and can confirm that the new B&PP module 1199 does indeed fix the issue of crashing Edge 86...
  2. Hello @Marcos, Thank you for your reply and I look forward to an update as to the status of this issue 👍 !
  3. Hello, I can verify and confirm this issue as it also occurs on my system when trying to use "Banking & Payment Protection" with the most recent stable version of Microsoft Edge Chromium (86.0.622.38 released yesterday Oct. 8). Edge crashes and closes every time it is launched and the only way to use Edge is without B&PP enabled.
  4. Hello @cutting_edgetech, While you are on the "Network connections" tab in the ESET GUI, right click in the "Network connections" pane and uncheck "Show only TCP connections". UDP connections should now show along with the TCP connections. I hope this helps...
  5. Hello @BrianE, Here you go: Future changes to ESET NOD32 Antivirus Future changes to ESET Internet Security and ESET Smart Security Premium
  6. Hello @100, I was thinking that this discussion has gone a bit off topic. You may have a better chance of receiving a definitive answer to your question if you start your own thread and topic... Perhaps with a title like "How can I determine if all of my modules are up to date?" or "How can I determine the most recent module versions available?". Just a thought...
  7. Hello @100, Only "Signaturdatenbank: 15765P (20170718)" will have the "P" at the end of the module version number. None of the others will. This was changed a while back but I do not remember the date. There is no easy way that I know of to tell exactly which module is a pre-release version or a regular version. You can always switch to the pre-release updates to see what module version you will have and then if you are uncomfortable staying on pre-release updates, you can switch back to regular updates. It could also be possible that maybe a staff member could comment on the current version numbers for regular updates but I have not seen ESET provide a public list of current module versions. If memory serves me, the versions can vary by OS version and bitness but I may be wrong. Normally, if your VSD is up to date, it is safe to assume that your modules are also up to date as they both use the same mechanism to update and update at the same time. As far as "difference of 2 versions and more than 2 month", sometimes modules receive several pre-release updates over a period of a few weeks to a few months before they are released to the regular update channel thus accounting for the version numbers and time period. I hope this helps ...
  8. Hello @100, @User is on pre-release updates. Maybe you are using regular updates?
  9. Hello @cindyatgreenacres and welcome to the ESET Security Forum! The first thing I would check is your "Webcam Protection Rules". If you do not know how to do this follow these steps: Right-click the ESET tray icon and click "Advanced setup". In the left-hand panel, click "DEVICE CONTROL". In the main panel, click "WEBCAM PROTECTION". To the right of "Rules", click "Edit". A new window appears which will list all webcam rules that you have created, if any. See if the application that is being blocked from accessing your webcam is listed. If it is not, click "Cancel" to exit the "Rules" window. Click "Cancel" again to exit "Advanced setup". If it is, click on that rule and the click "Remove" (bottom left). Click "OK" to exit the "Rules" window. Click "OK" again the exit "Advanced setup". I hope this helps ... Report back as to what you find...
  10. Hello SCR and itman, Thanks for both of your replies. Thanks for your feedback and I agree with you, learning something new is always a good thing. As far as the HIPS goes, the only wildcard symbol official supported by Eset at the present time is "*". It also is only allowed at the end of the path name e.g. C:\Windows\Temp\*. It means "this folder's files and all subordinate folders and files." I and others have been bugging Eset for some time to modify the HIPS for allow the same wildcards and use thereof that all allowed for the AV scanner. I agree totally with you, if for no other reason than consistency. Whatever wildcards are allowed, they should be the same for all of the ESET modules. Having different sets of wildcards just complicates things and adds to confusion. Keep it simple as I always say, same list of wildcards should be available in all the ESET modules.
  11. Hello SCR, I have never had the need to exclude files or folders in ESET either. I had been using HitmanPro.Alert but decided to beta test the Malwarebytes 3.0 since I have three lifetime licenses. As far as the exclusions that I have made for Malwarebytes in my testing, I have not noticed any performance improvements either (RAM, CPU, speed, or otherwise). It is just with my testing that I had the questions about exclusions for folders and sub-folders, so I decided to ask for for my own learning and knowledge of ESET products.
  12. Hello SCR and itman, Thank you both for your replies. I usually do not exclude anything either but I have been experimenting thus these questions came to mind. I have been alpha and beta testing the new Malwarebytes 3.0 and there have been some performance issues. In my experience, Malwarebytes and ESET have never worked well together performance wise on my machine. In testing, I wanted to exclude both programs entirely from each other to theoretically eliminate performance issues between the two to a minimum and possibly better evaluate Malwarebytes 3.0 on its own performance level. I do not know yet if I will keep Malwarebytes 3.0 in real-time or only use it as a second opinion scanner yet as it all depends on its final performance when it goes stable and how it will coexist with ESET. ESET is the one security software that is always present on my machine and anything else that I may add cannot interfere with ESET or affect my machines performance adversely. I did see the information that you mention in the help file but I found it a bit vague. The information is specific as far as excluding all files within a folder and everything on an entire drive, but not specific in the case of excluding everything including all files and all sub-folders within a specific folder. Therefore I make an assumption as in my original post as follows based on the help file information: If I enter the following as an exclusion: C:\Program Files\Malwarebytes\Anti-Malware\*.* - then only the files in that folder will be excluded from scanning, not any of the sub-folders. If I enter the following as an exclusion: C:\Program Files\Malwarebytes\Anti-Malware\* - this excludes the folder and all of the sub-folders within from scanning. I am just looking for a quick and easy method to exclude everything from a particular program (in this example it is Malwarebytes) for testing as I evaluate performance. The least number of exclusions that I have make, the better, as it is a lot quicker to just exclude one folder than several or many. Malwarebytes has quite a few folders/sub-folders/files and just using one exclusion rule would be so much easier. I do think that I have already learnt at least one new thing. I always knew that you could use these types of wildcards to exclude file and folders in the anti-virus scanner, but it seems that you can use the same wildcards for the HIPS module also. I assume that you can use the wildcards with both the source and target within the HIPS rules. Thank you both for your feedback so far and any additional feedback from anyone will also be greatly appreciated...
  13. Hello, I have two questions regarding folder exclusions that I really have not been able to find a definitive answer for: I am almost certain of the following so I am only asking for verification. If I enter the following as an exclusion: C:\Program Files\Malwarebytes\Anti-Malware\*.* - then only the files in that folder will be excluded from scanning, not any of the sub-folders. This is the one that I am not sure about and need to know if it works or not. If I enter the following as an exclusion: C:\Program Files\Malwarebytes\Anti-Malware\* - does this exclude the folder and all of the sub-folders within from scanning? Any definitive answers concerning these two issues would be greatly appreciated. Thanks in advance for your help...
  14. Hello throwaway9, IMHO, the default settings provide both ample security and protection with good performance. The changes in settings that I have made from the defaults are mainly just to satisfy my preferences and do not really increase security.
  15. Hello throwaway9, I am glad to hear that your upgrade went smoothly. At present, it does not look like ESET has any plans on discontinuing ESS anytime in the foreseeable future. I base this on the fact that ESET is still offering renewals for ESS. As to the blue highlights (blue dots with numbers inside), they just show what settings that have been changed from the defaults. For example from your screenshot, the blue highlight/dot with a "1" inside besides the "HIPS" selection means one setting in that category has been changed from the default setting. If it had been a "2" or "3", for example, that would have meant that either two or three settings in that category had been changed from the default settings. You can tell exactly which settings have been changed from default, as well as how many and which settings, by the blue highlight/bar to the left of the setting as shown in the following screenshot: I hope this helps...
×
×
  • Create New...