Author Topic: aswboot.exe keeps trying to run at boot  (Read 6615 times)

0 Members and 1 Guest are viewing this topic.

WhiteZero

  • Guest
aswboot.exe keeps trying to run at boot
« on: August 13, 2010, 12:03:09 AM »
I'm on Windows 7 64bit.
Every time I boot windows it tries to run aswboot.exe, the Avast boot scanner, and says it could not find the process. Windows then boots up normally.

This all started after I tried to run Diskeeper's boot-time defrag. It must have somehow triggered Avast too. Is there any way to tell Avast to stop trying to run the boot scanner? Especially when the boot scanner doesn't even work for 64bit.  lol

I guess this might not be Avast's fault at this point and I somehow need to edit my boot sequence to stop it.

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11849
    • AVAST Software
Re: aswboot.exe keeps trying to run at boot
« Reply #1 on: August 13, 2010, 12:09:52 AM »
Huh... I don't see any way how the boot-time scanner could have been scheduled on a 64bit OS...
Anyway, please post the content of the registry value BootExecute in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

WhiteZero

  • Guest
Re: aswboot.exe keeps trying to run at boot
« Reply #2 on: August 13, 2010, 12:11:39 AM »
Huh... I don't see any way how the boot-time scanner could have been scheduled on a 64bit OS...
Anyway, please post the content of the registry value BootExecute in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager


Ahha! Good call!
autocheck autochk *
autocheck aswBoot.exe /A:"*" /L:"1033" /heur:80 /pup /archives /IA:0 /KBD:3 /dir:"C:\Program Files\Avast5"

I guess I can just get rid of that 2nd line.

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11849
    • AVAST Software
Re: aswboot.exe keeps trying to run at boot
« Reply #3 on: August 13, 2010, 12:28:33 AM »
Yes, that's right - though I still don't know how it got there.

WhiteZero

  • Guest
Re: aswboot.exe keeps trying to run at boot
« Reply #4 on: August 13, 2010, 01:02:17 AM »
Some kind of weird glitch when Diskeeper tried to schedule it's boot-time defrag? They happened at the same time, so it must have been.