Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: nexus on October 08, 2003, 10:40:47 PM

Title: reboot after reboot after reboot...
Post by: nexus on October 08, 2003, 10:40:47 PM
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.
Title: Re:reboot after reboot after reboot...
Post by: igor on October 08, 2003, 10:57:10 PM
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?
Title: Re:reboot after reboot after reboot...
Post by: kubecj on October 08, 2003, 11:15:54 PM
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,
Title: Re:reboot after reboot after reboot...
Post by: nexus on October 09, 2003, 12:43:20 AM

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!  :)

Nex
Title: Re:reboot after reboot after reboot...
Post by: nexus on October 09, 2003, 12:45:21 AM

PS: my XPs are functioning really nice (how about that for a change  ;) )
<IF> they freeze, very very rarely, it turns out to be some ADSL problem with routers etc...
Title: Re:reboot after reboot after reboot...
Post by: techie101returns on October 09, 2003, 12:57:05 AM
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 :D

Title: Re:reboot after reboot after reboot...
Post by: nexus on October 09, 2003, 01:05:12 AM

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
Title: Re:reboot after reboot after reboot...
Post by: kubecj on October 09, 2003, 01:11:27 AM
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.
Title: Re:reboot after reboot after reboot...
Post by: Lisandro on October 09, 2003, 01:16:11 AM
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

I confirm what kubecj said... Everything is ok  ;D
Title: Re:reboot after reboot after reboot...
Post by: nexus on October 09, 2003, 01:29:07 AM

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
Title: Re:reboot after reboot after reboot...
Post by: kubecj on October 09, 2003, 01:50:54 AM
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...
Title: Re:reboot after reboot after reboot...
Post by: Lisandro on October 09, 2003, 03:20:14 AM
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...

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...  ;)
Title: Re:reboot after reboot after reboot...
Post by: kubecj on October 09, 2003, 03:32:33 AM
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?

Title: Re:reboot after reboot after reboot...
Post by: Lisandro on October 09, 2003, 03:41:30 AM
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?


Try to turn off the System Restoration and update avast! Maybe it works...  :'(
Title: Re:reboot after reboot after reboot...
Post by: nexus on October 09, 2003, 10:42:07 AM
Hi,
Good morning! (i.e. from The Netherlands  :)).
Thanks for your help so far. To get back to your questions:

Quote
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.


Quote
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...  :'(

Regards,
nex
Title: Re:reboot after reboot after reboot...
Post by: Lisandro on October 09, 2003, 02:01:10 PM
As a matter of fact, in my \SYSTEM32-folder there are alot of MSV??.tmp files.

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  ;)
Title: Re:reboot after reboot after reboot...
Post by: yildi on October 09, 2003, 02:39:49 PM
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.
Title: Re:reboot after reboot after reboot...
Post by: nexus on October 09, 2003, 04:07:37 PM
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:

Quote
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:

Quote
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,



Title: Re:reboot after reboot after reboot...
Post by: nexus on October 09, 2003, 04:17:16 PM
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...  :D )

nex

Title: Re:reboot after reboot after reboot...
Post by: Lisandro on October 09, 2003, 05:42:18 PM
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...  :D )
nex

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  :'().
Title: Reboot problem solved....Hope so!
Post by: yildi on October 10, 2003, 09:39:18 AM
Hi,

It seems (until now ;-)   ) that I have at the end been able to solve the reboot problem.

I have rebooted in the Repair mode (it is called mode sans echec in French) and logged in as the Administrator in my XP Home.

I have changed the read anly attribute of the problematic dll files in c:\windows\system32:

attrib +R MSVCI70.dll
attrib +R MSVCP70.dll
attrib +R MSVCR70.dll

and copied over these files the ones suggested by the previous mail of Nexus. I have also copied these tmp files over the files in the dllcache folder.

Put back the attributes of the dll files in system32:

attrib -R MSVCI70.dll
attrib -R MSVCP70.dll
attrib -R MSVCR70.dll

Then  reboot as normally and I have not received any message from Avast yet for rebooting.... Hope this will continue :-)

MY
Title: Re:Reboot problem solved....Hope so!
Post by: Lisandro on October 10, 2003, 02:59:53 PM
Hi,

It seems (until now ;-)   ) that I have at the end been able to solve the reboot problem.

I have rebooted in the Repair mode (it is called mode sans echec in French) and logged in as the Administrator in my XP Home.

I have changed the read anly attribute of the problematic dll files in c:\windows\system32:

attrib +R MSVCI70.dll
attrib +R MSVCP70.dll
attrib +R MSVCR70.dll

and copied over these files the ones suggested by the previous mail of Nexus. I have also copied these tmp files over the files in the dllcache folder.

Put back the attributes of the dll files in system32:

attrib -R MSVCI70.dll
attrib -R MSVCP70.dll
attrib -R MSVCR70.dll

Then  reboot as normally and I have not received any message from Avast yet for rebooting.... Hope this will continue :-)

MY

Thanks, yildi
You´re very wellcome to foruns  ;)
Title: Re:Reboot problem solved....Hope so!
Post by: nexus on October 11, 2003, 01:19:08 AM

<snip>
I have changed the read anly attribute of the problematic dll files in c:\windows\system32:

attrib +R MSVCI70.dll
attrib +R MSVCP70.dll
attrib +R MSVCR70.dll

and copied over these files the ones suggested by the previous mail of Nexus. I have also copied these tmp files over the files in the dllcache folder.
<snip>

Hi Yildi,

I wish the same would work for me, but unfortunately, whatever Win startup-option I choose...... when I try to copy copy those files onto MSVC?70.DLL I get an error message that I am not allowed to do so   :'(
Tried it in Repair as well as in Protected mode, but nope....  I guess I just got an awful machine (but only in this respect!)...

Any clues left from anyone? Even though it has not yet solved my problems, thanks to all for your time and help! I can only hope someone will get me a golden egg, I guess...

I think to have tried about everything, should I just install NAV?  ;D  
Woehaha, should I?? NO way....

Regards,
nex
Title: Re:reboot after reboot after reboot...
Post by: yildi on October 11, 2003, 01:22:24 AM
Has Xp allowed you to change the attributes of these files in System32 folder? I have only been able to copy the new files on the original ones after that operation (they are read only by default).

MY
Title: Re:Reboot problem solved....Hope so!
Post by: Lisandro on October 11, 2003, 02:59:41 AM
I think to have tried about everything, should I just install NAV?  ;D  
Woehaha, should I?? NO way....
Regards,
nex

Try MoveOnBoot 1.95 to delete files on next boot (http://www.webattack.com/get/moveonboot.html): it´s a freeware of course  ;D
Try to copy the files after the old ones were deleted  ;)
Title: Re:reboot after reboot after reboot...
Post by: techie101returns on October 12, 2003, 09:58:09 PM
Well,  I guess I am joining the problem group!

My Avast has decided, after weeks of running fine, to go nutty.

The blue update box now shows a "new" version 4.278 when I already updated to 280.

My XP wants to reboot and reboot and reboot.

The 3 files in question seem to definetly be the source of the problem:
msvc170     7.0.9447.0 created 12/17/2001   53.5
msvcp70     7.0.9447.0 created 1/21/2002     476kb
msvcr70      7.0.9466.0 created 7/9/2003       336kb

I have attempted using the solutions presented herein with no luck at all.

Any new ideas?

 ??? ???
Title: Re:reboot after reboot after reboot...
Post by: yildi on October 12, 2003, 10:15:39 PM
Techie, you have exactly the same problem as me. I do not understand why my solution is not working for you....

Have you replaced the files in system32 and in system32\dllcache by the good ones dated from january 2002? Has windows accepted the copy operation without complaining :

You should do the copy operations FROM a MS-DOS CONSOLE to see if it works really. I have also logged in as the administrator for doing the copies.

If Windows, refuses, you must first change the attributes to read/write (see above).

Once all the copies are done from the console, check the dates of the files in the explorer. If they are OK, restart and it should work.

I hope this will help. Avast is a magnificient software, it is a pity that this problem spoils our pleasure t use it :-(

MY
Title: Re:Reboot problem solved....Hope so!
Post by: nexus on October 12, 2003, 11:09:36 PM
Try MoveOnBoot 1.95 to delete files on next boot (http://www.pcworld.com/downloads/file_download/0,fid,22942,fileidx,1,00.asp): it´s a freeware of course  ;D
Try to copy the files after the old ones were deleted  ;)

Hi Technival

Could you once more put the link on this forum? The previous link doesn't work - but, moreover, searching for MoveOnBoot doesn't give me results at PcWorld.com..  ???

Thanks!

nex
Title: Re:reboot after reboot after reboot...
Post by: techie101returns on October 13, 2003, 02:42:21 AM
Techie, you have exactly the same problem as me. I do not understand why my solution is not working for you....

Actually it did work.  It was my fault.  I meant to remove the Read Only attribute from the files, but when I checked one of the files, the Read Only was not checked, so I continued trying the other solutions, without checking the remaining files which DID have the Read Only enabled.  I removed the Read Only (through the file properties tab), rebooted and everything is fine.


I hope this will help. Avast is a magnificient software, it is a pity that this problem spoils our pleasure use it :-(

Thank you.  However, I do not mind the little problems that creep up with AVAST.
As Avast grows, "bugs" are part of the natural order of things.
WE learn from them! and it doesn't spoil my pleasure at all.!

Glad you are with us at the Forum.

techie  :D
Title: Re:Reboot problem solved....Hope so!
Post by: Lisandro on October 13, 2003, 04:47:02 AM
Hi Technical
Could you once more put the link on this forum? The previous link doesn't work - but, moreover, searching for MoveOnBoot doesn't give me results at PcWorld.com...Thanks!

Your wish is an order!  ;D See http://www.webattack.com/get/moveonboot.html.
Btw, why don't you try a Google search?  8)
Title: Re:reboot after reboot after reboot...
Post by: Lisandro on October 13, 2003, 04:50:53 AM
Thank you.  However, I do not mind the little problems that creep up with AVAST.
As Avast grows, "bugs" are part of the natural order of things.
WE learn from them! and it doesn't spoil my pleasure at all.!
Glad you are with us at the Forum.
techie  :D

A happy avast! user again  8)
Btw, take the link for MoveOnBoot, it works even whit files with "read-only" attribute  ;D
Title: Re:Reboot problem solved....Hope so!
Post by: nexus on October 13, 2003, 11:28:28 AM
Hi Technical
Could you once more put the link on this forum? The previous link doesn't work - but, moreover, searching for MoveOnBoot doesn't give me results at PcWorld.com...Thanks!

Your wish is an order!  ;D See http://www.webattack.com/get/moveonboot.html.
Btw, why don't you try a Google search?  8)

Hi Technical,

Thank you so much for your efforts, I finally managed to resolve the startup problems on my desktop!  ;D
And yes, I should have googled myself around.... My laptop gives me a little more trouble at the moment, but I am confident I will manage to deal with it (if not, you'll hear from me).

That tool, MoveOnBoot, was really a great help - I'd like to suggest it to all of you who might encounter the same problem: give it a try with this handy tool!

Thanks to you all, I'm now a truly happy Avast-user!   :)

Regards,
nex
Title: Re:reboot after reboot after reboot...
Post by: Vlk on October 13, 2003, 11:44:43 AM
Hi, it would be extremely useful for us to find out which program iut the invalid files to your system directory. These seem to be files distributed with a BETA version of Microsoft Visual Studio.NET.

Any clues?

Thanks

Title: Re:reboot after reboot after reboot...
Post by: nexus on October 13, 2003, 11:58:55 AM
Hi VLK,

Oh gosh... that DOES ring a bell... I did indeed download some .NET stuff, although I do not think this to be beta stuff... maybe any of the other updates could have raised the problems as well? FYI: here is the Win update-history for my system...

Regards,
nex

Quote
Geslaagd maandag 6 oktober 2003 KB828026: Beveiligingsupdate voor Windows Media® Player Automatische update
Geslaagd maandag 6 oktober 2003 KB828750: Cumulatieve patch voor Internet Explorer 6 Service Pack 1 (oktober 2003) Automatische update
Geslaagd zaterdag 20 september 2003 Aanbevolen update voor Windows Rights Management Client 1.0 Website
Geslaagd zaterdag 20 september 2003 KB822603: Aanbevolen update voor Windows XP SP1 Website
Geslaagd donderdag 11 september 2003 Windows MovieMaker 2 Website
Geslaagd donderdag 11 september 2003 KB824146: Beveiligingsupdate voor Windows XP Website
Geslaagd donderdag 11 september 2003 KB824146: Beveiligingsupdate voor Windows XP Automatische update
Geslaagd dinsdag 9 september 2003 820223: Update voor Outlook Express 6 Service Pack 1 Website
Geslaagd vrijdag 5 september 2003 Beveiligingsupdate voor Q811114 (Windows XP of Windows XP Service Pack 1) Website
Geslaagd donderdag 4 september 2003 KB824105: Beveiligingsupdate voor Microsoft Windows Automatische update
Geslaagd dinsdag 2 september 2003 DirectX 9.0b End-User Runtime Website
Geslaagd dinsdag 2 september 2003 Nederlands taalpakket voor Microsoft .NET Framework, versie 1.1 Website
Geslaagd dinsdag 2 september 2003 Aanbevolen update: foutregistratie van Windows (Windows XP) Website
Geslaagd dinsdag 2 september 2003 Q282010: Aanbevolen update voor Microsoft Jet 4.0 Service Pack 7 (SP7) - Windows XP Website
Geslaagd dinsdag 2 september 2003 Microsoft .NET Framework versie 1.1 (Nederlands) Website  
Geslaagd dinsdag 2 september 2003 817778: Aanbevolen update voor Windows XP SP1 Website

"geslaagd" = 'succeeded"
"Nederlands taalkpakket" = "Dutch language pack"
Title: Re:reboot after reboot after reboot...
Post by: Vlk on October 13, 2003, 12:13:46 PM
Do you still have the msvcr* files (the versions that were causing the problem)? If so, can you post their file versions (accessible in the Windows Explorer, by righ-clicking and selecting Properties...)

Thanks
Title: Re:reboot after reboot after reboot...
Post by: nexus on October 13, 2003, 12:27:31 PM
Do you still have the msvcr* files (the versions that were causing the problem)? If so, can you post their file versions (accessible in the Windows Explorer, by righ-clicking and selecting Properties...)

Thanks

Hi Vlk,

Their file versions were: 7.0.9447.0 (all three files MSVCI70.DLL / MSVCP70.DLL / MSVCr70.DLL )

Title: Re:reboot after reboot after reboot...
Post by: Vlk on October 13, 2003, 12:31:25 PM
Right.

The version we distribute is 7.0.9466.0 -- i.e. newer. The thing is, these files are from the first, original release of VS.NET. So anything older must be from some BETA version, I guess....

I wonder how these files got to your system... ???

Vlk
Title: Re:reboot after reboot after reboot...
Post by: nexus on October 13, 2003, 12:39:38 PM
Hi all,

As mentioned, I fixed the problem on my desktop but was still encountering some errors on my laptop. I've fixed them by now, so let's share what I did so that you might all potentially benefit from this.

After copying those .TMP files to their respective .DLLs (see the earlier postings) I got strange error messages on startup: error ^%^@%#*^%@%#@ (non-readable text) Ashdisp.exe and Ashmaisv.exe could not find their entrypoints in MSVCR70.DLL, even if that DLL was the right version! (Yes, I checked their versions by then :))

So I guessed my system was getting really cluttered.... This is what I did:

* remove Avast by:
- running the Avast uninstaller.
To make sure nothing is left anymore:
- remove the directory C:\Program Files\Alwil Software\Avast4
- clean the WinRegistry with a tool (e.g. jv16PowerTools, although not freeware anymore, see http://www.macecraft.com/ (http://www.macecraft.com/) but any other tool works just as fine)
- remove the MSVCI70.DLL / MSVCP70.DLL / MSVCR70.DLL from your C:\WINDOWS\SYSTEM32\ and C:\WINDOWS\SYSTEM32\DLLCACHE

* reboot

* re-install Avast

* run MoveOnBoot and put the MSVCI70.DLL / MSVCP70.DLL / MSVCR70.DLL files into another folder

* reboot (Avast will not be able to start the DLLs: thus, you'll get error msgs. No panic.)

* copy those MSV24/25/26.TMP files as described earlier in this forum onto the respective DLLs

* restart

After having done so, it's working just fine again... Maybe this is of any help to someone.

Regards,
nex

Title: Re:reboot after reboot after reboot...
Post by: nexus on October 13, 2003, 12:40:11 PM
Right.

The version we distribute is 7.0.9466.0 -- i.e. newer. The thing is, these files are from the first, original release of VS.NET. So anything older must be from some BETA version, I guess....

I wonder how these files got to your system... ???

Vlk

I wish I knew too....  :-\
Title: Re:reboot after reboot after reboot...
Post by: techie101returns on October 13, 2003, 05:20:40 PM
VLK and et all:

This is a very intriquing problem although it is simple to fix.

I have to admit that I am ashamed that I did not do what I normally do with a problem file....rename it.  I would have been able to send you a copy.  However, I do not believe that the files are the problem, nor AVAST.  

This information may help.  In examining the 3 files on my XP system, I did notice that the older files were version 7.0.9447.0 dated 2001 which is the date when my laptop was purchased.  It is my belief that the files were OE installs.  Furthermore, I have found that for some unknown reason, MS likes to attach "read only" status to files in the Runtime Library to protect them.
Bah! hahaha
None of the files on my computer are BETA.  These would have to be voluntarily downloaded which I do not do often unless testing a program in a contained environment.

The repair was simple...very simple....
It did not require copying over, or deleting, or removing reboot.txt or anything like that.  Users should not try to do anything with the registry either.  It is not necessary in this case.  Extreme measures will usually bring about extreme results....some unwanted!

In one of the posts, Yildi brought up the attribute status.
If the Read Only is removed from the 3 files, AVAST has no trouble replacing the older files with the newer 7.0.9466.0

The only way to rectify this automatically would be to have Avast "exit" Windows, enter Dos and start a batch exe file to check attribute, remove attribute, set files and then exit back to windows.

This is not only excess work, but I do not like to hand over control of my operating system in Dos mode to another program.

At this point, making users aware of the simple corrective measure is the best course of action.

Another post by Nexus mentioned the Microsoft.Net framework update.  This is not a BETA release.  Updating MAY even correct the file problem.  Since MS won't comment on this.....it is kind of up to us to see where this goes.

I do believe in using the MS Windows Update often but only download and install those programs that are relevant.  Just because MS "recommends" doesn't mean that I "need" !

It is extremely difficult for a software vendor to anticipate any and all events that might occur between their program and others.

It is our task as AVAST afficianados to do what they cannot!

LONG LIVE AVAST AND THE PEOPLE WHO SUPPORT IT!!

 :D  :D   :D  :D  

Sorry for the long post.  It takes a bit of time sometimes to get my thoughts out.