> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/windows-workstation-mfa/installation/install-using-exe-legacy.md).

# Install using EXE (Legacy)

The EXE installer is supported for existing deployments and manual installations. For all new deployments, use the MSI installer instead.

***

{% hint style="warning" %}
The EXE installer is maintained for existing deployments and will be deprecated in a future release. If you are starting a new deployment, see **Install using MSI (Recommended)**.
{% endhint %}

### Installer Package Contents

The EXE installer package received from your 1Kosmos representative contains the following files:

| File                           | Purpose                                 |
| ------------------------------ | --------------------------------------- |
| 1KosmosCredentialProvider-.exe | Installer executable                    |
| 1KosmosInstaller.bat           | Batch script for automated installation |
| REGCONFIG.ini                  | Registry configuration file             |

{% hint style="info" %}
The `config.json` file is no longer included in the installer package from v2.4.0.0 onwards. All configuration is handled via `REGCONFIG.ini` and the Windows Registry.
{% endhint %}

***

### Manual Installation

1. Right-click `1KosmosCredentialProvider-<version>.exe` and select **Run as administrator**.
2. Accept the licence agreement and click **Next**.
3. Review the installation location and click **Next**.
4. Click **Install**.
5. When complete, restart the workstation.
6. Click **Finish**.

Default installation directory: `C:\Program Files\1Kosmos\BlockIDCredentialProvider`

Log files: `C:\Program Files\1Kosmos\BlockIDCredentialProvider\Logs`

{% hint style="info" %}
A restart is required for the Credential Provider to appear on the Windows login screen.
{% endhint %}

***

### Batch Script Installation

The `1KosmosInstaller.bat` script automates installation and registry configuration.

#### Basic installation

`1KosmosInstaller.bat -install 1KosmosCredentialProvider-<version>.exe`

#### Installation with registry configuration

Open the `REGCONFIG.ini` file and add your values:

```
VaultUrl=sampleurl
VaultUser=sampleuser
VaultUserCredential=samplecred
VaultProxyUrl=sampleurl
VaultProxyApiKey=sampleapikey
RdpDisabled=0
ClearLastUsedProvider=0
DisablePwdOnLogin=0
DisablePwdOnCredUI=0
CommunitySeed_<dns>_<communityName>=<seed value>
ProviderIcon=<full path to .bmp file>
UILogo=<full path to image file>
```

Then apply the configuration:

`1KosmosInstaller.bat -configure REGCONFIG.ini`

#### Install, configure, and restart in one command

`1KosmosInstaller.bat -install 1KosmosCredentialProvider-<version>.exe -configure REGCONFIG.ini -restart`

### Uninstall

`1KosmosInstaller.bat -uninstall`

{% hint style="warning" %}

* Values in the `REGCONFIG.ini` file must not contain double quotes. Passwords containing double quotes will cause the script to fail.
* The `-install` and `-uninstall` commands cannot be run simultaneously.
* The `REGCONFIG.ini` file is automatically deleted after the `-configure` command completes.
* This script can also be used to upgrade an existing installation.
  {% endhint %}


---

# 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.1kosmos.com/authentication/windows-workstation-mfa/installation/install-using-exe-legacy.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.