Microsoft Edge slow website load times when Endpoint Security is on

[GC82]

Hello there!

I have a user on Windows 11 24H2 with Microsoft Edge 130.0.2849.46 and Cisco Secure Endpoint 8.4.2.30317.

The user is experiencing issues with slow load times in Microsoft Edge. For example, it takes 5-7 seconds to load google.com. It can also take 5-7 seconds to open Settings or the F12 developer tools.
If I disable Cisco Secure Endpoint, Microsoft Edge works without any issues.
There are not the same issues in Google Chrome, for example.
I've tried Edge.Dev and also disabled all extensions - with no effect - same issue.

Does anyone know of a similar problem and know of a solution?

[Matthew Franks]

Have you tried disabling various engines in the policy to narrow it down? TAC can help you troubleshoot if you open a case with them. You might need an exclusion for something that is causing excessive scanning.

Thanks,

-Matt

[GC82]

Thank you for the suggestion.
Disabling the different engines etc. does not seem to have any effect on the error. Edge only works normally when fully disabling Secure Endpoint with the sfc.exe -k command.

[Matthew Franks]

In that case, I'd suggest working with TAC so they can help you isolate the issue.

-Matt

[Marlin]

We're seeing the same issue at one of our customers. Created a TAC for this just now.

[Marlin]

- removed -

[GC82]

I've been doing some more testen and narrowed it down to the "Exploit Prevention" feature.
If this is set to Block, we get the problems in Microsoft Edge. If set to Disabled Edge works fine.

[Bas S]

We are seeing the same. With exploit prevention on Block or Audit the performance issue is present. After disabling the module the issue goes away.

[Matthew Franks]

If you open a TAC case, they can work with you to narrow down a specific feature of Exploit Prevention that may be causing the issue (which we can get resolved in a future release) or offer options for exclusions to resolve the problem.

Thanks,

-Matt

[Panthro79]

Glad we didn't roll 24H2 out further than a few test users (who confirmed they have the issue), this would have been a huge problem.  Is there anything that can be changed within Edge to resolve this?

[GC82]

Cisco support made a change in their backend that resolved the issue for affected users in my solution.
The issue has now been escalated to Cisco's Exploit Prevention team to work on a permanent fix.
The case is still open. I will update this thread when I have news on the case.

[Panthro79]

I can't believe how long this has gone on and Cisco still haven't issued a fix yet

[GC82]

We tested a new Exploit Prevention Engine together with Cisco yesterday that fixed the issue. However, at this time, I don't have a timeframe for the general implementation of the fix.

[chickenriceandbeans]

How did they resolve it?

[chickenriceandbeans]

Hi,

Is there any update or solution regarding this issue? If anyone knows, could you please share the information?