Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    Please select

Recent Profile Visitors

798 profile views
  1. Suggestion for the Eset anti-spam filter: Mark mails as spam, based on own rules for individual X headers. Reason: My e-mail provider has decided no longer to add a note to the subject of e-mails classified as spam or to change the subject in any other way. Instead, spam mails are moved to a folder on the server that cannot be retrieved via POP3 (IMAP is not an alternative). However, I have created a rule on the server that moves all mails to the inbox that are not sorted out by other filters. Rules for X headers are not possible. Now, of course, I get the spam mails in my inbox, which are now only marked as spam in the mail header via "X-Spam-Flag: YES" and are not recognized as spam by Eset even with the extended antispam database.
  2. Tested today: Regular updates are still at 1195. Does anyone with regular updates have a version above 1195? Edit (09/21/2019): The cleaner version is officially still 1195 with the regular updates.
  3. Yes: https://help.eset.com/eis/12/en-US/idh_page_scheduler.html https://help.eset.com/eav/12/en-US/idh_page_scheduler.html
  4. See this posting from me: I didn't have any problems with 1199. The problem occurred with switching back to 1195 and unfortunately remains now after I am back to 1199 (without restarting the operating system). 1199 only protects against new locks but doesn't unlock existing ones.
  5. I know, and after a few minutes I had changed back to the test updates with cleaner module 1199, but the registry keys still remain locked.
  6. I thought that now with the regular updates at least the cleaner module 1197 would be available and so I changed back to it. But it's still on 1195! Now I unfortunately have 3 applications with the locked registry keys and I probably can't restart the system for the next 2 month because big calculations are running which will probably take so long. :-| Edit: I have created a batch file that should delete all folders and their files (except the RegHive files) of these sandboxes with a double click. @echo off FOR /D /R "C:\Sandbox\username\sandboxname1" %%x IN (*) DO rd "%%x" /s /q FOR /D /R "C:\Sandbox\username\sandboxname2" %%x IN (*) DO rd "%%x" /s /q FOR /D /R "C:\Sandbox\username\sandboxname3" %%x IN (*) DO rd "%%x" /s /q
  7. Hm, I cannot confirm this under Windows 7 (x64) and EIS 12.2.23 with the cleaner module 1199.
  8. Are the test updates still on wave 3? I have now also switched to the test updates.
  9. Eset has by far the best support of all antivirus software vendors. They are the only ones who take their customers seriously and listen to them!
  10. Have you also tested it as follows: Start a software (e.g. browser) in a sandbox. Install or update a software outside Sandboxie. Exit the program in the sandbox and try to clear it. This is how the problem always occurred with me.
  • Create New...