Emsisoft Anti-Malware and Emsisoft Internet Security 9.0 Public Beta

See post #403... neglect this post.

 

Yes, that is normal. We only create rules for applications if we actually need them. For EAM in particular, you will only find rules for applications that triggered some kind of behavior blocker response. The majority of files on your system will never trigger a response though, so the list is quite empty. It is different for EIS as a lot of applications do access the network and we create a rule for each of those applications.

 

That's logical after hearing the reason behind it. Thank you!

 

Fabian, Emsisoft earlier kept a record of files in cloud (I think it was called Emsisoft Anti-Malware Network) , in case you needed more info of the file. Will that service be discontinued and obsolete with EAM/EIS 9? Is it just me not finding it? If so, where can I find it in EAM/EIS?

 

In general, all the verification with the Emsisoft Anti-Malware Network is done invisibly in the background. But you can browse the whole database at any time here: www.isthisfilesafe.com

 

Thank you for the clarification!

 

AFAIK just random spikes but will keep an eye on it and when they happen from now on. Will there be any attempts to lower ram/cpu or will the final version be the same as the current beta is now?

 

You're welcome

 

I think there is an overlap between EAM v9 and SpyShelter Premium v9. Mind you, this was doing my head in even with EAM v8, but I had no clue what was causing it, since I use a number of security applications.
So I went and reinstalled Windows, did all the usual updates, and first thing I installed was SpyShelter Premium v9.

Then I went ahead and installed EAM v9 Beta, and SSP did kick up an alert. So I continued to install EAM v9 via SSP Installer Mode. All worked well. I also added the SSP executable into File Guard / Whitelist as a process with 3 ticks.

Then I tried to install something else, and SSP was silent. So, in EAM, I paused protection to see if SSP would provide me with an alert... and it did! Now I am questioning myself... in an Emsisoft forum thread I saw someone say that SSP is a HIPS, hence I decided to replace Online Armor with SSP. Now I am wondering if I need to remove SSP altogether or disable an EAM guard.

Thoughts?

 

Look in application rules. If Spyshelter is listed, make sure it's Trusted. If not, try whitelisting SSP! Should work out fine.

 

By Trusted, do you mean "All Allowed"? That is what it's on at the moment... If I tick "hide fully trusted applications", it disappears from the screen. So it must be trusted.

 

Ah, yes.

Try whitelisting the running process of Spyshelter as well.

 

What a tool I am...
"Auto-block suspicious behaviour" was ticked in SSP. I swear I thought I unticked it...

 

I'm glad the problem was solved!

 

We just released a new beta build today. Version number is 9.0.0.4096 for both Emsisoft Anti-Malware as well as Emsisoft Internet Security. If you have beta updates enabled under "Settings"/"Updates" the new version will be installed automatically.

Changes in version 9.0.0.4096 compared to the previous version:

• Added blocking of system sleep mode when a scan is in progress.
• Improved quarantine submit feature.
• Improved high DPI screen support.
• Several minor GUI improvements.
• Fixed a problem with notifications when a detected file is being removed before quarantine takes place.
• Fixed repeating alerts for the same malware in case malware was not deleted properly during first attempt.
• Fixed issue with slow removing of large amounts of same malware families after scan.
• Fixed a few potential crash errors.

 

We just released a second beta build today. Version number is 9.0.0.4103 for both Emsisoft Anti-Malware as well as Emsisoft Internet Security. If you have beta updates enabled under "Settings"/"Updates" the new version will be installed automatically.

Changes in version 9.0.0.4103 compared to the previous version:

• Fixed a rare crash caused by the bug reporting component we use during application shutdown.

 

No problems with latest beta here.

 

I have been getting this error when I shutdown the Guard.

 

Can you please check and make sure you have version 9.0.0.4103 installed?

 

Yes.. That is the one, but I am not in the snapshot at the moment. I am in the other snapshot that has v8.1.0.40 still.

 

So the error is from EAM 8.1?

 

No...it is from EAM 9

 

I will be able to compare when I switch back into EAM v9

 

I can delve...

 

Quite handy...