cancel
Showing results for 
Search instead for 
Did you mean: 

ENS on-access scan issues with Chrome.exe (75.0.3770.142)

Jump to solution

Over the past 24 hours we've noticed the on-access scan service (McShield) scanning Chrome browsers very heavily when a new browser session is launched.  We didn't make any changes to our McAfee environment during that time, and the issue seems to be only occurring with Chrome.exe and is maxing out the CPU at 100% for at least a few minutes before settling down.  We notice that the newest update for Chrome was on 7/15.  Has anybody else noticed a similar issue?

AmCore Content = 3777

Exploit prevention = 10.6.0.9419.

ATP = 10.6.1.1311

Threat Prevention = ENS 10.6.1.1550

ENS Platform = 10.6.1.1449

McAfee Agent = 5.6.1.157

1 Solution

Accepted Solutions

Re: ENS on-access scan issues with Chrome.exe (75.0.3770.142)

Jump to solution

This problem turned out not to be Chrome related, but rather changes to UEV configuration in group policy.

View solution in original post

3 Replies
parul1234 McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: ENS on-access scan issues with Chrome.exe (75.0.3770.142)

Jump to solution

Hi 

Thank you for the question.

Please check if in On Access Scan you have enabled the option for scanning during process startup.

The option states "Scan processes on service startup and content update" 

Please uncheck that option and observe if it helps.

Was my reply helpful?
If you find this post useful, Please give it a Kudos! l Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

Thanks

Re: ENS on-access scan issues with Chrome.exe (75.0.3770.142)

Jump to solution

This problem turned out not to be Chrome related, but rather changes to UEV configuration in group policy.

View solution in original post

AdithyanT McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 4

Re: ENS on-access scan issues with Chrome.exe (75.0.3770.142)

Jump to solution

Hi @nashcoop 

Kudos for letting us know that your issue is resolved. If you could spare some time in letting us know what specific policy was modified and the values, it would be helpful for other community users to understand and possibly we can come up with a KBA if we are able to replicate the scenario in our test environments.

Thanks again!

Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

Thanks and regards,
Adithyan T
You Deserve an Award
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.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community