Let’s get your links moving.
Start with the handoff, check the target, then collect only the diagnostic information you need.
Start with the setup guide
Understand the fallback browser and Windows HTTP/HTTPS associations before troubleshooting. Read the setup sequence.
A link opens in another browser
- Check the relevant default association in Windows Settings → Apps → Default apps.
- Confirm the source app uses the Windows default rather than an embedded viewer or its own browser preference.
- Test the configured target from Browter’s settings. A label alone does not prove its executable and profile arguments are correct.
- Check whether the app is paused, gaming mode is active or the armed selection has expired.
The shortcut does not show the wheel
The default is Alt + Q. The wheel needs at least two enabled browser/profile entries. Check the configured shortcut, possible conflicts and the app’s state. Gaming mode intentionally disables the hotkey. Also check that the trial is active or the app is purchased. If a source app has its own browser preference, use that app’s settings to choose Windows defaults where available.
Share diagnostics carefully
Disable verbose logging, use Settings → Open logs, and review the files before sharing. Verbose logs can contain complete private addresses. Ordinary diagnostics omit credentials, paths, queries and fragments, but hosts can still be sensitive.
Describe the app version, Windows version, source app, intended browser/profile and observable result. Do not publish credentials, private client URLs or unreviewed logs.