Replies: 2 comments
-
Are you using the 'generic' MeshCentral agent? Or do you have your agents customized with your own file name and branding? I also assume you probably aren't signing the agents with your own code signing certificate? All of those are somewhat necessary at this point to ensure MeshCentral isn't flagged by most antivirus apps. |
Beta Was this translation helpful? Give feedback.
-
The agent is customized, but not signed. Avast is not flagging it though. There is no notification that it was blocked. I found out by disabling Avast completely. The agent was able to connect with Avast disabled, so I started disabling features until I found Anti-Rootkit Shield causing it. I have had Avast quarantine the agent in the past, but this was not so obvious, so I posted this as a PSA. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Avast Anti-Rootkit Shield started blocking agents from connecting. I disabled it by going into Settings -> Protection -> Core Shields -> Potentially unwanted programs & tools, and un-checking Enable Anti-Rootkit Shield, then choosing MORE OPTIONS -> Until I turn it on again. Close settings and click notifications. Click the X next to the notifications regarding the disabled feature in order to stop it from warning you and reporting a problem in the Windows Security app. Hopefully Avast won't enable it again after an update. I am going to send them a message to ask if they will stop it from blocking the agent so I can enable the feature again.
Beta Was this translation helpful? Give feedback.
All reactions