Verify EN

Verify operation — English

Automatic diagnostics

Run the installed verifier:

powershell.exe -ExecutionPolicy Bypass -File "$env:LOCALAPPDATA\PROX2AutoSwitch\Verificar-PROX2-AutoSwitch.ps1"

It checks configuration, detection mode, endpoints and Audio Enhancements state.

Normal manual test

1. Power on/connect the headset.
2. Wait a few seconds. Some Bluetooth devices take longer after reconnecting.
3. Windows should select the headset.
4. Power it off/disconnect it.
5. Once Windows reflects disconnect and two consecutive runtime checks confirm it, Windows should select the fallback.
6. Power it on again and verify the headset is selected again.

The runtime requires two consecutive OFF readings to avoid switching on a one-off bad reading.

Reconfigure test

After changing headset/mode through Reconfigure...:

1. Complete the wizard's ON → OFF → ON cycle.
2. Confirm the tray shows the new headset/fallback.
3. Perform another normal OFF → ON cycle.
4. Choose Exit, start AutoSwitch again and repeat OFF → ON.
5. Inspect config.json: DetectionMode should match the selected path (WindowsEndpoint or LogitechGHub).

This exact flow was hardware-validated with PRO X 2 → Jabra Evolve 65, worker config reload, process restart and another OFF/ON cycle.

Live log

Get-Content "$env:LOCALAPPDATA\PROX2AutoSwitch\autoswitch.log" -Wait -Tail 40

Useful entries:

Reconfigure wizard: ON=Connected OFF=Disconnected ON=Connected (...)
Reconfigured: headset=... fallback=... mode=WindowsEndpoint
Config reloaded (reconfigure).
Output changed -> ...

On timeout, current diagnostics log the last observed state and the endpoints/IDs visible in svcl.

If switching does not happen

• Confirm AutoSwitch is Enabled in the tray.
• WindowsEndpoint: verify Windows really exposes Active ↔ Unplugged/absent.
• PRO X 2: verify G HUB is open and recognizes the headset.
• Run Reconfigure... if Windows recreated/changed the endpoint.
• Do not hand-edit GUIDs except for advanced diagnostics.