> 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/developer-tools/integrations/snyk-ide-plugins-and-extensions/troubleshooting-ides/ide-plugin-fails-with-scan-failed-on-windows-systems-with-.exe-download-blocking.md).

# IDE plugin scan fails on Windows systems with .exe download blocking

How to resolve Snyk IDE plugin scan failures from .exe download blocking on Windows

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## IDE plugin scan fails on Windows systems with .exe download blocking

### **Problem**

When you are using Snyk plugins in an IDE on Windows systems, the Snyk scan may fail.

You may see an error message in the logs that indicates `Error running command snyk.start: command 'snyk.workspace.scan' not found. This is likely caused by the extension that contributes snyk.start.`

### **Cause**

This issue is often seen on Windows systems that have a company policy in a firewall or other tool to prevent automatic `.exe` download by showing an interactive popup requesting approval.

This popup is not shown in the IDE, and the `.exe` file cannot be downloaded. This may result in a 0KB file being created in the download location.

To determine if this is the case, navigate to the location for the CLI or Language Server shown in your Snyk plugin settings in the IDE. If either the CLI or Language Server files are 0KB, this is likely the issue.

### **Solution**

The preferred solution for this is to allowlist `downloads.snyk.io` and `static.snyk.io` in the baseline policy for `.exe` files, so that downloads from this location are exempt from `.exe` popup approvals for all users.

You can use the following temporary solutions in the interim if the preferred solution will take time to approve.

* Manually download the relevant `.exe` file directly from either [Snyk CLI Releases](https://github.com/snyk/cli/releases) or [Snyk Language Server Releases](https://github.com/snyk/snyk-ls/releases), and place it in the location listed in your plugin settings. Ensure that you turn off the option to **Automatically Manage Dependencies**.

or

* If `CLI exe` is downloaded, you can use it to provide the language server function. Redirect the language server location to the CLI location in the plugin settings, and ensure that you turn off the option to **Automatically Manage Dependencies**.


---

# 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/developer-tools/integrations/snyk-ide-plugins-and-extensions/troubleshooting-ides/ide-plugin-fails-with-scan-failed-on-windows-systems-with-.exe-download-blocking.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.