symantec endpoint protection uninstall failed

There should be no other notifications displayed and no restart of your computer is required. When the process runs, you will see a notification that the SEP uninstall is proceeding. The removal process will begin on Friday, May 18, and continue until complete.įor Mines Windows computers that are joined to the ADIT domain, the SEP removal process will occur with little to no impact on your ADIT login routine. We are required to remove SEP client software from all Mines computers. SEP was installed on Mines computers and made available for students, faculty, and staff for use on their personally owned computers as well. Start the Cryptographic Services service.Computing, Communications, and Information Technologies (CCIT) will end our subscription to Symantec Endpoint Protection (SEP) security software effective May 31, 2018. Stop the Cryptographic Services service. Click start->run and type services.msc to open the system services dialog, then click OK. Navigate to %WINDIR%System32CatRoot2 and locate the file edb.log To fix issues with Windows XP complaining that each driver is unsigned ( MS KB822798):

After following the procedure below, I was able to uninstall and re-install Symantec EP using Add/Remove Programs. Luckily, however I noticed the issue with unsigned drivers when plugging in my thumb drive with CleanWipe on it. Next I tried CleanWipe from Symantec (which is supposed to uninstall Symantec EP manually) – it also failed to uninstall Symantec EP. So I tried uninstalling Symantec…got a failed error message and the product did not uninstall. Couldn’t be pinged and when I got onto the physical workstation it seemed like the entire network stack was out of whack.ĭouble clicking Symantec Endpoint protection revealed that the Firewall was was “malfunctioning” After the system rebooted at the end of the installation, it appeared offline. I found out about this problem after remotely pushing Symantec Endpoint Protection 12.1 managed client to an XP workstation via the network. Here’s how to fix it if it ever happens to you: Long story short the issue was the cryptographic service and the edb.log file. As if XP on a production Dell Optiplex 330 in 2012 isn’t lame enough. So, install a printer or pop in a thumb drive, and you get to click “Continue” a gazillion times. An XP SP3 system where all windows drivers including mass (USBSTOR.SYS) suddenly appear unsigned. So I saw a strange one today and got to exercise my noodle.

Symantec endpoint protection uninstall failed