Hello Mario.
We regret the inconvenience caused.
The latest version of AVG for Windows is 20.9.
Could you update your AVG to latest definitions and verify the issue?
Open AVG, click Menu -> Settings -> Update and click Check for updates.
Hi -
Using the latest version of AVG Free (20.7.3140 (build 20.7.5568.601)) on a test Virtual Machine running an up to date Windows 10 OS.
We are in the process of integrating Ansible as a Windows Baseline configuration management system over OpenSSH to maintain compliance with certain NIST standards. When an ansible playbook is launched against the Windows client VM above, it executes the Windows PowerShell.exe command to perform the necessary configuration tasks and gather statistics about the remote system.
However, AVG is flagging PowerShell as a "Command Line Threat". PowerShell is distributed by Microsoft as a standard part of the Windows 10 operating system, so this is clearly a false positive. So okay, as a workaround we added powershell.exe and OpenSSH* paths to the exclusion list per instructions provided on your FAQ. It still fails with the same error (even if the exclusion rules are in place before AVG flagged the binaries as a threat).
From reading posts on your support site, I discovered this issue has been around for several years (since at least 2017). So what's the deal; is this issue ever going to be fixed? At this point I'm ready to jettison AVG and recommend Avast or McAfee as our corporate AV solution since their exclusion rules, you know, ACTUALLY WORK.
Not able to post a screenshot on this forum, so here's what the AVG popup dialog displays:
Restart needed
Please restart your PC to move powershell.exe to your Quarantine
Threat Name: IDP.HELU.PSE20 - Command line detection
Process: C:\Windows\System32\Windows\PowerShell\v1.0\powershell.exe
Detected by: Behavior Shield
Status: Blocked
Hello Mario.
We regret the inconvenience caused.
The latest version of AVG for Windows is 20.9.
Could you update your AVG to latest definitions and verify the issue?
Open AVG, click Menu -> Settings -> Update and click Check for updates.
Hi Nathan,
We are sorry to hear this.
Please accept our apologies for the inconvenience caused.
We will help you to resolve the issue.
Please contact us through separate post to locate your account and help you further.
Keep us posted.
I am a paying subscriber and I am having the exact same issue.
I get the IDP.HELU.PSE20 every time I try to run nodejs / debug with vscode. (running npm start from the WSL bash command line in VS Code)
I added the exception.
I updated my software to the latest version.
I rebooted my computer.
The same exact error is still coming up.
Also, I've done some digging on the internet, it seems like this is some sort of false positive that's been going on for a few years, now. It's been registered many times.