Skip to content
  • There are no suggestions because the search field is empty.

Windows Defender (Windows 11)

Windows Defender may block components of Produce8 — including the Agent, Updater Service, or Desktop App. This guide provides step-by-step instructions to ensure Produce8 can run safely and reliably on Windows 11 devices.

Overview

Windows Defender can interfere with Produce8 in several ways:
  1. Attack Surface Reduction (ASR) rules blocking executables
  2. Microsoft Defender Antivirus quarantining agent files
  3. Windows Firewall blocking network communication
  4. App not being included in the Allowed Apps list
This guide covers:
  1. Required Folder & File Exclusions
  2. Microsoft Defender Antivirus Exclusions & ASR Rules
  3. Troubleshooting With Windows Defender Firewall
  4. Adding Produce8-Agent to Allowed Apps
  5. Creating Firewall Inbound & Outbound Rules
  6. If Produce8-Agent Is Already Listed as Blocked
  7. Additional Tips & Troubleshooting

 

1. Required Folder & File Exclusions

Windows Defender may block the Agent, the Updater Service, or the Desktop App.

To ensure proper functionality, add allow/exclusion rules for the following folders and executables.

Required Exclusions

Add the following paths:

C:\Program Files\Produce8-Agent
C:\ProgramData\Produce8-Agent-Updater
C:\ProgramData\Produce8-Agent
C:\Program Files (x86)\Produce8     (optional – only if the desktop app is installed)

Tip: If your endpoint security policies allow it, adding an entire folder exclusion is often more reliable than adding individual executables.

 

2. Microsoft Defender Antivirus Exclusions & ASR Rules

ASR rules are a common cause of blocked executable files. If these rules are enabled in your environment, exclusions must be added for the Produce8 Agent and Updater.

2.1 Required Folders for ASR Exclusions

Allow the following folders (same list as above):

C:\Program Files\Produce8-Agent
C:\ProgramData\Produce8-Agent-Updater
C:\ProgramData\Produce8-Agent
C:\Program Files (x86)\Produce8     (optional – only if the desktop app is installed)
2.2 Confirm ASR Rule Settings

If ASR rules are blocking execution, you may see entries similar to:

“Block executable files from running unless they meet a prevalence, age, or trusted list criteria.”

To resolve this:

  1. Open Microsoft Defender Security Center
  2. Navigate to:
    Endpoint security → Attack Surface Reduction → Attack surface rules
  3. For each relevant rule, add the Produce8 folders under
    ASR Only Per Rule Exclusions
  4. Ensure exclusions are applied to both the Agent and Updater folders.

 

3. Troubleshooting With Windows Defender Firewall

If the Produce8 Agent cannot communicate, Windows Firewall may be blocking the connection.

Follow the steps below to confirm the Agent is allowed through the firewall.

3.1 Check Allowed Apps List
  1. Open the Start menu and type Windows Defender Firewall
  2. Select Windows Defender Firewall


  3. Select Allow an app or feature through Windows Defender Firewall


  4. Scroll to find Produce8-Agent
  5. Ensure both Private and Public checkboxes are enabled

 

4. Add Produce8-Agent to Allowed Apps (If Missing)

If Produce8-Agent does not appear on the Allowed Apps list:

  1. Return to the Allowed apps window
  2. Click Change Settings (if required)
  3. Click Allow another app…

  4. Navigate to:
    C:\Program Files\Produce8-Agent\
  5. Select Produce8-Agent.exe
  6. Click Add


  7. Ensure both Private and Public checkboxes are enabled

  8. Click OK

 

5. Adding Firewall Inbound and Outbound Rules

Note: Most deployments will work after adding the folder exclusions and Allowed Apps entries. Inbound and outbound firewall rules are only required in environments with strict firewall policies.

5.1 Add Inbound Rule
  1. Open Start → type Windows Defender Firewall


  2. Click Advanced settings


  3. Select Inbound Rules


  4. If Produce8-Agent is not already listed:
    • Click New Rule…
    • Choose Program → Next

    • Browse to:
      C:\Program Files\Produce8-Agent\Produce8-Agent.exe
  5. Select Allow the connection → Next

  6. Check Domain, Private, Public → Next

  7. Name: Produce8-Agent


  8. Click Finish
  9. Confirm the rule appears with a green checkmark.

 

5.2 Add Outbound Rule

Repeat the same steps under Outbound Rules.

 

6. If Produce8-Agent Is Already Listed as BLOCKED

Windows Firewall may have automatically added the Agent as a Blocked Rule.

6.1 Fixing a Blocked Rule
  1. Open Outbound Rules
  2. Find Produce8-Agent with a blocked/red icon

  3. Double-click the rule
  4. Under Action, choose Allow the connection
  5. Click OK


  6. Confirm the rule status updates to Allowed


 

7. Additional Tips & Troubleshooting

If you still see ASR or firewall blocks:
  • Reboot after adding exclusions
  • Ensure no third-party AV/EDR is overriding Defender
  • Confirm Updater service is allowed
  • Ensure policies are not overridden by Intune / Azure AD

If Produce8 data is still not flowing:
  • Restart the Produce8 Agent service
  • Restart the machine
  • Confirm HTTPS communication is not blocked by DNS filtering

 

8. Need Further Assistance?

If you encounter issues after completing the steps in this guide, please contact Produce8 Support with:

  • Device OS version
  • Defender logs / ASR entries
  • Firewall rule screenshots
  • Produce8 Agent logs (if needed)

We’re here to help ensure smooth deployment.