Tech Forum

The last few days our Ward computer has been completely unresponsive. After a bit of troubleshooting, I found the problem to be Microsoft Security Essentials. It is no longer supported on Windows XP, and the new update has a flaw that freezes the computer.

The fix is to un-install Microsoft Security Essentials (This can't be done in Safe mode).

Also, this will require you to wait up to 10- 15 minutes after you type your Windows login, before the Desktop comes up. Once the Windows XP Desktop comes up, you should click on Start > Control Panel > Add / Remove Programs. Find Microsoft Security Essentials, and click Remove.

NOTE: Your clicks, may not bring up a Window right away. Be patient.

I understand the Church uses Sophos, but I don't know where I can download it.

Here is a link I found, that describes the symptoms I was seeing:
http://www.myce.com/news/windows-xp-sec ... ted-71147/

WorthingtonRP wrote:The last few days our Ward computer has been completely unresponsive. After a bit of troubleshooting, I found the problem to be Microsoft Security Essentials. It is no longer supported on Windows XP, and the new update has a flaw that freezes the computer.

The fix is to un-install Microsoft Security Essentials (This can't be done in Safe mode).

Thanks for sharing your experience. Hopefully your instructions won't be needed by very many people, since Sophos should have been installed long ago on all administrative computers, but your details will be quite helpful if anyone else has Microsoft Security Essentials.

WorthingtonRP wrote:I understand the Church uses Sophos, but I don't know where I can download it.

Instructions for downloading Sophos are on RKATS at Desktop Security Software (Sophos). It would be good to coordinate this with your stake technology specialist.

If Sophos isn't installed that implies that TEM isn't installed either, or isn't configured properly.

WorthingtonRP wrote:the problem to be Microsoft Security Essentials. It is no longer supported on Windows XP

It is supported. A bug in a signature update was the problem. It's since been fixed.

However, I would expect a ward computer to be running Sophos and not MS Security Essentials.