??? Main computer successfully updated to 5.0 on prompt from Avast. Backup unit which has exactly the same setup–XP Pro, SP3, etc. with Avast 4.8–loads program just fine, but after the first reboot, goes into a continuous reboot situation after about 30 seconds running. I have started from scratch, reloading XP and all the updates, plus the other programs–very tedious on dial-up. I have tried all the suggestions I have seen so far to no avail, including Avast removal tool, reloading 4.8, ad infinitum. It acted the same trying 5.0.418 as it does with 5.0.462. It apparently loads beautifully and will go through the update motions, etc. as long as you don’t shut down. When you do, on reboot, the icon comes up, but apparently when it tries to turn on the program, it croaks, and goes into the continuous reboot pattern. I would like to run 5.0, but so far, no luck. 4.8 does fine but won’t be around forever. Ideas??
I suggest an installation from the scratch:
- Download the latest version of avast! Uninstall Utility and save it.
- Download the latest avast! version and save it.
- Uninstall avast from Control Panel (if possible). If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after that. You have 2 tools, one for avast 4 and another for 5.
- Run the avast! Uninstall Utility saved on 1. If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after you’ve run it.
- Install avast! using the setup saved on 2. Boot.
- Register your free copy or add the license key for Pro.
- Check and post the results.
I have already followed this exact procedure at least twice–once with 5.0.418 and once with 5.0.462–same result. It should be noted that after reloading XP, all MS updates and the same programs I had previously, with the exception of Avast 4.8, the rig acted just the same when I tried to load 5.0.418 the first time. Before reloading the whole tamale, the problem was identical after the initial loading of 5.0.418–Avast asked did I want to restart, I said OK, and it was never right again. If this is not an Avast problem, it might be a compatibility issue with some setups of XP–I do not know. I do believe, however, after all the repeated attempts I have made, including this exact procedure, that there is a problem not related to my individual computer or my techniques, but I could well be wrong. If noone else has duplicated this malady, I will just have to wait and be satisfied with 4.8, which has served me well. It’s just that 5.0 looks cleaner and quicker–I don’t know for a fact that it is any better…Tryinhard
I had hoped that someone more knowledgeable than I would have some ideas beyond the removal/reinstallation vicious circle, all of which I have tried. I doubt that the problem is with Avast, but so far that is the only indicator of trouble I have had. I believe there is a compatibility problem that is affecting boot of Avast 5.0, but nothing else. It may be a boot sequencing issue, since 5.0 will run beautifully after installation, until I turn the computer off, and then it will not on the next restart, when the computer shuts down right as Avast tries to energize. It may be an issue with another program besides Microsoft in the boot process–I don’t know. That is why I am asking Avast users for help, but I am convinced the issue is not the preparation for, or the actual loading of Avast, and since 4.8 will run without incident, it must be something related in some way to 5.0. If anyone has a better idea of a forum for me to try, I would be grateful for that.
I’m still using 4.8, and happy with it for now, so the scope of any ideas I have is of course, limited.
What other security software is installed, or has been installed in the past, on this computer?
After 5.0 failed, I completely started over, reloading XP and everything else that had been in place. I was running 4.8 only before, and have gone back to it because of the problems with 5.0–no other programs. 4.8 continues to click away with no problems. It just seems odd that something in my system is allergic to 5.0…
Stabbing in the dark a bit, here, but do you have C++ installed?
Yes, actually I do have C++, and I think I unintentionally told a fib. For about a day, I had Avira Free after the initial problems with 5.0, but it irritated me, so I took it off immediately. Trying to remember–is C++ associated with Avira in some way??
Did you remove Avira completely?
http://www.avira.com/en/support/removal_tool_windows.html
What is the system specifications of the CPU as to speed and CPU type?
How much RAM does the system have?
I have no problem on my XP Pro system.
Avira is completely gone. The problem with Avast predates Avira, and even predates my last complete reload of XP Pro and everything else, as I tried to convey in previous entries. I am successfully running 5.0 Free on my other computer that is exactly set up like this one, with no problems. My system is more than adequate, and the program runs just fine as long as you don’t reboot. When you do, it goes into continuous reboot cycle, and 5.0 must then be removed. If someone could only tell me what is different in the setup between 4.8 and 5.0, maybe we could start to get somewhere. 4.8 works flawlessly, and I continue to be stymied…
Well, thanks to the few who tried to get beyond the somewhat worn-out umbrella of de-installation and re-installation. Net result, however, is no progress, and it appears that 5.0 will remain distant from this computer. I never said that Avast was the sole problem–only that some incompatibility issue existed between my unit and version 5.0 that didn’t exist with 4.8. It is interesting to note that not all of the seasoned veterans on this site are flocking to 5.0, perhaps because there are so many issues that keep popping up. At any rate, if I ever see anyone else’s predicament that mirrors my own, I will be curious to see what help they might garner. Onward and upward… :-\
Install with Options/Troubleshooting/Load Avast… checked.
This stopped my BSODs.
Ian
Ian–I’m “newbier” than you, so I’m not sure what BSOD’s are. Also, if you are talking about the settings in the 5.0 program, which I’m guessing you are, I have it downloaded and saved, but how can I get into the settings without installing the program?? The program won’t install without the reboot stuff going on, so I guess I’m not following how to get where you suggest. Also, I’m hoping for some insight on the cumulative updates for 4.8 in my other post. It is simply too big a deal to have to reload all the updates every time 5.0 fails and I have to go back to 4.8. If I could get a shortcut there, I would keep trying to get 5.0 going. Otherwise, it’s been too bumpy a ride…
I mean install the programme and before you reboot ensure Avast is ticked to load after other services as per my post.
I’m grasping at straws but it could work.
BSOD Blue screen of death. My problem was BSOD so I ticked for Avast to wait until other services have loaded and that solved the problem. To uninstall Avast after getting a BSOD I had to go into safe-mode. http://www.computerhope.com/issues/chsafe.htm
Good luck,
Ian
??? I’m definitely on the outside here, but is it possible that you have overlooked some difference in setup or hard parts that hasn’t had an impact before, but might with V5–like the Avira deal you mentioned earlier?? I understand your reluctance to go into details that you are reasonably sure can’t affect the installation, which you say is identical to the unit which is successfully running V5. The fact remains, though, that you are having a repeated problem after numerous attempts at removing V4.8 and going with 5.0, so something has not been addressed, and despit the troubles with 5.0 I have seen on this forum, none matches yours, so I am a little suspicious. I won’t take you to task like Mr. Yo Kenny, because it is sometimes difficult to see things right under your nose without help. I have problems with students in this regard, and am not saying there is an undiscovered answer there for sure, but think it over again, without prejudice, and see if anything pops up. :-\
OK–I’ll line-item everything and see, but the setups have been in place for a long time, and the only difference I can think of right now is that one accepts 5.0 and one doesn’t. I didn’t intend to alienate anybody, but I really am smart enough in this discipline, if not in forum ethics, to know when certain things are a wild goose chase. No, I don’t have the answer to my plight, but that shouldn’t automatically open up my skill level or integrity to ridicule from others.
Well back in the 4.8 version this could also happen (Operating system restart needed) when reboot.txt or a registry key wasn’t being reset after the boot for whatever reason (registry protection, some firewalls, etc.). Now this may well be way off base in version 5.0 if it uses the same method to initiate the reboot and to remove it after the reboot, but I guess it is worth a try.
This is the complete list of checks for 4.8 to try and resolve that:
Operating system restart needed by avast message - First check the contents of the C:\Program Files\Alwil Software\Avast4\Setup\setup.log file, which should show you why it thinks the reboot is needed. ([i] re 5.0 C:\Program Files\Alwil Software\Avast5\Setup\reboot.txt[/i]) This may be solved, in some systems, by deleting the file C:\Program Files\Alwil Software\Avast4\Setup\reboot.txt. With the avast self-defence module it will complain so disable that first, Program Settings, Troubleshooting.If that doesn’t resolve it check this:
You can also check this registry entry (right after computer restart):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager, if it contains “PendingFileRenameOpertaions”.Check its contents and if there’s only “reboot.txt” from avast4\setup folder, delete PendingFileRenameOperations, don’t delete any other key. (re 5.0 “reboot.txt” from avast4\setup folder)
Back-up (export) the registry key before you edit/delete, just in case.If that still isn’t the problem it could be a tweaking exercise that has an impact on avast.
- Also see 8,3 Tweak issue - Check out this thread and see if some of the possible solutions can help you too.
http://forum.avast.com/index.php?topic=28199.0
Now as mentioned this is 4.8 related so you will have to try and suss out the differences in 5.0 locations, etc. (bracketed italics) and see if any exist and if that resolves it.
In response to oldpro–I went through everything with a fine-tooth comb, including all Cdrive entries, registry, task manager–everything I could think of and found no flags. The only difference is that one has 5.0 and the other 4.8. Now, this is in regard to DOS and programming–I cannot verify about the BIOS setups, but am going on the basis that once Windows starts, they become a non-issue–hope that’s right. I have a nice reply from David R that I need to study on a while, but hope you will get back to me.
It took a little while to get through all your postings, and I just looked at David R’s reply also–I see a genuine good effort there. However, let me suggest a slightly different approach before you delve into his suggestions. Either way, if you are keen on keeping the 5.0 effort alive, it is going to require the removal of 4.8 yet again in any case, and if it were to be another non-successful install of 5.0, a reinstall of 4.8 plus updates, which I see is a thorny subject for you. However, you indicate you already have the removal tool for both, plus the 4.8 and 5.0 programs already downloaded, so that will be your decision. Now, after looking at all the activity connected with this problem, it is my humble opinion that this is most likely just a boot problem, and not a major program issue, which seems to agree with David R’s latest approach. I say this because you indicate that 5.0 downloads just fine, plus it will update and so forth as it should, AS LONG AS YOU DON’T REBOOT. That shows me that your system is fully capable of accepting AND running the program. When you reboot, you say the icon shows up, but after a short delay, it goes into the vicious reboot cycle. For some reason, 5.0 will not start as it should at that point. There may still be a conflict of sorts which is killing the program, but I believe it might just be a boot-sequencing problem, which one of your repliers–the one with the blue screen difficulties–alluded to. I would try changing the sequence first, and although I am hopeful for you, I am not totally convinced that the change will sustain a successful boot. If it does not, you have the information from David R to try, which looks like it has promise based on his previous experiences with the Avast system, which I am not overly familiar with. Long-time exposure has hopefully taught me to search for the simplest answers first, and observe, observe. I do wish you good fortune and hope I haven’t led you down a primrose path with lacerating thorns alongside.
Thanks to both of you guys. I am going to put any further effort off until tomorrow–my eyes are toasted–, but maybe there is a ray of hope after all. 