I’m using the lastest version of avast with the lastest VPS on WinXp Pro SP1a.
This morning, I’ve been trying to preform a boot-time scan. But when I restart my computer…I get a QUICK BLUE SCREEN FLASH the point where avast is supposed to load BEFORE XP starts with Avast beginning to start… and then before it BEGINS to scan, it bypasses the screen, fails the scan… and I’m at the login point for WinXP Pro.
I’m sitting here thinking: WHAT?! :
This has never happened before, and I have performed many boot-time scans in the past.
I ran CHKDSK /F ran this about 5 times as once never seems to be enough to get rid of errors and then tried the boot-time scan: Same result… a quick reference to the scan engine starting…and then before it can start… it bypasses and goes directly to the login screen of XP PRO.
I would really like to get this working again… and I’m wondering if anybody else is having this problem?
sigh… I thought I could get this going myself… guess not. :-\
Steele, remember me some of your configurations…
Did you install NAV before in this system?
Did you try to ‘Repair’ your avast! installation?
I’m not sure but maybe you have a report or log of the boot time scanning operation… If so, what does it tell us about?
I found this error in a log…there is an error CODE further below…this is what I saw briefly appear before a boot time scan could take.
I have not tried repairing the Avast4Home program…because I want you guys FIRST to be aware of the problem before I sweep it under the rug…that is…if a repair works. :-\
Woah… :o Is this what VLK is wanting?? I just saw that thread about 42003 errors.
CreateKbThread
new CKbBuffer
CKbBuffer::Init
CKbBuffer::Init end
ZwCreateEvent(g_hStopEvent)
ZwAllocateVirtualMemory - stack
ZwGetContextThread - NtCurrentThread
ZwCreateThread - KbThread
CreateKbThread end
ZwInitializeRegistry
KbThread start
Unschedule
Unschedule end
ZwSetEvent(g_hInitEvent)
ReadRegistry
ReadRegistry end
CreateTemp
CreateTemp end
cmnbInit
SetFolders
SetFolders end
aswEnginDllMain(DLL_PROCESS_ATTACH)
InitLog
InitKeyboard
s_dwKbdClassCnt: 2
InitKeyboard end
GetKey
InitLog end
InitReport
InitReport end
CmdLine
C:\PROGRA~1\ALWILS~1\Avast4\aswBoot.exe /A:“*” /L:“English”
CmdLine end
ZwCreateDirectoryObject - ASWObjects
LoadResources
LoadFile
LoadFile end
LoadResources end
CKbBuffer::Wait
CKbBuffer::Get
CKbBuffer::Get end
CKbBuffer::Wait end
FreeMemory: 471433216
aswintegInitialize
avworkInitialize
0, 29, 4, 0, 0
GetKey end
CKbBuffer::Put
CKbBuffer::Put end
GetKey
0, 69, 0, 0, 0
GetKey end
CKbBuffer::Put
CKbBuffer::Put end
GetKey
0, 29, 5, 0, 0
0, 69, 1, 0, 0
avworkInitialize Error:42003 <---- there it is :-
aswintegClose
TerminateKbThread
GetKey end
CloseKeyboard
CloseKeyboard end
KbThread stop
CKbBuffer::~CKbBuffer
CKbBuffer::~CKbBuffer end
aswEnginDllMain(DLL_PROCESS_DETACH)
FreeResources
CloseReport
CloseLog
Sorry, you need an advice from a programmer… It’s out of my domain. I cannot help you anymore in this trouble because I do not know how to interpret the error 42003. I have numberer errors
I’ve started to get the same error on a scheduled boot-scan.
The only recent software changes to my system that might have affected Avast is that I’ve removed Mozilla Thunderbird… Although it may be unrelated as I havent scheduled a boot-scan for a while.
OS : Windows XP SP1 - no updates since the last successful boot-scan.
Email : MS Outlook 2002
File System : NTFS
I’ve uninstalled Avast & then cleaned out any remaining avast related folders and regkeys, then after a reboot, reinstalled Avast entered my reg-code and updated the defs.
No change!
All other Avast features works a treat…
This is doing my head in, I too only ever use Avast anti-virus, I would never have Norton’s bloatware on my PC…
....
....
[bunch of some really weird stuff]
....
....
avworkInitialize Error:42003
That’s not very good I gotta say… 42003 means something like ‘general failure’ or in other words: ‘something went really wrong’ (to put politely). First, let me check if it happens in our labs… Unfortunately, no sooner than on Monday - as boot-time scanning is one of very few things I can’t try via remote access… :-\
Yea, I’m getting aboot time scan error too.
08.02.2004 17:03:47 NT AUTHORITY\SYSTEM 1656 AAVM - scanning error: x_AavmCheckBootDirectEx: avscanScanReal of *BOOTA failed, 00000005. This is on Windows XP Pro SP1 and all updates current. I’ve been able to schedule boot time scans before sucessfully until today.
Well, I may ahve fixed my problem. I uninstalled Avast and reinstalled it. It did a preboot scan just fine. I did have to reregister though after running the updates for the dat files and the program, Waiting for new key in email now.
I’ve got the same problem too. The only change I have made recently is to install Spybot from download.com and also to stop and restart system restore to clear out a potential virus.
I hope we figure it out soon. Keep us posted on your end. cheers! :-\
Well, I thought I had fixed the preboot scan error but after updating the program and entering the new reg key the preboot scan is broken again. >:(
Here’s the info, Program: Already up to date
(current version 4.1.357)
Vps: Already up to date
(current version 0404-0)
Now the program isn’t even logging the error messages with logging turned on. What gives?
Reinstalled again, entered license key and disabled auto-update.
boot scan is OK
manually updated the iAVS and the problem is back…
As VPS 0404-0 came out 2 days ago, maybe there’s a problem with vps-40400.vpu or vpsm-40400.vpu or the way the boot-time scanner is initializing the upadted database
I’ve attached a log of the update
Has everyone only had the problem in the past couple of days?
