> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/platform-administration/administration/digibeectl/getting-started/windows-install.md). # How to install Digibeectl on Windows Learn how to install Digibeectl if your operational system is Windows. {% hint style="warning" %} If you previously installed Digibeectl, please download the file again and replace the existing one to update Digibeectl. {% endhint %} To install Digibeectl on Windows, follow the steps below: 1. Download the Digibeectl ZIP file below according to your processor (CPU) architecture. * 32 bits: * 64 bits 2. Extract the files to a folder on your computer. To better use Digibeectl, add the extracted file `(.exe)` on your root path. For example, if your root path is `C:\Users\username`, extract the files inside it.
3. Open the Command Prompt (CMD) and type the path where the extracted Digibeectl file is located. For example: `cd C:\Path\To\Folder\Digibeectl`.
4. Enter the command below to configure the credentials for using Digibeectl: ``` digibeectl config set --file "path/file.json" --secret-key "encryption-key" --auth-key "encryption-password" ``` --- # 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.digibee.com/documentation/platform-administration/administration/digibeectl/getting-started/windows-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.