AppGuard's Memory Guard provides side-by-side memory protection and not in-line (parent > child) memory protection. It was never designed nor implemented for in-line blocking. That implementation was deliberate. Therefore, Memory Guard does not stop hollow process. Other protection mechanisms in the AppGuard product protect the system and valuable user files if the product is properly configured and used.
Dynamic forking, technically, is inherently different because of the parent > child relationship.
Last edited by a moderator: