What's new in v3.23:

*) added support for Ctrl+C and Ctrl+A shortcuts in read-only fields;
*) always use fixed width font in terminal window;
*) do not resize inner windows when main window is resized;
*) fixed default configuration approval window disappearing when using "Show Script" button;
*) fixed main window size saving between sessions;
*) improved large table loading speed in RouterOS v7;

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

thx

Nice job.

Problem of changing column width and row position in active window (i.e. which shows counters that are being updated during the change operation) has NOT been fixed!
Back to 3.21
(using winbox 32-bit under wine Debian buster)

Does not preserve chosen interior window sizing and spacing after selecting Session / Save. Windows 10, 125DPI.

Problem of changing column width and row position in active window (i.e. which shows counters that are being updated during the change operation) has NOT been fixed!
Back to 3.21

Copy that.. , Confirmed.. Thud
Back to the drawing board, eh?

"Inner window size" problem not solved

1. Fixed inner window size (first picture)
2. Exit from Winbox
3. Again open Winbox (second picture)
4. See second picture's Inner window is change automatically in width
But Winbox 3.21 not changed Inner window automatically

Thanks but any chance to get a native application in other OSes like MacOS or Linux without the need to use Wine?

I also confirm, resizing is NOT fixed. Still bugged.

Still have the problem with lines getting cut off in terminal when scrolling.

"Inner window size" problem not solved

1. Fixed inner window size (first picture)
2. Exit from Winbox
3. Again open Winbox (second picture)
4. See second picture's Inner window is change automatically in width
But Winbox 3.21 not changed Inner window automatically

I experience the same issue. Otherwise seems that the major resizing issues have been solved.

"Inner window size" problem not solved

From posted change list, I inferred that they admitted in advance that this part of the problem was not yet solved. Baby steps, I guess. I wish things got broken only in baby steps.

"Check for update" still does not admit availability of this version, though.

Hi to all

i using Winbox under *buntu18.04 & wine
from 3.22 and now in 3.23 i have an annoying problem with inner window resize

what bother me is INTERFACE window
it is stretched to MAX horizontal (width) whenever i open Winbox

i tried to delete session and save again, but nothing.

It is really problematic for someone who using winbox on daily basis

"Default Wireless Data Rates error"

I have noticed error regarding Data Rates setup in wlan interface.
Since WinBox v3.22, when I check default data rates, I still have them enabled, which is quite confusing.
I tried many versions up to 3.21 works fine. Since 3.22 (both 32bit and 64bit) has error. Problem seems to be independent of ROS of the device I connect to.

+1 for mac and please fix the resizing

Everytime I open a new Winbox .viw file it increases the scaling.
I'm using custom scaling in Windows 10 = 115%

Everytime I open a new Winbox .viw file it increases the scaling.
I'm using custom scaling in Windows 10 = 115%

It is true. On any interface scale more than 100% - inner window resize bug appears...
Version 3.23 still have this bug, and rows bug too...

Thanks but any chance to get a native application in other OSes like MacOS or Linux without the need to use Wine?

as a linux and macos user I'm going to ask they don't do this and instead release a 64 bit version of the dude so I can update to latest osx and future proof against a 64bit only linux future which is coming

Update in Winbox v3.22 only says:

"There are no new versions"

and shows me "What's new in v22" and the change log of 22 and previous ones.
So connection to Mtik server is working and resolving update server ...

What is the issue ? How can I fix this?

Resizing of the inner windows is still present and it's still highly annoying :/ Anyone know where to find 3.21?

Anyone know where to find 3.21?

32Bit: https://download.mikrotik.com/winbox/3.21/winbox.exe
64Bit: https://download.mikrotik.com/winbox/3.21/winbox64.exe

More than a month solved the size problem ... and they didn't do anything.
I'm in shoke

Its spam update. Nothings fixed [emoji52]

Sent from my C6833 using Tapatalk

Anyone know where to find 3.21?

32Bit: https://download.mikrotik.com/winbox/3.21/winbox.exe
64Bit: https://download.mikrotik.com/winbox/3.21/winbox64.exe

Thank you very much. I was so frustrated of this problem and now with the update I rushed to 3.23 but...

Interesting, it seems like that changelog entry is hinting at new RouterOS v7 functionality coming soon.

Hi,
Dear developers team, are there any news about winbox 3.23 bug fixes? I think, that 3.23 is the same soft as 3.21-3.22. Same bugs...
And one more issue: winbox auto-update does not see 3.23. Strange...

I think, that 3.23 is the same soft as 3.21-3.22. Same bugs...

Check your download/install procedure! This is certainly not right!

I think, that 3.23 is the same soft as 3.21-3.22. Same bugs...

Check your download/install procedure! This is certainly not right!

Only 15-25 mins ago auto-update solved. But all bugs, means before - still exists.

Looks like connecting to local devices is now broken. I can't connect to my router or switch at 192.168.10.x
Legacy mode, which I've never had to use before, doesn't work either. Gets stuck on "logging in" permanently.
Both are up to date on latest packages and firmware.
Back to 3.21 I guess.

Looks like connecting to local devices is now broken. I can't connect to my router or switch at 192.168.10.x
Legacy mode, which I've never had to use before, doesn't work either. Gets stuck on "logging in" permanently.
Both are up to date on latest packages and firmware.
Back to 3.21 I guess.

Go to Tools and check "Legacy Mode".

Looks like connecting to local devices is now broken. I can't connect to my router or switch at 192.168.10.x
Legacy mode, which I've never had to use before, doesn't work either. Gets stuck on "logging in" permanently.
Both are up to date on latest packages and firmware.
Back to 3.21 I guess.

Go to Tools and check "Legacy Mode".

I mentioned in my post that I tried Legacy mode. It didn't work, gets stuck on "Logging In" permenently.

Looks like connecting to local devices is now broken. I can't connect to my router or switch at 192.168.10.x
Legacy mode, which I've never had to use before, doesn't work either. Gets stuck on "logging in" permanently.
Both are up to date on latest packages and firmware.
Back to 3.21 I guess.

Go to Tools and check "Legacy Mode".

I mentioned in my post that I tried Legacy mode. It didn't work, gets stuck on "Logging In" permenently.

Try SSH and look inside logs... Or winbox via MAC-connection

Mikrotik really could've fixed this.. it has been reported long ago

Nothing's fixed

Still nothing... Too bad. And once again - more cli practice without good working winbox...

Same problem here: the connection window (that which pop-up just after starting Winbox, where you enter IP address) and inner windows are being bigger every time I start Winbox or enter a session.

Environment

• Winbox 3.22 x64 and 3.23 x64;
• Windows 7 and Windows 8.1;
• Resolution: 1920*1200 (16:10 ratio);
• DPI set at default 100%.

Problem doesn't occur on Winbox 3.21 x64.

Same problem here: the connection window (that which pop-up just after starting Winbox, where you enter IP address) and inner windows are being bigger every time I start Winbox or enter a session.

Environment

• Winbox 3.22 x64 and 3.23 x64;
• Windows 7 and Windows 8.1;
• DPI set at default 100%.

Problem doesn't occur on Winbox 3.21 x64.

Hi, but 3.21 have main window resize bug on hi res displays. I think, the stable version is 3.20, imho.

Hi, but 3.21 have main window resize bug on hi res displays. I think, the stable version is 3.20, imho.

Hello, I didn't check that, can tell only about my environment.
I've added my screen resolution to the specification though.

The problem with resize windows is still there.
I tried to delete the .viw file and make all windows settings again.
After close, autosave settings and open again winbox, the windows resized.
After every close/open the windows resized a bit again and again and again...

Dear friends, dear developers,

Maybe any news about new version?

Don't be so pushy! When there is a new version, there will be a new topic on the forum.
As long as there is no new version, there will be no announcement.
That is how it is with MikroTik.
(also, with MikroTik it is common that new versions are posted late on friday afternoon their local time)

Cant download the latest version. Getting warning about non-HTTPS certificate, and im unable to download the file..

Cant download the latest version. Getting warning about non-HTTPS certificate, and im unable to download the file..

Little precisely!?
https://mikrotik.com/download
On this site is certificate issue?

Problem that was also present in 3.22 with the display of the window when clicking on a certificate crl. The window is not resizable and exceed the size of the winbox window.

I keep resizing the windows in Winbox 3.23 64 on Windows 10 64. More than half of the time I am resizing windows to a smaller size instead of working in Winbox on the settings. It really a PITA this way.

Update: I was working on three routers using the same profile and I am now trying to have for each router a separate profile for Winbox.

Problem that was also present in 3.22 with the display of the window when clicking on a certificate crl. The window is not resizable and exceed the size of the winbox window.

3.22, 3.23 have resizing problem or bug.
3.21 has font\row bug...

Dear colleagues, any news on this problem, maybe some inside information about solving this issue?
Maybe some workaround exists?

Another (second or maybe third yet) Friday and no new winbox version... Too bad...

It is only Thursday today, so we do not know yet.
On the other hand, MikroTik are closed tomorrow and monday so indeed likely no release tomorrow.
However, I can assure you that posting messages like that will do absolutely nothing to change it.
I recommend you to go back to a release that works OK. For me that is 3.21 but I do not use scaling at all.
Newer versions that tried to improve things for users that use scaling have introduced far worse problems.

It is only Thursday today, so we do not know yet.
On the other hand, MikroTik are closed tomorrow and monday so indeed likely no release tomorrow.
However, I can assure you that posting messages like that will do absolutely nothing to change it.
I recommend you to go back to a release that works OK. For me that is 3.21 but I do not use scaling at all.
Newer versions that tried to improve things for users that use scaling have introduced far worse problems.

True. 3.21 - works fine, as I said before... Lets wait...

I noticed files called viw????.tmp littering the folder that winbox.exe lives. These files has IP, username and passwords in them. Winbox does not clean up these files on exit. I have also noticed that it keeps the ip username and password of the first connection made. This happens even if save password is unchecked. Can we get a cleanup process that removes these?

Anyone know where to find 3.21?

32Bit: https://download.mikrotik.com/winbox/3.21/winbox.exe
64Bit: https://download.mikrotik.com/winbox/3.21/winbox64.exe

Just loggin to say TY! resizing bug it's sooooo anoying!

Looks like Winbox needs an adequate beta test program. What it has now doesn't even pretend to qualify. This sort of thing should have been nipped in the bud prior to release. Now we can't get rid of it.

Hey guys - any chance of getting a checksum for the WinBox downloads too? Wary of downloading an EXE file without any confirmation it's safe to work with. Thanks in advance.

Hey guys - any chance of getting a checksum for the WinBox downloads too? Wary of downloading an EXE file without any confirmation it's safe to work with. Thanks in advance.

Checksum is not an reliable way of validating file authenticity - i.e. if it was modified after publishing. If an attacker can tamper the executable, then he can almost always tamper the provided checksum. Checksums are good to validate file's integrity - i.e. if the file wasn't broken while downloading for example.

What you should look at is digital signature. This is the way of validating file's both integrity and authenticity. Digital signature is finally provided to Winbox executables since version 3.13. You can validate it by going to file properties, then to the "Digital signatures" tab and double clicking the line with "Mikrotikls SHA256 <time>". Then in the new window you will see if digital signature is OK or not.

Although the attached digital signature is a good way of validating file authenticity - it's not perfect. There are many problems with PKI in general and that's why MikroTik should definitely sign Winbox executable and RouterOS packages with own GPG signature. But keeping in mind that - sorry to say that - they don't care about software security and quality as they should, so we probably won't see it in a long time - if at all. Also keep in mind that Winbox digital signature came way to late. I was requesting it in year 2015 [1], 2016 [5], then it was requested in March of 2018 [2] and we've finally got it in April 2018 [3] - most probably because of the emerge of Slingshot APT (malware) [4], which could impact company's image. Keep in mind, that such security measure should be present since the beginning of Winbox.

Looks like Winbox needs an adequate beta test program. What it has now doesn't even pretend to qualify. This sort of thing should have been nipped in the bud prior to release. Now we can't get rid of it.

The lack of dedicated software quality engineers and software security professionals is one of the things that prevents MikroTik hardware from being installed in sensitive installations. As they were serving mainly WISP in the beginning, then it was not noticed (from my experience, the ISP operators - generally speaking - don't know what they are doing, but everything is fine as long as money comes up). But now they are aspiring to be in the range of Enterprise hardware/software vendors, so such topics must receive top priority. But it requires the fundamental change in mindset, hiring more people and paying for work which doesn't directly translates to profits in a visible way. This is one of the things that makes difference between amateurs, money-hungry managers and real professionals. And I guess this is true all around the world.
You are right in what you're saying and you can be sure, that MikroTik's software has a lot more basic security problems which are there. But when you tell them about it, then you are treated like a kid who found a misspelling in the "About" window of the program. I have been treated personally like that many times, but this is not the way you treat security people.

[1] viewtopic.php?t=93307&start=300#p477897
[2] viewtopic.php?f=21&t=130319&p=648231#p648231
[3] viewtopic.php?f=21&t=132974
[4] https://securelist.com/apt-slingshot/84312/
[5] viewtopic.php?f=21&t=105799&p=527088#p527088

But now they are aspiring to be in the range of Enterprise hardware/software vendors, so such topics must receive top priority.

Unfortunately they are just aspiring to get into the enterprise sector. They don't actually try to.
I can't imagine any big enterprise that can wait for over 6 years for fixes/optimizations in BGP, or newer kernel.
Even WISPs that made MikroTik who they are, are switching to other vendors because of terrible wireless support, even since 802.11n.
Nstreme is dead. NV2 is terrible compared to pretty much every other TDMA implementation out there. 802.11ac wave 2? What is that? MikroTik still lives in pre-2016 era

In the meantime MikroTik has dedicated tons of resources to useless features in a futile attempt to appeal to the SOHO market, such as internet detect, kids control, quickstart, smartphone apps etc.

Even MikroTik doesn't appear to know which is their target group anymore...

• WISPs cannot get the best out of their available frequencies when using MikroTik.

• Enterprises cannot rely on "beta" software and tons of unfullfilled promises of eveyrhing will be fixed in v7 (which got released without a routing package - A Router OS without routing. It's like taking the latest car model, for a test drive that doesn't have an engine released yet - need I say more?)

• Home users simply don't understand networking - MikroTik has no business in homes with their current OS - unless they design something akin to TP-Link or Netgear so non-technical people can use. Hell, even cisco guys many times cannot use ROS, and they are supposed to understand networking.

Not to mention customer support. Imagine a big ISP having Cisco gear, but no support from Cisco.
That's MikroTik in the Datacenter/Enterprise.


So considering all that, digital signatures and other security features apparently are fine print...

Enterprises cannot rely on "beta" software and tons of unfullfilled promises of eveyrhing will be fixed in v7 (which got released without a routing package

V7 released ?? Where can I get it ?

RouterOS v7 limited beta:
viewtopic.php?f=1&t=152003

Hi,
Any news?

But now they are aspiring to be in the range of Enterprise hardware/software vendors, so such topics must receive top priority.

Unfortunately they are just aspiring to get into the enterprise sector. They don't actually try to.
I can't imagine any big enterprise that can wait for over 6 years for fixes/optimizations in BGP, or newer kernel.
Even WISPs that made MikroTik who they are, are switching to other vendors because of terrible wireless support, even since 802.11n.
Nstreme is dead. NV2 is terrible compared to pretty much every other TDMA implementation out there. 802.11ac wave 2? What is that? MikroTik still lives in pre-2016 era

In the meantime MikroTik has dedicated tons of resources to useless features in a futile attempt to appeal to the SOHO market, such as internet detect, kids control, quickstart, smartphone apps etc.

Even MikroTik doesn't appear to know which is their target group anymore...

• WISPs cannot get the best out of their available frequencies when using MikroTik.

• Enterprises cannot rely on "beta" software and tons of unfullfilled promises of eveyrhing will be fixed in v7 (which got released without a routing package - A Router OS without routing. It's like taking the latest car model, for a test drive that doesn't have an engine released yet - need I say more?)

• Home users simply don't understand networking - MikroTik has no business in homes with their current OS - unless they design something akin to TP-Link or Netgear so non-technical people can use. Hell, even cisco guys many times cannot use ROS, and they are supposed to understand networking.

Not to mention customer support. Imagine a big ISP having Cisco gear, but no support from Cisco.
That's MikroTik in the Datacenter/Enterprise.


So considering all that, digital signatures and other security features apparently are fine print...

This is so dam TRUE!! +100000 for this!

Winbox v3.24 has been released:

viewtopic.php?f=21&t=161320