Message Body (English – Recommended)
Hello MikroTik Support Team,
We would like to report a limitation and request an enhancement related to Winbox URI handling on Windows.
Current Behavior
When Winbox is launched via a registered URI protocol, for example:
winbox://10.250.113.41
Windows correctly invokes:
winbox64.exe "winbox://10.250.113.41"
However, Winbox does not parse the URI and treats the entire string literally as the address, which results in:
-
Displaying
winbox://10.250.113.41in the Connect To field, or -
An error such as:
ERROR: invalid address - winbox://10.250.113.41
Expected / Desired Behavior
We kindly request that Winbox support basic URI parsing, such that:
-
winbox://10.250.113.41
➜ treated as10.250.113.41 -
Optionally (if acceptable):
winbox://admin@10.250.113.41
➜ Address:10.250.113.41
➜ Login:admin
We fully understand and do not request password support via URI, for security reasons.
Why This Is Important
-
Many ISPs and NOC teams use web-based internal systems (CRM, CSMS, monitoring portals).
-
Launching Winbox directly from these systems would greatly improve workflow efficiency.
-
Currently, achieving this requires an external launcher or agent, which is undesirable and unnecessary if Winbox could handle simple URI parsing internally.
Comparison
Winbox already supports:
winbox64.exe 10.250.113.41
Adding minimal URI parsing logic (strip winbox:// prefix) would align URI usage with existing CLI behavior.
Security Consideration
-
No password handling is requested.
-
Only basic address and optional username parsing.
-
This change does not introduce additional security risks.
Request
Please consider adding native support for the winbox:// URI scheme, with simple argument normalization, in a future Winbox release.
Thank you for your time and continued excellent work.
Best regards,