I suspect I’m getting bad advice from Symantec Support, therefore asking for suggestions of theproblem I outline below.
Problem: Symantec service Symantec Endpoint Protection (SepMasterService) randomly doesn’t start on a reboot or booting. A reboot or running SymDiag with Debug Logging option fixes the problem temporally. The Debud Logging option from SymDiag runs a command to stop and then start the Symantec Endpoint Protection (SepMasterService) service at which point this service starts normally. Windows Event Logs indicate that the Symantec Endpoint Protection (SepMasterService) service stops on shutdown, but on boot there is no call to start this necessary service.
Affected Operating Systems: Windows 10 Professional x64 1709 (not observed with Windows 10 1703 or our Windows 7 computers)
Affected Version of SEP Client: 14.0.3897.1101 (14 RU1 MP1b) and 14.0.3892.1101 (14 RU1 MP1a)
Diagnostics Provide to Symantec Support: Numerous SymDiags from several different computers with and without Debug Logging option have been provided while the problem was occurring
Initial Proposed Solutions from Support: I was initially told this was a known bug with 14.0.3892.1101 (14 RU1 MP1a) and therefore I upgraded SEPMs to 14.0.3897.1101 (14 RU1 MP1b), upgrade affected clients, and additional computers with 1709 version of Windows 10. However this problem seems to be more wide spread with 14.0.3897.1101 (14 RU1 MP1b) and latest update for Windows 10 1709, KB4088776 (https://support.microsoft.com/en-hk/help/4088776), released a week ago.
Current Proposed Solutions from Support (as I understand): Install KB4073290 per TECH248552 (https://support.symantec.com/en_US/article.TECH248...) because this problem has been seen by Symantec Support and only solution from Symantec Support is to install the corresponding KB listed in TECH248552 (https://support.symantec.com/en_US/article.TECH248...) while 14.0.3897.1101 (14 RU1 MP1b) is installed.
Problems with Current Proposed Solution from Support: Checking Microsoft’s KB article for KB4073290 (https://support.microsoft.com/en-hk/help/4073290/u...) stated that is a cumulative update for Windows 10 Version 1709 with AMD processors only. The affected systems are running Intel processors including the system (Intel Core i5-6500) looked at by support this afternoon via WebEx. Also this cumulative update has been superseded by sequential cumulative updates, including KB4088776 (https://support.microsoft.com/en-hk/help/4088776) released by Microsoft March 13, 2018, and installed on the affected systems.
Background History of these 1709 Systems: These systems were originally Windows 10 x64 Professional 1703 systems which had both KB4057144 (listed in TECH248552 (https://support.symantec.com/en_US/article.TECH248...) and 14.0.3892.1101 (14 RU1 MP1a), had one or more cumulative updates for 1703 installed (KB4074592, KB4077528, KB4092077), upgraded to 1709, then latest cumulative update(s) for 1709 installed, and then SEP upgraded to 14.0.3897.1101 (14 RU1 MP1b).
Any ideas or suggestions would be greatly appreciated.