The issue with KAR is that they produced a product that concentrated on Cloud detection first with mechanism detection as an afterthought. This surprised me as this is the worst possible approach to employ to protect against ransomware, especially for an application geared to the business realm. As the Pro Blackhats are morphing their malware a few times daily, Cloud detection via definitions is guaranteed to fail, and not developing a mechanistic based blocking approach to the most common ransomware being morphed is beyond inexcusable.
The sad thing is that one will see reviews of KAR by both Pro and Amateur reviewers that will give it excellent marks. The reason for this would be that the tests will concentrate on either older samples (covered by the Cloud) and Script-Kiddie morphs of common stuff that will be stopped by the mechanistic based module. The problem here is that although many samples of this kind of stuff can be found (I also did this in the first section of this video), these malware samples constitute only a small fraction of the ransomware being churned out. The samples on which KAR failed currently constitute the bulk of the ransomware being produced.
In short, when watching a review don't be impressed by the QUANTITY of malware used, but instead insist on their Quality and pertinence (Rant ends).