What's new in v3.9:

*) fixed problem - some item disable did not work;
*) fixed problem - port numbers & related info could not be specified in firewall after tcp protocol was selected;

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.

Thanks guys for Fix.

Can we have MacOS version of WinBox instead of wine wrapper or ... emulators.

Cheers

Thanks guys for Fix.

Can we have MacOS version of WinBox instead of wine wrapper or ... emulators.

Cheers

Use Webfig.

Thanks guys for Fix.

Can we have MacOS version of WinBox instead of wine wrapper or ... emulators.

Cheers

Use Webfig.

It is not a WinBox and never be. with win box you can do way more stuff in few sec and compare and check in web your view is very limited to one page. ROS have a lot good feature compare to 2.97 since I was started with ROS, just hope one day I see WinBox for Mac and Linux, which is 100% missing it.

Still crashes on Win10 Insider, please get that heap corruption bug fixed.

Still crashes on Win10 Insider, please get that heap corruption bug fixed.

It is a Windows problem, it was already reported on feedback hub


Enviado de meu XT1580 usando Tapatalk

I agree having a native version for MacOS would be really nice to have as I am sure if you do a poll to see how many OSX users there are more then you think. Meanwhile the Wine version which is floating around works quite well, most of the time.

You have to remember a lot of us and organisations do not run Winblows operating systems, we either use Linux, MacOS, ChromeOS or something else. I know this comapny I am working for right now only uses Mac's, Windows is banned.

I agree having a native version for MacOS would be really nice to have as I am sure if you do a poll to see how many OSX users there are more then you think. Meanwhile the Wine version which is floating around works quite well, most of the time.

You have to remember a lot of us and organisations do not run Winblows operating systems, we either use Linux, MacOS, ChromeOS or something else. I know this comapny I am working for right now only uses Mac's, Windows is banned.

It is very necessary to have a MacOS and most of Mikrotik staff using MacOS too, most of the networking guys I just now which is a lot they all using Mac.

lets hope they going to change they mind and ask one of the developer to easily develop one for MacOS then Im totally going to wipe my Mac and clean Install the OS without any footprint of Windows.

I agree having a native version for MacOS would be really nice to have as I am sure if you do a poll to see how many OSX users there are more then you think. Meanwhile the Wine version which is floating around works quite well, most of the time.

You have to remember a lot of us and organisations do not run Winblows operating systems, we either use Linux, MacOS, ChromeOS or something else. I know this comapny I am working for right now only uses Mac's, Windows is banned.

It is very necessary to have a MacOS and most of Mikrotik staff using MacOS too, most of the networking guys I just now which is a lot they all using Mac.

lets hope they going to change they mind and ask one of the developer to easily develop one for MacOS then Im totally going to wipe my Mac and clean Install the OS without any footprint of Windows.

Aye

Noticed this in 3.8 but now I see 3.9 is out and it still occurs.

When quitting winbox wine is left running. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4)

Steps to reproduce:
- launch winbox
- connect to a device
- click on the session menu and then select exit (or click on the exit button on the left menu)

Expected result: Winbox closes and completely exits.

Observed result: Winbox's windows closes but the process is still left running. Running killall wine will close any outstanding processes. Right clicking on the icon in the dock and picking quit doesn't actually quit things. Also using force close to terminate the wine process works.

If you just open winbox and don't connect to a device and then click either the os x menu close button, or pick the file menu and select exit, winbox closes as expected and wine doesn't leave any extra processes running.

I realize this is a bit outside normal support (I am attempting to run winbox on a mac) but since it was working in 3.7 it seems there is a regression in 3.8 (and 3.9) to a state where it no longer closes completely.

If any assistance is required testing please feel free to let me know.

chris.

When selecting multiple entries in the neighbors tab you can't connect to all.

On the manage tab you can select multiple devices and the connect button changes to connet to all and functions as expected.

Not sure if this is something new, or if I just never realised which tab I was on when connecting to devices.
So if it isn't a bug, then consider it a feature request

chris.

Noticed this in 3.8 but now I see 3.9 is out and it still occurs.

When quitting winbox wine is left running. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4)

Steps to reproduce:
- launch winbox
- connect to a device
- click on the session menu and then select exit (or click on the exit button on the left menu)

Expected result: Winbox closes and completely exits.

Observed result: Winbox's windows closes but the process is still left running.

Exact same problem occurring here as well. Made a new wrapper to test in Winery and the same problem occurs.

Noticed this in 3.8 but now I see 3.9 is out and it still occurs.

When quitting winbox wine is left running. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4)

Steps to reproduce:
- launch winbox
- connect to a device
- click on the session menu and then select exit (or click on the exit button on the left menu)

Expected result: Winbox closes and completely exits.

Observed result: Winbox's windows closes but the process is still left running. Running killall wine will close any outstanding processes. Right clicking on the icon in the dock and picking quit doesn't actually quit things. Also using force close to terminate the wine process works.

If you just open winbox and don't connect to a device and then click either the os x menu close button, or pick the file menu and select exit, winbox closes as expected and wine doesn't leave any extra processes running.

I realize this is a bit outside normal support (I am attempting to run winbox on a mac) but since it was working in 3.7 it seems there is a regression in 3.8 (and 3.9) to a state where it no longer closes completely.

If any assistance is required testing please feel free to let me know.

chris.

I am still seeing the same thing using "Crossover", remaining Winbox processes after exiting. Downgrading to Winbox 3.7 solves the problem.

-tp

Guys. Can you add thew shortcut keys back in? Specifically enable, disable, delete. I don't understand why this has been removed.

Hi
All windows 10 insider preview user that is getting winbox crash.

I was thinking about
Maybe we get to work using a weird work around
If we install the the Linux that Windows is offering and inside we run wine?
Maybe it works



Enviado de meu XT1580 usando Tapatalk

both 3.8 and 3.9 do random crashes on win10 x64 home and 100% crash at exiting(instead of correctly closing session). 3.7(and earlier versions) works just fine.

...When quitting winbox wine is left running. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4)...

A workaround seems to be click on the session menu and pick disconnect. Then when back at the connect window pick file and then exit. Winbox and wine then close as expected.

chris.

...When quitting winbox wine is left running. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4)...

A workaround seems to be click on the session menu and pick disconnect. Then when back at the connect window pick file and then exit. Winbox and wine then close as expected.

chris.

My workaround is to revert back to Winbox v3.7

Maybe they'll figure it out eventually...

...When quitting winbox wine is left running. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4)...

A workaround seems to be click on the session menu and pick disconnect. Then when back at the connect window pick file and then exit. Winbox and wine then close as expected.

chris.

My workaround is to revert back to Winbox v3.7

Maybe they'll figure it out eventually...

Same, 3.7 when closing the window doesn't show crash error anymore. 3.8 and 3.9 crashes on exit

Faulting application name: winbox 3.8.exe, version: 0.0.0.0, time stamp: 0x382f3815
Faulting module name: winbox 3.8.exe, version: 0.0.0.0, time stamp: 0x382f3815
Exception code: 0xc000041d
Fault offset: 0x000957b8
Faulting process id: 0x1228
Faulting application start time: 0x01d271a2d29c0109
Faulting application path: C:\Users\x7007\Desktop\1\winbox 3.8.exe
Faulting module path: C:\Users\x7007\Desktop\1\winbox 3.8.exe
Report Id: fabc11a8-e8de-4cfb-96c4-4e518a3c03f3
Faulting package full name:
Faulting package-relative application ID:

I just wish WinBox would use a more standard Window than the one they use - in regular Windows apps you can double-click on a divider between columns and it will expand to the size needed to display the contents of that column - in WinBox we need to click and drag each column divider.

Also, WinBox needs a way to allow the possibility of a template to be used (and modified) so that the same columns are displayed on any MikroTik router that is connected to - especially new ones, so that we don't have to go through all the column options on each and every router we connect to.

Also, WinBox needs a way to allow the possibility of a template to be used (and modified) so that the same columns are displayed on any MikroTik router that is connected to - especially new ones, so that we don't have to go through all the column options on each and every router we connect to.

That's exactly what "Session:" is. Does it not do some detail you want?

Also, WinBox needs a way to allow the possibility of a template to be used (and modified) so that the same columns are displayed on any MikroTik router that is connected to - especially new ones, so that we don't have to go through all the column options on each and every router we connect to.

That's exactly what "Session:" is. Does it not do some detail you want?

Aha - yes! So, "sessions" are not really the current connection that's open, but are more like views? Right - now this makes sense. I can create a view I need, save it as a session and then use that "view" on various clients. AWESOME!

I'v my winbox 3.7,3.8 & 3.9 getting crashed after updating my OS (Win 10 pro x64) to release # "15007.100" insider preview release.

both 3.8 and 3.9 do random crashes on win10 x64 home and 100% crash at exiting(instead of correctly closing session). 3.7(and earlier versions) works just fine.

On WIndows Server 2012R2 as well

I can also confirm WinBox 3.9 not exiting properly on mac os X ... it is annoying but winbox has an option to connect to mac address which have proven to be lifesaving for me manny times. Webfig of course does not have this option. Also I like to have my windows and sessions as I left them for different routers I manage. A native macos app would be very welcome in the future... also ios app, not just android. I am not an apple fanboy, but I just find apple ecosystem more suitable for my needs at this moment

JF.

The same problem winbox 3.6-3.9 do no save import hosts, do not see hosts
windows 10 (3 PC)
windows 2008 server (1 server)
only work winbox 2.2.18

Windows Insider crashes and crashes on Exit will be fixed in next Winbox release. Thank you to those who reported these issues to support and sent supout files.

same problem here Windows 7 64-bit when exit winbox app
solution using back winbox 3.7

Windows Insider crashes and crashes on Exit will be fixed in next Winbox release. Thank you to those who reported these issues to support and sent supout files.

Thanks
Any idea when will be released?


Enviado de meu XT1580 usando Tapatalk

Today Microsoft published new build 15014 of Windows 10. Winbox is still crashing down.

Also running insider previews and I'm just realizing now how attached I am to Winbox!

Mayby it's time for a Winbox Insider program? 

same problem here Windows 7 64-bit when exit winbox app

Code: Select all

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	winbox.exe
  Application Version:	0.0.0.0
  Application Timestamp:	382f3815
  Fault Module Name:	StackHash_32d6
  Fault Module Version:	6.1.7601.23569
  Fault Module Timestamp:	57f7bb79
  Exception Code:	c0000374
  Exception Offset:	000ce8fb
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	32d6
  Additional Information 2:	32d6e2e1eb7016a26cfaadb32c99e841
  Additional Information 3:	9277
  Additional Information 4:	92778b60cb7b5a3b1e999db567f3c95b

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

solution using back winbox 3.7

same here

Problem signature:
Problem Event Name: APPCRASH
Application Name: winbox 3-9.exe
Application Version: 0.0.0.0
Application Timestamp: 382f3815
Fault Module Name: StackHash_3be9
Fault Module Version: 6.1.7601.18869
Fault Module Timestamp: 55636317
Exception Code: c0000374
Exception Offset: 000cea5f
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 9226
Additional Information 1: 3be9
Additional Information 2: 3be99e5a1f435c5c13f706cf2df994e0
Additional Information 3: c2ef
Additional Information 4: c2efffb2b4619e880e7930dc930de719


i deletede cache and winbox session folder, problem persists, y cannot rollback to 3.7 because some of routers i admin are on 6.38.1

Hi, im using the 3.9 version.

Sadly im not able to access throw cloud service.
Can you guys recomend me any topic for setup the remote access?

My primary router is a Mikrotik Rb2011 UIAS-RM conected for PPPOE to my ISP (Dynamic IP service).
Have some Ubiquiti antenas and ip cameras... its all working good in my local network my problem is to access from my office.

same here

Code: Select all

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	winbox 3-9.exe
  Application Version:	0.0.0.0
  Application Timestamp:	382f3815
  Fault Module Name:	StackHash_3be9
  Fault Module Version:	6.1.7601.18869
  Fault Module Timestamp:	55636317
  Exception Code:	c0000374
  Exception Offset:	000cea5f
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	9226
  Additional Information 1:	3be9
  Additional Information 2:	3be99e5a1f435c5c13f706cf2df994e0
  Additional Information 3:	c2ef
  Additional Information 4:	c2efffb2b4619e880e7930dc930de719

i deletede cache and winbox session folder, problem persists, y cannot rollback to 3.7 because some of routers i admin are on 6.38.1

what happen if i remote router on 6.38.1 using winbox 3.7 ? any problem in there ? all router i admin use 6.38.1
This I've done: trying disable windows DEP , delete folder on appdata, run ccleaner. still nothing change anything.
but when i'm trying reinstalling fresh windows , winbox 3.9 app running ok without app crash notice hmmm

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

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