Fix crashes, freezes, and startup problems

Recover the current call

Protect the conversation first. Restore a direct audio path for the participant, then restart Connect in a controlled order so that the calling app does not retain a stale virtual device or session. Keep the original setting noted so an unsuccessful adjustment can be reversed quickly.

• If the window responds, turn CONNECT-ON off before closing it.
• Leave the calling app or switch its microphone back to your physical headset so the call can continue without translation.
• Close Connect completely and reopen it.
• Confirm the physical devices and From/To settings, then run How I Sound? before returning to the call.
• Reopen the calling app if its Connect device list or audio state is stale.

Identify the trigger

The last successful action is often more useful than a generic crash description. Note exactly when the window froze, closed, or stopped responding, then use the matching investigation path below. Confirm the result in a controlled test before moving to the next decision or configuration step.

Reproduce with a minimal setup

A minimal setup reduces competing audio devices, effects, and applications. It helps distinguish a repeatable Connect fault from a conflict introduced by the wider desktop environment. Keep the original setting noted so an unsuccessful adjustment can be reversed quickly. This makes the outcome easier to evaluate, explain, and reproduce across future calls.

• Use one physical headset connected directly.
• Keep one calling app open and close extra browser tabs and audio utilities.
• Turn optional Audio Enhancer features off temporarily.
• Use default voice settings and a simple language pair.
• Test How I Sound? first, then a short call.

If the minimal setup is stable, restore one device or feature at a time.

Choose the correct recovery path

Installation, authentication, billing, and application stability are separate layers. Apply the recovery action that matches the failed layer instead of reinstalling unrelated components. Use the guidance here to make one deliberate change at a time and preserve a clear baseline. Confirm the result in a controlled test before moving to the next decision or configuration step.

• If Connect Mic or Connect Speaker is missing, use audio-driver recovery.
• If sign-in repeatedly expires, sign out and in again; do not uninstall drivers.
• If a feature reports insufficient credits or a plan limit, review Manage rather than reinstalling the app.
• If only one call app freezes, test another integration before changing Connect.

Capture a useful recurrence

In Profile Preferences, enable Report Bugs before reproducing a recurring issue. Record the exact time, last action, selected devices, calling app, translation type, and whether Connect recovered after restart. This makes the outcome easier to evaluate, explain, and reproduce across future calls. Use the guidance here to make one deliberate change at a time and preserve a clear baseline.

Frequently asked questions

These answers clarify which recovery actions are safe and what information makes a recurring stability issue actionable. If the result remains unclear, record the exact behavior and the conditions under which it occurs. This keeps troubleshooting focused and gives support enough context to reproduce the problem.