Winbox 4 windows 11 arm64 missing devices in saved

RouterOS General
1

Hi All

i was wondering if anybody else has seen this problem before?

ive moved from mac intel to windows 11 arm64 (brilliant btw!)

loaded up winbox 4, imported my .cdb file from my mac,

suddenly ive only got 7 out fo 30 devices listed?

i can see the devices are ment to be there tho? the lines are just blank!?

Screenshot 2025-07-11 190420
Screenshot 2025-07-11 190420990×1171 59.3 KB

if i use the switcher option next to filter, and specify a group, all devices for that group appear!

not sure if its a UI glitch or a bad import maybe?

Regards

Simon

WinBox v4.1rc released!
2

Sounds like problems with nameing the devices with non supported chars set.
Or even more stupid if they using not the same the newline character.
Have seen something like this before and last time it was the delimiter character within python.
With the locale settings, so the workaround then was just force locale to ‘C’. Something like : LC_ALL="C" ./WinBox

is it the same version of program on each end ?

3

no its all english no funny like characters or anything
yes same version in both devices, ive even tried older version 4 build too?
also im using windows so not sure how to run the change locale thing

EDIT: ok found a weird work around, if i zoom up to 159% from the settings panel,
the devices then appear, then i just click the percentage to reset back to 100% and it stays there
UNTIL i sort by a column, then it goes back only a few being displayed

4

Ohhh sounds like there is a rendering problem with some floats or integer division problem.
Don’t know if WinBox uses it’s internal fonts, or using the systems one.
Because WinBox is a Qt App, you could try to set some Qt variables.
When i do this in my Linux i can (zoom)
QT_SCALE_FACTOR=2 ./WinBox

So maybe if you open up a command prompt in windows and do something like this you can also tweak the Qt settings.
I have found this settings on the web, maybe you can find more of this settings.

C:\Users\User\Desktop> set QT_SCALE_FACTOR=2
C:\Users\User\Desktop> WinBox.exe

C:\Users\User\Desktop> set QT_AUTO_SCREEN_SCALE_FACTOR=1
C:\Users\User\Desktop> WinBox.exe

C:\Users\User\Desktop> set QT_FONT_DPI=192
C:\Users\User\Desktop> WinBox.exe
5

I’ve seen the same thing. Seems to only affect windows arm. Any window that had enough rows will mess up in this fashion.

6

weirdly enough i can use the old winbox 3 without any problems

but also if i connect an external display which is 1080p with 100% resolution,
then drag winbox 4 onto it, it sorts itself out
and works (mostly) no issues

so i think its a display issue?

im using 2496x1664 with 150% scale

7

I have same problem.

im using 2496x1664 with 150% scale on Microsoft Surface (arm64). Winbox 4.0 (beta 33)

8

Weird. Same here on my arm64 Thinkpad. Also that zoom-workaround seems to work.

9

I find that any tables in the Winbox UI are broken in Windows 11 on ARM64. It makes it semi unusable for e.g. viewing DHCP leases or the firewall log.

I’ve not found a setting to fix it yet. Might raise a Mikrotik support request because it doesn’t look like they’re testing on ARM64.

10
  1. Verify the import method by using WinBox's built-in import feature to ensure proper parsing of the .cdb file.
  2. Check if the data is present by clicking on blank lines to see if login fields populate, indicating a display bug.
  3. Re-export the .cdb file from the Mac and import it again on Windows for a clean export.
  4. Look for a backup file like winbox.cdb.bak and try importing it to avoid corruption issues.
  5. Test with a new entry to determine if the issue is with imported data or a broader rendering problem.
  6. Check file encoding or line endings by opening the .cdb file with a text editor to ensure it's not truncated.
  7. Investigate WinBox 4 known issues by checking forums or trying an older version to see if it reads the file correctly.
  8. As a last resort, create a fresh winbox.cdb file on Windows and re-import the Mac .cdb to start clean.