New update (4.7.826)

[Steele]

VLK:
Updated to 4.7.827 by invoking Program Update.

All is well.
DID NOT REQUIRE REBOOT!   

[igor]

- your OS was updated from Windows NT 4.0, OR
- you installed avast in other folder than the default Program Files folder (that was offered to you by the installer), OR
- previously, you converted your system volume from FAT32 to NTFS.

None of these is true for me.

But you still have "Full Control for Everyone" permissions for Program Files folder (or whatever the parent folder of the avast! installation folder is), right?

[njoyslife]

     Filehippo has version 4.7 817 if anyone needs it.

[Bargraline]

On Windows XP Home SP2
Did have 4.7.817 on a "personalized" folder, update this morning to 4.7.826
Update was wrong all avast services NOT running
Avast folder NOT accessible

Giving back rights on folder on my own. Erasing avast
Installing 4.7.817 --> OK (always on another folder than default)

Updating to 4.7.827 --> OK

Good job guys, thank you !

[njoyslife]

4.7.817 to 4.7.827 updated smoothly, thanks for the quick action, great job Avast team.

[greenhatch]

Nor me either    

- your OS was updated from Windows NT 4.0, OR
- you installed avast in other folder than the default Program Files folder (that was offered to you by the installer), OR
- previously, you converted your system volume from FAT32 to NTFS.

None of these is true for me.

[quard]

- your OS was updated from Windows NT 4.0, OR
- previously, you converted your system volume from FAT32 to NTFS.

No to both.

- you installed avast in other folder than the default Program Files folder (that was offered to you by the installer),

I installed to E:\Program Files\Avast

[greenhatch]

Thankyou! Just what I was looking for. I'm not touching .826 or .827, heh; I'll just waithing for the next version, tried and tested (by others).

     Filehippo has version 4.7 817 if anyone needs it.

[heinblöd]

Hi,

the new Version now works fine. THX Jörg ;-)

[Vlk]

There's a new FAQ entry about this problem now: http://www.avast.com/eng/4-7-826-problems.html


Thanks for helping to contain the situation.
According to my calculations, the problem affected 0.1 - 0.4% of our users.


Vlk

[Sunnyday26]

I am not able to access the avast4 folder, it denies me. I was not aware of the aswclear.exe and stupid me goes to regedit. I guess I will be using the aswclear to get myself under control.

None of these apply to my laptop
* the operating system was previously updated from Windows NT 4.0; or
* avast was installed in a different folder than the default Program Files folder (that was offered to you by the installer); or
* previously, the system volume was converted from FAT32 to NTFS.

But was this incorrect,
C:\Program Files\Alwil software\avast4

I must say that even though this is a small incovienence to me for one of my computers, I have always recommended Avast and I am glad to see the website address this error so quickly but I would probably put the following solution under updates as well as other questions.
"Q: After updating my avast! Home/Professional to version 4.7.826, it no longer works. If I try to run it, it doesn't seem to be doing anything, or displays an error message.'

[MikeBCda]

For what it's worth, no problems with upgrading to 827 here, on my XP system.  I haven't done any scans yet, but the resident providers seem to be running fine, and the interface opens with no problems.  And it sounds like most of the problems others are encountering show up at bootup.

Oh, and I did get the usual needs-to-restart notice.

[stmars]

Hi,

I went back to avast 4.6 and now can I use the program update from
the blue avast icon or wait a bit more.

Regards and thanks

Jean

Montreal

[alanrf]

Just a bit puzzled by the problem description.

I have avast installed on a physically different drive instead of my C: drive.

In the past couple of days I have used the auto-upgrade function to go from version 817 to 822 to 826.

826 installed and is running without any problems on my F: drive.

So the problem has to be a bit more complex than the description posted. 

[Vlk]

The FAQ entry is oversimplified as we wanted to avoid the use of tech-lingo (most people wouldn't understand it anyway).

In short, the problem occurs if, and only if, the folder ABOVE the avast folder (e.g. "C:\Program Files") has only one entry in its Access Control List, and this entry is Everyone -> Full Control.

That is, the list on the Security tab of the folder's properties has only this one entry.
Because that's when we were taking the special action (that was incorrect).


I hope that explains it a bit.
Vlk