Troubleshooting: SecureAuth Updater Will Not Launch on IdP Server

Version Affected: All
 
 

Overview

Double-clicking SecureAuthUpdater.exe does nothing, and the updater never launches. Running it from an elevated command prompt or PowerShell — for example with .\SecureAuthUpdater.exe -autorun — shows an unhandled exception in SecureAuthUpdater.ApplianceManager.ListAllRealmPaths(), and the process exits with result code 1.

 

Cause

The SecureAuth Updater requires both SecureAuth0 and SecureAuth1 realms to exist in D:\SecureAuth on the server, and requires that SecureAuth1\bin\ contains the MFC.SecureAuth.License.dll file.

 

Resolution

1. Check D:\SecureAuth for the SecureAuth0 and SecureAuth1 folders.
2. If a folder is missing, create a new realm with that name — this recreates the expected folder structure.
3. If both folders exist, check for MFC.SecureAuth.License.dll in SecureAuth1\bin\.
4. If the folder exists but the file is missing, copy the file into the \bin\ folder. This resolves the issue.

Special Considerations

If a realm does not get created correctly using step 2, contact SecureAuth Support for help creating the realm manually.


 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.