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.