> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/chaos-engineering/use-chaos-engineering/probes/command-probes/windows-command-probe.md).

# Windows Command Probe

This topic describes how to use the **Windows command probe** to execute Windows-specific commands and PowerShell scripts as part of chaos experiments targeting Windows environments. The Windows command probe extends the standard command probe functionality to support Windows Command Prompt (cmd) and PowerShell execution contexts.

In this guide, we'll walk you through setting up a Windows command probe that checks the system hostname during a Windows CPU stress experiment, demonstrating how to validate system responsiveness under load.

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* [Setup Windows chaos infrastructure](/resilience-testing/chaos-engineering/use-chaos-engineering/infrastructure/types/legacy-infra/windows.md)
* [Command Probe](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/command-probes/index.md)
* [Create a resilience probe](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/index.md#create-a-resilience-probe)
* [Windows chaos faults](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md)

### Steps to configure Windows command probe <a href="#steps-to-configure-windows-command-probe" id="steps-to-configure-windows-command-probe"></a>

1. Navigate to **Resilience Probe** in the left navigation pane, select **Windows** as your target infrastructure type, and then select **Command Probe**.

   ![Create Command Probe](/files/o4Dti5ZlxWyDlnhg1npi)
2. Enter a name for your command probe in the **Name** field.

   ![Enter Probe Name](/files/o4Dti5ZlxWyDlnhg1npi)
3. Enter the **Command**, **Type**, **Comparison criteria**, and the **Value**. Click **Configure Properties**.

   ![Enter Command](/files/rZoKyJNXBeKl5NCFpuPS)
4. Provide other values like **Timeout**, **Interval**, **Attempt**, **Polling Interval**, and **Verbosity**. Click **Create Probe**.

   ![Provide More Details](/files/MBBCqXJsJUbRknL4cusc)
5. Your Windows command probe is now ready to be attached to chaos experiments. You can monitor probe execution results during experiment runs to validate system behavior.

   ![Monitor Results](/files/9OM5bPWMGmi31sZdJyV2)

### Related topics <a href="#related-topics" id="related-topics"></a>

* [Command probe configuration](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/command-probes/command-probe-usage.md)
* [Windows chaos faults](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md)
* [Probe modes and timing](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/index.md#probe-modes)
* [Creating resilience probes](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/index.md#create-a-resilience-probe)