Sign in to follow this  
tempnexus

Shadow Defender and EIS conflict

Recommended Posts

I set up EIS up to date and perfect. I exclude the EIS folder from SD. Yet whenever I freeze SD i.e. Enter SHADOW mode and then exit SHADOW mode the EIS keeps telling me that EIS component is missing and the software needs to be re-installed. That kind of defeats the purpose of SD. No other security software does that. What gives?

http://i.imgur.com/3CGEeek.png

I have re-installed EIS numerous times because of this and eventually it will probably flag my Serial shareware of whatever you call it. I will be happy to assist in any matter since I want both of the security apps to run flawlessly.

By the way I am using Webroot Secureanywher, ESET NOD32 AV, and HitmanPro Alert without a hitch with SD. That goes along with on demand Zemmana antimalware and Malwarebytes.

post-9266-0-53807600-1467169878_thumb.png
Download Image

Share this post


Link to post
Share on other sites

Does Shadow Defender allow you to exclude drivers and services? If so a driver named epp (epp.sys) and a service named a2AntiMalware (a2service.exe) should be excluded.

Share this post


Link to post
Share on other sites

You need to  be using the latest version of Shadow Defender.   There was a conflict before build 624, but Tony fixed it.  Latest version should be fine

Share this post


Link to post
Share on other sites

You need to  be using the latest version of Shadow Defender.   There was a conflict before build 624, but Tony fixed it.  Latest version should be fine

Strange I have 636 installed. maybe because I was on EIS beta channel?

Let me try reinstalling it again and now just staying on stable channel.

Share this post


Link to post
Share on other sites

If it is beta related, then let us know. Our developers will probably want some debug logs to see if they can find out why it's acting differently.

Share this post


Link to post
Share on other sites

Ok

If it is beta related, then let us know. Our developers will probably want some debug logs to see if they can find out why it's acting differently.

Ok was on the beta channel, updated to the latest EIS, took SD off so I can update my system and boom I get this error again.
How can I get the logs out?

 

LOGS sent to GT500 via PM

post-9266-0-02939100-1468902745_thumb.png
Download Image

Share this post


Link to post
Share on other sites

Here's instructions for debug logs:

  • Open Emsisoft Internet Security from the icon on your desktop.
  • In the 4 little gray boxes at the bottom, move your mouse into the one that says Support, and click anywhere in that gray box.
  • At the bottom, turn on the option that says Enable advanced debug logging.
  • Either click on Overview in the menu at the top, or close the Emsisoft Internet Security window.
  • Reproduce the issue you are having (update to the beta again, wait for the error message to happen, and then downgrade from the beta).
  • Once you have reproduced the issue, open Emsisoft Internet Security again, and click on the gray box for Support again.
  • Click on the button that says Send an email.
  • Select the logs in the left that show today's dates.
  • Fill in the e-mail contact form with your name, your e-mail address, and a description of what the logs are for (if possible please leave a link to the topic on the forums that the logs are related to in your message).
  • If you have any screenshots or another file that you need to send with the logs, then you can click the Attach file button at the bottom (only one file can be attached at a time).
  • Click on Send now at the bottom once you are ready to send the logs.
Important: Please be sure to turn debug logging back off after sending us the logs. There are some negative effects to having debug logging turned on, such as reduced performance and wasting hard drive space, and it is not recommended to leave debug logging turned on for a long period of time unless it is necessary to collect debug logs.

Please note that if you have a lot of debugs logs, then you should not send all of them. There is a size limit, and currently there is no error if the message is rejected due to the size being too large. Normally we only need one copy of the 4 or 5 different logs that have been saved after the time you reproduced the issue (the list shows what time each log was saved). Those logs have the following names:

  • Security Center
  • Protection Service
  • Real-Time Protection
  • Firewall
  • Logs database (contains the logs you can view in Emsisoft Internet Security by clicking on Logs at the top of the window).

Share this post


Link to post
Share on other sites

It is not a universal problem.  I am running latest version of EIS and SD.   No issues here as of this date and no exclusions.

 

What other security software and similiar software do you run

Share this post


Link to post
Share on other sites

Here's instructions for debug logs:

  • Open Emsisoft Internet Security from the icon on your desktop.
  • In the 4 little gray boxes at the bottom, move your mouse into the one that says Support, and click anywhere in that gray box.
  • At the bottom, turn on the option that says Enable advanced debug logging.
  • Either click on Overview in the menu at the top, or close the Emsisoft Internet Security window.
  • Reproduce the issue you are having (update to the beta again, wait for the error message to happen, and then downgrade from the beta).
  • Once you have reproduced the issue, open Emsisoft Internet Security again, and click on the gray box for Support again.
  • Click on the button that says Send an email.
  • Select the logs in the left that show today's dates.
  • Fill in the e-mail contact form with your name, your e-mail address, and a description of what the logs are for (if possible please leave a link to the topic on the forums that the logs are related to in your message).
  • If you have any screenshots or another file that you need to send with the logs, then you can click the Attach file button at the bottom (only one file can be attached at a time).
  • Click on Send now at the bottom once you are ready to send the logs.
Important: Please be sure to turn debug logging back off after sending us the logs. There are some negative effects to having debug logging turned on, such as reduced performance and wasting hard drive space, and it is not recommended to leave debug logging turned on for a long period of time unless it is necessary to collect debug logs.Please note that if you have a lot of debugs logs, then you should not send all of them. There is a size limit, and currently there is no error if the message is rejected due to the size being too large. Normally we only need one copy of the 4 or 5 different logs that have been saved after the time you reproduced the issue (the list shows what time each log was saved). Those logs have the following names:
  • Security Center
  • Protection Service
  • Real-Time Protection
  • Firewall
  • Logs database (contains the logs you can view in Emsisoft Internet Security by clicking on Logs at the top of the window).

I just re-installed it.

The problem is that once this happens I can't fire off EIS from the icon on the desktop, it's all dead...nothing works. No GUI no menu no nothing.

Webroot and Eset Antivirus is what I am running in addition to EIS.

Share this post


Link to post
Share on other sites

The problem is that once this happens I can't fire off EIS from the icon on the desktop, it's all dead...nothing works. No GUI no menu no nothing.

That's pretty common when a problem by another anti-virus software opening hooks to Emsisoft Internet Security's running processes. Have you tried adding the Emsisoft Internet Security folder to the exclusions in your other security software, and then restarting the computer? The folder should be as follows:

C:\Program Files\Emsisoft Internet Security

Share this post


Link to post
Share on other sites

I just re-installed it.

The problem is that once this happens I can't fire off EIS from the icon on the desktop, it's all dead...nothing works. No GUI no menu no nothing.

Webroot and Eset Antivirus is what I am running in addition to EIS.

 

Ouch.  I am not surprised you are having a conflict.   Try starting with uninstalling Webroot and go from there.

Share this post


Link to post
Share on other sites

... Try starting with uninstalling Webroot and go from there.

That's another possible solution. We usually don't recommend more than 2 programs with real-time protection be installed at the same time.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.