problem - W2K/XP2 runaway system after 'apply choices' [beta 2]

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My experience with beta-1 under W2K was fine; but switching to beta-2 have me
a processor and hard drive runaway condition that mostly locked up the system
for tasks. After a quick/full scan, I would set the action choice for each
suspect item found and click apply.

I reinstalled a virgin XP2 system and have the same results as above. It
would seem my hardware configuration may be incompatible?
 
I've seen a Windows 2000 system where applying actions after a scan seemed
to go on forever (days!) However, it didn't lock the machine or make it
unusable.

When you say you reinstalled clean, and then had the same experience--what
was it detecting on a clean system?
 
Bill Sanderson said:
I've seen a Windows 2000 system where applying actions after a scan seemed
to go on forever (days!) However, it didn't lock the machine or make it
unusable.
Click to expand...

Very sluggish to mostly unusable would be a better description, only a few
times did it seem to freeze; never did it actually complete the selected
actions.

When you say you reinstalled clean, and then had the same experience--what
was it detecting on a clean system?
Click to expand...

In clean, I mean the system/os physical drive. The second physical drive
contains all my previous data. Following are the things they found - they
were all within ZIP archives from the data drive:

ABetterInternetAurora - HIGH - Failed, 0x80004005. Unspecified error
Songspy - HIGH - Failed, 0x80004005, Unspecified error
Home Watcher - SEVERE - Failed, 0x80004005, Unspecified error

BearShare - MEDIUM - (no status)
WHenU.SaveNow - MEDIUM - (no status)
RealVNC - MEDIUM - (no status)
Remotely Anywhere - MEDIUM - (no status)
TightVNC - MEDIUM - (no status)


Aside from Defender never finishing the Apply Actions function, I'm
concerned with how it regards my archive ZIP and installer files; I don't
want it nuking my complete archive of everything because it sees spyware+ in
the ZIP; and I don't want it tossing out installers either... just the
components that suck.

For example, I know BearShare contains spyware (WhenU.SaveNow) and Ad-Aware
can remove the nasty spy components - doesn't look like Defender could, but
instead would remove the whole package and/or installer.
 
The error message indicates that Windows Defender is quite aware of the
issue that you describe--it is not going to nuke your archive because one
part of the content is spyware. I don't think we are seeing the "final"
behavior with regard to threats found in archives, but I'm quite certain
that the behavior will not be to nuke the whole archive.

--
 
Back
Top