Though that last message was directed to Cathy because in lieu of the request for laymen terms... I posted it on IT-DISCUSS for the benefit of all those subscribed to the list who may need the simpler instructions.

Also, because Greg has just posted that the issue seems to at least resolved, at least temporarily, when simply uninstalling and reinstalling ESET NOD32 I would like to recommend to Cathy and all others following my directions based on Andrew's discovery to try to simply uninstall and reinstall NOD32 while skipping the Windows Update KB972260 removal step... if THAT doesn't work then follow all the steps.

As I've said, I'm working on a batch file that automates this... once I get it working I will post a link to it.


On Thu, Jul 30, 2009 at 9:15 PM, Tyler Whitney <[log in to unmask]> wrote:
I have not tried the fix myself just yet... I am in the process of testing it on my home machine here... I am making a batch file for each step I do... so I can link to it so everyone will be able to benefit if I get something working. However, what Andrew claims his fix was, was to uninstall ESET NOD32 AntiVirus and then uninstall the update KB972260, a Windows update fixing a vulnerability in most versions of IE... then reinstalling the antivirus software.
So here is what I would do... restart your system in Safe Mode... you do this by holding the F8 key when first booting the computer and choosing "Safe Mode" in the option list. Your system should then start and allow you to login to the computer with the administrator account "or your account if you are an adminstrator on the system" ...

Once in the system get the Control Panel, usually by clicking Start -> Control Panel... and then choose Add/Remove Programs option. From there choose ESET NOD32 antivirus, click the change button and follow the prompts to remove it. After, click the check box at the top of the Add/Remove Programs window so all the Windows Updates appear in the list and choose KB972260 and remove it.

Then you can go to and choose AntiVirus: ESET NOD32 and reinstall it. However, it is still too early in the game to be sure that it is a combination of both the update and the antivirus program, right now it seems to be the issue... but evidence does point to it.

Hope this helps a little.


On Thu, Jul 30, 2009 at 8:37 PM, Catharine A. Muskus <[log in to unmask]> wrote:
Tyler, I'm having the same issue at home on my laptop. Can you describe the fix in slightly easier layman terms. Thanks, Cathy

Quoting Tyler Whitney <[log in to unmask]>:

Glad to know we are not the only ones. This afternoon a few of us in ResLife
stayed a little late to see what the heck was up with our machines. It
wasn't happening to everybody, but seemed to be related to Windows Updates
we had done during the day and we all noticed NOD32 was taking 99% of the
CPU usage... so explorer would not respond to anything. I tried a couple of
tricks... ended up getting my machine to kind of work with a local account
and limited startup... of course safe mode works.

Thanks for this wealth of information... looks like tomorrow morning will be
slightly easier knowing we have a fix for it. At the moment it was only us
IT guys that had the problem... luckily... we will see how the rest of our
department pans out tomorrow.

Tyler Whitney
IT Support Specialist
Residential Life Department
The University of Vermont

On Thu, Jul 30, 2009 at 6:49 PM, Andrew Hendrickson <
[log in to unmask]> wrote:

Okay, tomorrow may just be a really really bad day for everyone.  Just fair

I've had two reports of machines freezing up with a busy cursor, one Vista
SP2, ESET NOD32 version 4 and one Windows XP SP2, ESET NOD32 version 3.

On the Vista machine a "failure - security options: Login process has
failed to create the security options dialog" would appear.

On the XP machine, Windows Explorer simply freezes and no keystrokes get a
response, including the venerable control-alt-del.

On the Vista machine I discovered that KB972260 had just been installed.
 When I removed that KB AND removed ESET NOD32, the problem went away.  If I
tried to run the machine after just removing the KB, the problem remained.

I confirmed that this was also the case on the Windows XP machine as well.

KB97260 appears to be a critical out of band update released to rectify
some serious security flaws in Internet Explorer and is an update for all
flavors of Windows currently supported and all flavors of IE.

And, just to set my evening to "extra crispy" when I returned to my office
my own Vista desktop was waving it's "Failure - Security Options" freaky
flag.  ;-)

So far the only thing that appears to work is to either remove the KB and
ESET, or remove both, block the KB in Windows Update and reinstall ESET.

Perhaps we could block this particular KB at the update server until ESET
gets this cleared up?

I don't think that this is just a bad ESET definition file, because the
machine runs fine with the KB removed and blocked but ESET installed.

Andrew Hendrickson
CAS, IT Administrator
UVM, College of Arts & Sciences
438 College Street #402
Burlington, VT

802-656-4529 (fax)

[log in to unmask]

To submit a request for service please use:

Catharine Muskus, MS, APRN, FNP-BC
Clinical Assistant Professor
Department of Nursing
203 Rowell Building
University of Vermont
Burlington, VT 05405
Fax: 802-656-8306

"If you tell the truth, you don't
have to remember anything"