The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    why does adaware 2007 sometimes require a reboot to clean after scans?

    Discussion in 'Security and Anti-Virus Software' started by ARGH, Aug 6, 2008.

  1. ARGH

    ARGH Notebook Deity

    Reputations:
    391
    Messages:
    1,883
    Likes Received:
    24
    Trophy Points:
    56
    the free version. why would it require a system reboot so it can clean the files after scanning? this is so annoying. i don't understand what it canno clean. sometimes it requires multiple reboots and scans to clean up.
     
    ARGH, Aug 6, 2008
    #1
  2. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    It's probably because the infected file is a dll or other protected system file that, if messed with during normal runtime, would just be automatically replaced from the system dll store, rendering the cleaning ineffective. Doing the clean at boot may be a way to prevent this automatic replacement from occurring. It could also be because the file in question is always in use during normal runtime, and locked by the process that's using it, thereby making it inaccessible for cleaning. Again, the file can probably only be cleaned at startup, when adaware can get a lock on it before the process that normally uses it does.
     
    Shyster1, Aug 6, 2008
    #2
  3. livesoft

    livesoft BUSTED

    Reputations:
    337
    Messages:
    1,411
    Likes Received:
    0
    Trophy Points:
    55
    Thats a full answer
     
    livesoft, Aug 6, 2008
    #3