> 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/faqs.md).
# FAQs
Does the Windows Workstation MFA agent work with third-party disk encryption software or other credential providers?
The Windows Workstation MFA agent permits the use of Trellix Drive Encryption (TDE) on workstations as per organizational policies and guidelines. However, you must update your registry settings to whitelist the TDE, as third-party credential providers will be blocked during system startup or restart.
Does the Windows Workstation MFA agent work with third-party disk encryption software or other credential providers?
The Windows Workstation MFA agent permits the use of Trellix Drive Encryption (TDE) on workstations as per organizational policies and guidelines. However, you must update your registry settings to whitelist the TDE, as third-party credential providers will be blocked during system startup or restart.
Which Vault does the Windows Workstation MFA agent support?
The Windows Workstation MFA agent supports fetching passwords for service accounts only from CyberArk vaults.
Where do I configure the Vault details?
You can configure the CyberArk connection details in the Windows Workstation MFA agent registry. This includes the vault URL, vault service account, and vault credentials. On the next launch, after vault details are updated, the 1Kosmos Windows MFA agent will read the data from the registry and encrypt data. Registry Path:
`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{90576E81-DDF8-4E8E-91E2-CA3A9CE52410}`
How do I update the registry?
The registry can be updated through SCCM / GPO policy by the organization OR can be handled through the **BlockIDInstaller.bat** script with the `-configure` directive.
---
# 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/faqs.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.