Does avast can cause Windows Update error?

[artx]

[Windows 7 Home Premium / Avast Free Antivirus and Avast Security Browser]
My problem is similar to the topic posted yesterday by haverdad „Windows 7, Avast, and latest Windows Updates KB4493472, KB4493448, and KB4493435„
The problem with the Windows Update began on March 17: some of the updates failed (error 80070490). I tried many options, but without success. Among the others , I launched the System Update Readiness tool (KB947821). CheckSUR.log showed: Found 116 errors, Fixed 98 errors
  CSI Unexpected Failure Total count: 8
  CSI C Mark Deployment Missing Total count: 2
  CSI F Mark Bad Type Total count: 90
  Fixed: CSI F Mark Bad Type.  Total count: 90
  CSI F Mark Missing Total count: 8
  Fixed: CSI F Mark Missing.  Total count: 8
  CSI Missing Winning Component Key Total count: 8 

In many log’s lines was "avast", e.g.
((f)    CSI Missing Winning Component Key    0x00000000    x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_a45421ee27ef60f7       
(f)    CSI Unexpected Failure    0x00000005    14.0.27012.0    x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_a45421ee27ef60f7    Error deleting winners map value.)
I decided to uninstall AVAST (using avastclear.exe) and restart KB947821 tool. This time it fixed 16 errors, 2 remaining, with "avast" in the log as well. I also uninstalled Avast Secure Browser and I restarted KB947821 tool once again. There are still 2 errors:
(f)   CSI C Mark Deployment Missing   0x00000000   c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_0b20a8ff883c3a4a   x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c   
(f)   CSI C Mark Deployment Missing   0x00000000   c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_c373722873c01144   amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396   
Found 2 errors  CSI C Mark Deployment Missing Total count: 2
I don’t know if  AVAST is the reason of the Windows Update failure but the convergence of dates is interesting:
March 17, 11:52 - installing of 1st update -success
March 17, 11:59 - installing of 2nd update -success
March 17, 12:00 - installing of 3rd update -success
March 17, 12:09 - date of INFCACHE.1 file modification (c:\Windows\System32\DriveStore)
March 17, 13:07 - installing of 4th update -failure
Avast Support recommends to rename INFCACHE.1 file to INFCACHE.1.BAK during reinstalling Avast software (https://support.avast.com/pl-pl/article/Troubleshoot-Antivirus-components). 
Windows Update error still exist so I would like to fix it as soon as possible and reinstall AVAST, especially Avast Security Browser. Let me know if you could help me.
Regards,   

[schmidthouse]

Avast is aware and is working to resolve via 'hot fix' today. Hopefully this fix will also resolve your issue

[DavidR]

See https://forum.avast.com/index.php?topic=226534.msg1501852#msg1501852.

Anyway, we have just released an emergency update for Avast 19.3 and 19.4 which should detect the problem with these KB- packages. The problem was caused by a new Windows functionality in these KB packages which may sometimes lead to deadlock during Windows startup process.

[davexnet]

This is the problem with avast and other third party A/V in Windows 10:
they're always playing catch-up to Windows 10 changes and new features resulting in a broken
OS while the third party vendors fix their stuff
I made the choice not to use them and have stayed with WD.  Even after reverting back to Windows
8.1, for now, I've also stayed with WD

If you're going to do it, just know, this is not a rare event, it will often
break while the A/V has to create another "hot fix"

Just my 2 cents worth

[schmidthouse]

This is the problem with avast and other third party A/V in Windows 10:
they're always playing catch-up to Windows 10 changes and new features resulting in a broken
OS while the third party vendors fix their stuff
I made the choice not to use them and have stayed with WD.  Even after reverting back to Windows
8.1, for now, I've also stayed with WD

If you're going to do it, just know, this is not a rare event, it will often
break while the A/V has to create another "hot fix"

Just my 2 cents worth

I personally have never had an OS break via MS updates while running Avast since xp through W8-8.1 and W10
19 years....just lucky I guess.
Just saying

[artx]

I informed in my post that I uninstalled AVAST.
Do I understand correctly that I need to reinstall Avast to fix the problem with Windows Update?

[DavidR]

In theory if you haven't got avast installed then the windows update should in theory work, unless of course you have installed another AV that is also effected.

Installing avast again should also trigger the emergency update check, which had you not uninstalled avast you could have initiated manually, the link I gave in this topic (to PKs reply) also had another post from me Reply #7 of that topic https://forum.avast.com/index.php?topic=226534.msg1501856#msg1501856 on how to initiate it manually.

[rocksteady]

I only had problems with Microsoft Update and Avast years back on WinXPSP3. Never on later Windows versions 8,8.1,10. Also not on WinXP of late where Microsoft Update is still valid for Office etc. But that is another story.

[DavidR]

I only had problems with Microsoft Update and Avast years back on WinXPSP3. Never on later Windows versions 8,8.1,10. Also not on WinXP of late where Microsoft Update is still valid for Office etc. But that is another story.

If you read my reply #2 with PKs quote, this is a very recent issue, as MS changed something "a new Windows functionality in these KB packages" and that effected not just avast but some other AVs.  That is why there was an Emergency Update to cater for that. 

It should be unrelated to any prior MS updates not using this  "new Windows functionality."

[rocksteady]

If you read my reply #2 with PKs quote, this is a very recent issue, as MS changed something "a new Windows functionality in these KB packages" and that effected not just avast but some other AVs.  That is why there was an Emergency Update to cater for that. 

It should be unrelated to any prior MS updates not using this  "new Windows functionality."

@DavidR. Yes I did read #2. Also aware of Emergency Update. I was just trying to say that I have not encountered any problems with MS update and Avast on Win10 1809.

[artx]

After uninstalling AVAST, I installed MS Security Essential. I do not think this AV will block Windows updates.
I would like to remove all traces of AVAST https://forum.avast.com/index.php?topic=226664.0, which in my opinion may cause a Windows Update error. Any suggestions? I tried to run MicrosoftProgramm_Install_and_Uninstall.meta.diagcab https://support.microsoft.com/en-us/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed, to automatically repair issues, including corrupted registry keys, that block installing or removing programs. Unfortunately this tool asks to enter 38-character Product Code, e.g. {9EEE2575-B66F-43F7-A455-7D419335C87E}. Could someone give me the AVAST Product Code, or tell me where to find it?

[rocksteady]

You can dowload the Avast Uninstaller from the Avast website here:
https://support.avast.com/en-gb/article/Uninstall-Antivirus

[Cluster-Lizard2014]

Just want to confirm so far so good on a Windows 7 Pro 64bit PC that I'd been holding off installing this month's Windows updates because of the concern expressed not just here but in other places too:-

2019-04 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4493472)
+ the usual Malicious Software Removal Tool 

Installation date: ‎18/‎04/‎2019 04:08

Installation status: Successful

The PC rebooted without issue. I fully restarted the PC this morning just to check again and all seems good. As usual after a shutdown/restart the resource gobbling Window Module Trusted Installer Service did run. That is, or should be, a one time, normal additional startup item immediately after a Windows update. But that's about it.

On that PC I'm using an older version of AVAST but I know there are others here using v8.0.1497 or earlier with Windows 7 too so I thought it worth posting to say that there appears to be no problem with installing KB4493472 if you're using this, admittedly pretty niche, OS/AVAST version combo.

BTW from today MS are apparently going to be targeting Windows 7 users again in an effort to get all those using it to "upgrade" to Win10. Apparently there are still almost as many Win7 users as Win10 so MS obviously want their money and personal details badly. It is supposed to be less obtrusive and less disingenuous 'persuasion' than tried in previous attempts but I'd still watch out for the reappearance of startup "telemetry gathering" Windows updates from now on.