reboot after reboot after reboot...

Avast Free Antivirus / Premium Security
21

Hi,

It seems (until now :wink: ) 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 :slight_smile:

MY

22

Thanks, yildi
You´re very wellcome to foruns :wink:

23

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

24

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

25

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

26

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?

??? ???

27

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

MY

28

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

29

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.

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

30

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

31

A happy avast! user again 8)
Btw, take the link for MoveOnBoot, it works even whit files with “read-only” attribute ;D

32

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

Regards,
nex

33

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

34

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

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”

35

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

36

Hi Vlk,

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

37

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

38

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/ 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

39

I wish I knew too… :-\

40

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

:smiley: :smiley: :smiley: :smiley:

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