Yes, the Process Guard may not work as designed when other security solutions are enabled and protect the LSASS process. This can result in failure to obtain a process handle to access memory for LSASS processes, as other security products attempt to perform a similar action. The following is a list of features and products where this behavior can occur:
Windows Local Security Authority (LSA) protection feature, which runs LSASS as Protected Process Light (PPL).
Credential Guard
Any other security products protecting LSASS processes.
To confirm that Process Guard is working as expected, note the plugin_state field in the Process Guard SysInfo JSON data in the How to verify if the Process Guard installation succeeded question.