I understand the importance of testing beta’s ‘in the field’ but is it not a little bit premature to recommend this beta version for a problem which should be easily solved by either switching the shields off or, failing that, doing a ‘repair’ on the OP’s current version of Avast? - Reading the ‘Beta’ forum the latest one still has its fair share of problems.
I must be missing something as the OP’s problem refers to Windows update, not the Avast ones. Hasn’t the beta introduced some new problems? Perhaps I’m wrong.
There isn’t any reason to disable avast! regardless of the version being used.
It would certainly be helpful to see a screenshot of the actual error code generated
by Microsoft when the Windows Update fails.
I had 8 this morning it may be different for others depending on OS and additional MS programs running.
Downloading the updates went OK, when restarting to finish them, it gets to 15% and reports failed, rolls back to the previous set up. Just tried on my 32bit laptop and that went OK, maybe just a 64 bit problem?
Here’s a screen shot from this morning.
It was suggested to only do a few at a time, not all 19 at once. Tried Microsoft Fixit 50123.msi as that was MS fix for the first failure; didn’t work.
Haven’t tried the beta yet, hoping for someone else with the same problem to post here.