I’m investigating an interaction between Avast Free Antivirus and a Java process running inside a zero-capability Windows AppContainer.
With Windows Security Center reporting Avast Antivirus as on, I launched a local Java executable inside the AppContainer under a process and module monitor. During startup, the monitor observed Avast’s aswhook.dll. The monitor’s existing module-origin policy did not admit that DLL, so it terminated the Java process before the compiler produced output.
Has anyone encountered this interaction or know of Avast documentation that explains:
What causes aswhook.dll to load into an AppContainer process?
Whether existing read-only diagnostics can identify the component and decision responsible for the load?
Whether there is a supported way to avoid the conflict while keeping Avast protection enabled and preserving the application’s module-origin policy?
I’m looking for guidance on the interaction. I haven’t included executables, logs, personal paths, or attachments.
First, I’m an Avast user and not an Avast Team member
I’m not entirely sure why the Windows Security is getting involved, as when you install another Antivirus (including Avast) Windows is meant to disable the Windows Antivirus/security function, to prevent conflict.
From memory the aswhook.dll is what it used so that the avast antivirus is able to scan sites before they are essentially loaded..
This from a search;
The FreeFixer Library Entry for aswhook.dll explains that aswhook.dll is a core Hook Library developed by AVAST Software (and used across Avast, AVG, and Gen Digital / Norton products). [1, 2]
What It Does
Real-Time Protection: It injects itself into running system processes to monitor and hook API and system calls (a technique known as inline hooking or detouring). [1, 2]
Malware Detection: By intercepting these calls, Avast can inspect application behavior in real-time, block suspicious actions (like process hollowing or unauthorized memory writes), and detect malware before it executes. [1, 2]
Legitimate Location: The file normally resides in C:\Program Files\AVAST Software\Avast\ (or equivalent AVG/Norton directories) and is digitally signed by the developer. [1, 2]