Troubleshooting Error 1722 – SetupHttpsLogin Failure During GFI Archiver 15.10 Upgrade

Overview

During the installation of GFI Archiver 15.10, the process fails with Error 1722, specifically at the SetupHttpsLogin custom action stage preventing you from loading Archiver. 

Root Cause:

This issue typically stems from a failure in the custom PowerShell script (register-https-login.ps1) used during the installation process to configure HTTPS for Archiver. Potential causes include:

1. Outdated PowerShell version on the Archiver server
2. Permission issues preventing script execution
3. Pre-existing SSL certificate bound to port 443
4. Language mismatch (e.g., server OS in German while script expects English group names)
5. Port 443 verification failure (due to firewall)

• In some cases, if the issue is solely due to a pre-existing SSL certificate, the installation can complete despite the Error 1722 and safely ignored. For all other causes, the underlying problem must be resolved before using Archiver normally.

Solution:

To determine exactly why the installation fails (especially with Error 1722 at SetupHttpsLogin), it's essential to manually execute the script used by the installer and:

Run the Script:

1. Open PowerShell as Administrator

2. Execute the command:
   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass 

3. Navigate to the Archiver directory (adjust if installed elsewhere):

   Set-Location "C:\Program Files\GFI\Archiver"

4. Run the installer script manually:

   .\register-https-login.ps1
5. The error message returned in the console will help pinpoint the issue
   • If the script completes with a successful message, you can continue using Archiver normally.

Troubleshooting Steps

Based on the error return, apply the steps below:

Clean Environment Setup

• Clear %temp% folder: Win + R → %temp% → Delete all files
• Reboot the server
• Ensure no residual GFI services are running (services.msc)

PowerShell Version Check

• Run Get-Host or Get-InstalledModule to verify PowerShell is up to date
• Update if below version 5.1

Port 443 Availability

• Ensure that port 443 is not being blocked by a firewall on the local server or network perimeter. 

  • To check if port 443 is accessible locally:

    1. Open PowerShell as Administrator

    2. Run:

       Test-NetConnection -Port 443 -ComputerName localhost

       • Success: Indicates port 443 is open and not blocked locally

       • Failure: Port 443 is being blocked by Windows Firewall or a security tool

  • If the test fails:

    • Open Windows Defender Firewall settings

    • Allow inbound and outbound traffic on port 443 for all profiles (Domain, Private, Public)

    • Re-run the test to confirm access

• Tip: If your organization uses third-party endpoint protection, ensure it isn’t silently blocking port 443 or IIS from binding to that port.

Language Mismatch Fix (Non-English OS)

• Edit register-https-login.ps1 manually
• Change the group name from "Everyone" to localized equivalent, e.g., "Jeder" for German or as per the system.
• Re-run the script in elevated PowerShell:

  Set-Location "C:\Program Files\GFI\Archiver"
  .\register-https-login.ps1
  

Step 6: Verify Permissions

• Run the installer as Administrator
• Confirm the user has sufficient rights to create bindings and modify IIS settings

After resolving the underlying issues above, you should now be able to run the register-https-login.ps1 manually. You will see a successful message at the bottom of the console, and you can proceed to use Archiver normally or run the installer and continue despite any 1722 Error.