FAQs about McShield.exe and high CPU utilization when running On-Demand scans
Technical Articles ID: KB85299 Last Modified: 11/9/2015
Why was this higher CPU usage not happening in patch 4? That was most likely because patch 4 contained a known issue where it used only one scanning thread was used during ODS.
This issue is resolved in patch 5, resulting in higher CPU utilization during ODS.
While patch 5 ODS does use higher CPU, scans finish faster. Intel Security recommends upgrading to patch 5 when it is approved for your environment, because patch 5 also contains useful security updates.
If settings on the performance tab do not change this behavior, why is that option available? Setting the system utilization on the performance tab to Low provides improved performance for other running applications. The Low setting is useful for systems with high end-user activity. Conversely, by setting the system utilization to normal, the scan completes faster. The normal setting is useful for systems that have large volumes and very little end-user activity. You can read more about this in the "Configuring Performance Improvements" section of the VirusScan Enterprise 8.8 Best Practices Guide (PD22940).
You can also make the following adjustments to ODS settings to improve performance, as required:
Enable scan cache.
Set up daily, targeted ODS for risky locations.
Set up complete ODS to run once a week.
Set up exclusions in ODS wherever needed, such as on an Exchange server.
Review KB74059 for Best Practice for On-Demand Scans in VSE 8.8.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.