> 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/post-installation-verification.md).

# Post-installation Verification

***

#### Step 1 - Verify the Agent Appears on the Login Screen

1. Restart the workstation if you have not already done so. The Credential Provider needs a restart for install completion
2. On the Windows login screen, confirm the **1Kosmos** tile is visible in Sign-In options.
3. The tile displays the 1Kosmos logo. If you have configured a custom logo via the `ProviderIcon` registry key, your organisation's logo will appear instead.

If the 1Kosmos tile is not visible after restart:

* Confirm the installation completed without errors. Check logs at `C:\Program Files\1Kosmos\1KosmosCredentialProvider\Logs`.
* Confirm `tenantUrl` and `communityName` are correctly configured in the Windows Registry (MSI) or `REGCONFIG.ini` (EXE)
* Confirm all runtime dependencies are installed 
* See **Troubleshooting** for further guidance

***

#### Step 2 - Verify Connectivity to the 1Kosmos Platform

Before testing authentication, confirm the workstation can reach the 1Kosmos platform.

1. Open a browser on the workstation and navigate to your tenant URL (e.g., `https://acme.1kosmos.net`).
2. Confirm the page loads without certificate errors or timeouts.
3. If the page does not load, review your Network & Connectivity Requirements and proxy configuration, see [Troubleshooting & Support](/authentication/windows-workstation-mfa/troubleshooting-and-support.md).

***

#### Step 3 - Test Login with MFA

Perform a test login using a user account that has an Adaptive Auth Journey configured in AdminX.

1. On the Windows login screen, click the **1Kosmos** tile.
2. If prompted, enter the username.
3. Complete the configured authentication method (e.g., enter password then approve push notification).
4. Confirm the user is successfully logged into Windows.

If the test fails, check the following:

* The user exists in the connected Active Directory or LDAP directory.
* An Adaptive Auth Journey is configured for the user or their AD group under **Applications > Windows MFA** in AdminX.
* The user has the required authentication method enrolled (e.g., 1Kosmos mobile app linked for Push / TOTP; 1Key enrolled for FIDO).
* Check log files at `C:\Program Files\1Kosmos\BlockIDCredentialProvider\Logs` for error details.
* See **Troubleshooting** for common failure scenarios.

{% hint style="info" %}
Always test with a non-administrator account first. Local administrator accounts bypass 1Kosmos MFA by design — a successful local admin login does not confirm the agent is working correctly.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/authentication/windows-workstation-mfa/installation/post-installation-verification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.