> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/dope.endpoint/windows-installer.md).

# Windows Installer

Supports Windows 10 & 11

### Downloading the Windows Installation Package

To download the Windows installation package, log in to the Dope Console. Then, click the download button in the top right corner. <img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FNalvdvMR2rGfsunPSm4V%2F7.0-endpoint-download_icon.png?alt=media&amp;token=07a31fe6-156b-41fe-a12a-bb5388a13e0a" alt="" data-size="line">

<figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FWmgjmQlKaJBa24OOCXU4%2Fgitbook-endpoint-2023_6.png?alt=media&amp;token=7a2eabe1-442d-43c7-a036-1bb964dc2056" alt=""><figcaption></figcaption></figure>

The ZIP file will be called **dope\_security*****\_windows\_\<build number>.zip**.*

Extract the ZIP file, it will contain the following three files:

* \<build number>.exe — The dope.endpoint installer.
* dope.security.crt — The dope.security Root CA, required for SSL inspection.
* agent\_parameters.json — Tenant specific data required for the installation process.

{% hint style="warning" %}
All three files must be in the same directory or the installation will **FAIL**
{% endhint %}

{% hint style="info" %}
If missing, the installer automatically installs the [Visual C++ redistributable](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version) (dependency). This causes a VC++ download prior to the dope.endpoint installation. Very rarely, this can cause install failures during managed deployments (bad network etc). To avoid, stage an install of VC++ first
{% endhint %}

To install the dope.endpoint, double click on the EXE file. This will launch the following Installer UI.

<figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FqI7OJQVxqnSBlJTvaihJ%2Fgitbook-screenshots_9.png?alt=media&amp;token=8f05c817-c8d1-4f71-91a3-fd9ae2600701" alt=""><figcaption></figcaption></figure>

Before installation can start the dope.security End User License Agreement (EULA) needs to be accepted. Once this has been accepted, select the install option to start the installation process.

MS Windows will also prompt to accept installing the dope.endpoint on the Windows machine.

<figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2Fegg6fteoTEtIKBsznNGN%2Fgitbook-screenshots_10.png?alt=media&amp;token=36a1e334-788d-4f26-bf10-fc7ef05c9099" alt=""><figcaption></figcaption></figure>

On selection of Yes the installation process will continue. Once it is complete the following dialog will be displayed.

<figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FRBKDnL2RkP2G5IZ5lZ0E%2Fgitbook-screenshots_11.png?alt=media&amp;token=e0aea876-8ec8-4172-8ee0-c29aa76dd64c" alt=""><figcaption></figcaption></figure>

Once the installation is complete a dope.security icon can be seen in the Windows systems tray icon.

Where endpoint authentication has been enabled (See [Users](/dope.console/settings/users.md)), then the user will be prompted to authenticate with their M365 or Google credentials.


---

# 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://inflight.dope.security/dope.endpoint/windows-installer.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.