Avast boot time scan wont run

[Vic]

Hi, When i try to run a boot time scan Avast quits with an unhandled exception error which vanishes too quick to read the rest of the details. Nothing gets scanned and no entry is made in the logs. I have just installed avast on my laptop after having to restore it to factory setup due to a driver problem. This installed Mcaffee security center which of course I removed (as the outlook intergration kept hanging and even when it didnt it slows outlook down unlike the avast integration). I installed avast from the web today, had it check for updates after I renewed my key as it had expired recently. set it to do a scan on reboot and set it off. I am running windows xp ver 5.1,build 2600, sp2.0 on a Gateway mx6922b laptop. No usb items connected at boot.

All critical updates are installed except latest internet explorer as I hate it and usually use firefox.

I hope this is just a glitch and can be sorted out.
Cheers
Vic

[news]

Hi....
Someone reported this problem yesterday. avast! already knows of the problem.

The information in the link below explains....
http://forum.avast.com/index.php?topic=30138.0
Hope this helps.

[Vic]

Thanks just seen the post. But it claims it has been sorted, yet I have the same problem even after running a complete update. maybe the mirror my update used has not yet got the updated files yet or maybe its an incompatibility with my system. But thanks for pointing it out. I should have looked closer before posting.

But after reading the other post I found the log file. Here is a cut and paste of it.

CmdLine - quick
aswBoot.exe /A:"*" /L:"English" /archives
CmdLine end
CreateKbThread
new CKbBuffer
CKbBuffer::Init
CKbBuffer::Init end
NtCreateEvent(g_hStopEvent)
NtAllocateVirtualMemory - stack
NtGetContextThread - NtCurrentThread
NtCreateThread - KbThread
CreateKbThread end
NtInitializeRegistry
KbThread start
ReadRegistry
DATA=C:\Program Files\Alwil Software\Avast4\DATA
PROG=C:\Program Files\Alwil Software\Avast4
BUILD=1029
Microsoft Windows XP Service Pack 2
SystemRoot=C:\WINDOWS
TEMP=C:\WINDOWS\TEMP
TMP=C:\WINDOWS\TEMP
ReadRegistry end
CreateTemp
CreateTemp end
cmnbInit
SetFolders
SetFolders end
aswEnginDllMain(DLL_PROCESS_ATTACH)
InitLog
InitLog end
CmdLine - full
aswBoot.exe /A:"*" /L:"English" /archives
CmdLine end
Unschedule
61,00,75,00,74,00,6F,00,63,00,68,00,65,00,63,00,
6B,00,20,00,61,00,75,00,74,00,6F,00,63,00,68,00,
6B,00,20,00,2A,00,00,00,61,00,73,00,77,00,42,00,
6F,00,6F,00,74,00,2E,00,65,00,78,00,65,00,20,00,
2F,00,41,00,3A,00,22,00,2A,00,22,00,20,00,2F,00,
4C,00,3A,00,22,00,45,00,6E,00,67,00,6C,00,69,00,
73,00,68,00,22,00,20,00,2F,00,61,00,72,00,63,00,
68,00,69,00,76,00,65,00,73,00,00,00,00,00,
Unschedule end
LoadResources
LoadResources end
InitReport
InitReport end
NtSetEvent(g_hInitEvent)
InitKeyboard
s_dwKbdClassCnt: 2
InitKeyboard end
GetKey
CKbBuffer::Wait
CKbBuffer::Get
CKbBuffer::Get end
CKbBuffer::Wait end
FreeMemory: 895381504
aswintegInitialize
avworkInitialize
Unhandled exception! Error:17419718
GetErrorText
Unhandled exception Error:0xC0000005 {The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".}


Dont know if its identical as yet as its a lot to read and compare.

[news]

It hasn't been fixed yet...even with the recent update.

According to igor they aren't sure if it will be fixed until the program update arrives.
As DavidR stated...they may include a quick fix again in one of the VPS updates later...maybe not.

We'll have to wait and see what the avast! team does.  In the mean time...if you need to run a scan outside the normal one...try the safe mode scan as DavidR stated. It does work as fewer items load at startup and gives the antivirus software a better chance at catching infections.

[Vic]

Thanks will try that now. This is the first time Avast has ever let me down in 2 years so I wont hold it against them. Keep up the good work team.

[Lisandro]

Thanks will try that now. This is the first time Avast has ever let me down in 2 years so I wont hold it against them. Keep up the good work team.

Alwil acknowledges the boot time scanning bug (http://forum.avast.com/index.php?topic=29999.msg247134#msg247134). You'll need to wait for the next program update. Igor answer here that the problem persists: http://forum.avast.com/index.php?topic=30138.msg248589#msg248589

[news]

Hi Vic...

Just wanted to let you know..I just had a VPS update today 08/27/07 000769-0...did a bootscan and it is working again.

We may experience this again as they are preparing to do a program update...never fear avast! is a good piece of antivirus software. Try to perform a bootscan after the update today.

Edited...had the incorrect VPS..should be 000769-0.

[DavidR]

Thanks for the update.

[news]

You're welcome for sure.