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

[Cliff_g]

"Hmmmm, tricky..." 

It appears (to me) not to be 19.3.2369 per se.  It may be a dual problem with 19.3.2369 but with a Microsoft update influencing matters?

As I was still having too many problems, even with Avast uninstalled (autochk/chkdsk worked but the machine was still running badly), I put my backup on and was surprised to find I had 19.3.2369 before the backup.  I thought I had (a) backed up, (b) updated MS updates (c) updated Avast in that order, but now it appears the other way round?  My memory of the order in which I did things is at fault. 

Checking logs, I updated Avast first, late Friday night, then set a backup going overnight.  Then I did a bunch of MS updates on Saturday, see .png attached - note I excluded the two Mar 2019 updates.

The problems started after that and I initially suspected Avast due to the Autochk issue, as it seemed those MS updates wouldn't be messing with the disc at a low level.  I removed Avast and Autochk/chkdsk worked.  But then the machine was still very slow so I put the backup on.

So I think 19.3.2369 is part of the problem, but it may need one of the MS updates to reveal it.  I'm now on my post-19.3.2369 and pre-MS-updates version and the machine is fine (touches wood)

Thanks

W7 Pro 64 bit

[harry.stewart999]

I'm having exactly the same problem with both Avast and AVG starting with the latest release.  Uninstall the antivirus and chkdsk /f works, install the antivirus and chkdsk /f doesn't work.

[pr_av_on]

Same problem with Autochk/chkdsk... I my case I found this problem in a very problematic way. My system drive (C:) filesystem was marked dirty due to a power fail, after which it was not possible to restart normally because chkdsk could not run and I couldn't reach Windows to uninstall Avast.
Terrible experience, ended up loosing a lot of time to circumvent this startup situation,  uninstall Avast and finally be able to run chkdsk.

This needs to be fixed and I'm a bit surprised there still isn't at least a patch or clear instructions from Avast how to resolve this situation.

(I did report the bug through Avast interface before anyone asks.)

[Cliff_g]

Last two posters - have you recently done any MS updates?  Interesting the problem appears with AVG as well

[DavidR]

Last two posters - have you recently done any MS updates?  Interesting the problem appears with AVG as well

Considering that AVG is now part of Avast Software and some of the underlying functionality will be the same.

If that has been triggered by MS updates in win7 I wouldn't know.

But as Alikhan mentioned:

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

Since Avast 19.4 is in beta testing, hopefully that won't be too long before release.

[pr_av_on]

Last two posters - have you recently done any MS updates?  Interesting the problem appears with AVG as well

No, there was no OS update involved in my case.

[baumgrenze]

+ One more with the problem.

baumgrenze

[dhphoto]

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!

[Asyn]

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)

[dhphoto]

Doesn't make it any easier to read them

[Asyn]

Doesn't make it any easier to read them

Unfortunately, it's necessary, else spam bots could read it as well.

[Burn_IT]

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.

[dhphoto]

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?

[Asyn]

You could try the latest beta: https://forum.avast.com/index.php?board=15

[dhphoto]

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