avast update with Windows 2000

Avast Free Antivirus / Premium Security
1

Hi
I just newly installed the current version of Avast on a computer running Windows 2000. I connect to the internet on this computer with a dial up and AOL. If I set Avast for automatic update, or if I put it on manual update, in either case, when Avast either updates or just checks for an update, it always says I need to restart the computer. Is this normal for Avast and Windows 2000 or is it a glitch?

thanks,

Tom

2

Hi and welcome to the forums.

I’m also runninq Win 2k: it is not normal, never had this problem. I’m sure somebody else knows how to solve it.

3

Now that i read this thread i remembered the last time i installed avast!( 2 or 3 weeks ago) it told me it had to restart for i think 3 or 4 times before the message disappeared i found that a little strange.

4

Well, I do know that in Win2k it may take several bootups before a new piece of hardware has got all its proper registry keys. For instance, the special function keys of a new keyboard may initially not work.

It’s a very old problem that goes back to the days of Win95. It was then called the “mouse problem” and concerned dragging and dropping. Often you had to insert the registry key manually. But in Win2k this bug has disappeared.

5

Hi
maybe this will help to get my question/problem answered. I copied this from the “setup” log in the DATA\log folder of the main program folder taken from the time I did an update. You can see there is a line that says “reboot.” If anyone knows what this means and if it is the cause of the problem, I’d appreciate your input.

thanks,
Tom

13.09.2005 09:50:00.000 1126623000 general Entering:UpdateInstallPackages
13.09.2005 09:50:00.000 1126623000 package Load C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
13.09.2005 09:50:00.000 1126623000 package LatestPartInfo: news = news-42
13.09.2005 09:50:00.000 1126623000 package LatestPartInfo: program = prg_av_pro-2b3
13.09.2005 09:50:00.000 1126623000 package LatestPartInfo: setup = setup_av_pro-2b3
13.09.2005 09:50:00.000 1126623000 package LatestPartInfo: vps = vps-53700
13.09.2005 09:50:00.000 1126623000 package FilterOutExistingFiles: 136 & 135 = 1
13.09.2005 09:50:00.000 1126623000 package FilterOutExistingFiles: 136 & 135 = 1
13.09.2005 09:50:00.000 1126623000 package FilterOutExistingFiles: 136 & 135 = 1
13.09.2005 09:50:00.000 1126623000 package ArePartsInstallable: 1
13.09.2005 09:50:00.000 1126623000 file SetExistingFilesBitmap: 699->136->135
13.09.2005 09:50:00.000 1126623000 package FilterOutExistingFiles: 136 & 135 = 1
13.09.2005 09:50:00.000 1126623000 package Extracting from av_pro_core-278.vpu (1)
13.09.2005 09:50:00.000 1126623000 file Direct delete of file: C:\WINNT\system32\psa1.tmp
13.09.2005 09:50:00.000 1126623000 system Reboot set by filRenameOnReboot(C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp_av_proI.tm~a01668\onefile,C:\WINNT\system32\psapi.dll)
13.09.2005 09:50:00.000 1126623000 file Installed file:C:\WINNT\system32\psapi.dll
13.09.2005 09:50:00.000 1126623000 package program: installed 1 files (28944 bytes), removed 0 files

6

If you search the board for psapi.dll, won’t you find your answer…
There are some threads about shuting down while updating.
Seems to be an old problem of Windows 2k (http://forum.avast.com/index.php?topic=9241.msg77255#msg77255) :cry:

Do you have a file into avast folder called:
\setup\reboot.txt

If so, delete it and see what you get.

7

There is not a reboot.txt file anywhere in the avast program folder. Should there be one and if so, what does in need in it?

I don’t necessarily have a problem with the “avast needs to restart your computer” message and clicking “no” after each update, I just want to make sure that in doing so, there is no compromise to my computer’s protection because of some need to reboot. Just want to know that Avast will work as needed despite this message.

thanks,
Tom

8

If the antivirus requires a boot then the update will be available only after boot.
Until there, the antivirus will work like the ‘old’ version you have in the computer few moments before.

9

Thanks, Tech
since the reboot message isn’t causing a safety problem, as I mentioned previously I don’t mind just clicking “no” to the reboot message. So I suppose we can close this thread unless someone comes up with a fix, or maybe it will be fixed in the next version.

thank you,
Tom