reboot after reboot after reboot...

Avast Free Antivirus / Premium Security
1

Hi,

I upgraded to version 4.1.280, both on a desktop and laptop, running Win XP Pro.
Every time I start one of these computers, an Avast message box pops up, saying I should reboot my system ( yes - no ). And again… and again… and again… Fairly annoying this is…

This is completely new, never seen this before. No other programs installed recently, besides latest Microsoft IExplorer patches (Win is fully up-to-date).

Does anyone know what the heck is going on? Avast needs a new build?

Thanks alot,
Nex.

2

Is there a file called reboot.txt somewhere in the avast installation folder? (setup subdirectory, maybe)
If yes, does it help when you delete it?

3

Nexus, this is strange. Are your XPs sometimes hanging on the shutdown?

I would like to get your logs.
Can you, please, run from the command-line program ashbug.exe /setuplog

That will send us the logs.

thanks,

4

Hi,

Just sent the setup logs to you.

Furthermore, I tried to solve the problem by deleting the reboot.txt from the \SETUP folder (I first checked to see what was inside: empty .TXT file).

Then something funny happens: after deletion, I manually reboot. First, Avast shows the blue info box to the right: info about the new 4.1.278 version! Either clicking or ignoring, the “reboot Y/N” box appears again! So, deleting reboot.txt does not do the trick. On the contrary, a new (blank) REBOOT.TXT file has been created into the \SETUP folder!?

Maybe this has something to do with it all?
Thanks for all the co-thinking work you people are doing! :slight_smile:

Nex

5

PS: my XPs are functioning really nice (how about that for a change :wink: )
they freeze, very very rarely, it turns out to be some ADSL problem with routers etc…

6

nexus,

You have me a little confused. You started the thread saying you had problems with Avast 280 and XP.

but then your last post said they were working nicely.

What did you do to fix the reboot problem?
I have also had rebooting troubles which have not been resolved as yet…even with build 280.

Thanks :smiley:

7

Hi,
My last reply was only a reaction to the previous question: is WinXP giving you problems during shutdown? Well, it is not. In my first posting I only mentioned XP Pro since that might ring a bell to others, should version 280 have known problems with XP. And frankly, I don’t believe this to be a WinXP problem, since they arose after an Avast update.

Regards & hope your problems will be solved too :-
nex

8

From the logs it seems that avast tries to update three files in windows\system32 directory:

MSVCI70.dll
MSVCP70.dll
MSVCR70.dll

All three files should be dated 5.1.2002, their fileversion 7.0.9466.0

From the report it seems you’re using files version 7.0.9447.0 - older.

Avast tries to overwrite them, it fails (because other programs use them), so it sets them ‘after the reboot’.

So, let avast do that again, reboot and check fileversion of the three dlls, please.

9

I confirm what kubecj said… Everything is ok ;D

10

Hi,
I let Avast (try to) update them again. I then checked the versions of these files. They remain old / not updated. No version 7.0.9466.0 but 7.0.9447.0 instead.

Ewwwwmmmm…maybe a stupid question, but how can I manually upgrade those DLLs ?

Tanks,
nex

11

Really? did you reboot and they stayed there? No messages about windows returning old files back? Can you check EventLog for suspicious messages?

Manually putting them there is hard - you have to turn off all the programs which may be using there.

Or overwrite before windows boot, but since you’re on XP’s…

12

Vlk, if he does not succeed, I suggest you let him download these files from the Alwil webpage. He must boot with the Windows Console on XP to change the dll (if closing/killing all applications does not allow the access to these files)

Luck… :wink:

13

The files are already on his computer…

Quoting from the log:
22:29:56 vrb/fil MoveFileEx(C:\WINDOWS\System32\MSV24.tmp, C:\WINDOWS\System32\MSVCI70.dll)
22:29:56 vrb/fil MoveFileEx(C:\WINDOWS\System32\MSV25.tmp, C:\WINDOWS\System32\MSVCP70.dll)
22:29:56 vrb/fil MoveFileEx(C:\WINDOWS\System32\MSV26.tmp, C:\WINDOWS\System32\MSVCR70.dll)

These records tell windows to rename files *.tmp to their *.dll counterparts. This fails for an unknown reason on that computer. I wonder if the tempfiles stay there?

14

Try to turn off the System Restoration and update avast! Maybe it works… :cry:

15

Hi,
Good morning! (i.e. from The Netherlands :)).
Thanks for your help so far. To get back to your questions:

Really? did you reboot and they stayed there? No messages about windows returning old files back? Can you check EventLog for suspicious messages? Manually putting them there is hard - you have to turn off all the programs which may be using there. Or overwrite before windows boot, but since you're on XP's...

Yes, I did reboot, but Win did not come up with such a message. No messages concerning that whatsoever. The DLLs remain at their old versions.

Quoting from the log: 22:29:56 vrb/fil MoveFileEx(C:\WINDOWS\System32\MSV24.tmp, C:\WINDOWS\System32\MSVCI70.dll) 22:29:56 vrb/fil MoveFileEx(C:\WINDOWS\System32\MSV25.tmp, C:\WINDOWS\System32\MSVCP70.dll) 22:29:56 vrb/fil MoveFileEx(C:\WINDOWS\System32\MSV26.tmp, C:\WINDOWS\System32\MSVCR70.dll) These records tell windows to rename files *.tmp to their *.dll counterparts. This fails for an unknown reason on that computer. I wonder if the tempfiles stay there?

As a matter of fact, in my \SYSTEM32-folder there are alot of MSV??.tmp files. An yes, the above do exist in this folder. Their “date modified” stands at 01/05/2002 (huh?) but the creation dat is 10/08/2003 which should be fine. All of these .tmp files have only the "a"rchive attribute.

I’ll go and try to shutdown system restoration and update again. We’ll see what happens… :cry:

Regards,
nex

16

I suggest a “cleaner” for your system (Empty Temp Folders may work well, see link at http://www.avast.com/forum/index.php?board=1;action=display;threadid=834;start=new

Cheers :wink:

17

I have now the same problem after the update to the last version. After each boot, Avast tells me that a new version has been installed and proposes me to restart the system. I have the old versions of the MSV* files on the System32 folder and do not know how to update them. Doing a system cleanup by hand does not solve the problem.

In my system32 folder, I have found a full bunch of *.tmp files that are in fact clones of three files:

one of 54784 bytes,
one of 344064 bytes
one of 487 424 bytes

All dated 5.12.2002.

I imagine that these are the clones of the original files but I do not which one I must use to replace by hand the old MS files.

This reboot demand is quite harassing and I would be happy to get rid of it quickly…

I use Win XP Home, French version and the system is fully update.

Please a solution for this problem…

Regards,

MY

PS. I have just sent the logs to you.

18

Hi people,

Nex is back,

Here is a quote from my emails with Alwil. The solution presented does not work for me, but maybe it does for someone else, so let’s share this information with you:

Hello, you can try to copy these files (but backup those files in dllcache first): C:\WINDOWS\System32\MSV24.tmp to C:\WINDOWS\System32\dllcache\MSVCI70.dll C:\WINDOWS\System32\MSV25.tmp to C:\WINDOWS\System32\dllcache\MSVCP70.dll C:\WINDOWS\System32\MSV26.tmp to C:\WINDOWS\System32\dllcache\MSVCR70.dll

Then try to restart again.
I think that Windows File Protection is always replacing these files
from dllcache, but avast tries to repair it by copying newer versions,
but Windows again replaces them by older version from dllcache etc.

Please let me know if it helped.

Jiri Forejt
Alwil Software

My reply for those interested:

Hi, Thanks for your help,

I tried to copy the files like you told me to… BTW: there was only a folder called SYSTEMS32\LASTGOOD\DLLCACHE. This folder had NO file calles MSVC…70.dll in it!
I copied MSV24.tmp etc to the folder, renamed them, but Avast keeps on asking for a reboot.

I then got so genuinely fed up with all this, that I completely removed Avast from my computer, rebooted, deleted ALL references in the WinRegister concerning Avast, I deleted \Program Files\Alwil directory, rebooted, downloaded the lastest version, re-installed… And guess what ???

I get a “reboot yes/no” !!!??!! Arrrgghhh! :-/
I really have NO IDEA whatsoever anymore as to what is going on…

Any ideas?? You know, the strange thing is: this is happening on TWO computers at the same time after the latest Avast! update. I’m using Dutch Win XP Pro, by the way. I am really out of ideas…

Best regards and hope you van help me out,

19

Oh Tech,

I forgot to mention: cleaning up the system and deleting the .tmp files (I use jv16Tools for this) did not do the trick either…

Could there be a problem with non-English versions of XP Pro?? (I’m just an idiot guessing… :smiley: )

nex

20

I don´t think it´s a language problem… But you can try install the English version and see what you get!
I just use the old version of jv16 (the Freeware one). It works fine, but I used just for Registry cleaning and not for temporary files. There are lots of better programs to do cleaning of files than jv16, although the jv16 is a powerfull application for Registry (unfortunatelly it becomes Shareware :'().