Windows Automation Node Installation Guide (GUI & Headless)

You can transform any Windows 10 or Windows 11 machine into a high-performance, background browser automation node for BrowserMesh. The node runs silently as a background service, executing scheduled Playwright automation workflows, rotating residential IP requests, and persisting structured data directly to your local drive.

Whether deploying on a dedicated home office workstation or a Windows Server virtual machine, BrowserMesh provides both interactive GUI and automated terminal installation paths.

Automated Setup Options

Option 1: One-Line PowerShell Command (Recommended)

Open Windows PowerShell (Run as Administrator for full service installation privileges) and execute:

powershell -NoProfile -ExecutionPolicy Bypass -Command "iwr -useb https://www.browsermesh.in/scripts/install-headless.ps1 | iex"

Option 2: Windows Command Prompt (CMD)

If running within standard Command Prompt or CI/CD pipelines, execute:

curl -sL https://www.browsermesh.in/scripts/install-headless.cmd -o install.cmd && install.cmd

Option 3: Double-Click Batch File Installer

1. Download install-headless.cmd directly to your Downloads folder.
2. Right-click install-headless.cmd and select Run as Administrator.
3. A terminal window will display installation progress and prompt you to link your BrowserMesh cloud account.

What the Installer Performs Under the Hood

The automated script executes an end-to-end, 5-stage setup sequence:

1. Runtime Verification: Checks for an existing Node.js environment (v18 or v20 LTS recommended). If missing, it installs a self-contained portable Node.js runtime.
2. Process Supervisor Setup: Configures pm2 globally to ensure the node daemon auto-restarts upon unexpected crashes or system reboots.
3. Daemon Extraction: Downloads the latest release bundle (backend-latest.tar.gz) and unpacks it to %USERPROFILE%\browsermesh-node.
4. Environment Initialization: Writes an optimized .env configuration file containing your node authentication token and API endpoint routing.
5. Chromium Engine Provisioning: Downloads sandboxed headless Chromium binaries with optimized Windows graphics acceleration flags.

Managing Your Node with the mesh CLI

The setup script creates a global command-line shortcut named mesh in your system PATH (%APPDATA%\npm). You can execute mesh commands from any terminal shell (PowerShell, CMD, or Windows Terminal):

• mesh status : Inspect active process state, CPU load percentage, and RAM consumption.
• mesh logs : Stream real-time workflow execution logs and extraction telemetry.
• mesh restart: Gracefully restart the background automation engine.
• mesh stop : Temporarily suspend background job processing.
• mesh start : Resume the background automation daemon.

Once the node reports online, visit your Cloud Dashboard. Your Windows device will immediately appear under the Active Devices tab with its residential IP classification.

Windows Firewall & Antivirus Whitelisting

Because BrowserMesh establishes a persistent WebSocket connection to dispatch automation jobs, corporate firewalls or aggressive third-party antivirus suites may occasionally flag Chromium network sockets.

To ensure uninterrupted connectivity, execute the following PowerShell snippet to whitelist the node daemon:

New-NetFirewallRule -DisplayName "BrowserMesh Node Daemon" `
  -Direction Outbound `
  -Program "$env:USERPROFILE\browsermesh-node\bin\node.exe" `
  -Action Allow

Auto-Start on System Boot (Task Scheduler)

To configure BrowserMesh to start automatically whenever your computer powers on (even before user login):

1. Open Windows Task Scheduler (taskschd.msc).
2. Click Create Basic Task and name it BrowserMesh-Node-Autostart.
3. Set the Trigger to When the computer starts.
4. Set Action to Start a program, entering:
   • Program/script: powershell.exe
   • Add arguments: -WindowStyle Hidden -Command "mesh start"
5. Save the task with Run whether user is logged on or not enabled.

Troubleshooting Common Windows Issues

• ExecutionPolicy Restriction: If PowerShell blocks script execution, prepend -ExecutionPolicy Bypass to the command line.
• Missing Visual C++ Redistributable: If Chromium fails to launch, install the official Microsoft Visual C++ 2015–2022 Redistributable (x64).
• High Memory Consumption: If automating complex single-page apps, configure your maximum concurrency limit to 3 inside Settings > Quotas to maintain under 4 GB of RAM usage.

Related Platform & Commercial Resources

• Download Windows Desktop App: Official Download Center (/download)
• Explore 250+ Workflows: Browse Plugin Marketplace (/marketplace)
• Pricing & Multi-Device Fleet: Transparent Pricing (/pricing)
• Engine Architecture: AutomationEngine Features (/features)
• Android Node Setup: Android Installation Guide (/docs/install-android)
• Linux Server Setup: Linux Installation Guide (/docs/install-linux)