AVG Behavior Shield repeatedly blocks Local’s PowerShell and cmd helpers on Windows 11

I installed Local from the official LocalWP source on Windows 11. While importing a private WordPress backup and attempting to use localhost Router Mode, AVG Internet Security repeatedly blocked Local-related command helpers.

AVG detections:

  • C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe

  • Detection: IDP.HELU.PSE91 - Command line detection

  • Status: Blocked

  • C:\Windows\SysWOW64\cmd.exe

  • Detection: IDP.Generic - Command line detection

  • Status: Blocked

Local also reported that it could not update the Windows hosts file. AVG’s Smart Scan subsequently reported zero malware threats.

Closing Local stops the AVG alerts. Reopening Local or opening its Advanced preferences causes the cmd.exe alert to return.

I have not disabled AVG, added exclusions, quarantined Windows system files, enabled Live Links, or opened the imported website. The site remains stopped.

I need the environment to remain private and accessible only from this computer.

Questions:

  1. Is there a supported way to use localhost Router Mode without Local invoking temporary PowerShell or batch-file hosts-maintenance commands?

  2. Why does Local continue trying to modify the hosts file when the site is stopped or localhost Router Mode is being selected?

  3. Can Local provide the expected command structure, helper-file details, or hashes needed to report these detections safely to AVG?

  4. Is there a supported configuration that prevents repeated hosts-file maintenance without disabling antivirus protection or broadly allowlisting cmd.exe or PowerShell?

Please do not recommend disabling antivirus or globally excluding Windows command processors.


Hey @dieterscleaning – welcome to the community and thanks for documenting this so carefully.

I took a closer look at the Windows behavior you’re seeing.

The AVG’s alerts appear consistent with legitimate maintenance tasks performed by Local, rather than Local detecting or installing malware. Behavior Shield is reacting to how Windows tools are being used—not necessarily to a known malicious file. That also aligns with AVG’s Smart Scan finding no malware.

Local uses Windows command tools for a few different jobs, including:

  • Cleaning up Local services left behind after a previous session
  • Running WordPress maintenance commands when starting or importing a site
  • Detecting installed browsers and terminals
  • Requesting administrator access when the Windows hosts file needs updating

Some of these patterns—especially PowerShell process inspection, temporary helper files, administrator elevation, and hosts-file changes—are also used by malware. It’s understandable that behavior-based protection may flag them, even when they come from a legitimate application.

To answer your questions:

  1. Localhost Router Mode should not require hosts-file maintenance.
    Once localhost mode has been selected and applied, Local uses addresses such as http://localhost:10005 and should stop trying to add site domains to the Windows hosts file.

    Local may still use cmd.exe or PowerShell for unrelated tasks, so choosing localhost mode will not eliminate every command-tool alert.

  2. In Site Domains mode, hosts entries are maintained for all sites—even stopped ones.
    Those entries describe Local’s configured domains and are not based on whether a site is currently running. This is why a stopped site can still lead to a hosts-file check.

    Also, changing the router selection does not take effect until the preference is applied. If hosts-file prompts continue after localhost mode has been applied and Local has been restarted, that would be unexpected and worth investigating through the Local logs.

  3. There may not be one stable helper hash to provide to AVG.
    The files shown in the alerts are Microsoft’s own cmd.exe and PowerShell. Some elevated maintenance operations also create short-lived helper files whose contents and paths can vary by machine and Local version.

    For an AVG false-positive report, the most useful information would be:

    • The exact Local version
    • The hash and digital signature of the Local installer/application
    • AVG’s full detection details
    • The process tree showing Local as the parent
    • The approximate time of the detection, so it can be matched with Local’s logs
  4. Localhost mode is the supported way to avoid repeated hosts-file maintenance.
    There isn’t a supported setting that keeps Site Domains mode while permanently disabling its hosts-file management. You should not need to disable antivirus protection or broadly allowlist PowerShell or cmd.exe.

For keeping the site private, leaving Live Links disabled is important—Local does not create a public tunnel unless that feature is explicitly enabled. A stopped site is not being served at all.

For the strongest “this computer only” setup, I’d recommend localhost mode with the nginx web server, Live Links disabled, and the normal Windows Firewall protections left enabled. Local is a development environment rather than a security sandbox, so it’s also sensible to scan any backup from an uncertain source before starting or opening it.

If you can share the Local version and the Local logs there should be a little more information. You can get a zip of those logs by clicking the “Download Local Log” button from the “Support” tab of Local. See this help doc for more information:

Thank you. The requested details are:

  • Local version: 10.1.2+7004

  • Windows 11

  • AVG Internet Security with Behavior Shield enabled

  • Live Links disabled

  • Imported site currently stopped

I downloaded and reviewed Local’s log.

The log confirms that Local invoked its hosts-file worker through Local.exe and then recorded:

Could not update hosts.

The log also shows that the first import encountered a GoDaddy-specific WordPress configuration dependency:

wp-config-hosting.php

Local classified the first attempt as a broken import, performed its automatic WordPress repair, set WP_ENVIRONMENT_TYPE to local, and completed the temporary-import cleanup. The site has not been opened or functionally tested.

The current log does not show that localhost Router Mode was successfully applied.

The log contains my Windows username, full local paths, local site ID, and local domain, so I have not attached the complete ZIP publicly. It does not appear to contain passwords, tokens, API keys, authorization headers, email addresses, or database passwords.

Please let me know whether you need the full log through a private channel, or whether specific redacted excerpts would be sufficient. I would also appreciate confirmation of the expected Local 10.1.2 behavior when applying localhost Router Mode while AVG blocks Local’s temporary command helpers.

Update: localhost Router Mode is now selected and persisted in Local 10.1.2+7004.

However, immediately after opening Local’s Advanced preferences, AVG Behavior Shield again blocked:

  • Process: powershell.exe

  • Detection: IDP.HELU.PSE94 - Command line detection

  • Time: October 12, 2026 at approximately 11:14 AM EDT

The WordPress site remained stopped, Live Links remained disabled, and I did not quarantine PowerShell, disable AVG, or add exclusions.

This confirms that localhost mode resolved the hosts-file/router selection, but Local is still invoking a PowerShell task unrelated to hosts-file maintenance. Can you identify which Local 10.1.2 startup or preferences task would run at this point and whether blocking it affects site operation, imports, WP-CLI, or Elementor testing?

I’ll send you a DM to collect your full local log @dieterscleaning and then I can connect with Ben and circle back!

Thanks for that log @dieterscleaning – it looks like a fairly typical Local log and I’m not seeing anything that would indicate that there’s a security issue with Local.

As you saw, we try to keep sensitive info out of the logs. Some private data like username or sitename might get through, usually in the form of paths, might get written. In general, having the full picture is helpful to get context around what’s happening and what other processes Local is managing around the time of any errors, so thanks for providing that to Nick!

To some of your specific questions:

I would also appreciate confirmation of the expected Local 10.1.2 behavior when applying localhost Router Mode while AVG blocks Local’s temporary command helpers.

It looks like Local wrote this line as a result of not being able to edit the hosts file:

{"class":"HostsFileService","error":{},"exitCode":{},"level":"error","message":"Could not update hosts.","stderr":{},"stdout":{},"thread":"main","timestamp":"2026-09-23T14:16:00.217Z"}

I wish that there were some more details here. Local accounts for some typical exit codes that might be encountered (like EBUSY if another process is holding the file, or EPERM if the file itself is not writeable for the user). I might improve the logging a bit to help in the future, but having an empty error makes sense given that the antivirus is likely just saying “NOPE” to Local and Local is logging that it tried its best.

This confirms that localhost mode resolved the hosts-file/router selection, but Local is still invoking a PowerShell task unrelated to hosts-file maintenance. Can you identify which Local 10.1.2 startup or preferences task would run at this point and whether blocking it affects site operation, imports, WP-CLI, or Elementor testing?

There isn’t anything on the “Advanced” screen that would fire off a subshell request, however, to get to the Advanced screen, you typically have to navigate to “Preferences > Appearance & Behavior” and then to what ever screen you want. That’s significant because that first screen has the “Default Apps” settings. Local does spawn subshells to determine if things like Gitbash is installed or what browsers are installed.

I think the “default browser” setting is the powershell command and the “default terminal” is a cmd.exe call.

Neither one of these would affect site operations, they just allow you to explicitly set some defaults that Local uses when opening a terminal or a browser for you.

None of the other screens fire off a subshell. There is one network call that happens on the “New site defaults” screen which checks to see what WP language translations are available so you can set a default for new sites.

Hope that help clarify things - Let us know if you have any other questions!