Skip to main content

Windows Error Codes

This page lists all the possible errors returned by HYPR Passwordless for Windows.

Code Prefixes

HYPR Passwordless for Windows error codes begin with 15.

Some of the defined ranges of errors are linked here. The easiest way to find an error is still just to search the page.

Error Prefixes by Component
1520xxx
Registration
1521xxx
Installation Tokens
1522xxx
Audit Events
1523xxx
Log Submission
1530xxx-1590xxx
Miscellaneous

HYPR Passwordless for Windows

CodeErrorCause and Resolution
Back to Top

Registration Error Codes (1520xxx)

1520001DupOOBRegistrationReqProblem
Registration failed. We're already waiting for a device to finish registering for this account, please try again in a minute.
There appears to be an active device registration in progress, or else a previous attempt at registration may not have timed out yet.

What to do?

Wait 3 minutes then try to register again. This should allow enough time for any pending requests to complete. If the error reoccurs, reboot the computer and try again.
1520002OOBClientSetupRequestTimeoutProblem
Registration failed. Something went wrong with that request. Check that you are connected to the Internet, then try again.
The request timed out. Either the registration took longer than the allowed duration, or no response was received from the server or domain controller during one of the steps in the pairing process.

What to do?

1. Make sure the workstation has a reliable network connection then try to register again.
2. If the issue persists, try to register again but proceed as quickly as possible through the pairing process to make sure user speed is not the cause of the issue.
3. If the issue persists, reboot the workstation before trying again.
1520003ServerRequestTimedoutProblem
Registration failed. Something went wrong with that request. Check that you are connected to the Internet, then try again.
The request timed out. Either the registration took longer than the allowed duration, or no response was received from the server or domain controller during one of the steps in the pairing process.

What to do?

1. Make sure the workstation has a reliable network connection then try to register again.
2. If the issue persists, try to register again but proceed as quickly as possible through the pairing process to make sure user speed is not the cause of the issue.
3. If the issue persists, reboot the workstation before trying again.
1520004UnspecifiedRegistration
Registration failed. Something went wrong during device registration. Please try again, or contact support if this keeps happening.
The workstation client isn't configured properly. The cause might be an invalid URL, incorrect app ID, or a problem with one of the other installation parameters.

This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users.

What to do?

1. Verify that all the workstation client configuration parameters are set correctly (RP URL, Application ID, Pinning Key Hash, and Install Token).
2. Check that the user is on a secure network (office or VPN). This will ensure the user is ready to begin pairing.
3. If the issue persists, try to register again but proceed quickly through the pairing process. This will ensure that end user speed is not the cause of the issue.
4. If the issue still persists, contact an admin with troubleshooting information.
1520005UnpairingDeviceFailed
Operation failed. Something went wrong unpairing your device. Please try again.
Failure to deregister a device. This may occur for several reasons, including a delay on the server.

What to do?

1. Wait 2 minutes and then try to deregister again. This should allow enough time for any pending requests to complete.
2. If the issue persists, try to deregister using the mobile app:
* Long press on the workstation icon
* click Computer Details
* Delete the connected device
1520006UnsecureRegistrationFailed
Registration failed. Something went wrong during device registration. Please try again on your company's intranet or over a secure network. Contact Support if this keeps happening.
The workstation isn't on an authorized network, which prevents the pairing process from generating a certificate with the domain. This issue may also be experienced when proxies are involved in the routing connection.

What to do?

1. Make sure the workstation is connected to the correct network (office or VPN) then try to register again.
2. If the issue persists, try to register again but proceed as quickly as possible through the pairing process to make sure user speed is not the cause of the issue.
3. If the issue persists, reboot the workstation before trying again.
1520007SecurityKeyCertificateWriteFailure
Registration failed. Something went wrong with that request. Failed to write the certificate to the Security Key.
What to do?

Retry updating the certificate on the security key. If you cannot remember the PIN, contact an admin for assistance and a possible factory reset.
1520008SecurityKeyGenerationFailure
Registration failed. Something went wrong with that request. Failed to generate key pair on the Security Key.
What to do?

Retry pairing with the security key. If the issue persists, contact an admin for assistance.
1520009QrFallbackNotAvailable
QR Fallback is not available.
Contact an administrator to verify that QR Fallback is enabled for the RP Application in use.
Back to Top

Installation Token Error Codes (1521xxx)

1521001CcTokenInstallTokenExchangeUnknownServerError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
There was a problem with the API endpoint protection token exchange request.

What to do?

Check the HyprOneService log files on the workstation for more information
1521002CcTokenInstallTokenEmptyError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
The workstation client does not have an API endpoint protection Install Token.

What to do?

Verify that the Install Token value in the workstation client install parameters is set correctly
1521003CcTokenFailedSaveError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
The workstation failed to save an API endpoint protection Exchange Token to replace the Install Token.

What to do?

Check the HyprOneService log files on the workstation for more information
1521004CcTokenInstallExchangeError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
The API endpoint protection token exchange request didn't return a valid Exchange Token.

What to do?

Check the HyprOneService log files on the workstation for more information
1521005CcTokenInstallExchangeExceptionError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
Exception processing the API endpoint protection token exchange response.

What to do?

Check the HyprOneService log files on the workstation for more information
1521006CcTokenHttp401UnauthorizedError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
The API endpoint protection Exchange Token is invalid.

What to do?

If the Install Token is still active and valid, the workstation should reacquire an Exchange Token on the next HTTP request.
1521007CcTokenHttp403ForbiddenError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
Access to the API endpoint protection Exchange Token denied due to a deviceID, rpAppId, or machineId mismatch.

What to do?

If the Install Token is still active and valid, the workstation should reacquire an Exchange Token on the next HTTP request.
1521008CcTokenInstallTokenInvalidOrExpiredError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
Invalid or expired API endpoint protection Install Token.

What to do?

Provide a new Install Token value in the workstation client configuration settings
1521009CcTokenInstallTokenForbiddenError
Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
Access to the API endpoint protection Install Token denied due to a deviceID, rpAppId, or machineId mismatch.

What to do?

Provide a new Install Token value in the workstation client configuration settings.
1521010CcTokenInstallUpdateFailed
Registration failed.
The attempt to update the Install Token did not succeed.
What to do?

Provide a new Install Token value in the workstation client configuration settings. It may be necessary to contact an administrator to edit your HYPR Passwordless installation parameters and/or reinstall HYPR Passwordless.
1521011CcTokenInstallUpdated
Install Token Updated.
Install Token successfully updated.
Back to Top

Audit Event Error Codes (1522xxx)

1522001InvalidPin
Operation failed. Invalid PIN entered.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522002FailedToUpdatePin
Operation failed. Failed to update PIN.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522003FailedToVerifyPin
Operation failed. PIN verification failed.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522004CertificateError
Operation failed. Certificate error.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522005FailedToEnrollSecurityKey
Operation failed. Failed to enroll Security Key.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522006FailedToResetSecurityKey
Operation failed. Failed to reset Security Key.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522007FailedToVerifyManagementKey
Operation failed. Management key verification failed.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522008InstallError
Operation failed. Error during install/uninstall.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522009ConfigurationError
Operation failed. Configuration error.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522010CryptoManagerError
Operation failed. Error reported by CryptoManager.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522011ServiceStartStopFailed
Operation failed. Error during service start/stop.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522012LockException
Operation failed. Exception during workstation lock.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522013UnlockException
Operation failed. Exception during workstation unlock.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522014RegisterWorkstationFailed
Operation failed. Failed to register workstation.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522015DeregisterWorkstationFailed
Operation failed. Failed to deregister workstation.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522016FailedToGeneratePin
Operation failed. Failed to generate PIN/token.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522017FailedToLoadStoredData
Operation failed. Failed to load stored data.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522018RegisterDeviceFailed
Operation failed. Failed to register device.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522019DeregisterDeviceFailed
Operation failed. Failed to deregister device.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522020FailedToUnenrollSecurityKey
Operation failed. Failed to unenroll Security Key.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522021OfflineAuthenticationFailed
Authentication failed. Failed to authenticate with offline token or recovery PIN.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522022FailedToCompleteAuthentication
Authentication failed. Failed to complete authentication.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522023FailedToCancelAuthentication
Authentication failed. Failed to cancel authentication.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522024UserPresenceFailed
Operation failed. User presence failed.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522025TryingRestApiPolling
Status update. Trying to switch to REST API polling due to WebSocket errors.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522026SwitchedToRestApiPolling
Status update. Successfully switched from WebSocket to REST API polling.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522027TryingWebSocket
Status update. Trying to switch from REST API polling back to WebSocket.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522028SwitchedBackToWebSocket
Status update. Successfully switched from REST API polling back to WebSocket.
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure.
1522029SmartKeyLogon
Status update. Successful workstation logon with Smart Key.
This error code is used only for log analytics and isn't displayed in the user interface. The event fields will contain information about the specific user and key. isSuccessful will be true.
1522030SmartKeyUnlock
Status update. Successful workstation unlock with Smart Key.
This error code is used only for log analytics and isn't displayed in the user interface. The event fields will contain information about the specific user and key. isSuccessful will be true.
1522031FailedToDecryptLoginCert
Failed to decrypt login certificate.
The workstation failed to decrypt the login certificate presented by the mobile device. Could be caused by a problem on the mobile device, but workstation problems are more likely. The workstation's private keys may be damaged, or the TPM may have been reset. Also seen after doing P2V migration of a PC with a TPM. Even if the VM has a virtual TPM, the keys stored on the PC's TPM can't be migrated.

What to do?

Most likely HYPR Passwordless will need to be uninstalled and reinstalled. User will need to re-pair their mobile device(s).
1522032InvalidSsoRequest
Invalid SSO request.
The workstation received an invalid Desktop SSO request.

What to do?

Collect HYPR logs from workstation and escalate to Engineering.
1522033SsoNotSupported
SSO is not supported.
Either HYPRspeed/Desktop SSO or Endpoint API Security is disabled.

What to do?

Contact HYPR Support to enable the correct features for this flow. If enabling Endpoint API Security for the first time, all users will need to uninstall and re-install HYPR Passwordless for Windows.
1522034InternalErrorDuringSso
Internal error during SSO processing.
An unexpected exception occurred during SSO operation.

What to do?

Collect HYPR logs from workstation and escalate to Engineering.
1522035NoSessionForSso
Last logon/unlock was not performed with HYPR.
SSO doesn't work if last login/unlock used a security key or password.

What to do?

Lock the workstation and then unlock using the HYPR Mobile App.
1522036ServerRejctedSso
Server rejected SSO.
The server rejected the SSO attempt. Most likely cause is that too much time has elapsed since login/unlock with the HYPR Mobile App.

What to do?

Lock the workstation and then unlock using the HYPR Mobile App. Open web browser and attempt SSO as soon as possible after unlocking.
1522037FailedToSaveDevice
Failed to save device data.
An error occured while adding a newly registered security key to the paired device database.

What to do?

This really shouldn't fail. It is likely that something is very wrong with the workstation. Check Windows event logs.
1522038FailedToSavePINs
Failed to save offline/recovery PIN data.
An error occured while saving recovery PINs for a newly registered security key.

What to do?

This really shouldn't fail. It is likely that something is very wrong with the workstation. Check Windows event logs.
1522039EnrollmentServiceError
The enrollment service encountered an error that wasn't directly associated with a request.
Internal error in the Enrollment Service.

What to do?

Collect HYPR logs from enrollment server and escalate to Engineering.
1522040FailedToEnrollCertificate
The enrollment service was unable enroll a user certificate.
Error during certificate enrollment.

What to do?

Collect HYPR logs from enrollment server and escalate to Engineering.
1522041FailedToRevokeCertificate
The enrollment service was unable revoke a user certificate.
Error during certificate revocation.

What to do?

Collect HYPR logs from enrollment server and escalate to Engineering.
1522042LoginCertificateExpired
Login certificate has expired.
The 'extendedMessage' event field will contain information about the certificate.

What to do?

If problem is persistent or affects multiple users, collect HYPR logs from phones and workstations and escalate to Engineering.
1522043SslPinsUpdated
SSL Pins updated.
New SSL Pins received from server.
1522044FailedToUpdateSslPins
Failed to update SSL Pins.
New SSL Pins received from server are invalid.
1522045BlockedPuk
Blocked the security device PUK.
This error code is used only for log analytics and isn't displayed in the user interface. The 'extendedMessage' event field will contain the security device serial number. 'isSuccessful' will be true.
1522046ChangedPuk
Changed the security device PUK.
A random PUK was assigned, and will be sent to CC as part of the enrollment. If the user forgets their PIN, an administrator can retrieve the PUK from CC, and the PUK can be used to set a new PIN.

This error code is used only for log analytics and isn't displayed in the user interface. The 'extendedMessage' event field will contain the security device serial number. 'isSuccessful' will be true.
1522047FailedToBlockPuk
Failed to block the security device PUK.
This error code is used only for log analytics and isn't displayed in the user interface. The 'extendedMessage' event field will contain information about the specific failure. 'isSuccessful' will be false.
1522048FailedToChangePuk
Failed to change the security device PUK.
This error code is used only for log analytics and isn't displayed in the user interface. The 'extendedMessage' event field will contain information about the specific failure. 'isSuccessful' will be false.
1522049CreatedFido2UsbHidDevice
Successfully created FIDO2 USB HID device.
This error code is used only for log analytics and isn't displayed in the user interface. 'isSuccessful' will be true.
1522050DeletedFido2UsbHidDevice
Successfully deleted FIDO2 USB HID device.
This error code is used only for log analytics and isn't displayed in the user interface. 'isSuccessful' will be true.
1522051PinUpdatedWithPuk
PIN successfully updated using Unlock Code.
This error code is used only for log analytics and isn't displayed in the user interface. 'isSuccessful' will be true.
1522052FailedToUpdatePinWithPuk
Failed to update PIN using Unlock Code.
This error code is used only for log analytics and isn't displayed in the user interface. The 'extendedMessage' event field will contain information about the specific failure. 'isSuccessful' will be false.
1522053FailedToRestorePriorPuk
Failed to restore prior PUK - PUK saved by CC is now incorrect.
The security device PUK was changed to a new random value. That value couldn't be saved by CC, and the original value couldn't be restored. The net result is that device no longer has a usable PUK. If PIN is ever lost or locked, the device will need to be reset (security key) or replaced (smart card).

This error code is used only for log analytics and isn't displayed in the user interface. The 'extendedMessage' event field will contain the security device serial number. 'isSuccessful' will be false.
1522054FailedToSetPinPukRetries
Failed to set PIN/PUK retry attempts.
A failed attempt was made to set the security device's PIN or PUK. Please try again; if the issue continues, contact an administrator.
Back to Top

Log Submission Error Codes (1523xxx)

1523001LogSubmissionSuccess
Workstation logs submitted.
Workstation log files were successfully submitted.
1523002LogSubmissionFailed
Log submission failed. Failed to submit log files.
This error code is used with failure Audit Events and is intended for log analytics. It isn't displayed in the HyprUnlock user interface. This code is used when a more specific error code isn't available (1523003, 1523004, or 1523005). Consult the message and extendedMessage Event fields for information about the specific failure.
1523003HyprLogCollectionFailed
Log submission failed. Failed to collect HYPR log files.
This error code is used with failure Audit Events and is intended for log analytics. It isn't displayed in the HyprUnlock user interface. This code indicates a failure while collecting HYPR application logs. Consult the message and extendedMessage Event fields for information about the specific failure.
1523004WindowsLogCollectionFailed
Log submission failed. Failed to collect Windows Event Logs.
This error code is used with failure Audit Events and is intended for log analytics. It isn't displayed in the HyprUnlock user interface. This code indicates a failure while collecting Windows event logs. Consult the message and extendedMessage Event fields for information about the specific failure.
1523005LogUploadFailed
Log submission failed. Failed to upload log files.
This error code is used with failure audit events and is intended for log analytics. It isn't displayed in the HyprUnlock user interface. This code indicates a failure while uploading the collected logs to the RP Server. Consult the message and extendedMessage Event fields for information about the specific failure.
Back to Top

Miscellaneous Errors (1530xxx)

1530001AuthenticationFailed
Registration failed. The password you entered is incorrect.
If the Require User Presence option is turned on in the Control Center, users must type in their current password when pairing a device to validate that they are the employee who is logged into the workstation. When this is incorrectly entered, for example if a rogue or malicious user tries to register on a colleague's unlocked workstation, the pairing process will not complete.

What to do?

Use the correct password for the user in question.
1530002PinLocked
Operation failed. Too many failed attempts. Your security key PIN is locked. Please contact Support for assistance.
An invalid security key PIN was entered while pairing or logging in. In contrast to HYPR Mobile App users, security key users are required to enter a PIN to accomplish multifactor authentication.

What to do?

1. Use an administrator-provided management PIN or a backup PIN method at the next attempted login session.
2. If you do not have a secondary method to use your security key, reach out to your Support team for further assistance.
1530003PukLocked
Too many failed Unlock Code attempts. Security Device can't be unlocked. Please contact support for assistance.
Security device is permanently locked, cannot be reset, and will need to be replaced.
Back to Top

Miscellaneous Errors (1540xxx)

1540001RegistrationCancelled
Registration failed. You cancelled the registration process so this device was not set up.
The pairing process was manually canceled. Typically this is a user-chosen action.

What to do?

1. If the pairing process was inadvertently canceled, wait 2 minutes and before attempting to pair the device again. This should allow enough time for any pending requests to complete.
2. If the issue persists without manual cancellation, identify at what step in pairing the action canceled and inform your Support team.
1540002BiometricRegistrationFailed
Biometric registration failed.
Biometric device was successfully paired using PIN, but fingerprint registration failed.

What to do?

Wait 1 minute, then try to pair with your fingerprint again.

If the problem persists, verify your fingerprint is registered with your device, and try again.
1540003SecurityDevicePairingDisabled
Security Device registration failed.
Pairing of new security devices is disabled.

What to do?

Please contact support for assistance.
1540004SecurityDeviceValidationFailed
Security Device validation failed.
Unable to validate serial number.

What to do?

Please contact support for assistance.
1540005SecurityDeviceRejectedByServer
Security Device rejected.
Enrollment of this security device was rejected by the server.

What to do?

Please contact support for assistance.
1540006FingerprintAdditionFailed
Biometric registration failed.
Unable to register fingerprint.

What to do?

Please contact Support for assistance.
1540007PukUpdateFailed
Security Device update failed.
Failed to notify server of PUK update.

What to do?

Please contact support for assistance.
Back to Top

Miscellaneous Errors (1550xxx)

1550001CertTemplateNameInvalid
Registration failed. Something went wrong with that request. Please try again, or contact Support if this keeps happening.
This error indicates that the workstation client may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users.

This can be caused by an invalid certificate template name during enrollment or that the certificate template does not exist.

What to do?

1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing.
2. If the issue persists, guide the user to reboot the workstation before trying again.
3. If the issue persists, an admin can check the registry editor to see the configured certificate template, and make sure the name matches the configuration in the AD Certificate Authority configuration.
1550002CertTemplateAccessDenied
Registration failed. Something went wrong with that request. Please try again, or contact Support if this keeps happening.
The user isn't authorized to enroll a certificate for the certificate template type.

What to do?

1. Check that the user is on a secure network (office or VPN) and try again. This will ensure the user is ready to begin pairing.
2. If the issue persists, reboot the workstation before trying again.
3. If the issue still persists, contact an administrator and have them try these steps:
* Select the User template in AD
* Add the user to the Group or user names list under Properties > Security in the template
* Click Enroll and try again
1550003CertTemplateCAunavailable
Registration failed. Something went wrong with that request. Please try again, or contact Support if this keeps happening.
The workstation client isn't configured properly. This is typically not a production issue and is usually only experienced during sandbox or deployment testing by internal or pilot users.

This can be caused by Active Directory Certificate Service (AD CS) not working properly.

What to do?

1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing.
2. If the issue persists, guide the user to reboot the workstation before trying again.
3. If the issue persists, an admin may analyze HYPROneService log for more information and ensure that certificate for this user can be issued from the Certificate Authority.
1550005HashMismatch
Registration failed. Something went wrong with that request. Your admin will need to verify configuration of the application. Please contact Support.
The workstation client isn't configured properly. This is typically not a production issue and is usually only experienced during sandbox or deployment testing by internal or pilot users.

This can be caused by the value of the public key pinning having been set to an invalid entry.

What to do?

1. An admin may validate that the correct value is set for a user or whether a new value needs to be set. In the event that a new value in set, it is recommended to restart the HYPR service or reboot the machine following the change prior to trying to pair again. Once ready to pair, check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing.
2. If the issue persists, an admin may analyze HYPROneService log for more information and ensure that a certificate for this user can be issued from the Certificate Authority.
1550006NotConfigured
Registration failed. Something went wrong with that request. Your admin will need to verify configuration of the application. Please contact Support.
This error indicates that the workstation user may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users.

This can be caused by the registry values having been set to an invalid entry or having experienced an issue during installation or upgrade.

What to do?

1. An admin may validate that the correct values reside in the user's registry editor is set for a user or whether a new value needs to be set. In the event that a new value in set, it is recommended to restart the HYPR service or reboot the machine following the change prior to trying to pair again. Once ready to pair, check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing.
2. If the issue persists, an admin may analyze HYPROneService log for more information and ensure that a certificate for this user can be issued from the Certificate Authority.
1550007UnknownConnectionFailure
Registration failed. Something went wrong with that request. Your admin will need to verify configuration of the application. Please contact Support.
Indicates an unknown event. Generally a user may retry the pairing or authentication and proceed successfully but may need further troubleshooting in the case where this issue is caused by a current or change in the enterprise environment.

This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users.

What to do?

1. Check that the user is on a secure network (office or VPN) before pairing. This will ensure the user is ready to begin pairing.
2. If the issue persists, an admin may analyze HYPROneService log for more information and ensure that a certificate for this user can be issued from the Certificate Authority.
1550008NoInternetConnection
Registration failed. Your computer appears to be offline. Please check this computer's network connection and try again.
The workstation client does not detect an internet connection.

What to do?

1. Check that the user is on a secure network (office or VPN) before pairing. This will ensure the user is ready to begin pairing.
2. Validate that the user can open a webpage that is not cached and will successfully load on their workstation. Then have the user try to pair with HYPR.
3. If the issue persists, restart the HYPR service from services.msc and try to pair again.
4. If the issue persists, an admin may analyze HYPROneService log for more information and ensure that a certificate for this user can be issued from the Certificate Authority.
1550009DomainAccountRegistrationDenied
Registration failed. The current configuration is not compatible with your domain. Please contact Support for more information.
The workstation client isn't configured properly. This is typically not a production issue and is usually only experienced during sandbox or deployment testing by internal or pilot users.

This can be caused by the Control Center settings being in conflict with the type of end user seeking to pair and use the product.

What to do?

An admin may need to validate on the Control Center that workstation login is enabled. If it is not enabled, it is likely that a domain user is attempting to enroll and that functionality is not supported when the toggle is disabled. Once this is updated, the end user should be able to seamlessly pair with success.
1550010LocalAccountRegistrationDenied
Registration failed. A domain user account is required. Please contact support for more information.
The user is trying to enroll a security key using a local user account.

What to do?

Log in as a domain user. Windows doesn't support security keys with local accounts.
1550011InvalidAzureUserConfiguration
Registration failed.
Azure AD User requires that FIDO2_MOBILE_AUTHENTICATOR feature flag be enabled.

What to do?

Please contact Support.
1550012AzureSecurityKeyRegistrationFailed
Operation/Registration failed.
The FIDO2 security key could not be registered with Entra ID. Please contact Support.
Back to Top

Miscellaneous Errors (1570xxx)

1570001ConnectionError
Operation failed. Something went wrong with that request. Check that you are connected to the Internet, then try again.
The workstation client does not detect an internet connection.

What to do?

1. Check that the user is on a secure network (office or VPN) before pairing. This will ensure the user is ready to begin pairing.
2. Validate that the user can open a webpage that is not cached and will successfully load on their workstation. Then have the user try to pair with HYPR.
3. If the issue persists, restart the HYPR service from services.msc and try to pair again.
4. If the issue persists, an admin may analyze the HYPROneService log for more information and escalate as needed.
1570002UnknownErrorMsg
Operation failed. Something went wrong with that request. Please try again, or contact support if this keeps happening.
The workstation client experienced an issue with the network.

What to do?

1. Check that the user is on a secure network (office or VPN) before pairing. This will ensure the user is ready to begin pairing.
2. Validate that the user can open a webpage that is not cached and will successfully load on their workstation. Then have the user try to pair with HYPR.
3. If the issue persists, restart the HYPR service from services.msc and try to pair again.
4. If the issue persists, an admin may analyze HYPROneService log for more information and escalate as needed.
1570003HyprServiceDownMsg
Operation failed. Something went wrong with that request. Please reboot your computer and try again, or contact support if this keeps happening.
The workstation client experienced an unrecoverable error.

What to do?

1. Restart the HYPR service from services.msc and try to pair again. If the user cannot restart the HYPR service, ask the user to reboot their workstation.
2. If the issue persists, an admin may analyze HYPROneService log for more information and escalate as needed.
Back to Top

Miscellaneous Errors (1580xxx)

1580001StoreReenrollmentCertError
Reenrollment failed. Failed to store reenrollment certificate.
Back to Top

Miscellaneous Errors (1590xxx)

1590001RequestQrCodeLowApiVersion
Registration failed. We could not reach the server to start the pairing process. Please try again, or contact support if it keeps happening.
The Control Center API version is less than 4 or not defined and a QR code cannot be generated.

What to do?

Validate the Server version and update if necessary.
1590002RequestQrCodeUnknownServerError
Registration failed. We could not reach the server to start the pairing process. Please try again, or contact support if it keeps happening.
The Control Center failed to generate a QR code.

What to do?

Check the Control Center Audit Trail or logs.
1590003RequestQrCodeRFC7807UnsupportedVersion
Registration failed. We could not reach the server to start the pairing process. Please try again, or contact support if it keeps happening.
The Control Center believes the workstation client doesn't support QR code functionality

What to do?

Validate the workstation client version and update if necessary.
1590004RequestQrCodeUnknownError
Registration failed. We could not reach the server to start the pairing process. Please try again, or contact support if it keeps happening.
A problem occurred during QR code request and response processing.

What to do?

Analyze the HyprOneService logs to see if there's a Control Center issue.