MikroTik

What's new in v3.10:

*) fixed crash on latest Windows developer builds;
*) fixed crash on disconnect;

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

Winbox is available here:
http://www.mikrotik.com/download

If you try to upgrade directly from Winbox loader and version is not available, then you might need to wait for a while until cache in path between your device and our servers is refreshed.

Is this version of winbox fixes "has stopped working" message at windows 10 insider preview build 15014 ?

Is this version of winbox fixes "has stopped working" message at windows 10 insider preview build 15014 ?

Yes
Just try yourself

Enviado de meu XT1580 usando Tapatalk

Is this version of winbox fixes "has stopped working" message at windows 10 insider preview build 15014 ?

Yes
Just try yourself

Enviado de meu XT1580 usando Tapatalk

Many thanks for you, I will upgrade to the new build.

Is this version of winbox fixes "has stopped working" message at windows 10 insider preview build 15014 ?

Yes
Just try yourself

Enviado de meu XT1580 usando Tapatalk

Many thanks for you, I will upgrade to the new build.

I can confirm this build of winbox works with windows 10 build 15014

So Far..So Good.. Works correctly using "MacOSX Crossover !!

-tp

UAU, four releases in 10 days!!!

No "disconnect/close"-issue on MacOS with wine-1.9.23 or wine-2.0-rc6

Good work!

Still crashing.
Windows 10 Insider Preview Build 15014.

When I click check for update of winbox then message show "There are no new versions", My current winbox version is 3.9

When I click check for update of winbox then message show "There are no new versions", My current winbox version is 3.9

you can download it from webpage directly. Check-for-update delays are usually down to proxies (cloud) - ether yours or ones that MikroTIk uses for version discribution.

Still crashing.
Windows 10 Insider Preview Build 15014.

Are you sure ?

MostafaAta - If Winbox is crashing it does not necessary mean that this is the same problem. Please try to reproduce crash and then send supout file from router to which you were connected to support@mikrotik.com

MostafaAta - If Winbox is crashing it does not necessary mean that this is the same problem. Please try to reproduce crash and then send supout file from router to which you were connected to support@mikrotik.com

I had upgrade to Windows 10 Insider Preview build 15014 now and Winbox 3.10 is working good.

thanks.

WinBox 10 has been working great for me..Kudos to the MikroTik Team that worked on it.

Future request: Please preserve the state of the "Torch" collect blocks when exiting Winbox so I don't have to keep reselecting them each time?

Thanks !!

-tp

Drag and drop is not working! (for upload files)

Future request: Please preserve the state of the "Torch" collect blocks when exiting Winbox so I don't have to keep reselecting them each time?

+11

I will ask once again.....
This problem can be solved?
It seems it was promised in version 3.0

No "disconnect/close"-issue on MacOS with wine-1.9.23 or wine-2.0-rc6

Good work!

Also, was solved the problem after close the winbox, which left a dead process running on the Arch Linux using wine 2.0rc6-1 or wine 2.0rc5-1.

Greak work!!

WInbox 3.10 running perfect without appcrash notice again. thank u team,

winbox 3.10 solved my issue with 3.9 thank you very much mikrotik !!!

When will new Winbox support that I keep working in the window while uploading new ROS files to a unit?

It is terrible annoying if I am upgrading a client and drag and drop the ROS files into file menu, then I have to sit there waiting till upload is complete to even do simple things!

How come this worked flawlessly in old Winbox, but is impossible in New Winbox???


Also I hate the "Pop up" window created when logging into new units!
If you are unlucky and click somewhere inside winbox window before you make the choice in the remove/keep option window that pops up in start, you have to search through running windows to be able to refind it and click it away. If you have many windows open that can be really annoying while configuring a lot of units simoultanioucly! This also was no problem in the Old Winbox!

Other then these annoyances, I think the NEW Winbox really starts working out well!

Cheers

I will ask once again.....
This problem can be solved?
It seems it was promised in version 3.0

You should check your display settings, custom screen font or similar, it works fine for the rest of us ...

hmmmm, same here, works ok

Normis, it seems from screenshots, that conrad uses other than default text size setting (which in fact works with font DPI). So if application is not able to use current text DPI in text width calculations, results are not correct.
This setting can be changed here: https://technet.microsoft.com/en-us/lib ... 29368.aspx
It is especially useful for example when notebook has large display with very high resolution, because it helps to increase text size.

Yes, Winbox does not play well with non standard DPI.

Suddenly: that's what he's asking to fix =)

Yes, Winbox does not play well with non standard DPI.

Resolution of the display 2560 x 1440
Font very small and I am forced to put the scale of 125%
After that a part of information isn't displayed in winbox log
The problem can be solved, having given the chance to users to move apart fields
(
Разрешение дисплея 2560 х 1440
Шрифт очень мелкий и я вынужден ставить масштаб 125%
После этого часть информации не отображается в winbox log
Проблему можно решить, дав возможность пользователям раздвигать поля )

Sorry, using Webfig is the only option right now. It is not trivial to fix.

P.S: side note. isn't it a bit strange, that a laptop at it's native resolution shows too small text?

Sorry, using Webfig is the only option right now. It is not trivial to fix.

P.S: side note. isn't it a bit strange, that a laptop at it's native resolution shows too small text?

It is difficult to make fields more?
Or to give the chance to change them. (especially in one of versions 3.0b you already lay it, and then in the final version have removed)

Anyone else get this error message when rebooting a board when logged into ROMON? Have to delete all sessions/cache to get Winbox working again.

Actually there is one small annoyance in the latest versions of winbox ...
If I click on a new session (menu/session/new) it does more or less nothing except deleting the IP address from the session text box and I stay connected to the same router but I am unable to close winbox any more ... or exit session ... or anything ... I have to kill the process using task manager ...

MostafaAta - If Winbox is crashing it does not necessary mean that this is the same problem. Please try to reproduce crash and then send supout file from router to which you were connected to support@mikrotik.com

strods- How Can i get support file from router?

Thanks

It fix the crash on windows 2012R2 and WIN10 latest insider build from 15002 to 15019

MostafaAta - If Winbox is crashing it does not necessary mean that this is the same problem. Please try to reproduce crash and then send supout file from router to which you were connected to support@mikrotik.com

strods- How Can i get support file from router?

From Winbox or from Webfig, from the left menu, press "Make supout.rif
The file supout.rif will be created in files.

I've a problem at winbox 3.10, when i make user bypassed it is marked letter B not P and users regular it was marked letter P, please how can i resolve this problem.

I apologized about my poor english language

mbfound - If you get disconnected also from RoMON agent, then Winbox jumps to state where you have to connect to RoMON agent first. It is saved in Winbox loader from previous session. If it is not saved in Managed list, then Winbox does not know RoMON username/password and you can not connect. You have to go Tools/Advanced Mode and delete RoMON manager IP address from RoMON Agent field and then conenct to Agent and to other device afterwards

bratislav - Thank you. We managed to reproduce this problem and will try to fix it as soon as possible.

WalidMorsi - I can not seem to reproduce such issue. Please provide an example.

Wine on debian testing.

On right click on some item , which have ADD menu, and drag mouse over pop menu, and when you point to ADD option, pop menu is closed.

fposavec - Thank you. Managed to reproduce. Actual only when there is Add function with another drop list available. For example, in Interface menu, but no in IP/Address menu.

mbfound - If you get disconnected also from RoMON agent, then Winbox jumps to state where you have to connect to RoMON agent first. It is saved in Winbox loader from previous session. If it is not saved in Managed list, then Winbox does not know RoMON username/password and you can not connect. You have to go Tools/Advanced Mode and delete RoMON manager IP address from RoMON Agent field and then conenct to Agent and to other device afterwards

bratislav - Thank you. We managed to reproduce this problem and will try to fix it as soon as possible.

WalidMorsi - I can not seem to reproduce such issue. Please provide an example.

Please, How can i upload a photo here to provide example ?

Hi guys,

Is it possible to run Winbox from my Dropbox folder?

I have 58 highsites and it would be great if i could sync my winbox between my office and my laptop.
If so, which files would i need to copy to my Dropbox folder?

Clive.

In fact it is bypassed, and look blocked.

mbfound - If you get disconnected also from RoMON agent, then Winbox jumps to state where you have to connect to RoMON agent first. It is saved in Winbox loader from previous session. If it is not saved in Managed list, then Winbox does not know RoMON username/password and you can not connect. You have to go Tools/Advanced Mode and delete RoMON manager IP address from RoMON Agent field and then conenct to Agent and to other device afterwards

bratislav - Thank you. We managed to reproduce this problem and will try to fix it as soon as possible.

WalidMorsi - I can not seem to reproduce such issue. Please provide an example.

Please, How can i upload a photo here to provide example ?

WalidMorsi - Image can not be opened without registered account. Please provide commands how we can add problematic entry or send screen shot to support@mikrotik.com

Hi guys,

Is it possible to run Winbox from my Dropbox folder?

I have 58 highsites and it would be great if i could sync my winbox between my office and my laptop.
If so, which files would i need to copy to my Dropbox folder?

Clive.

You can move sesion folder to dopbox and then synced with many pc-s.

On winbox tools -> Move session folder ...

I use ownclod and works like charm

WalidMorsi - Image can not be opened without registered account. Please provide commands how we can add problematic entry or send screen shot to support@mikrotik.com

it says "Your session has either timed out or has not been correctly established. Please login again."
use 'Attachments' tab when editing message to attach a picture to your post

Big problem!

Compatibility problems with older RouterOS versions. I had one CRS226 with v.6.30 and was not able to configure VLANs in switch mode.

It works with WinBox 3.7, but with 3.10 it looked like switch was in router mode i.e. there was no VLAN menu under 'Switch'. I was unable to understand what was wrong until I tried this with older WinBox.

These things necessitate the need for keeping multiple versions of WinBox to be able to work. Fortunately it is technically possible...

nmt1900 - I can not seem to reproduce such problem. Does it persist if in 3.10 Winbox loader you go to Tools/Clear Cache and only then connect to device?

not crashed, yet both on "Stable", eg 1607/RS1 version and "legacy" retail build(august 2016) of Win10.
can't say anything bout "insider preview" branch, yet(not time to test this wave).

Log Name: Application
Source: Application Error
Date: 2/1/2017 15:55:37
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-VIET79P
Description:
Faulting application name: winbox.exe, version: 0.0.0.0, time stamp: 0x382f3815
Faulting module name: USER32.dll, version: 10.0.15019.1000, time stamp: 0xb2624dbc
Exception code: 0xc000041d
Fault offset: 0x00062c01
Faulting process id: 0x20d0
Faulting application start time: 0x01d27c92dc694edb
Faulting application path: D:\install\winbox.exe
Faulting module path: C:\WINDOWS\System32\USER32.dll
Report Id: 226f1173-69d8-4f0a-9d37-092e40aa8eb7
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-02-01T13:55:37.683152500Z" />
<EventRecordID>1178</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-VIET79P</Computer>
<Security />
</System>
<EventData>
<Data>winbox.exe</Data>
<Data>0.0.0.0</Data>
<Data>382f3815</Data>
<Data>USER32.dll</Data>
<Data>10.0.15019.1000</Data>
<Data>b2624dbc</Data>
<Data>c000041d</Data>
<Data>00062c01</Data>
<Data>20d0</Data>
<Data>01d27c92dc694edb</Data>
<Data>D:\install\winbox.exe</Data>
<Data>C:\WINDOWS\System32\USER32.dll</Data>
<Data>226f1173-69d8-4f0a-9d37-092e40aa8eb7</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Hipsters may use whatever they want, we don't care. But reasonable admins with working brain use 2.2.18.

I am glad that I am not the only one using v2.2.18

But reasonable admins with working brain use 2.2.18.

Can you give any reason why? Very surprised about this. I use only newest Winbox, it works excellent and has so many neat features, that were not possible before.

BTW by the widely accepted definition of "hipster", it would be quite opposite. Hipsters would use any older and less popular version (words associated with hipsters are indie, alternative, vintage, ironic)

Can you give any reason why? Very surprised about this. I use only newest Winbox, it works excellent and has so many neat features, that were not possible before.

Some new features don't make up for the lost productivity that v3 imposes.
I've mentioned my problems with winbox 3 many times since v3.0 (~2015).

http://forum.mikrotik.com/viewtopic.php ... 66#p570666
http://forum.mikrotik.com/viewtopic.php ... ox#p543538
http://forum.mikrotik.com/viewtopic.php ... ox#p523127
http://forum.mikrotik.com/viewtopic.php ... ox#p518630
http://forum.mikrotik.com/viewtopic.php ... ox#p506559

And to me it seems that you don't care about your customers. I see no interest taking into account your customer's feedback.

What is your offer, to make selectable behavior? Most of these were done because of other user requests. You know how it is. We will fix your issues but all the others will complain.

I see that you have the following complaints:

1. Shortcut keys are different, because CTRL was added (this was done to avoid accidental problems)
2. Winbox (not loader) always opens on Main monitor, not where it was open before (this was done to solve problems on laptops, Winbox 2 often got lost because external screen was disconnected)
3. Escape key does not quit loader. (no other Windows program does this. ALT+F4 is the normal key combo)

Winbox 3.x is OK, only one problem which I have is - durig upload file (for example new Router OS) is not posible working in active window.
After file is uploaded, then is possible working.
In winbox 2.2.18 this works. Can you fix it?

What is your offer, to make selectable behavior?

That's a good idea. Even though I personally don't care about these specific shortcuts, I can definitely appreciate how annoying it is when you lose ability to use shortcuts you were used to. I had that experience myself when WinBox 3 at first didn't understand Ctrl+Ins and friends for clipboard operations and I didn't like it a bit. To have program remember its position on right monitor is reasonable request too. If it's undesired or dangerous behaviour for some (or most), then an off by default option is a solution that can make everyone happy.

Winbox 3.x is OK, only one problem which I have is - durig upload file (for example new Router OS) is not posible working in active window.
After file is uploaded, then is possible working.
In winbox 2.2.18 this works. Can you fix it?

+1
This is very annoying on slow connections.

Could you please add a scroll bar to some windows? For example firewall rule window as on screenshot. It's very annoying, I'm used to winbox, but now I have to use terminal to change something. Already saw same request long time ago, but it's still unimplemented for some reason.
I'm using a notebook with 1366*768 resolution.

I will ask once again.....
This problem can be solved?
It seems it was promised in version 3.0

I have this problem also. Windows 10, using a 24" monitor with DPI set to 125. The Log display seems to be the only one with an issue.

Could you please add a scroll bar to some windows?

It is unusable on smaller screens ... You could use WebFig for now ...

How small is that screen? What resolution? We have tested using standard sizes, like 11" and 1200x720 for example.

How small is that screen? What resolution? We have tested using standard sizes, like 11" and 1200x720 for example.

Hi, normis, actually it's not that small, as I wrote in my post, it's a laptop with 1366*768, 15.6"

I'm not sure, but I think this problem appeared on latest winbox/routeros version.

( http://forum.mikrotik.com/viewtopic.php ... 09#p581808 )
Note: Sorry for crossposting, but probably I've wrong posted earlier and this is a winbox problem.

"/ip accounting" settings are not correctly shown by winbox (current/lastest 3.10), testing on board CRS125.

Steps to reproduce:
1) Try to configure/enable ip accounting via winbox > all seems to be fine (service works)
2) Exit winbox and relogin, you will see ip accounting disabled and web-access settings are not shown (despite service is working)
3) If you check via CLI, settings are there, only winbox ignore them.

Also "/ip traffic-flow" have the same behaviour (winbox 3.10, tested on board RB3011).

Anyone can confirm, please ?

Sorry, using Webfig is the only option right now. It is not trivial to fix.

P.S: side note. isn't it a bit strange, that a laptop at it's native resolution shows too small text?

Some manufacturers seem to like putting 2k-4k panels in 13 -15" laptops, not really sure the point to be honest.

Also windows 10 defaults to 125% scaling on some 15" 1080p laptops, I usually change it to 100% and it's about the smallest I'd like to go before things get uncomfortable.

Tried windows on a 13" retina mac once, that's fun on a app that doesn't do scaling.

bajodel - We will try to fix accounting issue as soon as possible, however I can not reproduce same issue with Traffic Flow settings.

How small is that screen? What resolution? We have tested using standard sizes, like 11" and 1200x720 for example.

1366x768 is quite common. I've had this issue too. I need to scroll, especially when I turn on "Advanced" options in the Wifi menus.

Winbox is not displaying correct information for Ip accounting. Winbox 3.10 CCR1009-8G-1S-1s+ V6.37.4

Winbox 3.11 has been released:
http://forum.mikrotik.com/viewtopic.php?f=21&t=118408