Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Steele on April 03, 2004, 11:17:03 AM
-
Hello:
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. :-\
Kindest regards,
~Steele Wolf~
-
08/03/2004 21:49
Scan of all local drives
Number of searched folders: 3038
Number of tested files: 100939
Number of infected files: 0
----------------------------------------
11/03/2004 15:06
Scan of all local drives
Number of searched folders: 3044
Number of tested files: 102027
Number of infected files: 0
----------------------------------------
03/04/2004 01:25
----------------------------------------
03/04/2004 02:01
----------------------------------------
03/04/2004 03:18
----------------------------------------
03/04/2004 04:03
-THESE ARE THE SCANS I TRIED TODAY-> Nothing does get scanned.
-
There is some error during the initialization....I can't catch it. :-\
-
There is some error during the initialization....I can't catch it. :-\
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?
-
Hi Technical ;D
No.... I have never installed any Norton or McAfee product. I always use Avast4Home.
Where would I find a report or log of the boot time scanning operation? What's the file called?
You mean the log-viewer?
I have not tried repairing the installation.
You do this through Add/Remove Programs in XP Pro right?
~Steele Wolf~
-
Where would I find a report or log of the boot time scanning operation? What's the file called?
Maybe at the 'report' folder of avast installation. I do not know the name of the file, if any, but will be an *.txt file I suppose.
You mean the log-viewer?
No. Report files are different from log. Logs are for errors and Report about activities of the antivirus.
I have not tried repairing the installation.
You do this through Add/Remove Programs in XP Pro right?
Yeah...
-
Technical:
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 :(
-
Okay... thanks anyways. :)
I don't get this code when performing a FULL+ARCHIVE scan from within XP Pro.... only at boot time.
~Steele Wolf~
-
Hi peeps...
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....
Ideas anyone?
-
Hmm,
....
....
[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... :-\
Anyway thanks a lot for your report!
Vlk
-
Hi VLK... thank you so much for appearing on a Saturday! ;D
I can't send you any file because...the error does not appear to be generated by a bad file....rather the engine.
It still happens if I un-check archives.
Oh well... everything still works.
I'm going to CHKDSK /F /V then defrag using Diskeeper 8 Pro.
-
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?
-
Exactly same issues here as reported by 'Steele'.
First noticed since my PC was freshly re-formatted yesterday afternoon. Installed software includes Ad-aware, Spybot and SpywareBlaster.
-
EXACT error that Bagmaster50 is reporting.
Installed Avast! Home fresh on a new PC yesterday.
Scheduled first boot time scan which ran fine.
Secheduled a second boot time scan and it bypassed the scan just as described by others above with the error.
UNinstalled Avast! and REinstalled
First boot-time scan worked again.
Next one failed in the same way.
-
ouch! I'm sure someone will come to our rescue soon.. :'(
-
Hi again...
I've had another bash at the problem
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?
-
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. :P
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
-
But I do try to fix a problem if I find it so there ya go. :P
Let's see if the Avast guys find a fix.
Vin - nethomehelp.co.uk ;)
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
-
Where would I find a report or log of the boot time scanning operation? What's the file called?
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 :(
-
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!* :P
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. :P
Keep checking this thread for updates on the issue!
And welcome to the forums BuBbly01! ;D
-
Technical!!! :o
I'm so sorry, I forgot about that IM you sent... :-\
I'm hoping this is what you were wanting? ???
-
Technical!!! :o
I'm so sorry, I forgot about that IM you sent... :-\
I'm hoping this is what you were wanting? ???
I forgot what and why I asked for... ::)
My registry key is the same of yours: autocheck autochk *
-
Uninstall, reinstall, same issue...no new software...yada, yada, yada...then I finally wake up and decide to check the BB re the insidious bootscan 42003 error. I think it's the first time I've actually (1) seen intelligent posts on a BB, and (2) got a clear and acceptable answer to a problem. Hoo-yah!
-
I too have exactly the same problem with a 42003 error.
Have removed and re-installed (incl. checking registry for anything left behind beforehand) and have used their removal tool too.
I like to run a full scan before windows loads every once in a while and this kind of fault dis-illusions ones faith in the product. I cannot continue to use/recommend it until resolved.
Any fix for this?
-
People PLEASE can you read?
Everyone has the problem -- it's a bug that will be fixed in the next program update.
Thanks
Vlk
-
Well, here it is Sunday, April 18th. Where's the program update we've been promised to fix this preboot scan error?
Bump.
-
I guess the fix is taking a while because...well.... it just HAS to... and delays should be "expected". ::)
It's a SERIOUS bug that needs to fixed PROPERLY.
I was hoping for the release this weekend myself, but since it is not ready to be released, I am more then willing to wait.
Un-installing and re-installing does not work no matter how many times you try. There is no fix yet.
I think we can live without the boot-time scan for a little while longer? The most important thing is that the MAIN parts of the program, the resident shield, and system scans...work. :)
~Steele~
-
This specific bug has been solved the same date it was reported. But the update is taking a bit longer because of a few other issues... Sorry for that.
Well, here it is Sunday, April 18th. Where's the program update we've been promised
Hmm, I'm not totally sure I like this tone... :-X
Vlk
-
This specific bug has been solved the same date it was reported. But the update is taking a bit longer because of a few other issues... Sorry for that.
Vlk...no apology necessary...accept my thanks for all the hard work and keeping on top of so much--especially the things we don't know about ;)
Well, here it is Sunday, April 18th. Where's the program update we've been promised
Hmm, I'm not totally sure I like this tone... :-X
I shall attempt to sing a soft and peaceful tune to drown out any other tones--and, yes, I can sing ;D
cojo
Vlk
-
This specific bug has been solved the same date it was reported. But the update is taking a bit longer because of a few other issues... Sorry for that.
Well, here it is Sunday, April 18th. Where's the program update we've been promised
Hmm, I'm not totally sure I like this tone... :-X
Vlk
:D
Yet another newbie to avast with the same problem, but like someone else in this forum I am quite happy knowing that a fix is on the way. After 20 years in IT the whole un-install/re-install game is such a joke, having said that I do have a warped/skewed/sick/perverted/unbalanced sense of humour.
I ditched Nortons, then BitDefender, in favour of Avast! mainly cause of the headaches I've received from both companies Tech support which in turned had me do the remove-install limbo game with no change in outcome.
So how relieved do you think this little bear was when Avast found several viruses that they both neglected! My stress ball is on holidays...
Anyways... enough of this chit chat...
I happily look forward to the update and the return of my monthly preboot scan...
HUGS and Thanks to all involved...
GrizzBearCub
-
Sorry about that VLK. I can wait for the update however long it takes. I just don't want to have customers come back on me when this problem happens to them after I've recommended Avast to them. I've contacted all my customers that've downloaded it so far and informed them not to worry about it, that the update to the program will be out soon. Keep up the good work.
-
I have exactly the same problem. I hope that avast! people will solve this problem. I heard that this update that we all are waiting for , should be yesterday, but my problem still remains.
It would be very nice if someone let us now when will, or was this update released. :) :)
Thanks
Avast! is the best!
-
To be honest, I really don't understand what all this fuss is "aboot". ;D
I've scheduled it three or four times just to test it, and it's worked fine....Everything is up to date too BTW- (XP Pro).
Not to mention, how often do you really need to perform a boot scan? Answer??? Not to often! ;)
Just kidding around, and I'm fairly new to this program (a refugee from AVG!)
I really love the Program. (Although it is a bit more of a resource hog than AVG was).
The many more features, really cool interface and Skins make it well worth it though........And speaking of "well worth it"- after reading through this thread, it's amazing to me people can be complaining so much about a FREE program.
I mean, be patient....Give these guys a break!
AVG couldn't care less if you have a problem with their free addition!
My hat's off to Avast! Great work!
(Well I don't wear a hat, but thanks just the same for some really cool Software!)
-
I have run program update, and now everything works!!!!!!
Thanks ALWIL!!!!!! :) :) :) :)
:) :) :) :) :) :)You're the best!!!!!!! :) :) :) :) :)
-
I am pleased to report that this bug has been fixed for me ;D
Many thanks to the Alwil team for taking the time and effort needed to fix this specific bug.
I am now one big happy doggie!! ;D
Patience really does pay off. ;)
Sincerely,
~Steele~