Knowledge Center

Microsoft Memory Manager and VirusScan Enterprise 8.8
Technical Articles ID:   KB76157
Last Modified:  4/7/2017


McAfee VirusScan Enterprise 8.8.x

Microsoft Windows Memory Manager

For details of VSE 8.8 supported environments, see KB51111.



Products like VirusScan Enterprise (VSE) and McAfee Agent (MA) do not dictate the paging of physical memory (RAM). This function is handled by the Microsoft Memory Manager, which determines when memory should be paged to disk to free physical memory.

There is a scenario where memory can be migrated from virtual (paged) to physical (active) memory as a result of memory scanning by VSE. Scanning of memory can occur as a result of the Processes on Enable setting for the On-Access Scanner or when you perform an On-Demand Scan of memory on running processes.  If you are running applications that are sensitive to the allocation of physical memory, you may choose to disable these VSE features.

The product development team has assisted in the investigation of various system events that can lead to the supposition that McAfee has paged memory that was in use by non-McAfee tasks. While McAfee products do consume memory, they do not request the paging of physical memory. The consumption of physical memory is very dynamic; when physical memory resources become depleted, the Microsoft Memory Manager pages the contents of seldom-accessed physical memory to disk to free physical memory for use by more currently demanding tasks.

This behavior is described in depth in the following Microsoft article: http://support.microsoft.com/kb/918483

The consumption of physical memory is a result of the current product architecture. If you have a suggestion or design enhancement request to improve protection and performance. The product development team recommends that you submit a Product Enhancement Request.



If you are running applications that are sensitive to the allocation of physical memory, you may choose to disable the following VSE features:
  • Processes on Enable (Requires Reboot)
  • Memory for Rootkits and Running Processes (located in the On-Demand Scan section)


The content of this article originated in English. If there are differences between the English content and its translation, the English content is always the most accurate. Some of this content has been provided using Machine Translation translated by Microsoft.

Rate this document

Did this article resolve your issue?

Please provide any comments below

Affected Products

VirusScan Enterprise 8.8


This article is available in the following languages:

English United States

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms

 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.