AVLaunch.exe - Bad Image Errors following 22.7 update

[jsessions]

Since updating to 22.7 I'm getting 'AvLaunch.exe - Bad Image' error messages on startup relating to the file C:\Windows\system32\cssguard64.dll with error code 0xc000022.  Alert states the dll file is either not designed to run on Windows or it contains an error.  Tried uninstalling/reinstalling with same result.  Also tried AVG Free instead of Avast Free but get same error with AVG.  Rolled back to 22.6 which works fine.  (This is on latest version of Windows 10).

[Spec8472]

Hi jsessions,

Avast self-defense is preventing 3rd party (non MS) module injection (Comodo in this case) into Avast processes since version 22.7. The 0xc000022 is STATUS_ACCESS_DENIED, which is expected. But this blockage should be silent (no message box). We are investigating this.

Thank you for reporting this

[jsessions]

Thanks for your reply.  I haven't used any Comodo software for a few years so this Comodo Secure Shopping related file must be a remnant leftover from a previous uninstall which I'll deal with!  I'm glad that report was helpful.

[wir1313]

I also have this error and many others.

When starting Windows 10 while loading Avast, I get an error and until I click OK, Avast will not start. Further errors occur when, for example, saving / recovering Avast configurations. Reinstalling Avast does not improve the situation.

VisthAux.exe
AvLaunch.exe
C:\Windows\system32\guard64.dll
0xc0000022

Windows 10 and Avast free 22.7.6025 (build 22.7.7403.736)

Yes I use Comodo Firewall 12.2.2.8012

[Spec8472]

Hello,
the problem was identified. A fix will be released ASAP.

[wir1313]

Hello,
the problem was identified. A fix will be released ASAP.

Eta?

[markinson]

Same issue here, unfortunately. 
Both with AVAST and with AVG, too.

Hope fixing this problem ...

[Spec8472]

Hello wir1313, probable release of fix is Monday, 1 August

[Spec8472]

Hello,
the fix is released. A reboot is needed to reload afflicted driver.

[wir1313]

Hello,
the fix is released. A reboot is needed to reload afflicted driver.

Thank you, the fix is working fine.

[markinson]

Well done and thank you so much! The issue was fixed!
Cheers!

[Tavi]

Hello,
the fix is released. A reboot is needed to reload afflicted driver.

Indeed, it's fine now! Thank you!
For the record I had to download and (re)install the new (fixed) version. It didn't want to be fixed through the Update on the ("old" version) app interface.