> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/mdr/deploy/sentinelone/os/windows.md).

# Windows

Install the SentinelOne agent on a Windows workstation or server manually, through an MDM or with a GPO. To deploy the EDR on a large scale, start with a manual test installation on a few endpoints.

## Prerequisites

* Your current antivirus is completely uninstalled: SentinelOne replaces it. If the firewall is managed separately, keep it running. If it is part of the same solution, copy any custom rules to Windows Firewall first.
* The machine has been restarted after removing the previous antivirus and after the last Windows updates.
* You are logged in with an administrator account on the machine.
* If outbound traffic is blocked, the addresses in [Network requirements](https://docs.stoik.io/mdr/deploy/sentinelone/network.md) are allowed.

## Installation

{% stepper %}
{% step %}

### Download the right installer

The installer depends on the Windows version and the processor of the machine. To find them, press the Windows key, type `About your PC` and press Enter. Read the `Edition` (Windows version) and `System type` (processor) lines. On Windows 7 or 8, open the `Start` menu, right-click `Computer` and select `Properties` instead.

In Stoïk Protect, go to `MDR` > `Settings` and click `Windows`.

<figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2Fgit-blob-b76c8b283ffc7b58936e5f3915185f1c3af8df6e%2Fs1-windows-setup.webp?alt=media" alt=""><figcaption></figcaption></figure>

Download the file that matches the machine:

| The machine has                                                       | Menu in Stoïk Protect      | File to download                                           |
| --------------------------------------------------------------------- | -------------------------- | ---------------------------------------------------------- |
| Windows 8.1 or later, 64-bit, x64 processor (Intel / AMD)             | `Download this executable` | `SentinelInstaller_windows_64bit_v<version>.msi`           |
| Windows 8.1 or later, ARM processor                                   | `Download this executable` | `SentinelOneInstaller_windows_arm64_v<version>.exe`        |
| Windows older than 8.1 (7, 8, XP, Vista, Server 2003 to 2012), 64-bit | `Legacy Plus installer`    | `SentinelOneInstaller-64bit_windows_legacy_v<version>.exe` |
| Any Windows, 32-bit                                                   | `Legacy Plus installer`    | `SentinelOneInstaller-32bit_windows_legacy_v<version>.exe` |

<details>

<summary>Supported Windows versions</summary>

**Standard installer** (`Download this executable` menu):

* Windows 8.1 / 10 / 11 / 11 23H2 / 11 24H2 64-bit
* Windows Server IoT 2019 / 2022 / 2025
* Windows Server / Server Core 2012 R2 / 2016 / 2019 / 2022 / 2025

**Legacy Plus installer** (`Legacy Plus installer` menu, 32-bit and 64-bit files):

* Windows 8.1 / 10 32-bit
* Windows 7 SP1 / 8 32/64-bit
* POSReady 7
* Windows Server / Storage Server / Server Core 2012 (not R2) 32/64-bit
* Windows Server 2008 R2 SP1 32/64-bit
* Windows XP SP3 / Vista SP2 32/64-bit
* Windows XP SP2 64-bit (AMD64/EM64T)
* Windows Embedded POSReady 2009
* Server 2003 SP2 / 2003 R2 SP2 / 2008 SP2 (not R2) 32/64-bit

</details>

{% hint style="warning" %}
Most machines have an Intel or AMD (x64) processor. For them, download both the `.msi` (to install with a double-click) and the x64 `.exe` (`SentinelOneInstaller_windows_64bit_v<version>.exe`, to install from the command prompt if the `.msi` fails). ARM and Legacy Plus versions are rare.

Save the file on the machine itself, for example on the Desktop. Do not run it from a USB key or a network share.
{% endhint %}
{% endstep %}

{% step %}

### Find your site token

Go to `MDR` > `Settings` and copy the site token, shown as `Customer ID`. The installer asks for it in the `Site Token` field.

<figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2FemeExV0LCLaQAfG1qQgL%2Fimage.png?alt=media&amp;token=99f2d142-fd0d-4753-9c72-f1002e271f6d" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Install SentinelOne

{% tabs %}
{% tab title="Manual" %}
For an Intel / AMD (x64) machine, with the `.msi`:

1. Double-click the `.msi` file.
2. Accept the license agreement.
3. Paste your site token in the `Site Token` field.
4. Click `Install`. When Windows asks `Do you want to allow this app to make changes to your device?`, click `Yes` (with a standard account, an administrator types their name and password).
5. Wait for the end of the installation, then click `Finish`.

{% hint style="warning" %}
Never double-click the x64 `.exe`: it does nothing and no longer asks for the site token. Use the `.msi` for a double-click installation, and the `.exe` only from the command prompt (see [Troubleshooting](https://docs.stoik.io/mdr/deploy/sentinelone/os/windows/troubleshooting.md)).
{% endhint %}

<details>

<summary>Legacy Plus machine (older than 8.1, or 32-bit)</summary>

1. Double-click the Legacy Plus file.
2. If Windows asks `Do you want to allow this app to make changes to your device?`, click `Yes`, or have an administrator type their name and password.
3. Paste your site token in the `Site Token` field, then click `Install`.

The command prompt methods do not apply to the Legacy Plus installer. If it fails, go through [Troubleshooting](https://docs.stoik.io/mdr/deploy/sentinelone/os/windows/troubleshooting.md), then contact <protect@stoik.io>.

</details>

<details>

<summary>ARM machine</summary>

The ARM installer has no installation window: it only works from the command prompt.

1. In `C:\`, create a folder `Temp` and, inside it, a folder `S1`. Move the installer into `C:\Temp\S1`.
2. Press the Windows key, type `cmd`, right-click `Command Prompt`, select `Run as administrator` and click `Yes`.
3. Type the commands below, pressing Enter after each line. Replace `<version>` with the version in your file name and `<site_token>` with your site token, and remove the `<` and `>` characters.

```
cd C:\Temp\S1
SentinelOneInstaller_windows_arm64_v<version>.exe -t "<site_token>" -q
```

4. Wait about 5 minutes, then type `echo %errorlevel%` and press Enter. `0` means the installation succeeded. Any other number: see [Troubleshooting](https://docs.stoik.io/mdr/deploy/sentinelone/os/windows/troubleshooting.md).

</details>
{% endtab %}

{% tab title="MDM" %}
Run the following command, replacing `<customer_ID>` with your customer ID:

```
<file_name>.exe -t <customer_ID> -q
```

{% endtab %}

{% tab title="GPO" %}

1. Place the `.exe` installer in a network share. Example: `\\Server\Share\SentinelOneInstaller_windows_64bit_v<version>.exe`. Give **Read** permissions on the share to `Domain Computers` (the computer accounts), not only to users: the script runs as the machine, not as a user.
2. Create a deployment script named `InstallSentinelOne.bat` with the content below. It is a plain batch script: it runs in the command prompt, which is what the SentinelOne `.exe` requires.

```batch
@echo off
set "INSTALLER=\\<server>\<share>\SentinelOneInstaller_windows_64bit_v<version>.exe"
set "SITETOKEN=<customer_ID>"
set "LOG=C:\Windows\Temp\S1_GPO_Install.log"

:: Skip if SentinelOne is already installed
sc query SentinelAgent >nul 2>&1
if %errorlevel% equ 0 (
    echo %date% %time% SentinelOne already installed >> "%LOG%"
    exit /b 0
)

echo %date% %time% Starting installation from %INSTALLER% >> "%LOG%"
start "" /wait "%INSTALLER%" -t "%SITETOKEN%" -q
echo %date% %time% Installer exit code: %errorlevel% >> "%LOG%"
```

Replace the installer path with your share path and `<customer_ID>` with your customer ID. Remove the `<` and `>` characters as well. The check at the top stops the script from reinstalling SentinelOne at every restart.

3. Create a GPO:
   1. Open the Group Policy Management Console: `Windows + R` > `gpmc.msc` > `Enter`.
   2. Right-click the target container (domain or OU) and click `Create a Group Policy Object in this domain and link it here`. Name it (e.g. `SentinelOne Deployment`).
   3. Right-click the new GPO and select `Edit`.
   4. Go to `Computer Configuration` > `Policies` > `Windows Settings` > `Scripts (Startup/Shutdown)`. Use `Computer Configuration`, not `User Configuration`: startup scripts run with system rights, so there is no administrator prompt and users have nothing to do.
   5. Double-click `Startup`, click `Show Files`, and copy `InstallSentinelOne.bat` into the folder that opens.
   6. Click `Add`, then `Browse`, select `InstallSentinelOne.bat` and click `OK`.
4. Apply the GPO:
   1. On a target machine, run `gpupdate /force`, then restart it to trigger the script.
   2. Check that the machine appears in Stoïk Protect under `MDR` > `Monitored Assets`.
   3. If it does not, open `C:\Windows\Temp\S1_GPO_Install.log` on that machine and see [Troubleshooting](https://docs.stoik.io/mdr/deploy/sentinelone/os/windows/troubleshooting.md).
      {% endtab %}
      {% endtabs %}
      {% endstep %}

{% step %}

### Check the installation

* On the machine, look for the SentinelOne icon in the notification area, at the bottom right of the taskbar (click `^` to see hidden icons).
* Within 5 minutes, the machine appears in Stoïk Protect under `MDR` > `Monitored Assets`. No restart is needed.

If the machine does not appear after 15 minutes, see [Troubleshooting](https://docs.stoik.io/mdr/deploy/sentinelone/os/windows/troubleshooting.md).
{% endstep %}
{% endstepper %}

## Troubleshooting

If the installation fails or the machine does not connect, see [Troubleshooting](https://docs.stoik.io/mdr/deploy/sentinelone/os/windows/troubleshooting.md): it covers how to locate the problem, administrator rights, the command prompt fallback, connection issues, and the exit codes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/mdr/deploy/sentinelone/os/windows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
