Thank you for reporting this. I have come across a very similar incident in the past where "cbengine.exe" used to get blocked as it attempts to touch ENS files during its backup routine (I presume) and thereby fails since our self protection blocks that from happening!
Thank you for the suggestion. We already have cbengine.exe set as a Low Risk process. I've checked the self-protection log file but it only contained issues with smhstart.exe which is HP's System Management Homepage Service.
Hi @marksmith972 ,
Thank you for the update. In his case I would recommend following the second post from my nd that talks about component isolation.
This would help us isolate which component is causing the issue and further add necessary exclusions as needed to specific component/feature.
As a general recommendation, I would recommend progressive disabling of components to narrow down which component is exactly causing the issue here!
It would go something like this: