Hi All,
I just installed Avast build 4.1.501 VPS 445-1, this is the second machine I am installing this home edition, on this particular machine the boot time scan doesn’t function at all, I have tried setting it repeatedly but to no avail, I have tried uninstalling Zone Alarm Pro and tried scanning but no go. The PC has software RAID STRIPED configuration with two drives, it is a dual Athlon MP 2800.
Boot time scan only works on NT based systems.
Well, I would sort of expect that a dual Athlon machine is running on NT-based system ;D
What exactly does it mean that “it doesn’t function at all”?
Is there a file called aswBoot.log in \Data\Log folder?
Hi Igor,
Good guess, was my oversight, should have mentioned the OS, it is Win2K SP4, and yes there is a \data\log folder in my Alwill Software folder.
By doesnt scan I mean exactly that, if I set the machine for boot time scan, it restarts the PC, but doesnt scan during boot time, it however scans nicely under Windows if it tell it to.
The PC has software RAID STRIPEDCould this be the clue for solving this problem? Raid drivers are not loaded (yet?) when Avast starts the boot scan.
I know there is a \data\log folder there - the question is if there’s a file called aswBoot.log inside (and if yes, what is its content).
Nope, no aswBoot.log in the folder, all I see is aswMaiSv and Setup.
OK. When you schedule the boot-time scan (and before you restart the computer), please open regedit (or maybe rather regedt32) and navigate to the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
What is the content of the BootExecute value?
Hi Igor,
The BootExecute value is PDBoot.exe autocheck autochksmrgdf F:\Program Files\iolo\System Mehchanic5\C:\Program Files\Alwil Software\Avast4\aswboot.exe/A""/L:“English”/RA:delete /archives
Looks like this key needs to be deleted.
The RAID configuration works fine with my other system so I guess this key is the problem.
Well, the main problem are the long file names (even though I must say the key does look strange… can you export the BootExecute key to a file and send it to me?)
It seems that you have the generation of short filenames turned off for the system. Unfortunatelly, avast! 4.1 cannot work with this option.
avast! 4.5 boot-scan executable will be installed into windows directory (instead of avast! program folder), so it should work correctly.
Igor,
I deleted the reg key and restrated the system but the scan still doesnt work, I do have short filenames turned on. I truly appreciate your help and input.
Arup, I suppose you return to your first BootExecute value… The other entries are valid for your system… Arup, did you do a copy and paste of the information or retyped it?
Igor:
Technical,
PD Boot is probably from my Perfect Disk boot time defrag routine, ther is no space after the entries and smrgdf most likely belongs to autocheck. Stragely even after deleting the key and starting all over, the boot time scan refuses to work.
When you clean the key completely and then schedule a boot-time scan - what will be the new content of the key?
Hi Igor,
Seems like I have a serious problem with system, none of the boot time programs are working anymore, Perfect Disk as well as System Mechanic have all stopped working so I dont think the problem is with Avast, now I have to format and start it all over again, it is a real bummer.
It seems like a drastic solution… couldn’t the problem be only the corrupted BootExecute key? What if you delete the whole BootExecute value, then create it again (REG_SZ_MULTI) an fill in “reasonable values” there?
Arup, did you try what Igor said?
Did you backup your original BootExecute value?
Hi Igor/Technical,
First of all Avast rules and you guys are the reason why, your commitment in solving the problem makes this product really worth it. I have tried deleteing the original value and starting with a fresh reg key, my only other option would be to check the autoexec.nt to see some rogue entries which may be behind all these hoopla. Will keep you guys updated.