Impossible to execute Autochk on disc C: - error (766f6c756d652e63 3f1)

[xobal]

Since the latest version of Avast 19.3.2369 it is impossible to execute Autochk on disc C: - refused access to the disk, error (766f6c756d652e63 3f1). With previous version 19.2.2364 Autochk was OK. Avast had similar problem four years ago (at that time the problem was caused by Secure Virtual Machines (NG)).

[Alikhan]

Have you tried a clean installation of Avast?

There hasn't been many reports on this and I can get it escalated assuming the problem is still there after a clean install.

[xobal]

No, I haven't tried a clean installation of Avast. I tried only a repair of Avast.  However, the problem persists and I have the same problem on two PCs. And you have tried to perform chkdsk of C: with the newest version of Avast 19.3.2369? Everything is OK?

[steens]

Confirmed as per my post here: https://forum.avast.com/index.php?topic=225874.msg1498300#msg1498300

[Computer Solutions]

I can confirm this and yes even with a clean install of Avast. Besides the two machines I use that have the same problem with chkdsk with Avast, I also ask others and they also have the same results. Once the user uninstalls Avast, Auto chkdsk will work again as it should.

[xobal]

The problem evidently exists. I don't believe that other users of the latest version of Avast (19.3.2369) have no problem with chkdsk. They just don't know about it yet.

[Alikhan]

This bug has been reported and confirmed by the Avast team.

It is caused because of IDP and is reported under AV-19648.

I don't have an ETA yet but when I get one, I'll update the thread.

[mchain]

IDP = Behavior Shield?

[Asyn]

IDP = Behavior Shield?

Yep.

[COBKA]

I have this problem on each of my systems and suspected it was AV related after searching for the error message. Uninstalled Avast and the problem went away. Is there a short term work around and if Behaviour Shield is implicated would disabling this work?

[xobal]

Hmmm, more than a week and the problem still persists. 

[DavidR]

I have this problem on each of my systems and suspected it was AV related after searching for the error message. Uninstalled Avast and the problem went away. Is there a short term work around and if Behaviour Shield is implicated would disabling this work?

Disabling the Behaviour Shield temporarily before running the Autochk function on disc C: would probably work.  However, if this is a much more frequent exercise running autochk it would be a bit of a pain.  I would say would be better than uninstalling the Behaviour Shield component, which would be better than uninstalling avast.

Hopefully this would be a short term issue before a fix is found and tested to see it doesn't impact anything else..

[Alikhan]

The fix is scheduled for next version (19.4) but Avast will also consider update for 19.3.

According to an Avast team member, they think the behaviour shield component must be uninstalled and a restart required. I haven't been able to get a response from someone within the Behaviour Shield team for a precise answer.

[DavidR]

Thanks for the clarification Alikhan.

[Cliff_g]

+1 on those affected.