To investigate the issue, McAfee built a test harness tool to invoke cryptographic APIs, and observed the same memory increase in the test tool. This issue occurred without the presence of any McAfee code. So, McAfee engaged Microsoft to investigate this issue. Microsoft confirmed that the root cause is a bug in CRYPT32.DLL.
 

The rate of memory increase is entirely dependent on system use. And, the requirement for McAfee to invoke cryptographic APIs to validate and verify system calls being made that use McAfee code. Internal testing shows that you might need to reboot after about five days. The reason is because mfevtps.exe memory use reaches a level, more than 1 GB, which noticeably impacts system performance.