Why is avast! asking for a Reboot Daily ?

[martosurf]

hi guys thanks 4 your time

Tech Yes indeed. When I first come with issues with the latest build and after applying the 8.3 tweak to revert to windows by default name system, I just had to uninstall avast! and download a fresh new copy from the website because the continued ask for reboot. Before installing the fresh copy I was asked to reboot anytime I manually checked for updates or even right after log in, now I have reboot requests just after updating VPS  :'(

alanrf I already did:

1. Get back to 8.3 system by downloading and applying the registry tweak from avast! I checked later with regedt32 and it worked fine.
2. As vlk and igor asked I already did that.
3. I didn't Repair yet avast!

Will try this and let you know 

Best regards, Martín

By the way: I don't want to open a new thread on main forum so because I have you both at hand I need to ask you about the webshield: do you experience a notorious slowdown when websurfing and the WebShield on? I just started to note this today... I did read about this on other topics but never experienced it to this point until today... there's a real noticeable lag between hitting enter and IE7 showing for example this forum, and I didn't make any other change to the system so far...

[water]

Deleting the reboot text file and then doing the repair works for me... so far.

[Lisandro]

I just had to uninstall avast! and download a fresh new copy from the website because the continued ask for reboot.

But when you uninstall, did you boot and the use the Avast Uninstall for complete uninstallation? I mean, to install from the scratch, you should have NO avast previous folder in the computer.

[martosurf]

Yes already did it   
Just for the case I did a repair too, let's see next update 

[gdiloren]

  I repeat, read the past previous threads. You only need to delete the Reboot.txt file in Avast/setup (see appropriate past thread for more precise location).

[DavidR]

For some, deletion of the reboot.txt isn't enough.

[martosurf]

Yes already did it  
Just for the case I did a repair too, let's see next update 

still the same... :'(

[Tarkus.]

martosurf,

one of the folks I support reported the same issue to me after the 4.7.1001 update.

Before trying a complete re-install I took a look at his system (remotely). 

Here's what worked for him:

1) checked and found he had the 8.3 registry tweak installed - set it to 0 (as advised by avast).
2) deleted the reboot.txt file from the folder C:\Program Files\Alwil Software\Avast4\Setup
3) used the Repair option of avast - it said it had repaired avast and requested a restart
4) restarted the system

Since then there have been no more requests by avast to restart after a manual VPS update check or an automatic VPS update.

I was having the same problems with rebooting and gollower the steps here and it resolved the rebooting issue.  It also fixed another problem that I was having which I would not hve attributed to the change by Avast.  I have been having connectibity issues over my wireless link the past two weeks and poof once I did this that all cleared up.  I mention this because in another post someone else mentioned connectivity issues.

I wish we had an explanation for the change.  There may be more that are fighting connectivity issues and have not made a connection to Avast being a part of them.

Tarkus

[martosurf]

I love this AV but this recent issue bothers a lot. I just uninstalled and cleaned with the avast! cleanup, reinstalled then and after the first signatures update it asked to reboot (f*ck)

besides that it seems to be stable, let's see what happens after next signatures update...

meanwhile i tested nod32... excellent, but i get stuck with avast!... it's a skin matter xD

[DavidR]

<snip>
I was having the same problems with rebooting and gollower the steps here and it resolved the rebooting issue. 

It also fixed another problem that I was having which I would not hve attributed to the change by Avast.  I have been having connectibity issues over my wireless link the past two weeks and poof once I did this that all cleared up.  I mention this because in another post someone else mentioned connectivity issues.

The above issue (8,3 file name tweak) reverses a tweak that was applied by the user to their copy of windows, avast's action of providing a .reg file to reverse that user initiated tweak is correcting a windows tweak problem by the user not an avast problem. avast happened to bump into it in probably the same way your other program did.

[Tarkus.]

The issue is that all was fine before the avast update.  Disabling 8.3 filenames did not cause any issues prior to the avast update and that has been for over a year on this box.  The box worked great.  Updateing avast caused connectivity issues with my wireless setup and also avast wanted me to constandly reboot.  Applying their 'fix' , which basically was enabling 8.3 filenames and doing a repair on avast fixed both of these problems.  There should never had been any effect to connectivity but there was.  You figure it out.

Tarkus

[bob3160]

I just tried installing a program and now get the following error:



This is obviously the result of fixing the reboot request problem for avast!

GreenBorder Pro. will not install without reversing the fix requested to fix the reboot problem.
Does someone from Alwil have an answer for me? 

[alanrf]

bob3160

I am not from avast but I think you are are having a little trouble with English as she is used.

That message asks you to do precisely what avast asked you to do. 

Try:

fsutil behavior query disable8dot3

on your system.  GreenBorder wants you to make sure the setting is 0 which is just the same as avast asked.

[bob3160]

Thanks alanrf I've changed the value to 0 and that did the trick.

[ComputerVet]

Here's how I fixed it.

In regedit I had to set BOTH the following keys to 0 AND delete the file reboot.txt mentioned previously.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisable8dot3NameCreation
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisableLastAccessUpdate

I stumbled across
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem : NtfsDisableLastAccessUpdate
while looking at the NtfsDisable8dot3NameCreation value and thought "Gee, I wonder if Avast is looking at when something was last accessed"... (I hate uninstall/reinstall as a fix)