Well, no idea then. According to the devs it has been released and I can confirm it.
Mine is ver. 19.6.2383 - build 19.6.4546.511
Just tried to update. Still the same version from a month ago. June 25th 2019.
Does the release cycle differ between premium and free?
Nope, I’m on beta channel.
I’m not. Regular channel (I assume). Free version. Maybe it is still in beta then.
According to the devs, they also pushed it to stable channel.
Yes, I initially checked my Regular channel version installation which is .390
I have subsequently checked my Beta Channel installation and it is .394
So there’s the difference 
Edit: I will be watching for the update on Regular installation
Yeah I’m not keen on beta-testing with an AV. I’ll wait.
@Asyn. Ah you must have got priority treatment
Like groundhog day here. Update>Reboot and again 390.
Edit: Sorry guys, I had missed page 2 of the thread, but my comment above is still true status of latest version available here.
Still .390 ¯_(ツ)_/¯
Same here. I’ve reported it.
Dev-Info: If you didn’t get the UI update yet, there’s a workaround. Open and edit avast5.ini
[AAVM]
ArPotEnabled=0
What does that do?
Still at .390 btw.
It disables Rootkit detection.
OK.
Well, when I try to modify that file Windows tells me it is in use and I can’t save. Even if I disable Self-Defense. Now, I could edit the file from a Live-CD or something but I shouldn’t have to go through all that trouble just because an update won’t show up on the ‘stable’ channel. If it was pushed to stable it should appear, right?
Edit: OK I did it the hard way. Rootkit-detection is now disabled. Also Exploit-detection. Now I can test. However I now have a notification about the disabled Rootkit-detection that I can’t dismiss. Slightly annoying but OK.
Also: why is Avast still popping up with a warning about editing Avast-files when Self-Defense has been disabled?
Post a screenshot.
I can’t now. It was an alert about editing avast5.ini, by Avast, even though Self-Defense was disabled.
Edit: Avast has now luckily figured out to offer me to ignore the notification about the disabled Rootkit-Detection. It didn’t before. So that blue dot is gone. That is something.
Sounds good.
I’m not 100% sure what is going on.
I had disabled Self-Defense. Because i assumed I had to to edit Avast files. I hadn’t re-enabled it, but also no notification about it being disabled was visible in the Avast status screen. So that is already weird. I tried to edit the file and it said it was in use and I couldn’t save. I tried another method to edit the file and now I could save, but I got the alert popup about if I was sure? Now, still I hadn’t re-enabled Self-Defense. But Avast must’ve re-enabled it itself because when I went to turn it back on I found it on already. So again: weird behavior. Especially because I just disabled Self-Defense again (to test) and now it stays off. So why didn’t it earlier? I just don’t know.
I hope the update will show up soon so I can use the UI for these changes.
If you’re in a hurry, you could install the latest beta: https://forum.avast.com/index.php?board=15
Not only do you have to disable the avast self-defence module, but you have to use notepad.exe the windows text editor (that is the only one allowed) to be able to edit the avast5.ini file.
I don’t know if you were using notepad for the edit.