New update (4.7.826)

[Vlk]

Please hold on for a while. The bits are just being pushed to our distribution servers. It takes some time...

Thx

[quard]

Ok and thank you very much! Having any problems with Avast! is scary because we rely on it and love it so much! Even with this it has far less problems than Mcaffee and Norton's; I've used Avast for quite  afew years and recommend it to everyone I know. Again, thanks.

[njoyslife]

     Thx 4 the heads up VLK

[Spyros]

Vlk, will there be another version of aswClear.exe, or should I try to remove everything manually?

[njoyslife]

     I did mine manually, i hope when i get a notifacation for  the new download, everything will work

[Vlk]

Spyros,

are you sure you downloaded/ran the NEW version of aswClear.exe?
It should work quite reliably. Are you logged on as Administrator (you must be, actually).

Anyway, you can remove the folder manually. All it takes is to Open the properties of the Avast4 folder, go to the Security tab, click Advanced, and do "Take ownership".  Then add Everyone/FullControl to the list of rights, and delete the folder.


Thanks
Vlk

[Spyros]

Vlk,
yes, I ran the latest version, but no luck with it.
Inside avast's folder, I had to give to a lot of files and folders full rights to "Everyone" as they had none (look at the previous pictures I sent to Igor). Now everything seems to be gone, I'll take a look at registry too.

[DavidR]

No problems here with the original update, XP Pro SP2, since my drives are in FAT32 format I would be immune to any permissions issues relating to the avast folders.

[Vlk]

The new build is already on the servers.
It should definitely solve the problem, even though it's just a temporary fix. We'll have to look into this further.

Right now, we think that the problem appears if ANY of following 3 conditions is met:

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


Can you please guys confirm that this is really the case?


Thanks
Vlk

[Steele]

VLK, I installed 4.7.826 immediately after it was released on public servers this morning.
Is this a new build that will require me to invoke a program update?
Again, I am not experiencing any issues with 4.7.826.
BTW: What is the version number of this new build?

[Vlk]

The build number is 4.7.827, and you can (but don't have to) update to it -- it's just a couple of KB's long and won't require a reboot, so it really doesn't make any difference.

Thanks
Vlk

[Steele]

Thanks for your time.   

[Osc]

I've updated to 827, everything now seems fine.

After getting the access denied error, but before discovering this thread, I found the avast folder had no permissions for any user or group. I tried adding administrator with full, which let me start the gui, but somehow the permissions reset (to blank). I then gave full permission to administrator, everyone, system and service, forced permissions to inherit to all child objects and was then able to run the gui again *and* update.

Reboot requested and done. avast is now working  =]

ps: os is w2k and avast is installed in a folder other than "c:\program files", in fact, it's installed to "d:\avast"

[Coris]

vlk

i downloaded last version 827 after 826. Still OK for me

[FreewheelinFrank]

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