Jump to content

SeriousHoax

Member
  • Posts

    62
  • Joined

  • Last visited

Posts posted by SeriousHoax

  1. You better check this two instead. NextDNS is amazing, Adguard DNS is great as well.

    NextDNS is like pihole without requiring a pihole. You can configure it to block ads, trackers, malicious, phishing domains, adult sites, safe sites, manually blocking particular sites, etc tons of customization. It's free for 300,000 queries per month and $2 per month for unlimited. 300,000 plenty for a single user.

    https://nextdns.io/

    Adguard DNS is great but don't let you configure. Blocks, ads, trackers, malicious, phishing sites and also have a family protection service if you prefer that.

    https://adguard.com/en/adguard-dns/overview.html

     

  2. 1 hour ago, Batman said:

    With "Alert", EAM does not check suspicious program via Anti-Malware Network.

    It does. When something is detected by signatures you'll see an alert. Other things that looks suspicious to behavior blocker, it'll check for reputation on Emsi cloud and if its marked as safe in the cloud then the action will be allowed automatically. 

  3. 2 minutes ago, GT500 said:

    We just released a stable update with changes that we believe will fix this issue:
    https://blog.emsisoft.com/en/36069/emsisoft-anti-malware-2020-4-1/

    If anyone who had this issue is still on the Delayed update feed, please feel free to switch back to the Stable update feed.

    Thanks. I just came here ask whether the changelog is related to this one. Good to know it's finally fixed.

  4. You should remove the (Windows Defender) word in parenthesis from this popup. There's no need to diss Windows Defender for nothing. It's kind of a scummy behavior that I don't expect from an ethical company like Emsisoft.

    1.PNG

  5. On 2/21/2020 at 12:13 PM, GT500 said:

    @SeriousHoax and @Jakub K. thanks for the debug logs. Would it also be possible to send us FRST logs? You can find instructions for downloading and running FRST at the following link:
    https://help.emsisoft.com/en/1738/how-do-i-run-a-scan-with-frst/

    Note: When FRST checks the Windows Firewall settings, Emsisoft Anti-Malware's Behavior Blocker will quarantine it automatically. This can be avoided by clicking "Wait, I think this is safe" in the notification that is displayed while FRST is scanning.

    I have FRST logs but it was after I uninstalled Emsisoft due to the bug. Would this log be helpful? If yes then how should I sent it to you?

  6. 31 minutes ago, JeremyNicoll said:

    Not unless the logs you attached are /debug/ logs - which you'd have had to enable (at the foot of the list of options in: Settings - Advanced).

    Yes I enabled that before submitting the logs. Logs attached above should have the info I guess.

    32 minutes ago, JeremyNicoll said:

    That might not be enough.  The users who've seen this problem might have systems which share a characteristic that causes the problem.

    Already 2 other users in this thread faced similar issue so maybe they can share their logs too. In my case both times it was a fresh installation and the second time it was a freshly installed Windows 10 too so that's why I said maybe it would be possible to reproduce the issue with a new installation of Emsisoft.

  7. 5 hours ago, GT500 said:

    Would you be willing to switch back to the Stable update feed and get us debug logs?

    Since only two people have reported this issue, we won't know what's causing it until we get some debug information.

    I have attached logs in my post above. Does that contain the necessary data?

    Besides I faced another problem today. Emsi was installed and running fine but suddenly I noticed Anti malware service, the service which is related to Windows Defender was running. Why would that be enabled? Didn't go away after reboot. Even Windows Security center was showing that I have Windows Defender enabled. Other utility programs which can show security center information was showing that both Emsisoft and Windows Defender are enabled. So what actually happened? Maybe while downgrading Emsisoft didn't register itself properly in security center.

    I had no choice but to uninstall Emsisoft. Btw, in another thread I showed that even after unstallation, Emsisofts registry key was still there in security center section. The same happened again. This is a freshly installed Windows 10 so it's not possible that it's a continuation of the my previous issue but rather the uninstaller of Emsisoft probably has some kind of a bug which is why it's failing to remove its registry key from security center.

    Anyway, I had too much trouble with Emsisoft this week and won't install it again till the bugs are fixed. I may try reproducing the issue in a VM and share logs. In the meantime, maybe other users facing these issues can provide the necessary logs.

    To reproduce the bug on your system try installing Emsisoft in a fresh system where it wasn't installed before.

  8. 15 hours ago, GT500 said:

    Did you try the Delayed update feed? That would allow you to downgrade to a previous version that doesn't have this issue on your computer.

    Here's how to switch to the Delayed update feed:

     

    1. Open Emsisoft Anti-Malware.
    2. Click on the little gear icon on the left side of the Emsisoft Anti-Malware window (roughly in the middle).
    3. Click on Updates in the menu at the top.
    4. On the left, in the Updates section, look for Update feed.
    5. Click on the box to the right of where it says Update feed, and select Delayed from the list.
    6. Right-click on the little Emsisoft icon in the lower-right corner of the screen (to the left of the clock).
    7. Select Update now from the list.

     

    I haven't tried this but I don't wanna risk anything for the time being. I'll wait till it's fixed with an update.

  9. This two services are using high CPU for seemingly no reason. Specially a2start.exe which is using CPU even when the system is idle. For few seconds everything goes back to normal then it starts using CPU again. When a2start uses CPU, commservice starts using it as well. Both processes are causing unnecessary cpu usage.  What's causing this issue? I've attached the logs and task manager image.

    Logs:  link removed and sent to GT500

     

    t.png

    t2.png

  10. So not just me but many people are suffering from it. There can be unexpected issue sometimes which I understand and it's Sunday plus they also have a smaller team compared to other big guns out there so maybe that's why they've not been able to fix it yet but for me the worst thing is, they didn't bother asking the user before adding this email verification to out account. I never set up any email verification in my account they automatically added it few months ago. It surely secures the account but they should've asked the user's permission before doing it. This is absurd and extremely frustrating.

×
×
  • Create New...