This article explains why the following errors occur when attempting to install the Windows Credential Provider (RDP) agent during both Graphical User Interface (GUI) and Command Line Interface (CLI) installations:

• Error 1: Error 1001. Failed to validate configuration. ClientID or ClientSecret are not valid
  

• Error 2: Error 1001. Failed To Validate Configuration. URL Is Not Valid.
  

• Error 3: Error 1001. Exception occurred while initializing the installation: System.IO.FileNotFoundException: Could not load file or assembly...
  

• Error 4: Error 1001. An exception occurred during the Commit phase of the installation. This exception will be ignored, and installation will continue. However, the application might not function correctly after installation is complete. --> Specified cast is not valid.
  
  
• Error 5: Error 1001. InstallUtilLib.dll:CorBindToRuntimeHost (hr=0x80070003): The system cannot find the path specified.

• Windows Credential Provider (RDP)
• Okta Identity Engine (OIE)
• Multi-Factor Authentication (MFA)
• Error 1001

Error 1

Error 1001. Failed to validate configuration. ClientID or ClientSecret are not valid. 

This error generally occurs if the Client ID or Client Secret is incorrect. If the error occurs with known, valid credentials, a delay or blockage in communication during the installation process may prevent the client from communicating with Okta. Potential blockers include:

• Tunneling
• Proxies
• Secure Sockets Layer (SSL) inspections
• Firewall rules

If none of these blockers are present, the request may not arrive with a correct timestamp. Okta rejects requests with incorrect timestamps as a preventive measure. Time skew on the server, even by a few seconds, can cause this error.

Error 2

Error 1001. Failed To Validate Configuration. URL Is Not Valid.

This error may appear because *.okta.com has not been added to the trusted sites.

Error 3

Error 1001. Exception occurred while initializing the installation: System.IO.FileNotFoundException: Could not load file or assembly...

 

This error may appear because the user performing the installation does not have the necessary permissions to install in the target folder. 

Error 4

Error 1001. An exception occurred during the Commit phase of the installation. This exception will be ignored and installation will continue. However, the application might not function correctly after installation is complete. --> Specified cast is not valid.

This error is known to be caused by misconfigured registries, where a registry entry is set as a string instead of a DWORD.

Error 5

Error 1001. InstallUtilLib.dll:CorBindToRuntimeHost (hr=0x80070003): The system cannot find the path specified.

This error typically occurs when a customer has an Endpoint Protection or Behavioral Monitoring product, such as SentinelOne, installed and active on their Windows Server. These may intervene at the point where the Windows Installer tries to execute a .NET custom action using InstallUtilLib.dll. Endpoint Detection and Response (EDR) solutions are particularly aggressive toward these actions because malware often utilizes installation scripts and custom actions to deeply embed itself within the operating system.

Error 1

Error 1001. Failed to validate configuration. ClientID or ClientSecret are not valid. 

1. During Windows Credential Provider (RDP) installation, if any middleware is used for network traffic, temporarily disable it. Re-enable the middleware after the installation is complete, or configure the middleware to ignore Okta traffic on the server side. (Consult with an internal Network Team for assistance with middleware configuration).
2. Check for time skew on the server. If the server time is incorrect, it must be corrected.

Error 2

Error 1001. Failed To Validate Configuration. URL Is Not Valid.

1. Add *.okta.com to the trusted sites. This can be done by navigating to Internet Options > Security > Trusted sites.
2. Go to Settings > System > Apps & features, then uninstall the Okta Windows Credential Provider.
3. Execute the standard installation by running setup.exe as Administrator.
4. Ensure the organization's Uniform Resource Locator (URL) is added in the format https://<example.okta.com>, without a trailing slash (/).
5. If the issue persists, run the script provided in the documentation titled RDP Error "Multi Factor Authentication Failed" - System.Net.WebException - SSL/TLS Negotiation Errors.

Error 3

Error 1001. Exception occurred while initializing the installation: System.IO.FileNotFoundException: Could not load file or assembly...

1. Navigate to the folder path indicated in the error message.
2. Verify that the user account performing the installation has read and write permissions for this folder.
3. Add the necessary permissions if they are missing.
4. Attempt to reinstall the agent.

Error 4

Error 1001. An exception occurred during the Commit phase of the installation. This exception will be ignored and installation will continue. However, the application might not function correctly after installation is complete. --> Specified cast is not valid.

1. Open the registry (admin rights needed): Start > Run > regedit.
2. Review the registry entry for registry: SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceAutoLogon.
3. This key should be a DWORD, and not a string. If the value shows as a string, delete the entry and recreate it as a DWORD value.
4. Reinstall the Okta MFA Credential Provider. 

Alternatively, follow the steps below:

1. Uninstall the Okta MFA Credential Provider entirely.
2. Review the installation path and remove any residual entries (reboot preferred after uninstall).
3. Perform a fresh install of the Okta MFA Credential Provider.

Error 5

Error 1001. InstallUtilLib.dll:CorBindToRuntimeHost (hr=0x80070003): The system cannot find the path specified.

The solution is to temporarily disable the Endpoint Protection, Behavioral Monitoring, or EDR product. To prevent this issue in the future, they should add an Exclusion in their EDR policy.