> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/developing-with-ndi/utilities/bridge-service-for-windows/installation/silent-installation.md).

# Silent Installation

The Bridge Service installer supports silent installation, allowing you to specify your desired configuration via the command line instead of using the installation wizard. The following command line arguments are supported:

* `/verysilent` This flag is required to perform a silent installation.
* `/web` This flag specifies whether the web interface should run. It is optional and defaults to true. Valid options are true or false.
* `/port` This flag specifies the port on which the service should run. It is not optional.
* `/binding` This flag specifies which interface to bind to. It is not optional. Use 0.0.0.0 for broadcast.
* `/ssl` This flag specifies whether or not to use SSL. It is optional and defaults to false. If this flag is set to true, the */cert* flag is also required. Valid options are true or false.
* `/cert` This flag specifies the certificate to use when SSL is enabled. It is not optional when SSL is enabled. The certificate should be in Common Name format (CN=). SSL certificates must be installed in the local machine certificate store under the ”Personal/Certificates” logical store path.

Example use: *`/verysilent /web=true /ssl=true /port=443 /binding=0.0.0.0 /cert=mycertificate.loca`l*


---

# 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.ndi.video/all/developing-with-ndi/utilities/bridge-service-for-windows/installation/silent-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.