symantec endpoint protection 14 high cpu usage

Run sc config idsvia64 start= disabled or sc config idsviax86 start=disabled from cmd,.

Boot in Safe Mode and perform the following for 圆4 or x86 installations of SEP,.

BSOD workaroundsĬustomers who cannot apply the new signatures by running LiveUpdate on their systems can use the following workaround: Users who haven’t yet experienced any BSODs are advised to “rollback to an earlier known good content revision to prevent the BSOD situation,” following the step-by-step definition rollback procedure detailed here. Symantec did not specified which specific versions of Windows were in conflict with the problematic version 4 r61, nor did they begin to give any figures regarding the number of victims.

Read also: Microsoft and NIST will teach business how to install patches The updated version, 4 r62, fixed the bug, and now the developers recommend that all victims arrange it as soon as possible. Some victims reported that the problem affected dozens of machines in their organization, while others wrote that they had problems with more than 10,000 systems.įirst, users fixed the problem on their own (for example, the rollback to the previous version of Symantec Endpoint Protection helped), and then the developers finally reacted to what was happening. “Not feeling well today, but still having a better day than Symantec, who are apparently busy BSOD’ing entire enterprises through a bad signature update in their Endpoint Protection product”, - writes Twitter user addition, some users complained about an arbitrary reboot of the servers, but did not indicate which OS they were running. The affected devices malfunctioned, and the update provoked a blue screen of death (BSOD), which referred to problems with IDSvix86.sys and IDSvia64.sys. This update triggered the legendary Blue Screen of Death (BSOD).

Windows 7.8 and 10 users encountered an unpleasant problem after updating Symantec Endpoint Protection to version 4 r61.

Symantec endpoint protection 14 high cpu usage