> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment/verify-an-installation.md).

# Verify an installation

How to confirm ADS installed on a machine, and what to check when the results are not what you expect

Confirm that Agentic Development Security (ADS) installed correctly on a machine: check that the installer is present, then confirm that the machine appears in Evo.

## Check that the installer is present

These checks apply to package installs, which leave the installer at a fixed path.

{% tabs %}
{% tab title="macOS" %}

```bash
/usr/local/bin/snyk-ads/snyk-ads-installer --version
pkgutil --pkg-info io.snyk.ads-installer
```

{% endtab %}

{% tab title="Windows" %}

```powershell
& "C:\Program Files\Snyk\ADS Installer\snyk-ads-installer-windows-x86_64.exe" --version
```

{% endtab %}
{% endtabs %}

For a managed mode install on Windows, run the check from an elevated PowerShell session.

A command-line install on macOS or Linux deletes the installer when it finishes, so there is nothing to check on the machine. Confirm those installs in Evo instead.

## Managed mode on Windows

After Intune reports the app as installed, confirm the products are in place. Run these commands from an elevated PowerShell session, because managed mode places the products in machine-wide paths owned by the system:

```powershell
& "C:\Program Files\Snyk\ADS Installer\snyk-ads-installer-windows-x86_64.exe" --version
Get-ChildItem "$env:ProgramFiles\Snyk\ADS\ads-scan\bin" -File | Select-Object Name, Length
Get-ChildItem "$env:ProgramData\Snyk\ads-scan" -File | Select-Object Name, Length
schtasks /Query /TN "\Snyk\ADS\" /V /FO LIST 2>$null | Select-String "TaskName|Run As User"
```

`Run As User` for the scheduled task shows `BUILTIN\Users` rather than one specific account. That is the machine-wide principal that applies the scan to every local user.

The scheduled task exists only when Machines is on version 0.6.8 or later. On an earlier version the query returns nothing, which does not mean the install failed.

## If a machine is missing from Evo

The first scan runs when the installer runs, so a machine appears in Evo once that run finishes. If it does not, check the causes in [Troubleshooting](/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment/troubleshooting.md): an unpublished configuration, a failed onboarding step, or the wrong region.

If none of these applies, collect the output from the installer run and your Tenant ID, and contact your Snyk account team.


---

# 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.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment/verify-an-installation.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.