Version: Avast 17.5.2303

[bob3160]

Bonjour;
La nouvelle version bloque tous les téléchargements et tous les sites web !!!!
Une fois l'agent web désativé tout fonctionne.
Cordialement

https://forum.avast.com/index.php?topic=204845.0

Any language other than English is forbidden here. 

This is the English Section which also happens to be the default language on this forum.
There are many other languages available which is why I posted a link to the other language forums.
https://forum.avast.com/index.php?board=21.0

[Dix Huit]

Bonjour;
La nouvelle version bloque tous les téléchargements et tous les sites web !!!!
Une fois l'agent web désativé tout fonctionne.
Cordialement

https://forum.avast.com/index.php?topic=204845.0

Any language other than English is forbidden here. 

This is the English Section which also happens to be the default language on this forum.
There are many other languages available which is why I posted a link to the other language forums.
https://forum.avast.com/index.php?board=21.0

Yes sir, that is what I was attempting to communicate.

[midnight]

I had to disable the shields to sign into one of my checking account's.  Never had a problem before I updated Avast.

[zenzor]

And I'm still seeing this when Avast gives a program access (looks like one that's very simple to fix):

[jan.svoboda]

To clarify, this release is mainly for business. SMB (Small & Medium Business).

Thank you, the first post was updated so it is not confusing what does SMB mean.

[jan.svoboda]

I can't believe, beta 17.5.2303 released on Friday, new stable version 17.5.2303 released on Tuesday. I wonder what could have been achieved in the beta release.

If "this version contains mainly fixes under the hood for SMB customers." What benefit for non SMB customers ?

I'd like to know which of the many bugs that were in the last release have been fixed in this one
With the timeframe from beta to final release, why bother having a beta version at all

From non SMB customers point of view, there should be no changes. The main reason for this release was to fix issues in SMB (Small & Medium business ). We just wanted to have the same version of product in nonSMB and SMB channels. Also we wanted to have feedback and data (for example crash reports) from beta and also from non SMB customers.

Simply its just the way how it works for us - Beta -> Release -> SMB Release.

[bob3160]

@ Dix Huit,
Sometimes it's not what you say but how you say it that matters.

[REDACTED]

Well it didn't fix the HTTP Scanning Problem that is affecting XP and Vista users. 
All it did was put my Vista laptop right through the mill 
My CPU was stuck at 100% for about 10 minutes. And I really didn't think the update was ever going to finish.
Still got to update my sons Windows 7 desktop yet. Not looking forward to it!

The problem was with HTTPS.

Do you think this [HTTPS Scanning] and Web Shield ] is complicated problem to fix the program?

Is it possible to ask how long do we expect to wait for repair?
1 month, 2 months 3,,,?

Do you know where is the webpage to ask question to Avast Tech person?

I found that:
Since many Avast user are starting to change to Avira anitivirus soft, during long waiting time.

[bob3160]

Well it didn't fix the HTTP Scanning Problem that is affecting XP and Vista users. 
All it did was put my Vista laptop right through the mill 
My CPU was stuck at 100% for about 10 minutes. And I really didn't think the update was ever going to finish.
Still got to update my sons Windows 7 desktop yet. Not looking forward to it!

The problem was with HTTPS.

Do you think this [HTTPS Scanning] and Web Shield ] is complicated problem to fix the program?

Is it possible to ask how long do we expect to wait for repair?
1 month, 2 months 3,,,?

Do you know where is the webpage to ask question to Avast Tech person?

I found that:
Since many Avast user are starting to change to Avira anitivirus soft, during long waiting time.

I can't answer that. I don't work for Avast. I use the program same as you.
I'm waiting for the correction just as you.

[REDACTED]

Getting the same here on win10, hands on "verifying dmi pool data".

Applied the update via the Avast user interface. Rebooted when requested. The box (i7 Win7(64) Pro Lenovo) is still sitting at the BIOS boot screen (very pre-Windows logo) after 15 minutes with the disk drive activity light on constantly.

Not. Happy.

Take a chance and do a forced shutdown?  Sit tight and hope for the best? Kill a chicken and sprinkle its blood on the keyboard??

Really ... Not. Happy.

[REDACTED]

Hi, just new to this forum, so please be gentle,

I have experienced a major pc crash (BSOD) after a standard restart process once the latest avast update was installed. I have been running windows 10 (1607) for at least a month after the latest win 10 update. I have followed the avast recommendation in regards to running the latest version before installing win 10 anniversary etc, and it's been running sweet.

I usually manage to fix these problems myself, but this BSOD/ inaccessible boot device is a beauty, it's got me completely baffled. After the auto repair continuously fails, it lets me get to advanced options/change start up settings (safe mode etc) and that's all folks. It will not even allow me to start win in safe mode. The only access to the pc is through the asus UEFI BIOS, which only has limited options or command prompts, which I am a bit under skilled with.

I updated win 10 via the net so, I don't have an install DVD, or even a back-up disc. I don't understand how it has come to this, everything was working perfect, right up until the avast update restart.

Is there a kind person out there who knows the right tricks to get me out of this pickle.

Cheers

[REDACTED]

Well it didn't fix the HTTPS Scanning Problem that is affecting XP and Vista users. 
All it did was put my Vista laptop right through the mill 
My CPU was stuck at 100% for about 10 minutes. And I really didn't think the update was ever going to finish.
Still got to update my sons Windows 7 desktop yet. Not looking forward to it!

CONFIRMED...latest update blocking many, but not all, of my HTTPS sites on my VISTA computer.  AVAST???

[Asyn]

Known issue on Vista. It should help to disable HTTPS scanning in the web shield.

[bob3160]

Hi, just new to this forum, so please be gentle,

I have experienced a major pc crash (BSOD) after a standard restart process once the latest avast update was installed. I have been running windows 10 (1607) for at least a month after the latest win 10 update. I have followed the avast recommendation in regards to running the latest version before installing win 10 anniversary etc, and it's been running sweet.

I usually manage to fix these problems myself, but this BSOD/ inaccessible boot device is a beauty, it's got me completely baffled. After the auto repair continuously fails, it lets me get to advanced options/change start up settings (safe mode etc) and that's all folks. It will not even allow me to start win in safe mode. The only access to the pc is through the asus UEFI BIOS, which only has limited options or command prompts, which I am a bit under skilled with.

I updated win 10 via the net so, I don't have an install DVD, or even a back-up disc. I don't understand how it has come to this, everything was working perfect, right up until the avast update restart.

Is there a kind person out there who knows the right tricks to get me out of this pickle.

Cheers

You should find some helpful recovery information here:
https://support.microsoft.com/en-us/help/12415/windows-10-recovery-options

[REDACTED]

Hello,
After upgrading to the new version 17.5.2303, the firewall blocks the access to Microsoft SQL SERVER and my applications do not work if you do not deactivate the firewall.
I use Windows 10 Pro and Avast Internet Security.

Greetings
Jose