Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: Karel Šťavík on January 02, 2019, 03:28:38 PM
-
Hi everyone,
new beta version 19.1.2360 (build 19.1.4142) is released.
What was fixed
- Final tuning before release to public
Download links:
http://public.avast.com/mkt/betaav/avast_free_antivirus_setup_online.exe
http://public.avast.com/mkt/betaav/avast_internet_security_setup_online.exe
http://public.avast.com/mkt/betaav/avast_premier_setup_online.exe
http://public.avast.com/mkt/betaav/avast_pro_antivirus_setup_online.exe
Enjoy this beta!
We are looking forward to your feedback.
AVAST Team.
-
Thanks Karel, testing it asap...
-
Updating on Beta Channel.
THanks :)
-
The bankmode bug isn't fixed..!!
https://forum.avast.com/index.php?topic=223975.msg1488049#msg1488049
-
The bankmode bug isn't fixed..!!
https://forum.avast.com/index.php?topic=223975.msg1488049#msg1488049
There was no reply/acknowledgment to your post in this thread.
Is Avast aware?
-
The bankmode bug isn't fixed..!!
https://forum.avast.com/index.php?topic=223975.msg1488049#msg1488049
There was no reply/acknowledgment to your post in this thread.
Is Avast aware?
I also posted it on Slack now, let's see...
-
The bankmode bug isn't fixed..!!
https://forum.avast.com/index.php?topic=223975.msg1488049#msg1488049
There was no reply/acknowledgment to your post in this thread.
Is Avast aware?
I also posted it on Slack now, let's see...
I see that now. :)
-
"Final tuning" :D
-
"Final tuning" :D
Yep, should be out soon... 8)
-
Sometimes disappears (when pc turn on or restart) the Windows security center icon in system tray.
-
New year, New version :)
Thanks!
-
The bankmode bug isn't fixed..!!
https://forum.avast.com/index.php?topic=223975.msg1488049#msg1488049
There was no reply/acknowledgment to your post in this thread.
Is Avast aware?
I also posted it on Slack now, let's see...
I see that now. :)
The problem has been identified and will be fixed soon. Thanks for reporting to Slack because it helped a lot.
-
Updating is working fine now here.
-
I reinstalled Avast for my Win10 machine, and I got white, blank AvastUI.
I did repair and reboot, now it works as it should.
BTW, it seems resetting settings does NOT reset exclusions to default. Is it intentional, or a bug?
-
The bankmode bug isn't fixed..!!
https://forum.avast.com/index.php?topic=223975.msg1488049#msg1488049
There was no reply/acknowledgment to your post in this thread.
Is Avast aware?
I also posted it on Slack now, let's see...
I see that now. :)
The problem has been identified and will be fixed soon. Thanks for reporting to Slack because it helped a lot.
Thanks for the update ondrejz. :)
-
The bankmode bug isn't fixed..!!
https://forum.avast.com/index.php?topic=223975.msg1488049#msg1488049
There was no reply/acknowledgment to your post in this thread.
Is Avast aware?
I also posted it on Slack now, let's see...
I see that now. :)
The problem has been identified and will be fixed soon. Thanks for reporting to Slack because it helped a lot.
You're welcome.
-
The bank mode still is not working. When is it expected to be repaired?
-
The bank mode still is not working. When is it expected to be repaired?
....Soon :)
-
In my case the bankmode is working again, I just had to re-activate the extenxion (which is deactivated, without knowing why, in the update)
A greeting
-
In my case the bankmode is working again, I just had to re-activate the extenxion (which is deactivated, without knowing why, in the update)
A greeting
Confirmed. Unfortunately, it's off again after restarting ASB.
-
The bank mode still is not working. When is it expected to be repaired?
The Bank Mode isn't working in the stable version, either ... :(
-
The bank mode still is not working. When is it expected to be repaired?
The Bank Mode isn't working in the stable version, either ... :(
You can always use the following till the fix is made:
(https://screencast-o-matic.com/screenshots/u/Lh/1546939423675-85096.png)
-
Thank you bob3160 :)
It never even dawned on me that right clicking would work. I just assumed Bank Mode was not working.
That is what I get for assuming not checking.
-
Confirmed. Unfortunately, it's off again after restarting ASB.
Right, you're absolutely right. Until I closed ASB, I did not realize that detail ;)
-
Hi, I have done as suggested here but my bank mode is still not working. It worked fine until a couple of months ago. I can open the Bank mode but as soon as I try to log in to my internet banking I get the following message:
This site can’t be reached The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_RESET
-
Interesting as I've had no problems with this beta (with Bank Mode) entering via 'right' click the Avast taskbar Icon as Bob has shown. I've used that option from the get-go; never using the ASB (browser) option.
-
The bank mode still is not working. When is it expected to be repaired?
The Bank Mode isn't working in the stable version, either ... :(
You can always use the following till the fix is made:
(https://screencast-o-matic.com/screenshots/u/Lh/1546939423675-85096.png)
I've right clicked on every avast icon I can find and cannot get this screen.
-
It's the icon in the system tray.
Make sure it's not one of the hidden ones.)
-
This version doesnt have support for TLS 1.3 either. I have to disable HTTPS for browsing.
Seeing this everyday in Firefox
https://support.mozilla.org/en-US/kb/secure-connection-failed-error-message#w_avast-and-avg-security-products
-
Avast supports TLS 1.3 since V18.6, see: https://forum.avast.com/index.php?topic=183543.0
-
Mozilla says that in their KB and as workaround works well. If I dont disable the HTTPS scanning, I cant browse some pages in the last FF.
-
Well, I can't confirm/reproduce it here with FF.
-
I'm not experiencing any issues with FF 64.0.2 and latest beta
-
I'm not experiencing any issues with FF 64.0.2 and latest beta
I don't know why there any new posts in this beta topic, considering this beta has been released as a regular update ?
-
I'm not experiencing any issues with FF 64.0.2 and latest beta
I don't know why there any new posts in this beta topic, considering this beta has been released as a regular update ?
Since there aren't any new betas, If you're on the beta version, where else would you post ???
-
I'm not experiencing any issues with FF 64.0.2 and latest beta
I don't know why there any new posts in this beta topic, considering this beta has been released as a regular update ?
Since there aren't any new betas, If you're on the beta version, where else would you post ???
Why would they still be on the beta when the regular program update has been released. As we keep saying in other topics if you haven't got the latest version update and see if it has been resolved.
Avast certainly aren't going to make any changes in the old beta version when it is released to production.
Which gets me back on to favourite hobby horse, I hate the practice of retaining the beta program version number when it is released to the regular update channel. It just causes confusion, how does one tell what they have when the version numbers are the same.
EDIT: Typo.
-
1. Why would they still be on the beta when the regular program update has been released. As we keep saying in other topics if you haven't got the latest version update and see if it has been resolved.
2. Avast certainly aren't going to make any changed in the old beta version when it is released to production.
3. Which gets me back on to favourite hobby horse, I hate the practice of retaining the beta program version number when it is released to the regular update channel. It just causes confusion, how does one tell what they have when the version numbers are the same.
Hi Dave,
1. Some of us (beta testers) always stay on beta-channel.
2. I may correct you, BC differs from SC and gets updated more often.
3. Totally agree with that, a differentiation would be helpful.
-
<snip quote>
Hi Dave,
1. Some of us (beta testers) always stay on beta-channel.
2. I may correct you, BC differs from SC and gets updated more often.
3. Totally agree with that, a differentiation would be helpful.
1. Yes, that was me until I did a clean reinstall to remain on the regular update channel. Unless you were on the Alpha Channel (usually in house testing) any updates going on to the Beta Channel would surely result in a NEW topic announcing the new beta as has been the practice in the past (no secret beta versions ?).
2. Those beta testers on the Beta Channel would be switched to the latest beta possibly earlier than the announcement in the forums. But they certainly wouldn't be using the 'OLD' beta topic if it has indeed been updated/superseded, it wouldn't (or shouldn't) have the same version number as the OLD beta.
3. The same version number has been going on for some time now, but it never used to be like this the regular release had a very small change in the last part of the version number. End of confusion.
-
The only way to get off the Beta Channel, is to do a clean install of the regular version.
-
The only way to get off the Beta Channel, is to do a clean install of the regular version.
Which is what I did, Reply #37 (above your post) point 1.
-
Well, I can't confirm/reproduce it here with FF.
Test with this page as example
https://www.fayerwayer.com/
-
OK, just tested it, the page works for me.
-
FF 65, with another page, I have this error
: SSL_ERROR_NO_CYPHER_OVERLAP
This is the page
https://www.cocinerosargentinos.com/recetas/Guisos/1715-Risotto-de-pollo.html
-
If I dont disable the HTTPS scanning, I cant browse some pages in the last FF.
If you want to keep HTTTPS scanning enabled, have you tried importing Avast's certificate? Instructions at: https://support.avast.com/en-eu/article/Troubleshoot-invalid-email-certificate (https://support.avast.com/en-eu/article/Troubleshoot-invalid-email-certificate)
-
Only have worked with one of the sites. I have to uninstall the default root Avast certificate.
https://www.fayerwayer.com/ still dont work with the scanning enabled.