Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: xobal on March 14, 2019, 06:12:52 PM
-
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)).
-
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.
-
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?
-
Confirmed as per my post here: https://forum.avast.com/index.php?topic=225874.msg1498300#msg1498300
-
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.
-
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.
-
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.
-
IDP = Behavior Shield?
-
IDP = Behavior Shield?
Yep.
-
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?
-
Hmmm, more than a week and the problem still persists. :(
-
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..
-
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.
-
Thanks for the clarification Alikhan.
-
+1 on those affected.
-
"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
-
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.
-
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.)
-
Last two posters - have you recently done any MS updates? Interesting the problem appears with AVG as well
-
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.
-
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.
-
+ 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!
-
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
-
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.
-
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
-
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
-
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.
-
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
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.
-
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
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
-
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
-
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.
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 :(
-
Everybody is affected. Some just don't know it yet
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.
-
Everybody is affected. Some just don't know it yet
Which to a certain degree shows the urgency required.
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.
-
I don't work for avast, I'm a user just like yourself.
I did some time as a systems analyst/programmer so I have an idea of what goes on in the background when a bug is reported. Finding exactly what caused it has to be found, how to resolve it and how this fix/resolution might impact on other functions within the program. Then it has to be tested before release, usually through QA, Alpha testing and the Beta testing channel before being released.
As has been mentioned earlier in the topic this is meant to be resolved in the 19.4 release and there is a beta testing session ongoing and it is on its 2nd beta update 19.4.2371.
-
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.
Yes, don't forget that some people had problems with the old version.
For my part, I could no longer use my VPN with the avast firewall.
-
The new 19.4.2374 (April 2019) regular program update has now been released https://forum.avast.com/index.php?topic=226462.0 (https://forum.avast.com/index.php?topic=226462.0), time to check and see if this issue has been resolved.
-
19.4.2375 seems to have fixed the autochk/chkdsk on the system drive for me...however a new problem came up. See
https://forum.avast.com/index.php?topic=226462.msg1501311#msg1501311
-
19.4.2375 seems to have fixed the autochk/chkdsk on the system drive for me...however a new problem came up. See
https://forum.avast.com/index.php?topic=226462.msg1501311#msg1501311
Thanks for the confirmation.
I have answered your post, I just wonder if the certificate needs reimporting again.
-
I can report that the problem was solved when I updated to Avast to 19.4.2374 to fix my 'cannot run CHKDSK problem.
https://forum.avast.com/index.php?topic=226462.0 (https://forum.avast.com/index.php?topic=226462.0)
NEW Version: 19.4.2374 (April 2019) « on: April 09, 2019, 03:21:46 PM »Checking file system on C:
Thanks to all who participated in getting this fixed and tested in record time.
baumgrenze
+ One more with the problem.
baumgrenze
-
Thanks for confirmation!
(as well as reporting the issue)
Pavel