What's new in v3.24:

*) fixed WinBox crash when viewing firewall rule with src/dst-address-type configured;
*) fixed checkbox group disabled state inheritance;
*) fixed dates and times in interface link up/down properties (RouterOS v6.47 required);
*) fixed system comment message display;
*) fixed vertical font alignment in optional fields;
*) fixed window size inheritance from the previous session;
*) keep advanced and simple mode table settings separately;
*) make WinBox upgrade work with wine 5.0 or newer;
*) properly show popup windows on top;

If you experience version related issues, then please report them to support@mikrotik.com.

Both Winbox 32-bit and 64-bit versions are available here:
https://www.mikrotik.com/download

Finally the window resizing has been fixed after numerous Winbox releases. Winbox now saves them and if you log in they are not getting bigger and bigger anymore.

Looks good and no more resizing of the windows on it's own is a big relieve. Running it on a Windows 10 system.

Hallelujah !!!!
It works...

Everything is good on hidpi display, but terminal font is too thin. Can you change terminal font?

^^^ If you do, please don't break it for default dpi, it's perfect there.

It'd be great if you support Arabic characters in the next version like on Winbox Android App.

New Winbox shows strange changelog in "system -> packages" for stable tree ??!?!?!?
The error comes after "clear cache" only on the first device you connect after downloading descriptors. On other devices the changelog is OK. It stays strange only on the first connected device after performing a "clear cache" .....
No sorry....it is every 2nd time you connect
connect rb4011 .... changelog OK ... closing winbox .... connect rb4011 .... changelog NOT OK .... closing winbox .... connect rb4011 .... changelog OK .... and so on

New Winbox shows strange changelog in "system -> packages" for stable tree ??!?!?!?
The error comes after "clear cache" only on the first device you connect after downloading descriptors. On other devices the changelog is OK. It stays strange only on the first connected device after performing a "clear cache" .....

Unbenannt.PNG

That has different cause and Winbox is correct here. It will be fixed when the Mikrotik software server is fixed/updated.

No sorry....it is every 2nd time you connect
connect rb4011 .... changelog OK ... closing winbox .... connect rb4011 .... changelog NOT OK .... closing winbox .... connect rb4011 .... changelog OK .... and so on

No sorry....it is every 2nd time you connect
connect rb4011 .... changelog OK ... closing winbox .... connect rb4011 .... changelog NOT OK .... closing winbox .... connect rb4011 .... changelog OK .... and so on

What if you enforce it to use only one of the two servers under the domain dowload.mikrotik.com? Round Robin behaviour of DNS could be causing that.

Mikrotik has first get their download servers in order again before we can draw any conclusions from that. It went all wrong at the end of last week.

See: viewtopic.php?f=21&t=154662#p793526

Hello

With Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?

Regards

Hello

With Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?

Regards

Yes, the same here

With Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?

Yes, the same here

Just tried it on several routers, but only see this behavior on a single device. A differentiating factor appears to be the number of records kept in the log. I see this on a device with 1000 record in the log buffer. And it is the actual number of rows that matter, as I have a CHR instance with the line limit set to 1000 but with only 120 records currently in the buffer, and I do not see this problem there.

Hi,

Error, sorry.

Regards.

Are there any plans to introduce something analogous to a taskbar in winbox, so that we can move seamlessly between open windows? Along with this, a miimize feature for open windows would also be useful.

With Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?

Yes, the same here

Just tried it on several routers, but only see this behavior on a single device. A differentiating factor appears to be the number of records kept in the log. I see this on a device with 1000 record in the log buffer. And it is the actual number of rows that matter, as I have a CHR instance with the line limit set to 1000 but with only 120 records currently in the buffer, and I do not see this problem there.

I tried to set limit to 990 lines, there are 927 lines currently. Nothing changes, log goes to beginning after window restore. BTW, it's RB1100AHx2, RouterOS 6.45.9.

Hi,
Bug still exists on PC with HiRES display with 150% interface resize.
After winbox resized to needed size and disconnected, the winbox scale turns back to default.

Implement multiple tabs with routeros sessions in winbox

The problem with windows that have dynamic updates remains the same, I went back to 3.21 after 10 seconds of test...

To reproduce: open a window like "IP firewall filters" in a router that is in active use, and make sure the hit-counts of firewall rules are being displayed (and changing all the time).
Now, position the mouse over a header separator and keep mouse button pressed to attempt to move the separator to set the column width appropriately.
Result -> column jumps to some default width at the same time the counters are updated. Dragging is ignored.

Similar problem occurs when you keep mouse button pressed over a filter line to drag it to some other place. Line jumps to wrong place, not the place you drag it to.

This is a critical problem that makes all recent versions of winbox unusable!

I never had this happen to me when I downloaded previous versions but now 3.24 is being flagged by MalwareBytes as having Malware.Generic malware. I suspect its a false positive but something changed since Malware Bytes never complained about previous versions...(and yes, I did download direct from MT site)

open a window like "IP firewall filters" in a router that is in active use, and make sure the hit-counts of firewall rules are being displayed (and changing all the time).
Now, position the mouse over a header separator and keep mouse button pressed to attempt to move the separator to set the column width appropriately.
Result -> column jumps to some default width at the same time the counters are updated. Dragging is ignored.

Similar problem occurs when you keep mouse button pressed over a filter line to drag it to some other place. Line jumps to wrong place, not the place you drag it to.

Never experienced this problem, so now I went and tried it myself. Tested against several devices, result- cannot reproduce, everything works as expected for me.

I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?
I have seen others confirm this problem in the release topics of earlier versions (3.22 and 3.23)...

I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?

Sounds plausible. I run Winbox (64-bit) natively on Win10. And (simply out of curiosity) I have just tested 32-bit version, which also works fine for me.

I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?

Sounds plausible. I run Winbox (64-bit) natively on Win10. And (simply out of curiosity) I have just tested 32-bit version, which also works fine for me.

It would be interesting to hear if wine users on the Mac experience the same issue, and/or if other Linux users see it as well.
Under Linux it could maybe depend on the window manager in use? (KDE/GNOME/XFCE etc)

I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?

Sounds plausible. I run Winbox (64-bit) natively on Win10. And (simply out of curiosity) I have just tested 32-bit version, which also works fine for me.

It would be interesting to hear if wine users on the Mac experience the same issue, and/or if other Linux users see it as well.
Under Linux it could maybe depend on the window manager in use? (KDE/GNOME/XFCE etc)

Let me check that on macos

I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?

Sounds plausible. I run Winbox (64-bit) natively on Win10. And (simply out of curiosity) I have just tested 32-bit version, which also works fine for me.

It would be interesting to hear if wine users on the Mac experience the same issue, and/or if other Linux users see it as well.
Under Linux it could maybe depend on the window manager in use? (KDE/GNOME/XFCE etc)

Let me check that on macos

Nope, macos catalina, wine64 (wine-5.7) and WinBox 3.24 - I can resize columns why they're updating all I like.

It'd be really great if you can fix group sorting

I put all my routers into groups, then I sort by group and go 'Show Categories' - this used to work in that it would be unique per group, but for the last few releases it does it by first letter, so if I have a heap of

Client1
Client1
Client2
Client2

They will all just sort under 'C' not under 'Client1' then 'Client2' with the category headers.

PLEASE fix this so I can get my groups set normal again

Next add dark mode will great

Why you couldn't fill file version value in file property field (details)?

how do we disable all this high DPI setting or winbox following system DPI?
i like how it was on 3.20 and want it to work how it was there so is there any command line switch which we can apply to disable the new dpi feature coz its turning out headache for me so sticking to 3.20 for now

I run winbox with my system set to a custom scaling of 121 the first time it shows big, then I close and reopen and then it shows small and then again big and again small, what's going on.
Can we please have a tick box to not follow system dpi settings or a parameter with which we can disable dpi scaling or else I'll be stuck to 3.20 which was fine for me

I run winbox with my system set to a custom scaling of 121 the first time it shows big, then I close and reopen and then it shows small and then again big and again small, what's going on.
Can we please have a tick box to not follow system dpi settings or a parameter with which we can disable dpi scaling or else I'll be stuck to 3.20 which was fine for me

Agree!
And please rpair other BUG: when I disable Simple Queue - the (new) icon of queue is not turning gray - it's still greean like enabled.

I wiped my .wine config and ended up with the old problem of the cursor and text being misaligned when running winbox on wine in fields of text to be edited, especially as the line grows longer. I had made some forgotten changes ages ago which fixed this but also turn off font smoothing - winbox looked perfectly fine without smoothed fonts and the cursor was always in the right place.

This old registry trick still works and you get to keep your smooth fonts, which is nice!

[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"ClientSideWithRender"="N"

Create a file test.reg with the key/text above, and on terminal:
regedit test.reg

This works with winbox 3.24, wine-stable 4.0.3~bionic and Linux Mint 19.3.

I wiped my .wine config and ended up with the old problem of the cursor and text being misaligned when running winbox on wine in fields of text to be edited, especially as the line grows longer. I had made some forgotten changes ages ago which fixed this but also turn off font smoothing - winbox looked perfectly fine without smoothed fonts and the cursor was always in the right place.

This old registry trick still works and you get to keep your smooth fonts, which is nice!

[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"ClientSideWithRender"="N"

Create a file test.reg with the key/text above, and on terminal:
regedit test.reg

This works with winbox 3.24, wine-stable 4.0.3~bionic and Linux Mint 19.3.

Edit: I noticed now the initial login window for Winbox still has font-cursor misalignment, but once in Winbox it's fine. WTF!?

@UpRunTech
Thank you! I've been wondering how to do that.

After connecting by IP address, the Winbox does not show any RouterOS settings, either interfaces or licenses, nothing, all windows are empty. Sometimes, after connecting, it shows, after a while, the connection disappears and after the connection there is already nothing. Frequent shutdowns of winbox also happen. Winbox version 3.24. Version RouterOS 6.45.9 long term. The problem is not only mine but also in another organization.

Hello

With Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?

Regards

Yes, the same here

Yes, the same

@UpRunTech
Thank you! I've been wondering how to do that.

Ugh I made a typo - it was missing the REGEDIT4 which stopped the key being made in the registry. It should be below. The unsmoothed version of the fonts are displayed but there is now no longer a cursor problem any more.


REGEDIT4

[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"ClientSideWithRender"="N"

Thanks for the update, i like the progress / new features on winbox!

One thing i would like to see reverted back, is the log window. I preferred it when the log messages "wrapped" so that you could see the entire entry.

as of this change to the log window lines are truncated to the width one sets the column to. Especially with firewal log messages, this can make many enries unreadable (unless are on 4k monitor where you can stretch the window and column to huge widths).

I know some requested this feature for some reason, so i would really like to see an option added to the menu where you can choose to WRAP log lines (or choose to Truncate them, as it is now)

(i do really like the find feature on the log window)
thanks!

I run winbox with my system set to a custom scaling of 121 the first time it shows big, then I close and reopen and then it shows small and then again big and again small, what's going on.
Can we please have a tick box to not follow system dpi settings or a parameter with which we can disable dpi scaling or else I'll be stuck to 3.20 which was fine for me

Yes, true. Very annoying bug: even on any interface resize scale.

Hello
WinBox (64bit) v3.24 - the program starts normally, but crashed only when try connect to router from the list (tested on 6.47 & 6.46.6)
WinBox (32bit) v3.24 - all OK


tested under W7 x64 SP1

Still have problem with window size reverted after closing winbox.
Winbox v3.24 - 64bit
Windows 10 Pro - Build 18363
2 x 4k display - Scale 150%

Could rules' icons be grayed out when rules are disabled to be consistent with grayed out text?
When you look at them you are fooled that they are active even rules are not,

The normal version is 3.19
3.24 GUI text so small @ windows 100% dpi
this image auto delete @ 1 month

v3.24 has adjustable font size. in the loader, tools > zooom in

Secret!

It's for MUM EU2025, relax for a bit

v3.24 has adjustable font size. in the loader, tools > zooom in

For me its not under tools, but under setting. You should name stuff the same on Windows/Mac

v3.24 has adjustable font size. in the loader, tools > zooom in

Screenshot 2020-06-11 at 11.25.32.png

when zoomin...font too big.so ugly

Hi,
Winbox client main app window has a bug. Оn HiDPI displays (~2k) with interface resize to 125-125%, main window started one time with small font and next time with larger font, plus window scaled up to full height of desktop...

Feature Request:

Use a check-box or option to on/off fixed font in logs...
Currently i run the logs in terminal to show proper distance but in WinBox>Logs I see that not-fixed font who should be default of cource but nice will be to set it as fixed sometimes as option.
Photo:

Feature Request:

Please add a AUTO-reconnect.
If we connect to IP:PORT then this should still reconnect when he detect that port of WinBox is alive again - this will be life change feature !
So many times I see and hope to connect....

Feature Request:

Please add a AUTO-reconnect.
If we connect to IP:PORT then this should still reconnect when he detect that port of WinBox is alive again - this will be life change feature !

I think it should not disconnect so quickly either... when there is a couple of seconds of network interruption, winbox immediately disconnects. SSH or telnet is alive.
Winbox should keep connected like 30 or 60 seconds, maybe there should be a config option for it. So you can reboot a router somewhere in the network without losing all winbox sessions to routers further down.
There could be an icon that lights up in RED when it detects that the connection seems dead (no network traffic going for 2 seconds) but it should remain connected until the user decides to close the session or considerable time has elapsed.

pe1chl :

I think it should not disconnect so quickly either... when there is a couple of seconds of network interruption, winbox immediately disconnects. SSH or telnet is alive.
Winbox should keep connected like 30 or 60 seconds, maybe there should be a config option for it. So you can reboot a router somewhere in the network without losing all winbox sessions to routers further down.
There could be an icon that lights up in RED when it detects that the connection seems dead (no network traffic going for 2 seconds) but it should remain connected until the user decides to close the session or considerable time has elapsed.

Agree, at mREMOTE NG they solve it in very good idea, they give you option what to do :)

If you want to have good visual representation of the contention being lost due to reboot, upgrade or just no connections then Winbox should not be responding to any changes and the screen should be become transparent to white. The box as SiB suggest could then the only part of the Winbox screen that is responsive and also not transparent.

There is already an indication present, in local networks, when Neighbors is seeing the MAC address and IP address. That could be a local trigger to reconnect.

I am not so concerned about local devices. I manage larger networks where there can easily be 4 router hops towards a central router which I keep open in Winbox all day.
Whenever there is a slight interruption on one of the links (e.g. a reconnect due to DFS or similar) or a firmware upgrade anywhere along the path, I lose the connection. Even when there are alternative paths that BGP can select, the time that takes is sometimes too long.
And WORST: the Winbox does not save the session in such cases. SO all work I have done on the session setup (window sizes, column settings, etc) is LOST in that case.
So I need to remember to do Session->Save each time I change something. Annoying! It would be so much better when winbox would not close sessions merely because there is a small network hickup. SSH and Telnet don't do that either.
I'm not asking for "auto reconnect", I want "session persistence" until there is unreasonable outage of the network. And I want an "autosave on disconnect" option too.

So I need to remember to do Session->Save each time I change something. Annoying! It would be so much better when winbox would not close sessions merely because there is a small network hickup. SSH and Telnet don't do that either.
I'm not asking for "auto reconnect", I want "session persistence" until there is unreasonable outage of the network. And I want an "autosave on disconnect" option too.

Hmm, I thing my sestion are save but I notice long time ago that "red X" not save session. The Exit button save session infromation.
Thats way from point when I close WinBox by "Exit" - all session works as should without additional stuff.

Yes, when that "Autosave on Close" option is enabled the session is saved when you use Exit or you hit the X at the top right of the window.
That works fine.

However, when the session is closed because of a network failure OR because the connected router is rebooted (you use System->Reboot or upgrade the router with automatic reboot), the session is NOT saved. No matter how that option is set.
That is why I mention that another option for "Autosave on DIsconnect" would be helpful.

Yes, when that "Autosave on Close" option is enabled the session is saved when you use Exit or you hit the X at the top right of the window.
That works fine.

However, when the session is closed because of a network failure OR because the connected router is rebooted (you use System->Reboot or upgrade the router with automatic reboot), the session is NOT saved. No matter how that option is set.
That is why I mention that another option for "Autosave on DIsconnect" would be helpful.

Hi,
Autosave on Close - does not save font sizing within winbox session

Yes, when that "Autosave on Close" option is enabled the session is saved when you use Exit or you hit the X at the top right of the window.
That works fine.

However, when the session is closed because of a network failure OR because the connected router is rebooted (you use System->Reboot or upgrade the router with automatic reboot), the session is NOT saved. No matter how that option is set.
That is why I mention that another option for "Autosave on DIsconnect" would be helpful.

I am facing this issue too. It is really annoying because when I get disconnected (network issues, switching from eth o wlan, etc.) then WinBox initializes as a small square window with all the subwindows really small, and I have to redo all the layout again.

Having an issue with zoom settings in both 32 and 64 bit versions after upgrading from 3.20 to 3.24. I saw something in the change log about fixing zoom settings in 3.22, but honestly, I never had an issue until upgrading past that version.

No matter what I do, Winbox will not save my zoom settings and the default microscopic level is rather horrid on the eyes.

https://youtu.be/oCHUE0SGP88

I don't know is it bug or intended behaviour. Selected to display columns in firewall settings window are not saved.

The problem with windows that have dynamic updates remains the same, I went back to 3.21 after 10 seconds of test...

I confirm the problem on Windows 7 64, using 64bit winbox.

The problem with windows that have dynamic updates remains the same, I went back to 3.21 after 10 seconds of test...

I confirm the problem on Windows 7 64, using 64bit winbox.

Thanks! That saves me from testing on Windows machines. Strange that other people deny that they have a problem, maybe they don't understand what issue I mean?

Strange that other people deny that they have a problem, maybe they don't understand what issue I mean?

Probably.
I just confirmed the issue is also present on Windows 10.

Based on viewtopic.php?f=21&t=161887&p=804375#p804344 I ended up here.

To reproduce: open a window like "IP firewall filters" in a router that is in active use, and make sure the hit-counts of firewall rules are being displayed (and changing all the time).
Now, position the mouse over a header separator and keep mouse button pressed to attempt to move the separator to set the column width appropriately.
Result -> column jumps to some default width at the same time the counters are updated. Dragging is ignored.

I tried to reproduce the issue as per quote but it just does not occur.

My setup:
- Winbox 3.24 (tested both 32 and 64bit)
- Windows 10 Pro x64 1909 build 1836.836
- Intel UHD 630 GPU (integrated in Core i5-8600K), driver version 26.20.100.7263
- dual screen 1920*1080, default zoom level in windows (100%)

Not sure what else could affect it, but happy to do any test. There must be some very specific condition to trigger the bug.

Strange that other people deny that they have a problem

I am not denying that I have the problem. I really DON'T have the problem. On the other hand, I wouldn't deny that someone else may have the problem. It may not be that widespread as you think.

EDIT: AHA! after some playing with zoom levels in winbox, I think I was able to reproduce it once (changing column width and it jumped weirdly but did not really break anything). I did exactly the same procedure again and it did not happen. I am really struggling to find a way to reproduce it reliably.

Can you please provide a video so I can try to reproduce situation as close as possible?

Well, as these things go, I setup a video capture on my system that runs wine-4.0 and now I cannot really reproduce it on that system, it does what you describe as well:
When I open a firewall filter screen on a busy router which has 134 firewall rules and a lot of traffic, when I try to change the column width it shows glitches of jumping to a larger column width and then immediately back to the width where the mouse is at that time.
I don't dare to move a firewall rule on that router because it may lock me out when it drops a rule at a place where I don't want it to go.

I did most of my testing on a system which has wine-1.8.7 (Debian 9), where it was really terrible as it was almost impossible to set a column width and firewall rules were dropped all over the place when moved. The routers I manage there have even more firewall rules, about 250.
So maybe to reproduce it requires more than a simple setup.

When managing routers like this I sometimes wish there is a a "PAUSE" button on such screens, so it does not update the counters all the time. This causes a few hundred kbps of network traffic when such screens are open, which is sometimes inconvenient on certain slow networks. Likely that would also fix this issue.

Ok so I updated my Debian 9 system to Debian 10 as well, so it has wine-4.0
This does not seem to have any effect on the problem. It remains the same, and on the router I manage from that system, which has 250 firewall filter rules and a lot of traffic, it is much more present than on my other system which already had Debian 10 and where I manage a router with 134 firewall rules.
On the larger router it is very apparent that the column width changing is broken, and I do not want to risk moving firewall rules there either.
I switched it back to Winbox v3.21, while on the second system I keep 3.24 for now so I can get more info.

Interestingly, on the system I updated I also manage a CHR running v7 beta. When I connected that from 3.24, it was downloading the desciptors very slowly and the router crashed.
After reboot the log shows "kernel failure on previous boot". This never happened with 3.21.

I found this issue in WinBox in IP->DNS-Static window where stuff is not drawn properly. If you minimize and restore WinBox it redraws content of the window properly.

It affects most if not all windows.

Finally . No more resizing of the windows is nice. Let me try it.

Finally . No more resizing of the windows is nice. Let me try it.

??? All resizing problems are still here. Within winbox and winbox itself...

Finally . No more resizing of the windows is nice. Let me try it.

??? All resizing problems are still here. Within winbox and winbox itself...

Not for me, all the crazy windows resizing was finally fixed for me in 3.24

Finally . No more resizing of the windows is nice. Let me try it.

??? All resizing problems are still here. Within winbox and winbox itself...

Not for me, all the crazy windows resizing was finally fixed for me in 3.24

Problem still hare on 2k displays with interface resizing to 125-170%.
Winbox itself and its inner windows has this problem too.

It is expected that the font size used can be stored when logging out. But now, every time you log out of winbox and then log in again, the font becomes larger. After logging in and logging out multiple times, the font size will be maximized. Every time I have to manually adjust to a smaller value, which is inconvenient.
In addition, the line spacing is too close, not conducive to reading, not as good-looking as before 3.20.

Problem still hare on 2k displays with interface resizing to 125-170%.
Winbox itself and its inner windows has this problem too.

I have 2K resolution with 100% scaling and its ok. So it must be scaling.

Problem still hare on 2k displays with interface resizing to 125-170%.
Winbox itself and its inner windows has this problem too.

I have 2K resolution with 100% scaling and its ok. So it must be scaling.

Hi,
Older version, like 3.20 does not have this problem...

ARGGGG!! The default zoom level sucks! Why can't this setting be remembered? Win10 64bit w/ 4k monitor, tried 32 and 64 bit winbox, been like this for a few versions now. Have to manually zoom in twice to be able to read the text. Is there a solution?

ARGGGG!! The default zoom level sucks! Why can't this setting be remembered? Win10 64bit w/ 4k monitor, tried 32 and 64 bit winbox, been like this for a few versions now. Have to manually zoom in twice to be able to read the text. Is there a solution?

YES! This is the most annoying thing EVER! I can't even use Winbox until I zoom in. There's not even a keyboard shortcut to zoom, so it has to be a bunch of clicks. ARGH. PLEASE FIX IT. You know what? I'm going to make a ticket.

Good day,
whole month - gone and no any news... All bugs are here.
Dear developers, please fix resizing issues, please...

Finally that "zoom in" issue has been fixed ;')

Anyone else with a problem of not saving the IP address and the user in the Winbox quick access list? Using Winbox 3.24 and Windows 10 v2004

No! Zoom issue on Hires displays still here!

Winbox after a few days continuous connection to CCR2004 (it seems doesn't matter) with ROS 6.47.1. Used memory growed from 10 MB to 695.

Sorry for flood, but very strange with no any updates, news from developers and "near to developers" persons on many problems...
Very strange and it looks alarming...

Yes, zoom state is not saved between sessions, it's a bug, it will be fixed, but any other issues with HiRes displays is hard to reproduce, There is some kind of compatibility between external display and internal display, if different DPI is used. We have no issues on any of the testing computers with HiRes displays.

About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.

About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.

A generic problem with winbox is that when you open some screen where there are lots of items and a lot of activity (e.g. a complex firewall rules page with updated counters or a page of active connections or address list items), both the link and the system are loaded with the update data. It would be useful when there would be some kind of "pause" button or a way to configure the update rate of such screens, so this can be managed a bit better.
It could also be a workaround for the problems I (and some others) have when dragging items on such a screen in winbox versions 3.22 - 3.24.

Yes, zoom state is not saved between sessions, it's a bug, it will be fixed, but any other issues with HiRes displays is hard to reproduce, There is some kind of compatibility between external display and internal display, if different DPI is used. We have no issues on any of the testing computers with HiRes displays.

About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.

Thank you for feedback. Problem with HiRes appears on Microsoft Surface 4,5 with any resolution and any interface resize scale.

It would be useful when there would be some kind of "pause" button or a way to configure the update rate of such screens

+1

This would be very helpful, especially on the connections tab (firewall window) and on the routes window.
On routers with hundreds of thousands of connections and/or routes, those two windows are barely usable.

About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.

Oh cmon.... there is clearly memory leak somewhere in winbox if it starts with 80MB and gets to 700MB in a day. It's understandable that some amount of memory should be consumed by graphs or something else that accumulates data over time, but amount of data required to see what's on the screen is pretty low...
But 600MB is just way too high for this to be anything else than a memory leak.

Suggestion: a way to copy and paste things in WinBox

1) Select something (in this case firewall rules):
2) Copy items in clipboard using standard keyboard shortcut or from right-click menu.
3) Select target, either different position in same WinBox, or in completely different one (another router):
4) Paste items from clipboard
5) Enjoy the result:
Why? Because it would be useful and convenient. I have redundant routers (online at the same time), where I have to keep same config. Same firewall rules, same address lists, same parts of IPSec config, etc. Ideally there would be some built-in and completely reliable synchronization of selected parts of config, but there isn't and it's probably difficult to implement something like that. I've seen some attempts with script, but I don't trust it, something can go wrong with that. So I keep two synchronized configs manually and it's no fun at all.

If I need to add for example ten new firewall rules, I can either add them on both routers manually one by one, which is horrible and error prone. Or I can add them on one, export config, find them in there (no fun again, those configs are long), paste commands in Terminal on other router and drag them to right place. That's slightly more reliable, but still far from good.

How should it work? It could produce the same output as export, so for this example it would be:
This shouldn't be difficult, right? Even if there was only copy without paste, it would already be big help. Paste could have problems e.g. when something would reference some item not available on target router, but that's fine, it could simply stop with error, same as when pasting such config in Terminal.

Winbox after a few days continuous connection to CCR2004 (it seems doesn't matter) with ROS 6.47.1. Used memory growed from 10 MB to 695.
winbox_memory.png

Check the Google Chrome memory usage, bet you that was used to monitor Cisco equipment :-)

OK. It is not bug, it is feature ... Microsoft's favorite answer.

I don't use winbox for monitoring. But in lab I have long time sessions. And if sometime problems in network, winbox is fast for the detection.

About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.

I "always" have 3 winbox windows open to 3 different routers. I have the "log" open full-screen as kind of background, and then usually at least a "Routing->BGP->Peers" window and sometimes another window e.g. IP->Neighbors or PPP->Active connections.
But I do not experience this issue at the moment. I am using winbox 3.21 under wine (Linux).

Looks good and no more resizing of the windows on it's own is a big relieve. Running it on a Windows 10 system.

It is not work on a W10 LTSC En (1809) if Checking Open In New Window and User name in OS's have any symbols like backspace in Name. For any time opened - All resized to smaller. If Logon name like 1 words is Ok. I hope that it shall be fixed.

And I didn't find "copy" item at right click for all place like Firewall. Now I need open any rules for copy it, but can set comment without. Can make it,Please, If it is possible.

For ludvik:
The memory leak is probably happening only for one specific type of window/data. You can try to find which one it is by slowly increasing amount of winbox windows you have open until memory starts going up...

well, I'm now also in the having to zoom in three times for any window to get readable business...
please fix this.
Win10 2004, Surface Pro, HiDPI - if that makes any difference.

4k monitor, have to zoom 3x to use it. Even a '+' in the menu bar would be better than menu zoom/menu zoom/menu zoom. Irritating.

well, would like to go back to 3.20 with no HiDPI support - at least it worked :)
anyone got an archive link as I seem to dumb to find the previous releases in the download-section...

Direct download link to 3.20 x64: https://download.mikrotik.com/winbox/3.20/winbox64.exe ... for the rest of variants, make necessary alterations.

Winbox v3.25 has been released:

viewtopic.php?f=21&t=165525