Well, I’ve uninstalled it again, hopefully for the last time. did a regedit to clean it fully from the system, then reinstalled the original download I had saved on 2nd hard drive. Updated the data base files but will not update the program till this preboot problem is fixed.
Wow… thanks so much for posting your personal results guys. 
It’s good to see I’m not alone. 
I however have chosen not to do anything about this…
I don’t want to repair something or uninstall it in case there’s something there that just needs to be looked at…like the VPS or…the scanning engine.
People have already tried doing this with the same results… 
It very well could easily be fixed in an update.
Who knows. ???
At least full scans in XP PRO works okay for me.
Hope the issue is addressed sometime. :-\
… I’m a big patient wuff!! ;D
~Steele Wolf~
Well… I’ve noticed that vps 0404-1 is now released so rather go through the pain of the reinstall and reboots on the desktop I’ve just updated my laptop which never gets updated and like my desktop runs XP Pro SP1a & Avast 4.1.357
Guess what… same problem. :-[
Thing is according to the log, both vps-040400.vpu & vps-040401.vpu where installed so 040400 could still be the culprit.
The boot time scan isn’t really that important to me, I’d prefer the on-access & manual scanner to be upto date.
But I do try to fix a problem if I find it so there ya go. 
Let’s see if the Avast guys find a fix.
Vin - nethomehelp.co.uk
Well, I did the reinstall and ran a preboot scan with no problems. Let system boot up and did the data base update but not the program update. Back to square 1, preboot scan fails after updating the data base. Log file not being generated either.
- Vps: Already up to date
(current version 0404-1)
Here’s the boot log text.
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
InitLog end
InitReport
InitReport end
CmdLine
C:\PROGRA~1\ALWILS~1\Avast4\aswBoot.exe /A:"C:" /L:“English”
CmdLine end
ZwCreateDirectoryObject - ASWObjects
LoadResources
LoadFile
LoadFile end
LoadResources end
InitKeyboard
s_dwKbdClassCnt: 2
InitKeyboard end
GetKey
CKbBuffer::Wait
CKbBuffer::Get
CKbBuffer::Get end
CKbBuffer::Wait end
FreeMemory: 314761216
aswintegInitialize
avworkInitialize
avworkInitialize Error:42003
aswintegClose
TerminateKbThread
GetKey end
CloseKeyboard
CloseKeyboard end
KbThread stop
CKbBuffer::~CKbBuffer
CKbBuffer::~CKbBuffer end
aswEnginDllMain(DLL_PROCESS_DETACH)
FreeResources
CloseReport
CloseLog
Could you please start regedit, go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager, select the value BootExecute and export it to a file? If you could post the file as an attachment here, the team would like to check what could be wrong there.
I forgot to say that it will be useful if you post here the content of the file C:\Program files.…\Avast\Data\Report\aswBoot.txt
Steele, the file is C:\Program files.…\Avast\Data\Report\aswBoot.txt as I posted before… Hope this help in anyway.
I can’t post the registry information. :-
The file is 350K at least.
I can’t even post it as a .ZIP. (too many limitations on file type, size…ect)
It also can not be posted as a .TXT file because…lol…belive it or not it’s 600KB!!
I’m trying to contribute and help out the best I can… :-\
I already posted this info at the beginning of the thread, no?
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
InitKeyboard
s_dwKbdClassCnt: 2
InitKeyboard end
GetKey
SetFolders end
aswEnginDllMain(DLL_PROCESS_ATTACH)
InitLog
InitLog end
InitReport
InitReport end
CmdLine
C:\PROGRA~1\ALWILS~1\Avast4\aswBoot.exe /A:“*” /L:“English” /archives
CmdLine end
ZwCreateDirectoryObject - ASWObjects
LoadResources
LoadFile
LoadFile end
LoadResources end
CKbBuffer::Wait
CKbBuffer::Get
CKbBuffer::Get end
CKbBuffer::Wait end
FreeMemory: 471539712
aswintegInitialize
avworkInitialize
avworkInitialize Error:42003
aswintegClose
TerminateKbThread
GetKey end
CloseKeyboard
CloseKeyboard end
KbThread stop
CKbBuffer::~CKbBuffer
CKbBuffer::~CKbBuffer end
aswEnginDllMain(DLL_PROCESS_DETACH)
FreeResources
CloseReport
CloseLog
Hi there!
I want to report the same bug either. I’ve downloaded and installed Avast 4 Home at friday, ran a boot-time scan (it’ve found a trojan on my computer that my previous antivirus didn’t see). Then i’ve downloaded the most recent update - and tried to run a bootscan again and it failed with same error message! avworkInitialize Error:42003
Welcome! ;D
Just know you INDEED are NOT alone…
We’re all working together “as users” with the support team to find a fix soon.
It’s becomming more and more clear however that… although I did report the initial findings… there are many others here that are experiencing the same problem too.
I am no longer alone… and that is a relief!
Hang in there!
Kindest Regards,
~Steele Wolf~
OK I’m confirming this problem. In short, it’s a bug in the boot-time scanner. Curiously, it only started happening with VPS files version 0404-0 or later (the bug was there since Day One but it only started showing now after updating to VPS 0404-0 or later :)).
A fix will be included in the next program update, due early next week.
In the meantime, please use alternative scan methods (from the Windows GUI) - the problem only applies to the Boot-Time Scan module.
Thanks
Vlk
Excellent result. Many thanks for the quick response to this issue.
Rockin’ chief…
Job’s a goodun. 8)
HI Guys,
I am a user of AVAST for about 1.5 years now ;D
I have te samen problem with the bootscan. A very good module!
I read that the AVAST team wil fix this with the next program update.
I wil gave you a big compliment for the software and for the resolving of this problem.
marcthin
Thanks VLK!! ;D
It’s great to hear that you guys can re-create this problem in the labs and it’s not just us.
I don’t mind waiting at all for a fix.
Thank you very much for the acknowledgement.
~Steele Wolf~
Ok, I’ve updated the program and the VPS files just today and the preboot scan still throws the same error.
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
InitKeyboard
s_dwKbdClassCnt: 2
InitKeyboard end
GetKey
SetFolders end
aswEnginDllMain(DLL_PROCESS_ATTACH)
InitLog
InitLog end
InitReport
InitReport end
CmdLine
C:\PROGRA~1\ALWILS~1\Avast4\aswBoot.exe /A:"C:" /L:“English”
CmdLine end
ZwCreateDirectoryObject - ASWObjects
LoadResources
LoadFile
LoadFile end
LoadResources end
CKbBuffer::Wait
CKbBuffer::Get
CKbBuffer::Get end
CKbBuffer::Wait end
FreeMemory: 317075456
aswintegInitialize
avworkInitialize
avworkInitialize Error:42003
aswintegClose
TerminateKbThread
GetKey end
CloseKeyboard
CloseKeyboard end
KbThread stop
CKbBuffer::~CKbBuffer
CKbBuffer::~CKbBuffer end
aswEnginDllMain(DLL_PROCESS_DETACH)
FreeResources
CloseReport
CloseLog
Build: Mar2004 (4.1.357)
VPS file version: 0404-4
There was no program update yet (you have still build 357).
This error should be fixed in the next “PROGRAM” release.
I thought I would bump this up for others as I am seeing double posts of the issue.
Take care!
~Steele~
Hey, i’m with the same problem as everyone else who replied, just one question, is my pc still safe without the boot time scan? i’m using xp, and the same error 42003 occurs, tried uninstall, reinstall…deleted the setup, downloaded the new setup…for the 2nd time and i still have this prob… :-[…
Hello BuBbly01:
Yes… your computer is just fine. I thought somehow I messed up my XP Pro machine or some of my Avast4Home files were corrupted.
But that is not the case.
There is an issue with the initialization of the scanning engine when you try to run a Boot Time Scan. :-\
When the boot time scan fails… all that will happen is it will bypass the boot time scan screen and leave you at the login prompt for NT/2000/XP.
There is supposed to be a new PROGRAM release this week to address the issue. So all that you will have to do is download the entire program file through “auto-update” and then restart the PC.
The boot time scan should THEN work.
Were all waiting patiently for a fix. There has been no new program update yet for avast. The only updates there have been are the VPS updates that include newly discovered viruses.
We’re not waiting for a VPS fix…but a PROGRAM fix.
There is nothing wrong with your PC… it’s just a bug in the scanning engine.
Keep checking this thread for updates on the issue!
And welcome to the forums BuBbly01! ;D