@seetha123 Are you running an On Demand Scan at that the time of this behavior? In the event you are, please review best practices for ODS.
If this is not during an ODS, or when you launch a particular application, then you likely need to implement some strategic On Access Scan exclusions to eliminate scan overhead. Start with the ZZZ test from the How to troubleshoot High CPU article, and if your issue resolves then you know exclusions will solve the problem. Then, revert your policy and reproduce the issue while running a McAfee Profiler capture to determine what needs excluding. For information on wildcards for your exclusions go here.
Also check in the supported platforms article under "hardware requirements" to make sure you meet the minimums.
Was my reply helpful?
If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?