Endpoint Protection

I have recently started to do some testing with version 14.x.  My client enviroment is mostly Windows 7 Enterprise x64 and some Windows 10 1607 Enterprise x64.  I also use Microsoft System Center Configuration Manger and that client is installed on all the machines. 

The Windows 7 machines function fine after the upgrade to 14.x.  However all the Windows 10 1607 machines have a constant failure message pop from "UpdateTrustedSites.exe"

This is part of SCCM, however the crashes don't occur when version 12.1.6 build 7004 is installed.  If I watch the process in process monitor its interacting with some registry keys that reference SEP right before it crashes. 

The following is logged in the eventviewer:

Faulting application name: UpdateTrustedSites.exe, version: 0.0.0.0, time stamp: 0x5768bae9
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff96c0000c4
Faulting process id: 0x3554
Faulting application start time: 0x01d23aab8c637865
Faulting application path: C:\windows\CCM\UpdateTrustedSites.exe
Faulting module path: unknown
Report Id: 52a92417-1a94-46af-b0c5-1481f22ea529
Faulting package full name:
Faulting package-relative application ID:

How would I go about submitting this bug?

You need to open a case with them. If it's easily re-producible they will have you enable advanced logging as well as any dumps.

I have opened a case now and I am working with support.  I have also noticed the error only occurs when logged in as a regular user.  You don't get the issue if logged into the computer as an administrator.

For anyone else having the same issues, a file exeception was added to the Exception Policy in the SEPM Console.  This appears to have "fixed" the issue.

So this happened because of the application control component needing an exception?

I faced the same in version 12 with OS win 7 since I am using system Lockdown. 

I gone through the same exceptions and it solved the issue for me as well. 

it seems System Lockdown feature set is not compatible with some applications so it generates application crash notifications if there is compatibility issue.

Hello!

We have the same issue - SEP 14 and Windows 10 (1607). I think this is temporary solution and there must be official fix.

I agree.  Adding an exception for the file is a good workaround, but by no means a solution.  I don't know if the actual problem is with Symantec or ConfigMgr, but clearly there's an issue with one of them.  It definitely began right after upgrading SEP to v14.  The ConfigMgr version has been the same for the last few months, and did not have any issues with the prior version of SEP.