Version: 17.6.2310

[cruiser25]

As mentioned by bruce_b behavior sheild still is not turned on when starting up , Windows 7 home premium, avast antivirus pro. Should have been solved with this update acording to a previus answer in this forum. Not so !

[Patrick2]

In my Opinion they should've squashed more bugs in latest 17.6 version and released the stable version closer to Windows 10 Fall Creators update,  though I think when Avast was running version 12, there was longer beta periods and not monthly stable build releases, which in my opinion is rushed release it feels like as so many old bugs,  plus new bugs being introduced with latest Avast builds

[mchain]

Couple days late and saw new version available 8/31/2017.  Did a clean install using Programs and Features>reboot>avastclear.exe>safe mode as admin>run avastclear>reboot>install newest version.

Confirmed two-stage gui opening:

• Initial open results in white box, nothing inside for about 30 seconds
• Subsequent open gui 4-6 second range, see attached below:

About the same amount of time to open gui as with version 17.5 once the initial start is done.

Rescue Disk is working.

Firewall popups now say "allowed" instead of "banned" as in version 17.5.  Thank you.

At least the popup notifications were not moved to center stage in this OEM version as was done in the betas before now.

[REDACTED]

UI fail to load (avast service is stop loading) after installed , and firewall component automatic deactive at first time restart , please check avast "internet security" installer......

[A. User]

I like the new loading of the UI. As slow as before, not slower than before. HOWEVER, the issue with the behavior shield not turning on on startup is not fixed, and you said that it was fixed in the beta. Seems the fix is not working.

[Alikhan]

I like the new loading of the UI. As slow as before, not slower than before. HOWEVER, the issue with the behavior shield not turning on on startup is not fixed, and you said that it was fixed in the beta. Seems the fix is not working.

Please create your own thread. Are you running Windows XP.?

[A. User]

I like the new loading of the UI. As slow as before, not slower than before. HOWEVER, the issue with the behavior shield not turning on on startup is not fixed, and you said that it was fixed in the beta. Seems the fix is not working.

Please create your own thread. Are you running Windows XP.?

Windows 10 version 1703. Isn't this topic monitored by Avast team, i thought i would have greater chance to get noticed here. 

[REDACTED]

Windows 7 SP1 64bit.
Since I've updated Avast to 17.6.2310 Firefox (and Internet Explorer) won't start - "Firefox has stopped working".
 "Fault Module Name:   ntdll.dll
  Fault Module Version:   6.1.7601.18798"

I've tried to turn off and on streaming updates without success.
As I can see the only current cure is uninstalling Avast.
Or?

[Alikhan]

I like the new loading of the UI. As slow as before, not slower than before. HOWEVER, the issue with the behavior shield not turning on on startup is not fixed, and you said that it was fixed in the beta. Seems the fix is not working.

Please create your own thread. Are you running Windows XP.?

Windows 10 version 1703. Isn't this topic monitored by Avast team, i thought i would have greater chance to get noticed here. 

It's best to create your own thread since posts are easily lost in this topic.

The Avast team may also require logs assuming you've tried a repair and clean install.

[Asyn]

Windows 7 SP1 64bit.
Since I've updated Avast to 17.6.2310 Firefox (and Internet Explorer) won't start - "Firefox has stopped working".
 "Fault Module Name:   ntdll.dll
  Fault Module Version:   6.1.7601.18798"

I've tried to turn off and on streaming updates without success.
As I can see the only current cure is uninstalling Avast.
Or?

-> https://forum.avast.com/index.php?topic=208097.0

[REDACTED]

Windows 7 SP1 64bit.
Since I've updated Avast to 17.6.2310 Firefox (and Internet Explorer) won't start - "Firefox has stopped working".
 "Fault Module Name:   ntdll.dll
  Fault Module Version:   6.1.7601.18798"

I've tried to turn off and on streaming updates without success.
As I can see the only current cure is uninstalling Avast.
Or?

-> https://forum.avast.com/index.php?topic=208097.0

Thanks!

[Asyn]

Windows 7 SP1 64bit.
Since I've updated Avast to 17.6.2310 Firefox (and Internet Explorer) won't start - "Firefox has stopped working".
 "Fault Module Name:   ntdll.dll
  Fault Module Version:   6.1.7601.18798"

I've tried to turn off and on streaming updates without success.
As I can see the only current cure is uninstalling Avast.
Or?

-> https://forum.avast.com/index.php?topic=208097.0

Thanks!

You're welcome.

[gpw]

Hi
After installation of the new version I got very unpleasant bugs.

1. Completely disappeared text from "Save as..." and "Open file" forms of my browsers. At least in Chrome and Firefox like

moreover, I couldn't even type of filename in the textfield of those forms!
Need to say that other Save as.. or Open forms from MS Office, or other programs were not corrupted like in browsers. But maybe I have tested not all of them.

2. Adobe Acrobat Reader DC got the next GUI:


3. Thinking it was trouble of Acrobat Reader tried to reinstall it. And got the next type of message:

Also similar picture for GUI was noticed for my HxD - Hex editor, but after scanning by Avast its GUI restored.

After rolling back of my OS (Win 7) to the previous state all those bugs disappeared. After I performed update of Avast Premier all those mentioned bugs appeared again that proved for me that failure happened just in Avast product.

Any ideas, gentlemen how to fix this? I'm afraid of making update again, as soon as I'm nost sure that even deinstalling of Avast can return back functions corrupted with this update.

regards
Alex

[Asyn]

Any ideas, gentlemen how to fix this?

Hi Alex, see: https://forum.avast.com/index.php?topic=208097.msg1418018#msg1418018

[gpw]

Hi Alex, see: https://forum.avast.com/index.php?topic=208097.msg1418018#msg1418018

Aha, thx. Looks it works. After renaming the bug looks to be fixed.