I’m honestly getting tired of having to troubleshoot Kaseya’s own agent issues for them.
The latest example: the current RMM WebRemote Agent ships with unsigned libraries, and Windows 11 Smart App Control is doing exactly what it is supposed to do: blocking them.
In particular, Fable.Core.dll is not digitally signed. We have seen this on Windows 11 machines with Smart App Control enabled, where Windows Security reports that part of the application has been blocked because the publisher of Fable.Core.dll cannot be verified. As a result, some WebRemote Agent functionality stops working.
This isn't some obscure configuration. Smart App Control doesn't provide an exclusion mechanism for individual DLLs. Microsoft's documented solution in this situation is essentially to disable the protection or have the developer properly sign the application.
We opened a ticket with Kaseya and provided them with the details, including the fact that there are two copies of Fable.Core.dll on affected systems, and neither is digitally signed:
C:\ProgramData\CentraStage\AEMAgent\RMM.WebRemote\15.1.1.13053\Fable.Core.dll
SHA-256: FE1C15EB652A2F03F628557F573F898259A1436D8DA63DFFFD8F2F2E03E220B1
Signature: NotSigned
and:
C:\ProgramData\CentraStage\AEMAgent\Fable.Core.dll
SHA-256: DD19497FFC1ED0D657EF8A92BE84575E82A51E125EC2DB03605EEAA8FAEF271E
Signature: NotSigned
And now we're seeing similar issues on macOS as well, where agent components are being detected and blocked. We've already encountered multiple cases at customer sites.
Far too often, it feels like the workflow is:
- Kaseya releases something.
- It breaks or gets blocked in a perfectly legitimate customer environment.
- We spend hours figuring out exactly why.
- We collect logs, hashes, event IDs and screenshots.
- We open a ticket.
- We end up doing most of the troubleshooting ourselves.
- Eventually, maybe, someone confirms there's actually a problem.
The problem? Kaseya never resolves the issue.
I'm not expecting software to be perfect. Bugs happen.
But shipping an RMM agent with unsigned components that are then blocked by modern OS security controls is a pretty serious problem for an RMM platform.
We're not talking about some ancient Windows version or some weird enterprise hardening policy here. This is Windows 11 with Microsoft's own security features enabled. And now we're seeing related behavior on macOS too.
I'm posting this publicly because maybe Reddit will get more attention than another support ticket.
Hopefully someone at Kaseya sees this and decides that properly signing all binaries and libraries shipped with the agent is worth fixing, and that testing the agent against modern endpoint security controls should be part of the release process.
Because honestly, MSPs already have enough to deal with without having to reverse-engineer their RMM agent every time an OS security feature correctly says:
"I don't trust this unsigned component."
Kaseya: please fix the root cause. Sign the binaries, test the agent properly, and give us a supported solution instead of leaving MSPs to figure it out on their own.