On this page

Hybrid Bridge on Windows

Hybrid Bridge installs as the Windows service TripleCLabsController. It does not require Steiger or WSL unless your implementation includes those separately.

Use the Intel/AMD 64-bit Windows installer. ARM64 users should ask their implementation team for an approved installation route.

1. Save your provisioning bundle

Ask your CoCoCo contact for the bundle assigned to this bridge. Download it to a protected location on the Windows machine. Keep the file exactly as supplied; do not open and resave it in Word. You will select this file during setup, so you do not need to copy its contents into a command.

2. Download the MSI

Download the Hybrid Bridge MSI and its checksums.

To verify the download, open PowerShell and run the following, adjusting the path if you saved the file elsewhere:

Terminal
Get-FileHash "$env:USERPROFILE\Downloads\HybridBridge-2.2.0-x64.msi" -Algorithm SHA256

Compare the displayed hash with the matching filename in checksums.txt. The values must match (letter case does not matter). If they differ, do not run the installer; download it again or contact your implementation team.

3. Install and select your bundle

  1. In File Explorer, double-click the downloaded MSI. Approve administrator access when Windows asks.
  2. Select Install and wait for installation to finish.
  3. On the Finish screen, leave Configure and start using a downloaded bundle selected, then select Finish.
  4. Approve the administrator prompt for Hybrid Bridge Setup. Select your downloaded bundle when the file picker opens.
  5. Wait for setup to confirm that the bridge is configured and its Windows service is running.

This MSI is not digitally signed. Windows or your organisation's security controls may show an unknown-publisher warning or block it. If policy blocks installation, ask your IT/security administrator to approve the deployment. Do not disable organisation-wide protection.

The bundle step is optional. Clear the Finish checkbox or cancel the file picker to configure later using Start → Hybrid Bridge Setup. A new installation remains stopped until configured. If configuration already exists, setup keeps it and starts the existing bridge without asking for another bundle.

The MSI finishing successfully confirms that the software is installed. Wait for the separate setup confirmation before treating configuration as complete. If provisioning fails, ask your contact to check the error before retrying: a one-time bundle may already have been used. If configuration is saved but service startup fails, rerun Hybrid Bridge Setup; it will reuse the saved configuration.

4. Confirm the connection

Open Services from the Windows Start menu and find TripleC Hybrid Bridge (service name TripleCLabsController). It should show Running. Alternatively, in PowerShell:

Terminal
Get-Service TripleCLabsController

Ask your CoCoCo contact to confirm that the bridge appears connected, then test one agreed integration, such as access to the intended system or folder. Service status alone does not verify that integration permissions are correct.

Keep the bundle protected. After successful provisioning, retain or remove the original bundle file according to your organisation's credential-handling policy. Do not delete the generated configuration and certificates in C:\ProgramData\TripleCLabs.