Why did NOD do the following scan?

Discussion in 'NOD32 version 2 Forum' started by ejr, Aug 16, 2006.

Thread Status:
Not open for further replies.
  1. ejr

    ejr Registered Member

    Nov 19, 2005
    I was revieiwng my NOD scanner logs this evening and noticed one that seemed odd. I have all my other scans programmed to run at 7:15pm. This scan ran this morning at 6:30am. I wasn't even at my computer then. Any ideas what this could be? (see below)

    Scan performed at: 8/16/2006 6:33:52 AM
    Scanning Log
    NOD32 version 1.1709 (20060816) NT
    Command line: C:\Documents and Settings\Owner\Start Menu
    Operating memory - is OK
    Active boot sector of the 1. physical disk - Error reading disk sector

    Date: 16.8.2006 Time: 06:34:02
    Scanned disks, folders and files: C:\Documents and Settings\Owner\Start Menu\
    Number of scanned files: 32
    Number of threats found: 0
    Time of completion: 06:34:03 Total scanning time: 1 sec (00:00:01)
  2. alglove

    alglove Registered Member

    Jan 17, 2005
    Houston, Texas, USA
    Was anyone else at the computer? He or she could have clicked on an NOD32 icon in the Start menu by mistake. o_O
  3. NOD32 user

    NOD32 user Registered Member

    Jan 23, 2005
    There's only a couple of normal ways that scan could have happened.
    One of them (the easiest way) is to right click on your start button and select NOD32 from the context menu.
    The other is via command line, something like
    "C:\Program Files\ESET\nod32.exe" "C:\Documents and Settings\Owner\Start Menu"
    Do you have a scan scheduled that only scans your start menu? In the fourth step of setting up or editing a scheduled task there is an option to set the response if a task cannot be run at it's scheduled time. A couple of these options will make the scan run as soon as possible, so that could easily account for it.

    Cheers :)
Thread Status:
Not open for further replies.