Arch Linux User Repository

The download URL for winbox64.exe has changed. The new URL is: https://download.mikrotik.com/routeros/winbox/3.40/winbox64.exe.

diff --git a/PKGBUILD b/PKGBUILD
index a52f18c..e037d63 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -13,7 +13,7 @@ optdepends=(
   'ttf-ms-fonts: for better fonts'
 )
 install=${pkgname}.install
-source=("${pkgname}-${pkgver}.exe::https://download.mikrotik.com/winbox/${pkgver}/${pkgname}64.exe"
+source=("${pkgname}-${pkgver}.exe::https://download.mikrotik.com/routeros/winbox/${pkgver}/${pkgname}64.exe"
         "${pkgname}.desktop"
         "${pkgname}.png"
         "${pkgname}")

@yanboyang713 Remove sudo from the command. I'm not sure if it will resolve your problem, but regardless you shouldn't run it as root.

I get two error msg below. I don't know what is that.

yanboyang713@Meta-Scientific-Linux ~ % sudo winbox
[sudo] password for yanboyang713:
creating Window Class routeros_null
creating Window Class routeros_connect
DPI=96
EMS=13
ERROR: bad bmp format id=2329
biPlanes=1, biBitCount=1, biCompression=0
ERROR: bad bmp format id=3329
biPlanes=1, biBitCount=1, biCompression=0
creating Window Class routeros_dbl_canvas
rescaleDPI starting-dpi=96, zoom=0 result=96
 discovery started
rescaning
connecting to 10.153.63.255
connecting to 172.17.255.255

For configuring HiDPI run:

WINEPREFIX=$HOME/.winbox/wine /usr/bin/winecfg

and change the "Screen resolution dpi" setting found in the "Graphics" tab

WinBox dropdown

Thanks for explaining. When I clicked earlier, nothing happened (because ad blocker) so I assumed I was already in the right place.

Would someone mind explaining the versioning to me? This package is 3.40, but on the website, all I see are 6.x/7.x. Thanks.

6.x/7.x are RouterOS versions, not WinBox. If you click the WinBox dropdown on this page, you will see WinBox 3.40 downloads for x64 and x86_64.

Would someone mind explaining the versioning to me? This package is 3.40, but on the website, all I see are 6.x/7.x. Thanks.

After the one time it had the checksum on the PKGBUILD of 3.40-1 it flipped back (to what turns out to be the right one then). Checking again right now, it's still incredibly slow/unstable to download but the checksum has, aside from that one time, always ended up as 91f7b0456619dbfc19940a85566c949ce3718321f32709886df5125c71f0b6b7.

It's good to have confirmation which one is supposed to be the right one (they should really have this on their website or forum release posts honestly...). Now it's not really a gamble any more whether we'd be running something invalid or not.

FWIW, I have been able to reproduce the issue where it throws ERROR: One or more files did not pass the validity check!. I am using yay on EndeavourOS and have been able to delete ~/.cache/yay/winbox and it works the second time, every time. I'm not sure it's a Mikrotik issue, or it would not work so reliably after wiping cache.

Also, this issue reoccurred at 10:00PM PST 10/23, so Mikrotik's fix as of 10/20(previous comment) was either not successful or not present in latest version.

I've contacted Mikrotik and they've fixed the issue:

Thank you for the report.
We've found and fixed the issue.
Please verify if you now receive the accurate value:  91f7b0456619dbfc19940a85566c949ce3718321f32709886df5125c71f0b6b7