Spyware scan details

  • Thread starter Thread starter Greg
  • Start date Start date
G

Greg

Please Explain

Spyware Scan Details
Start Date: 2/3/2005 2:00:25 AM
End Date: 2/3/2005 2:07:11 AM
Total Time: 6 mins 46 secs

Detected Threats
No spyware threats were found during this scan.

I am sure I was not logged in, and that my computer was
off.

Thanks,
Greg
 
There are some bugs in Microsoft Antispyware, but none that I've heard of
that can turn your computer on and off again, and record timestamps in a log
file.

So--if your system clock is correct, I'd say that you were mistaken about
the machine being off and you being logged out.

I can't explain the apparent contradiction. What about the timestamps on
files in the installation directory for Microsoft Antispyware--I don't know
whether this would leave such a trail, but are any of them between 2 and
2:30 this morning?
 
On my system, it looks like at least errors.log and
gcThreatAuditScanHistoryData.gcd get timestamped bracketing the scan, which
on my system runs without UI (looks like setting that via the command-line
switches leaves it set for the gui!) My scan runs at 11:11, and errors.log
has that timestamp, and the longer one is stamped at 11:50 which was
probably the end of the scan--makes sense.
 
And, of course, I meant to ask you whether you were going to test by logging
off your machine and turning it off overnight. <g>
 
Bill Sanderson said:
And, of course, I meant to ask you whether you were going to test by
logging off your machine and turning it off overnight. <g>
Click to expand...

Well I didn't get a peep out of my system (full shut down at 1:45 AM) at
2:00 AM. Maybe the poster thought he was shut down, but was stand by or
hibernation? I'll test those tonight.

Cordially,
Steven Fredette
President http://www.prowebsites.net
Indianapolis, Indiana. USA (-5 GMT/UT)
"For Your Internet Wants and Needs" Since 1997
 
I had a later thought which I wrote in another thread which involved the
same poster, I think. The PC in question is a work machine.

On some large (and not so large) networks, there are systems to turn
machines on nightly for various maintenance operations. I do this myself in
several small offices, but manually--i.e. I can VPN in to a server, turn on
a range of machines, make sure they are patched up to date, and turn them
off again.

This is one possible explanation for what he saw.
 
Back
Top