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.)
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. >:(
What's new: We did not finished any new feature in adequate BETA quality.LOL Funny to hear from Avast ;D ;D ::)
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.
Thank you NON and Eddy for reporting this problem. We did not experience the same issue, however my colleagues will look at it.
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.
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. 
- 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.
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).
Thanks for the dump. It is already reported to developers who are working on a fix. It will be fixed in next beta.
When it’s ready (as usual).
I will do that Petr, for both AVG and AVAST as I test it in different platforms.
It’s working now, thanks for the fix
My system just rebooted ???
Only thing I’ve been able to see was a VPS update just before the re-boot ???
Interesting, I didn’t get any VPS updates for the beta since the 18th October.