No, there was no OS update involved in my case.
- One more with the problem.
baumgrenze
I also have the problem on my 2 paid for installations and my son has the issue on his version of Avast Free (all running Windows 7)
I also found the issue has been seen in the comments of a youtube video about fixing the CHKDSK error 766f6c756d652e63 3f1 issue.
You can get round it by temporarily entering the passive mode but it’s a kludge
PLEASE can you issue a fix
I should also say it is nigh on impossible to see what letters you are supposed to put in to prove you are not a bot, most annoying!
Captcha is only needed for your first 3 posts. (Spam protection)
Doesn’t make it any easier to read them
Unfortunately, it’s necessary, else spam bots could read it as well.
Another with problem.
It is a bit of a bummer if you actually had a disk problem and needed to do a CHKDSK.
It is also a bit much that it has had no immediate fix.
I have lost two whole days of work finding that it is a known problem.
Avast are quick enough to notify people about new stuff, but extremely bad at revealing problems.
It’s terribly annoying on my son’s installation, which is running Avast Free. It seems if I disable the setting in Avast I then can’t stop the pc running a full Chkdsk every time it boots, the ‘press any key’ doesn’t stop it. So I have to turn the pc off and press F8 on the restart to re-enable the setting in Avast before I can get the pc to run at all.
It’s incredibly annoying. Where’s the fix Avast?
You could try the latest beta: https://forum.avast.com/index.php?board=15
No thanks, don’t want to be an Avast guinea pig
NP, you need to wait for the release version then.
Then I guess it is a waiting game until the fix in version 19.4 (as mentioned by Alikhan in Reply #12) is released and not in beta.
We really shouldn’t have to though.
We pay for this stuff to work and the operating system is not new
Unfortunately the process of bug resolution, identifying/rectifying/testing/beta-testing and final release (can be a lengthy one) as either part of the next program update or a fix delivered via a VPS update.
Then why not just roll back to the previous version until Avast have it fixed?
Avast have caused the issue, they should take responsibility for it
Roll back for whom (how would Avast know who to roll back), not everyone is impacted by this bug, those who aren’t impacted by the bug wouldn’t want to roll back.
Then there are the potential issues with any rollback, what change caused this problem for those impacted. If it were security related then you would be exposing everyone to that vulnerability. Or that vulnerability and other changes (bug fixes possibly) in the 19.3.2369 would also have to be re applied, or should they wait also. Or wait fro them to be applied to 19.4 or possibly even later 19.5.
This certainly isn’t something that can be rushed.
Everybody is affected. Some just don’t know it yet
I think the bug fixing process is more like a monthly version, no more and no less, it’s why the version post-its now clearly mention the month (Mar 2019)
I’m sure that for a problem like this one, avast could release an update much faster but will wait until mid-April no matter what.
Personally, I don’t like this type of policy, especially since it is a security tool 
Which to a certain degree shows the urgency required.
That however, doesn’t get round any potential issues related to rolling back I mentioned in my earlier post.
Whilst like Chris… I don’t particularly like this bug resolution process.
I’m playing devils advocate on which might be more problematic, a quick resolution of the bug or the potential problems of a version roll back for everyone and possibly losing any security updates that might have been in the 19.3.2369 program version.
Not sure if you work for Avast, if you don’t I apologise in advance.
If you do what a glib reply!
Not all of us are computer nerds and nearly all of us didn’t know what was causing our issue, we just let Avast do it’s thing and IT created the problem, all by itself.
It took me over an hour to track down that it was Avast software I paid for that was causing an issue on my pc.
So Avast not really bothering to help doesn’t bode well for whether I will continue to use Avast when my subscription expires.