tetonbob

Thanks for your report, Virginia!

Thanks for the feedback. The inconsistent nature makes it a bit more challenging to identify the problem and to begin to formulate a possible solution. I've sent you a Private Message.

Hi Virginia. Can you tell us exactly which games you're seeing the issue with please? Is it always the same game, or is it random? It looks like you say it can happen during an attempt to launch a game, install a game, or upgrade a game, is that correct? I've been trying to reproduce this with several of the free games on the Big Fish platform, but I've not seen any issue. If this is something you can reproduce even somewhat reliably, I'd like to request some additional diagnostic info. Please let me know.

Great, thanks for your report. Please do let us know if this same file version gets detected again. It should not.

Yes, it should no longer be detected, even if you remove the exclusion for it. That being said, it's not harmful to keep it in the exclusions list.

For others who may read this topic.... For XP and Vista, you'll need to use the legacy installer: https://downloads.malwarebytes.com/file/mb3_legacy See:

Thank you for the file. So even after Rich's post above you were still seeing a detection on the same version of NomadeskClient.exe ?

Hello, duginov Can you see if this file exists, and attach it if it does? C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\ArwDetections\3b2ba044-9805-11e8-8f9f-001fbc08959f.json Thanks.

Hi @Clutch Cargo - thanks for your report. This has already been fixed as a false positive and should no longer be detected. To restore function to the file, temporarily disable the Ransomware Protection, and then re-enable it. That should free it up for use.

If it were a complete memory dump, it would be located at C:\Windows\MEMORY.DMP You'd need to copy it from that directory to your desktop before being able to zip. It would likely be too large to attach to a forum post, you could use an upload site such as wetransfer.com and then provide the link to @dcollins or myself via a reply here, or a Private Message. It's possible it's not a complete dump, but a minidump in which case it would be located at C:\Windows\minidump

Hello again, @AnandaT We believe this issue is related to similar reported issues with the Web Protection, for which we believe we have a fix in our upcoming release. The specific date of that release is yet to be determined, but it's currently undergoing internal testing.

Hello. Thanks for confirming. Let me confer with my colleagues.

Greetings, @AnandaT - If you disable Web Protection only, does that provide a workaround for you?

Great, thanks for the followup, Bill! And for your patience.

My apologies, mb2003. I did overlook your original comment about this particular issue being related to the Web Protection. We are aware of a similar issue as well, unfortunately it's still under investigation and did not make it into this latest release. I've been able to reproduce this issue, and will let our engineers know so they can include this program in the investigation. For now the only workaround we can suggest is to disable Web Protection while the affected application is checking for updates.