Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Wildchild- on September 26, 2009, 01:16:18 AM
-
Well the topic says the problem. I just recently reinstalled my XP (32-bit) and now my boot time scan does not work. Just gray screen and then i must restart my computer. Also, after i had to force restart this came along:
I try start avast:
(http://img23.imageshack.us/img23/8302/nimetnc.jpg)
then..
This screen only disappears via pressing esc and the help file does not open with the program, just white page.
(http://img62.imageshack.us/img62/8199/nextn.jpg)
(i have registered avast, that says i dont)
This problem countinues, until i reinstall avast.
The os is Windows Xp Pro (sp3) and Avast 4.8 Home edition.. Nothing in my hardware / software has not changed, eventhought i reinstalled Windows..
-
What you are showing isn't the boot-time scan but the initiation of the Simple User Interface by using the ashAvast.exe icon on the desktop, is that what you are doing ?
If the first bit fails then I wouldn't expect the second part to work either.
Try a repair of avast. Add Remove programs, select 'avast! Anti-Virus,' click the Change/Remove button and scroll down to Repair, click next and follow.
First you shouldn't have to use that ashAvast.exe shortcut, but right click the avast 'a' icon, select Start avast! Antivirus. Try that, does it work ?
If not try launching the C:\Program Files\Alwil Software\Avast4\ashSimpl.exe file directly, does that work ?
Have (or did) you another AV installed in this system, if so what was it and how did you get rid of it ?
-
This is the cause of boot time scan not working.
Okay, lets start over.
1. I schedule a boot time scan.
2. Restart the computer
3. When the boot time scan supposed to run, screen is just gray and i have to reboot the computer... (waited an hour and nothing happens)
4. Now, when i try to start ashSimpl.exe, those problems comes, what are in the first post.
ashSimpl.exe works perfectly when just istalled avast.. When i make the boot time scan and it fails, this starts... The not working scan makes all the problems to ashSimpl.exe too.
And yes, ashSimpl.exe works, but the memory test and splash creen dont..
-
You didn't mention about other/previous AVs as this can have an impact.
You also didn't say if you tried the avast repair.
In the meantime, try this (as strange as it may seem) it could be another shell extension clashing with avast.
- Menu, Display Remnants, Log Viewer Remnants, Graphics glitches, etc.
- Edit the C:\Program Files\Alwil Software\Avast4\DATA\avast4.ini using Notepad [Common] section, add the following line to the section SunbeltKPFHack=2, save the file, you will be prompted by the avast! Self-defence module if this is OK answer Yes. Whilst this is primarily for Sunbelt or Kerio Personal Firewalls it may well work even if you don't use either of these firewalls.
Also see http://forum.avast.com/index.php?topic=37609.msg315764#msg315764 (http://forum.avast.com/index.php?topic=37609.msg315764#msg315764) - Also see, http://forum.avast.com/index.php?topic=40840.msg342656#msg342656 (http://forum.avast.com/index.php?topic=40840.msg342656#msg342656) which mentions a similar issue relating to McAfee Site Advisor and remnants of menus, etc.
Now why you have a grey screen on the boot-time scan I don't know it should be a basic blue showing the avast.
-
Oh sry, i dont have another antivirus programs and i tried to repair avast. It didnt work.
Yes, i have kerio, i put that extra line into ini file, nothing. Problem fixes only if i reinstall avast.
The problem occures when i rightclick the avast balloon in taskbar witch open the ashAvast.exe. The ashSimpl.exe works if i go from C:\Program Files\Alwil Software\Avast4\ashSimpl.exe.
The scanner works, but somehow the failed boot scan srews up the ashAvast.exe.
Main problem still is the boot scan. :-[ Is there a windows option/setting witch would block the boot scan? And its bit mystery why program starts to function this way after i force boot from failed scan.
(I must apoligise my english, aint perfect) ;)
-
Oh sry, i dont have another antivirus programs
Did you have in the past?
I suggest an installation from the scratch:
1. Download the latest version of avast! Uninstall Utility (http://www.avast.com/eng/avast-uninstall-utility.html) and save it.
2. Download the latest avast! (http://www.avast.com/eng/programs.html) version and save it.
3. Uninstall avast from Control Panel (if possible). If, for any reason, you can't run it, try booting in Safe Mode (http://www.pchell.com/support/safemode.shtml) and doing it from there. Anyway, boot after that.
4. Run the avast! Uninstall Utility saved on 1. If, for any reason, you can't run it, try booting in Safe Mode (http://www.pchell.com/support/safemode.shtml) and doing it from there. Anyway, boot after you've run it.
5. Install avast! using the setup saved on 2. It will be good to accept the boot time scanning. Boot.
6. Check and post the results.
-
Oh sry, i dont have another antivirus programs and i tried to repair avast. It didnt work.
Yes, i have kerio, i put that extra line into ini file, nothing. Problem fixes only if i reinstall avast.
The problem occures when i rightclick the avast balloon in taskbar witch open the ashAvast.exe. The ashSimpl.exe works if i go from C:\Program Files\Alwil Software\Avast4\ashSimpl.exe.
<snip>
Having made the changes, you would probably have to reboot for avast to use the new avast4.ini settings, so it may work. Reinstalling avast would effectively undo the changes you made to the avast4.ini, so the hooking/shell extension problem is highly likely to return.
Even a clean reinstall as suggested is unlikely to get round this conflict with shell extensions. The problem with conflicts, they may not happen for some time or right away, hense the period previously where it worked for a while.
So I suggest that you make the changes to the avast4.ini again and reboot and see how that goes.
-
Did you have in the past?
No.
I suggest an installation from the scratch:
1. Download the latest version of avast! Uninstall Utility (http://www.avast.com/eng/avast-uninstall-utility.html) and save it.
2. Download the latest avast! (http://www.avast.com/eng/programs.html) version and save it.
3. Uninstall avast from Control Panel (if possible). If, for any reason, you can't run it, try booting in Safe Mode (http://www.pchell.com/support/safemode.shtml) and doing it from there. Anyway, boot after that.
4. Run the avast! Uninstall Utility saved on 1. If, for any reason, you can't run it, try booting in Safe Mode (http://www.pchell.com/support/safemode.shtml) and doing it from there. Anyway, boot after you've run it.
5. Install avast! using the setup saved on 2. It will be good to accept the boot time scanning. Boot.
6. Check and post the results.
When i unstalled avast, i cleaned up registy keys ect, anything that releated to avast. Do the uninstall utility make same thing? Ill try this anyway.
Having made the changes, you would probably have to reboot for avast to use the new avast4.ini settings, so it may work. Reinstalling avast would effectively undo the changes you made to the avast4.ini, so the hooking/shell extension problem is highly likely to return.
Even a clean reinstall as suggested is unlikely to get round this conflict with shell extensions. The problem with conflicts, they may not happen for some time or right away, hense the period previously where it worked for a while.
So I suggest that you make the changes to the avast4.ini again and reboot and see how that goes.
I rebooted after making that change into inifile. Nothing..
-
That's weird as at the very least you should get the blue avast boot-time scan screen, on occasion some can't use their USB keyboard (not an avast but BIOS issue), but they at least get the scan screen.
So I'm at a loss as to what else to suggest, I would have what firewall as Online Armor can get in the way on occasion, but you said you are using Kerio and I haven't heard of that occurrence.
I would also have asked if you had a registry protection application, etc. which would block the creation of the registry key which is needed for the scan. But then again if that was the case then it wouldn't have even attempted to run, so on reboot it would have gone into windows directly, as I said weird.
-
I suggest an installation from the scratch:
1. Download the latest version of avast! Uninstall Utility (http://www.avast.com/eng/avast-uninstall-utility.html) and save it.
2. Download the latest avast! (http://www.avast.com/eng/programs.html) version and save it.
3. Uninstall avast from Control Panel (if possible). If, for any reason, you can't run it, try booting in Safe Mode (http://www.pchell.com/support/safemode.shtml) and doing it from there. Anyway, boot after that.
4. Run the avast! Uninstall Utility saved on 1. If, for any reason, you can't run it, try booting in Safe Mode (http://www.pchell.com/support/safemode.shtml) and doing it from there. Anyway, boot after you've run it.
5. Install avast! using the setup saved on 2. It will be good to accept the boot time scanning. Boot.
6. Check and post the results.
Now tried this couple of times, still nothing. I tried newest english version, older english version (4.8.1229 what i found from computer) and newest finnish version.
And the errors what are in first post now comes right after i put the registation code to avast, or if i skip registration code and try start program again. :(
That's weird as at the very least you should get the blue avast boot-time scan screen, on occasion some can't use their USB keyboard (not an avast but BIOS issue), but they at least get the scan screen.
So I'm at a loss as to what else to suggest, I would have what firewall as Online Armor can get in the way on occasion, but you said you are using Kerio and I haven't heard of that occurrence.
I would also have asked if you had a registry protection application, etc. which would block the creation of the registry key which is needed for the scan. But then again if that was the case then it wouldn't have even attempted to run, so on reboot it would have gone into windows directly, as I said weird.
Yeah, im starting to wonder if theres something wrong with hardware or with kerios programcontrol. Cause i noticed that Mozilla Thunderbird cant open links anymore to Firefox. Well, i must reistall kerio too, lets see what happens.
-
OK, good lock.
-
Reinstalling kerio did not work. The program control asked everything it supposed to and i gave access. :-\ Im out of ideas..
-
Did you follow steps 1 and 4?
-
Did you follow steps 1 and 4?
Yes i did.
-
Strange... what is happening in your computer???
How many admin accounts do you have in this computer?
-
If you have Windoes installation disk or can run Recovery Console you could try Fixboot (and posibly Fixmbr if still no luck).
But very much doubt if this is your problem.
Tech mentioned you're admin accounts. Good idea to have a good look through User Accounts to see the rulings and policies that are active on your computer and what is permitted to you and what is not.
-
Strange... what is happening in your computer???
How many admin accounts do you have in this computer?
Just my own account and the Admistator account (witch is hidden)
If you have Windoes installation disk or can run Recovery Console you could try Fixboot (and posibly Fixmbr if still no luck).
But very much doubt if this is your problem.
Okay, ill try this..
-
Fixboot amd Fixmbr :o :o
For what? Does not seem to be the problem...
-
I thought perhaps boot problem. But as I said very much doubt standard boot error.
Perhaps virus in mbr? I dont know what could be causing his problem.
If he has Admin hidden and one active user account, then that user account must have full admin privileges. Perhaps boot into Safe Mode, into Admin account, and then schedule boot-time scan there, Restart and see what happens.
-
I thought perhaps boot problem. But as I said very much doubt standard boot error.
Perhaps virus in mbr? I dont know what could be causing his problem.
If he has Admin hidden and one active user account, then that user account must have full admin privileges. Perhaps boot into Safe Mode, into Admin account, and then schedule boot-time scan there, Restart and see what happens.
fixboot didnot work and repair mode could not allow to do fixmbr cause is wrong ect ( cant remember/ cant translate that all ;) ). Also i scheduled boot scan via safemode and Admin account, still nothing. Well the last try would be reinstall windows again, but ill try to fix this..
-
Overinstallation can solve the problem and you won't lose your programs, settings, data, files, etc.
Just choose 'Repair' installation of Windows and install 'over' the old installation.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;315341
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314058
http://support.microsoft.com/?scid=kb%3Ben-us%3B315341&x=15&y=0
http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx
-
I heading out for brk / lunch but Tech if I he cannot write new boot sector (mbr) perhaps something going on with admin rights / rulings / policies (I cant guess at all what) even tho he can get into Administrator. Seems he being held up somewhere like block yet no hard message to screen any time to say this happen.
WildChild what are yr screen messages at any time if they come up.
Also, yeah probably shouldn't advise write new boot record (fixmbr). I often do fixboot and fixmbr as part of standard optimise when repair of Windows or where specific boot problems apparent. I've never had any problems in the least when have run fixmbr as part of general optimise but still the action does not come without warnings.
-
Also, yeah probably shouldn't advise write new boot record (fixmbr). I often do fixboot and fixmbr as part of standard optimise when repair of Windows or where specific boot problems apparent. I've never had any problems in the least when have run fixmbr as part of general optimise but still the action does not come without warnings.
Mkis, the problem is when you have a problem while booting... then trying to repair could be disastrous.
But, what makes me think is that Wildchild- does not have booting problems.
Right now, I won't suggest anything else before Wildchild- say precisely what is happening.
I don't want to suggest "can't undo" solutions...
-
Overinstallation can solve the problem and you won't lose your programs, settings, data, files, etc.
Just choose 'Repair' installation of Windows and install 'over' the old installation.
Well i have done it so manytimes that i know what will i loose ect ;) I allways backup needed data to other harddisk. Its just on hour job to reinstall / istall all the programs and put settings back in..
WildChild what are yr screen messages at any time if they come up.
Hmm, it said that its not possible to write new or there is no sector. But if u shoose to do this, it maight do damage to ... something... roughly translated and memorised ;D
Also i checked all the registry keys and start programs that i have deleted, and there was no nessacery windows files / avast files, or anything that could do this..
And sorry, i misspelled the fixboot didnot work and. Fixboot did work, fixmbr did not.. :-[
-
Problem solved! One of my HDD was busted. Thats why it didnt start boot time scan. I noticed this cause it did not even start Perfect Disk degrafment.. Eventhought drives S.M.A.R.T status was ok, it was broken. ( Im glad that the drive was allmost empty and it had warranty left)
Thank you all anyway trying solve the problem 8)
-
Hi Wildchild. sorry I've been out to lunch or would have responded earlier. Yr post came in as I was bout to post, but I have sent this off anyway.
What tech says is correct, if repair is not go well this time then outcome can be disaster for you. That is why the action to fix will come with warnings. Personally, I will say now that it is not worth to run fixmbr. To have run fixmbr with fixboot as I said as a general optimise would have been to instate your default Windows boot functions as clean running (as day they were born). This is why I do it as general optimise.
I thought - perhaps with boot all back to default, and clean, maybe boot-time scan would run ok or maybe action would prompt message to screen when runs first time through new boot. Even though unlikely that you have boot problem - you are booting through okay to Windows environment both with user account and Administrator, which pretty much says all. And like Tech says there is definite element of danger when repairing where boot problems. More than that, Tech is very experienced with avast program and is familiar with the many particulars (or peculiarities for avast unique type functions) that come with the running of the program. His advice is good.
-
Problem solved! One of my HDD was busted. Thats why it didnt start boot time scan. I noticed this cause it did not even start Perfect Disk degrafment.. Eventhought drives S.M.A.R.T status was ok, it was broken. ( Im glad that the drive was allmost empty and it had warranty left)
Thank you all anyway trying solve the problem 8)
Thanks for the update, good news that you have found the problem, bad news about the HDD though.