Symantec Protection Cannot open because some Symantec services are stopped.

[BigAnvil]

This seems very much like the issue from last January...  This happens on (possibly more than just) Windows 10 clients but, it is happening on dozens of them - both clean Windows 10/SEP installs and when pushing the updated client via SEPM.

"Symantec Protection Cannot open because some Symantec services are stopped.  Restart the Symantec services, and then open Symantec Endpoing Protection."

We are running SEP(M) 14.2.1031.0100.  This happened ocassionally on 14.2.770.0000 but is happening far more with the newer version of the client.  It started happening a couple days ago on my own laptop (only have the client installed, no remote SEPM management tools or the console), but all the Symantec services are started when I check them. 

SymDiag has been run and while there are some warnings, like Symantec firewall and the Outlook scanner are not enabled, that is by our design.  It is also complaining about TCP ports 139 and 445 being open with a restricted scope.  We have restricted the scope to the server running SEPM, so that should not be a problem either.

A restart does not fix the issue.  A repair usually does not either - we typically have to reinstall but this is getting really old.  There are only two Symantec services not running on my computer when I get this error (screen capture attached).

I will open a case as the next step but cases spend so much of my time and frequently go nowhere and provide no answers, so I'm hoping someone here has experienced this and has figured it out.

 

 

[BMS777]

This has happened to me occasionally and I just redeploy from SEPM.  It has only happened a couple times on about 60 assorted W10 clients.  I use the install option to remove existing software that can't be removed automatically so the computer gets an extra reboot.  Less work for me to ensure the client functions properly. There seems to be a couple odd things lately with SEP.  I think many of them revolve around Windows 10.  Hope this was at least slightly useful to know its happening to others.

[Scott K]

We have seen something similar with SEP 14.2.1015.0.100 with Windows 10 x64 version 1803 and 1709 after installing the latest Windows 10 cumulative update each month from Microsoft and rebooting. In our case, we tracked the problem to be a conflict between SEP, old Intel LAN NIC drivers (embedded NICs our Dell OptiPlex and Latitude), and the latest cumulative update for Windows 10. If we keep the Intel LAN drivers up to date with releases by Intel then the problem doesn't come back.

[bartman]

We have the same issue since 14.2.x. Funny thing is, although it says "Symantec Protection Cannot open because some Symantec services are stopped.  Restart the Symantec services, and then open Symantec Endpoing Protection." the relevant service is running.
It is not stoppable with smc -stop. But when you try to stop the services via smc -stop and do a repair of Symantec in the software panel, that always helped me to get the service back to normal mode.

Hoping to get this fixed with SEP14.2. RU1.