New Beta version 17.8.2315

DavidR · 2017-10-14T22:02:57.000Z

Asyn post:17:

DavidR post:16:

Plus the lack of information on previous bugs squashed or not (Known Issues should include these), how else are we to know what to test (what has been fixed and what hasn’t) !

According to Petr (Reply #7), this will change in the next beta. Let’s see…

It isn’t just that, recently betas have sailed through Q&A and Alpha testing with lots of issues. That is bloody frustrating, same things again and again being reported in the forums, yet unresolved and new functions being added.

Patrick2 · 2017-10-15T00:13:19.000Z

I’d be More Comfortable testing betas on my most used Desktop if I knew more of what is fixed and what isn’t fixed, if I do any testing lately it’s on my less used that I don’t care about Much little Windows 7 Desktop, as if it took a hard crash wouldn’t really bother me, then again lately I sometimes skip beta testing as have no idea what is fixed

I still use Avast since i feel it offers the right amount of protection, doesn’t slow down performance, i started back in 2006 using Avast after a bad time with Windows Live Care antivirus missed a bad boot sector virus that idiot me at the time opened, (was testing that at the time for Microsoft) ever since then haven’t trusted Defender, and have always stuck to Avast on each PC and operating system

Just want the serious bugs with Avast caught, fixed, and then a nice stable version released, and i know the more testers you have with different system configurations is for the better probably, but also don’t got the time or patience to test as much as i used to anymore, i do test at times off and on still, but with no info what this version is fixing, i sorta feel like passing this time

NON · 2017-10-15T06:03:17.000Z

Thanks for the new beta

NON · 2017-10-15T06:38:49.000Z

I can’t sign-in to Avast Account via AvastUI… it just closes/crashes.

Installed over stable build (17.7.2314). Avast Premier. Win7 SP1 64bit.

bob3160 · 2017-10-15T12:33:28.000Z

NON post:21:

I can’t sign-in to Avast Account via AvastUI… it just closes/crashes.

Installed over stable build (17.7.2314). Avast Premier. Win7 SP1 64bit.

No problems here getting to the my.avast.com account from the Avast UI.
( I’m on the latest beta.)

Eddy · 2017-10-15T12:52:26.000Z

Same problem as NON.
Windows 10.

Open the GUI.
Click on “sign in”
Had to be really quick to capture the attached screemshot
Can’t even start to type anything in the boxes before the GUI closes

Something like this should have come up in Alpha testing already.
A very clear sign to me that avast isn’t doing anything close to decent Alpha (internal) testing at all. >:(

system · 2017-10-15T14:44:53.000Z

What's new: We did not finished any new feature in adequate BETA quality.

LOL Funny to hear from Avast ;D ;D ::)

FranceBB1 · 2017-10-15T21:58:05.000Z

I’ve been facing a “nasty” bug.
As beta tester, Avast Premier upgraded automatically from the former beta to the latest one.
Unfortunately, though, it broke something.
It seems that auto-upgrade corrupted Avast and, although I was able to log in my Desktop, I didn’t have any internet connection.
LAN was connected, but it was showing no ip, no mask, nothing, just a blank screen.
When I logged in safe mode, internet was working fine 'cause Avast wasn’t loaded.
I tried to repair Avast using another installer and it didn’t work.
Then, I tried to uninstall Avast from the control panel and it froze, so I had to use AvastClear.
When I installed the latest beta using the offline installer from scratch, I worked flawlessly.
This is a bug that happens randomly.
I’ve been facing it few months ago with other builds.
It seems that something doesn’t quite work as it should during the auto-upgrade process and it sometimes corrupts the installation.
An internet connection error, perhaps? Incomplete download? Does Avast checks the integrity of the downloaded version with something like MD5 Checksum?
I’m just asking, out of curiosity.
It’s not a big deal, it’s a beta, we are “advanced” users, we know how to handle simple tasks, but it would be better to fix this “bug”.

Intel i7 6700HQ 2.60 GHz 4c/8th
16 GB of RAM DDR4 (8x2)
NVIDIA Geforce GTX 950M, 4GB GDDR5
Seagate SSHD 1TB connected through Sata III, AHCI.

Windows XP SP3 Professional x86 32bit
Microsoft Extended Support renewed annually.

petr.kolacek · 2017-10-16T05:50:21.000Z

NON post:21:

I can’t sign-in to Avast Account via AvastUI… it just closes/crashes.

Installed over stable build (17.7.2314). Avast Premier. Win7 SP1 64bit.

Thank you NON and Eddy for reporting this problem. We did not experience the same issue, however my colleagues will look at it.

petr.kolacek · 2017-10-16T06:00:29.000Z

Hi Francesco Bucciantini, thank you for your feedback. We did not experienced any similar issue with networking during or after update from previous versions despite we do such a test. As you resolved the problem by reinstall the program, there will not be any information left (in logs) that would help us debugging it. Could you please next time enable debug logging (in Settings → Maintenance - Enable debug logging), try to induce the issue again and send the logs (%ProgramData%\Avast Software\Avast\log and %ProgramData%\AVAST Software\Persistent Data\Avast\Logs) to us (e.g. to ftp.avast.com).

Regarding to your question whether Avast checks the downloaded material for integrity - yes, it does, so if the file is “corrupted” it will not be used.

TheLightgg · 2017-10-16T07:19:03.000Z

Big thanks you to all the development team for this new version beta!

I have two questions:

The following bugs in this post could be found and corrected in this new version ?
https://forum.avast.com/index.php?topic=209420.0
(Avast 17.7.2314 passive mode and anti rootkit problem)
When the “release” of this new version beta will be available ?

Again thanks to all team.

Asyn · 2017-10-16T07:24:49.000Z

TheLightgg post:28:

The following bugs in this post could be found and corrected in this new version ?
https://forum.avast.com/index.php?topic=209420.0 (Avast 17.7.2314 passive mode and anti rootkit problem)

When the release of this new version beta will be available ?

Should be fixed.
Not sure what you mean, the beta is available already.

TheLightgg · 2017-10-16T08:02:05.000Z

Asyn post:29:

TheLightgg post:28:

The following bugs in this post could be found and corrected in this new version ?
https://forum.avast.com/index.php?topic=209420.0 (Avast 17.7.2314 passive mode and anti rootkit problem)

When the release of this new version beta will be available ?

Should be fixed.

Not sure what you mean, the beta is available already.

Thx for the reply.

Sorry I was talking about the “release” version.

NON · 2017-10-16T10:15:04.000Z

petr.kolacek post:26:

NON post:21:

I can’t sign-in to Avast Account via AvastUI… it just closes/crashes.

Installed over stable build (17.7.2314). Avast Premier. Win7 SP1 64bit.

Thank you NON and Eddy for reporting this problem. We did not experience the same issue, however my colleagues will look at it.

Hello petr.kolacek, thanks for your reply. I can easily reproduce it here and every time it creates .mdmp file… do you need them?

KarelŠťavík · 2017-10-16T12:27:58.000Z

NON post:31:

petr.kolacek post:26:

NON post:21:

I can’t sign-in to Avast Account via AvastUI… it just closes/crashes.

Installed over stable build (17.7.2314). Avast Premier. Win7 SP1 64bit.

Thank you NON and Eddy for reporting this problem. We did not experience the same issue, however my colleagues will look at it.

Hello petr.kolacek, thanks for your reply. I can easily reproduce it here and every time it creates .mdmp file… do you need them?

Yes please

It would be the best if you:

enable debug logging (open Settings - General - Maintenance)
reproduce the issue
upload all logs and dumps in ZIP archive to our ftp
how to about ftp - https://www.avast.com/en-us/faq.php?article=AVKB160#idt_02
let us know the name of the archive once uploaded

Thanks for help!

Karel

NON · 2017-10-16T12:49:51.000Z

karel.stavik post:32:

NON post:31:

(snip)
Hello petr.kolacek, thanks for your reply. I can easily reproduce it here and every time it creates .mdmp file… do you need them?

Yes please

It would be the best if you:

enable debug logging (open Settings - General - Maintenance)

reproduce the issue

upload all logs and dumps in ZIP archive to our ftp

how to about ftp - https://www.avast.com/en-us/faq.php?article=AVKB160#idt_02

let us know the name of the archive once uploaded

Thanks for help!

Karel

I always have my machine debug logging enabled ;D

File was uploaded. Filename: NON_log_2017_10_16.7z

Please be noted that there are dumps which are not related to this (can’t sign-in) issue but to another one (Smart Scan issue; already reported in Slack channel).

KarelŠťavík · 2017-10-16T13:50:37.000Z

NON post:33:

karel.stavik post:32:

NON post:31:

(snip)
I always have my machine debug logging enabled ;D

File was uploaded. Filename: NON_log_2017_10_16.7z

Please be noted that there are dumps which are not related to this (can’t sign-in) issue but to another one (Smart Scan issue; already reported in Slack channel).

Thanks for the dump. It is already reported to developers who are working on a fix. It will be fixed in next beta.

Asyn · 2017-10-17T05:50:36.000Z

TheLightgg post:30:

Sorry I was talking about the “release” version.

When it’s ready (as usual).

system · 2017-10-17T15:13:03.000Z

petr.kolacek post:12:

J.Bryl post:10:

The issue with 17.7 with the passive mode is still not fixed.
Especially if you have an old version of AVG though you removed it completely it will still switch to passive mode when you install the new version whether the 17.7 or this new beta 17.8. It will say that the conflicting AV is the old version.

Hi J.Bryl there are several issues with passive mode and we have a plan to test it further - the scenario you described will be retested too. However, if you were not already asked to do so, could you please enable debug loggin (Settings → Maintenance → Enable debug logging), restart the machine and send us all logs from ProgramData\Avast Software\Avast\log*.log (or ProgramData\AVG\Antivirus\log*.log if you have AVG) in ZIP archive?

If you have troubles with uploading to ftp://ftp.avast.com/incoming or sending directly to me over email, please drop me a message (email or forum). Thank you for your feedback!

I will do that Petr, for both AVG and AVAST as I test it in different platforms.

NON · 2017-10-22T12:39:13.000Z

karel.stavik post:34:

Thanks for the dump. It is already reported to developers who are working on a fix. It will be fixed in next beta.

It’s working now, thanks for the fix

Announcements