Avast stops file copies and new MS patches for XP against Spectre and Meltdown

[DavidR]

 
Asyn - thanks for hoping, but how do we contact Avast? 

You can try using the avast tray icon > About Avast > Submit Feedback.

[Asyn]

Asyn - thanks for hoping, but how do we contact Avast?

Paid products: https://support.avast.com/contact
Avast Free: You can submit a bug report in "About Avast".

[REDACTED]

Same issue as others... files (handles) get locked when copying/moving. It doesn't effect all files, but most. It definately seems to effect them if they have been downloaded off the internet or untrusted network. Disabling the shields (file shield, web shield,...) doesn't fix it. Only uninstalling avast fixes the problem.

OS: Win XP SP3
Avast: 17.9.2322 build 17.9.3761.0

[chris...]

It has been fixed already via uUpdate. (https://forum.avast.com/index.php?msg=1439072)

Sorry but what I'm seeing in this msg reply (   Alikhan) is
The fix for Win XP will be out soon with the next micro update.
or did you make a mistake with an other post/issue?
Asyn saying that it was solved by referring to the Alikhan bond was visibly deceived

So as usual clear as mud.

still clear with always the same subject, Alikhan last message today?
https://forum.avast.com/index.php?topic=212278.msg1440565#msg1440565
The micro update should hopefully go out today. The fix is currently still in progress.
I'm not sure that yesterday you (or Asyn) could say that it was solved 

I also note that you still have a little doubt 

Well my issue with a data backup batch file on my XP System is working again.  I have no idea if that was down to my reconstruction of it (essentially the same set of commands) or Avast fixing the issue in XP.

@glnz ,  garibaldi22 and others
This may not be the moment to rush to contact avast, wait a while for the (right) fix

[Alikhan]

Chris,

Avast did state the fix would be released with the next microupdate as I posted earlier, however, the fix was delayed due  to issues and another fix is still in progress but close to release.

When it is released, I'll post an update on this topic.

[chris...]

Thank you for these clarifications that I assumed
We must not go faster than music, as we say in France 

[glnz]

 
Hey - Avast - this problem of blocking the copy function is also making me delay other updates to XP (which I can do through the POS hack).

So, Avast is delaying security updates in general.  This violates Avast's core purpose.

When will you issue the "micro" fix?

Thanks.
 

[glnz]

 
There is STILL no new "micro" update from Avast to fix this problem.  And I hesitate to install other updates (from yesterday's "Update Tuesday") because the Avast-file-copy-block might hurt those installations as well.

Avast - when will this be fixed?
 

[Alikhan]

The micro-update from Avast to correct the new file-copy problem was released 3 hours ago. The fix will automatically roll out within the next 12 hours but you can do it manually now.

Running AVEmUpdate.exe as admin from Avast directory and rebooting or you can execute: schtasks.exe /Run /TN "Avast Emergency Update"

[bob3160]

The micro-update from Avast to correct the new file-copy problem was released 3 hours ago. The fix will automatically roll out within the next 12 hours but you can do it manually now.

Running AVEmUpdate.exe as admin from Avast directory and rebooting or you can execute: schtasks.exe /Run /TN "Avast Emergency Update"

https://www.youtube.com/watch?v=S4o-5GjNujw

[DavidR]

 
There is STILL no new "micro" update from Avast to fix this problem.  And I hesitate to install other updates (from yesterday's "Update Tuesday") because the Avast-file-copy-block might hurt those installations as well.

Avast - when will this be fixed?
 

I rather think it will be a very long wait, given that MS no longer supports XP SP3, there is no fix on WU for XP as far as I'm aware. That may be different if you have the XP POS hack to continue updates, but if you had I don't know if avast would be creating the compatibility registry key.

There is no HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\QualityCompat key in my XP registry.  There is on my win10 registry and both systems are running avast free 17.9.2322.

I think that the dual question of the topic title isn't helping as far as clarity goes they are so completely different.

[chris...]

 
but if you had I don't know if avast would be creating the compatibility registry key.

I dreamed about it, avast did it 

[=Snake=]

Yes, I have the copying problem now, apparently caused by Avast.

I had the problem, too on my main machine and went back to a earlier version of Avast Free (see my signature) and after that, I don't have any problem.

=Snake=

[glnz]

 
DavidR - I do have the registry key on my XP machine.  But I am waiting for Avast's micro-fix on the copy-file problem before I try to run ANY recent updates.

Agree that I started with the Meltdown and Spectre update problem, but it quickly became clear that such problem derives from the copy-file issue caused by Avast, which is bad in itself.

They go together like peanut butter and jelly, when the bread falls jelly side down.
 

[REDACTED]

Hello

A key question here is: if one CPU is not affected by Meltdown or Specter and no MS patches are installed, will Avast find it out and update the antivirus engine accordingly?

Regards