Troubleshooting: TwinPane not connecting (Client and Server)

Diagnose and fix TwinPane Client and Server connection issues across AVD, RDS, RemoteApp, and Citrix environments.

Use this guide when TwinPane appears installed but the Client and Server do not connect.

Symptoms

  • Local file opening does not trigger.
  • Mirror Mode does not populate local folders in the remote session.
  • Client or Server UI shows disconnected/inactive state.

1. Confirm both components are installed

Verify:

  • TwinPane Client is installed on the local user device.
  • TwinPane Server is installed on the remote host/session environment.

If needed, reinstall silently with known-good commands from Silent install (Client and Server).

2. Validate licensing and registry values

Check license and install path values:

  • HKLM\SOFTWARE\FileSyncBridge\Client
  • HKLM\SOFTWARE\FileSyncBridge\Server

Required values should exist and be non-empty (especially LicenseKey and InstallPath).

Reference: Registry keys (Client and Server).

3. Validate environment pairing assumptions

Connection requires an active remote session path between:

  • Local endpoint running TwinPane Client.
  • Session host running TwinPane Server.

If users connect through multiple host pools or published app routes, validate they are landing on hosts where TwinPane Server is installed.

4. Confirm startup context

TwinPane components generally run in user context. Confirm:

  • User is fully signed into Windows.
  • Any startup entry expected by policy is present.
  • Security tools are not delaying execution at logon.

For managed rollout, align startup behavior through your endpoint tooling and policy baseline.

5. Check policy and security controls

Common blockers:

  • Endpoint hardening prevents process launch.
  • Application control policy blocks unsigned/unknown binaries (verify your allow rules).
  • Session environment restrictions prevent expected host-side execution flow.

Coordinate with security policy owners before broad rollout.

6. Isolate with a known-good pilot pair

Create one controlled test pair:

  1. One local device.
  2. One remote host.
  3. Fresh install on both sides.
  4. Verified license key.

If pilot works, issue is usually collection scope, policy variance, or assignment targeting in production.

7. Deployment-channel checks

If using Intune:

  • Confirm assignment includes affected users/devices.
  • Confirm detection rules are correct and not causing install loops.

If using SCCM:

  • Confirm content is on all required distribution points.
  • Confirm deployment type detection logic is stable.

See:

8. Escalation bundle to collect

Before escalation, collect:

  • Affected environment type (AVD/RDS/RemoteApp/Citrix).
  • Client and Server install versions.
  • Confirmation of license key presence in registry.
  • Screenshot or exact wording of connection status/errors.
  • Whether issue reproduces in the known-good pilot pair.

Send findings to support@twinpane.com with subject: TwinPane connection troubleshooting.

Related guides

Related guides

Group Policy rollout for registry defaults

Configure TwinPane default settings at scale using Group Policy registry preferences for HKLM and HKCU paths, including license and server behavior flags.

Intune deployment for TwinPane (Win32 app step-by-step)

Deploy TwinPane Client and Server through Microsoft Intune as Win32 apps, including install commands, detection rules, assignment strategy, and rollout tips.

Registry keys (Client and Server)

Reference for the Windows registry keys and values used by TwinPane Client and Server for settings, license, and deployment.