On my Vista machines,  Windows Defender is completely turned off -- both the startup item and the service is disabled.

The freezing still happens.

On the other note, I just came across an XP machine that even when I did what I did with the others (Upgraded NOD32, Updated to newest def file) it did not fix the issue.   It's the first XP machine where this was the case.

Will "Chip" Sawyer wrote:
[log in to unmask]" type="cite">
On my own Optiplex 745, I have only had the freezing problem when Windows 
Defender decides to do an automatic scan.  I have the KB972260 update and 
ESET 4.0.437.0.  And have not uninstalled and re-installed either.

I turned my Defender auto-scan off.

Not sure how useful my experience is, however, since not all computers have 
Defender.  Has anyone checked to see if it might have a role?


On Fri, 31 Jul 2009 10:04:29 -0400, Andrew Hendrickson 
<[log in to unmask]> wrote:

Okay, I have several people running NOD32 this morning with no
problems, however they all have today's definition file.  I also had
two people who *did* have problems and they had yesterday's definition

How does one remove a bad definition file from ESET and force it to
retrieve the most current?  I'd like to try that as an experiment.

On Jul 31, 2009, at 8:54 AM, Dean Williams wrote:

As we try to find a consistent pattern to the problem, one more data
point:  My GX270 is fine after restarting with the KB972260 update.

OS: Vista Enterprise, joined to CAMPUS domain
IE: 7
NOD32: 3.0.650.0, with virus definitions from 7/31

-Dean W.

On Jul 31, 2009, at 8:42 AM, Peter K Zahn wrote:

For the record, Windows 7 RC is also experiencing the same problem
with the same solution of uninstalling ESET.


Gail Starks wrote:
We have IE7 machines experiencing the problem in our office.


Tyler J Whitney wrote:
Some information you all may find interesting. So far it seems to
me to only be apparent for those users that have IE8. I have seen
a number of computers that have IE7 and the Windows Update AND
NOD32 and no problems... however, it seems those with IE8 are the
ones affected.


Quoting Jarlath O'Neil-Dunne <[log in to unmask]>:

I tried this solution and it did not fix the problem.  ESET
still maxes out
the CPU.  Completely removing ESET resolves the issue.


Jarlath O'Neil-Dunne

Geospatial Analyst

University of Vermont

Spatial Analysis Laboratory



From: Technology Discussion at UVM [mailto:IT-
[log in to unmask]] On
Behalf Of Tyler Whitney
Sent: Thursday, July 30, 2009 9:15 PM
To: [log in to unmask]
Subject: Re: Recent Windows Vista and XP freezing problems


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
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
"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/
Programs window so all the Windows Updates appear in the list
and choose
KB972260 and remove it.

Then you can go to http://uvm.edu/software/ 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]

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
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

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
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

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"

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:


Mickey Mossey

System Administrator / Programmer

University of Vermont

Development and Alumni Relations Information Systems

Personal Line: 802-656-4133 DARIS Main Line: 802-656-8310


UVM's Alumni Website:      http://alumni.uvm.edu/