> For the complete documentation index, see [llms.txt](https://docs.pritunl.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pritunl.com/kb/vpn/client/silent-install.md). # Silent Automated Install Automate Windows client installation The Windows client can be run with the options `/SILENT` or `/VERYSILENT`. These options can be used to automate installs and run unattended installations with deployment systems. The silent option will run the installer with the dialog shown and confirm all prompts. The very silent option will run the installer in the background without any visible windows or prompts. **Currently the installer kills all processes named Pritunl.exe to close the GUI application before updating it. This has the effect of also causing the installer to fork to a new process if the installer has the same Pritunl.exe name. When doing automated installs the installer filename should be renamed to avoid this issue.** --- # 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.pritunl.com/kb/vpn/client/silent-install.md?ask=&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.