What's new in v3.39:

Important note!!!

Upgrade from older WinBox versions might not work due to the new digital signature. Manual WinBox upgrade is required.

*) added support for QR code field;

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

Quick Tip: Now you can use Back To Home feature with regular Wireguard app in your phone or other device. Once BTH has been set up, in your "IP -> Cloud" menu you will be able to scan a QR code from any device with a stock Wireguard app, to quickly configure the tunnel there.

Apart from this:

*) added support for QR code field;

If one doesn't use that feature at all, do you still recommend upgrading because something else, not reported, has also been fixed?

Thank you.

The only changes:

1. New EXE signature (no effect for users)
2. QR code support

The dark theme is an important feature that you do not add!

Why is it important?

would it be possible to add an option to auto enable safe mode on connection?

I tried to upgrade... upgrade file is corrupt, on three different pc

EDIT: I tried the auto-upgrade mode and if failed with 3 different PCs.
I didnt replace the exe though.

I tried to upgrade... upgrade file is corrupt, on three different pc

Did you bother to read opening post in this thread. It says:

Important note!!!

Upgrade from older WinBox versions might not work due to the new digital signature. Manual WinBox upgrade is required.

Yes, I read. It says "might not work". I just reported my experience.

The problem is that you wrote "upgrade file is corrupt" which is something very different from what was mentioned in announcement (and is probably the reason for upgrade to fail). If you phrased your post like "upgrade fails indeed, I tried on 3 different pcs", the meaning would be whole lot different (for starters, it would show that you did read the announcement and that you encountered the predicted problem).

You are right! I just wrote quickly

New phrasing, in case this will be more clear:

Built in upgrade will not work! This is because new Winbox has new exe signature. It will say "upgrade file corrupt". So download new winbox manually here: https://mt.lv/winbox64.

Yes, I read. It says "might not work". I just reported my experience.

I kind of agree there. That line should be changed to "it will probably not work so upgrade manually".
EDIT: and it's done

I've seen it happen too (hey, maybe I was lucky... ) but after the first occurrence I already made my conclusion how to proceed for the second one.
And the message effectively said "file is corrupt". Quite confusing ...

Windows find some virus on 64 version

Try other antivirus software

when running on windows 10 enterprise, up to date as of yesterday

...new Winbox has new exe signature.

Something's wrong with this signature:

RE-DOWNLOAD PLEASE.
FIXED

Why hasn't it been added to the window header next to the name "WinBox" to display its version when it is connected?

The dark theme is very interesting and useful for tired eyes.

Why is it important?

Maybe Dark Theme is not important but, nowadays is a very common feature on most desktop applications, many websites include it also, in my case i use it every day when available

And I avoid it like the plague...
I hate dark theme.

Those who want the black theme don't really work, they just want it as a whim "because others do it"...

Try to work under the sun with a fuck–g black theme that doesn't let you see correctly what is present on the screen....

Quod Erat Demonstrandum.

Try other antivirus software

something is in the 64x is triggering the Microsoft Defender SmartScreen and preventing from downloading, the 32bit is ok....

See above, re-download for the fix

Those who want the black theme don't really work, they just want it as a whim "because others do it"...

Try to work under the sun with a f---–g black theme that doesn't let you see correctly what is present on the screen....

Will all respect intended, I work in front of three large monitors for 10+ hours a day, dark themes save my eyes a lot of stress.

Just because you don't see it as useful does not automatically mean it's not useful to anyone. ;)

I would very much like that feature.

Those who want the black theme don't really work, they just want it as a whim "because others do it"...

Try to work under the sun with a fuck–g black theme that doesn't let you see correctly what is present on the screen....

"don't really work" ... how come you conclude that?
working at a DC for over 6 years and in IT/ISP well over 10 years and where there is a good implementation of a dark theme i use it. it is way easier on the eyes

if you are out in the sun - switch to your beloved whatever-not-dark-theme or upgrade to a good display

EDIT:
+1 for dark-theme option to be switchable

I am mostly inside.
Usually I don't even switch on the lights in the office because I can't stand the light.
And yet I don't want dark theme.

Working with computers since 1980.
I started on monochrome CRT screens so I know what it is like to have black background.
Still don't like it.

I am mostly inside.
Usually I don't even switch on the lights in the office because I can't stand the light.
And yet I don't want dark theme.

Working with computers since 1980.
I started on monochrome CRT screens so I know what it is like to have black background.
Still don't like it.

same with the light.

well ... good for you if you do not like it. why is it such a thing for people here on a dark theme to be asked for implementation?
if it is there as an option and you do not need to use it... do, not, use, it!

I tried to update my Winbox on several of my computers to v3.39

All of them give me "ERROR: Upgrade file was corrupted"

I get it some do want dark theme.
But it is not there now and there are more urgent things to fix, no ?
So let's use resources where they are most beneficial.

And then, when all is done and fixed, we pull out the someday/maybe list and see what's left there

I tried to update my Winbox on several of my computers to v3.39

All of them give me "ERROR: Upgrade file was corrupted"

corrupted-001.png

Manual upgrade

See above, re-download for the fix

downloaded 5 minutes ago (manually downloaded from website)

I tried to update my Winbox on several of my computers to v3.39

All of them give me "ERROR: Upgrade file was corrupted"

corrupted-001.png

Manual upgrade

OOOooo , I guess I should read the post first then do ...

The dark theme is very interesting and useful for tired eyes.

Yet again...

If you are not interested in the dark theme, then you should not respond to such messages, and do not use the dark theme. That's what the right to choose is for.

Chechito
Also that problem should have been fixed ?
But the file should be named winbox64.exe ?

See above, re-download for the fix

downloaded 5 minutes ago

Yet again...

The dark theme is very interesting and useful for tired eyes.

To everyone else

If you are not interested in the dark theme, then you should not respond to such messages, and do not use the dark theme. That's what the right to choose is for.

Chechito
Also that problem should have been fixed ?
But the file should be named winbox64.exe ?

name was modified by me, to be able to distinguish from the other versions in the folder

To everyone else

If you are not interested in the dark theme, then you should not respond to such messages, and do not use the dark theme. That's what the right to choose is for.

Yeah, i agree with you nobody said anything about a Mandatory not switchable Dark Theme

interested people in dark theme just want to have the option to be able to select Dark Theme if they want

i cant believe this kind of clarifications are needed for such a simple topic

looks like empathy is scarce these days

See above, re-download for the fix

Microsoft edge keep saying that have a virus on the 64bit

Just manually downloaded winbox64.exe and it still has the invalid digital signature due to being signed after the signing certificate had expired... Either it has been signed with an expired certificate (and signed after the certificate expiry date) or if MT have fixed the problem (i.e. They must have signed it with an expired certificate to start with - Yes they did I have the digitally signed proof, published it, then published a new file after discovering the mistake - hopefully).

So either (1) They are continuing to sign with an expired key or they have update the key, resigned the file and there is a caching issue at MT end (since this is the first time I've downloaded the file).

Content-Length 2287960
Content-Type application/octet-stream
Date Wed, 26 Jul 2023 23:41:18 GMT
ETag "64c0f648-22e958"
Last-Modified Wed, 26 Jul 2023 10:32:40 GMT
Server nginx/1.18.0

winbox64.exe SHA256: 475ff5996ad6558f2966eb26129e167d48105105b0e4d5e44b8c4d57f6a84627

It says the certificate "Mikrotikls SIA" is valid from "10-Feb-2020 to 10-May-2023", so obviously that certificate would be outside of its validity range to have just signed a new winbox64.exe executable.

@MT please check your signing key is updated, and that your publishing system is using the new signing key.

@normis

how u mean , Back To Home feature with regular Wireguard app in your phone or other device.

Does Back To Home work independent?

pls need more info

between dark theme and an option to automatically turn safe mode on, i would do safe mode first and then dark theme

I found that there are 2 versions of winbox64.exe when I download from different networks on Mikrotik main site. It looks like some CDN / Web servers are not updated with latest version. Mikrotik should publish the hash of their firmwares and winbox software

Expired certificate winbox64.exe SHA-256
SHA-256 475ff5996ad6558f2966eb26129e167d48105105b0e4d5e44b8c4d57f6a84627

Valid certificate winbox64.exe SHA-256
SHA-256 b4ff98aa38183948beb78b2d5077bad116d166b520f869bcfb5936811fd11dad

If now Winbox has *) added support for QR code field, what about button or command to generate QR code for Wi-Fi login from configuration?

i think i got that, with back-to-home u can add allowed-address manually,which is so hendy.

Thanks for the FIX for the QR code, much better!
Re-downloaded as advised.

If now Winbox has *) added support for QR code field, what about button or command to generate QR code for Wi-Fi login from configuration?

Yes, it gives possibility to make something like that for the future. Do you really need it in the Winbox? Will you show Winbox to your family, when they come over? You can just use this and print it: https://www.qr-code-generator.com/solut ... i-qr-code/

If now Winbox has *) added support for QR code field, what about button or command to generate QR code for Wi-Fi login from configuration?

Yes, it gives possibility to make something like that for the future. Do you really need it in the Winbox? Will you show Winbox to your family, when they come over? You can just use this and print it: https://www.qr-code-generator.com/solut ... i-qr-code/

I usually use https://qifi.org/, however it would be nice to have this feature directly in Winbox, better with possibility to export it as image. As no one can be 100% sure that SSID and password is not stored anywhere by 3rd party (owner of QR generator website). Also it might come to Mikrotik mobile apps (Home or Pro app), right? :D It is just "nice to have" feature (configure network, export QR, print it and connect). :D

http://asciiqr.com/index.php?i=&t=WIFI% ... word%3B%3B

How did you get the logo in the middle?

With my hands.

what else 😜🤪

what else 😜🤪

:lol:

"Gimp" ?

INFO: regarding QR codes for wifi processed locally...

1/ to generate and print QR -- can be done via label printers and their sw -- they can do that also as batch processing using database/csv.

2/ just to share QR code for wifi -- some smartphones today can natively show QR code for connected wifi -- just tap on connected wifi in the settings.
Of course you can also printscreen displayed QR code and send the image to any printer -- only some taps on the phone.

SIDENOTE1: Not having phone photos autosync to the cloud (and also not having wifi logins autobackup to the cloud) can be recommended...
SIDENOTE2: Some more advanced auth methods than one pwd (Personal mode) for SSID can be recommended also.(i.e. Enterprise ways)
and RouterOS offers several ways/functions for that.

what else 😜🤪

:lol:

"Gimp" ?

no, all good :-)

QR Code is very useful if it would be implemented in UserManager-Users.
There is a field OTP Secret.

It works which GoogleAuth!

I use this QR Generator:
https://jwessel.github.io/totp-gauth-to ... rator.html

But if Mikrotik would implement this in Winbox or even better WebPortal. We could have a nice 2FA solution for VPN!

As this apparently has turned into a wishlist for winbox, let me add my 2 cents:
- settable timeout for router connections, so that a 5 second interruption of the network does not always result in a disconnect
- better recognizable "active" state of the Safe Mode button (make it yellow or red when active, not just a different shade of grey)
- allow to "lower" a window in the windows list (e.g. via right-click), in addition to the current possibility of "rising" a window
- make the BGP "sessions" window auto-refreshing, like the BGP "peers" window was with v6 RouterOS (and like most other windows are)
- change the .viw files from binary to some user readable and editable format (JSON, XML, text, whatever). I HATE to have to discard an entire .viw file because there is some small corruption in it. and unfortunately, these occur all to easily over time
- fix the bug in skin handling where the menu buttons hidden in webfig skin still appear in winbox

- settable timeout for router connections, so that a 5 second interruption of the network does not always result in a disconnect
+1

- better recognizable "active" state of the Safe Mode button (make it yellow or red when active, not just a different shade of grey)
+1

- allow to "lower" a window in the windows list (e.g. via right-click), in addition to the current possibility of "rising" a window
=

- make the BGP "sessions" window auto-refreshing, like the BGP "peers" window was with v6 RouterOS (and like most other windows are)
+1
+1
+1
+1
+1
+1
..........

- change the .viw files from binary to some user readable and editable format (JSON, XML, text, whatever).
uhm... +1

- fix the bug in skin handling where the menu buttons hidden in webfig skin still appear in winbox
+2

Mikrotik should publish the hash of their firmwares and winbox software

Totally agree that MT should publish the Winbox hash in their checksums list like their NPKs. In the meantime, I'm used to validating the digital signature. But I recently moved to running Winbox in Wine and I wasn't able to find a GUI way to do that. Here's what I ended up doing:

* Downloaded Sigcheck from Sysinternals
* Opened Terminal and typed "wine cmd" to get a Windows command prompt
* Navigated to the Sigcheck path and entered the following: sigcheck -accepteula -a -i your_Winbox_path

In the output, you see whether the file is signed or not as well as show/validate the certificate chain. And yes, on real Windows you could follow these steps as well if you'd rather use the command line for some reason.

@roe1974

https://www.qrcode-monkey.com/#email

@roe1974

https://www.qrcode-monkey.com/#email

THX !!!!! :-)

- better recognizable "active" state of the Safe Mode button (make it yellow or red when active, not just a different shade of grey)

+1

- allow to "lower" a window in the windows list (e.g. via right-click), in addition to the current possibility of "rising" a window

you can cycle trough windows in WinBox with [F6] as a workaround

- make the BGP "sessions" window auto-refreshing, like the BGP "peers" window was with v6 RouterOS (and like most other windows are)

+1 YES PLS!

- fix the bug in skin handling where the menu buttons hidden in webfig skin still appear in winbox

still a thing? works for me

- allow to "lower" a window in the windows list (e.g. via right-click), in addition to the current possibility of "rising" a window

you can cycle trough windows in WinBox with [F6] as a workaround

Thanks! I did not know that. I always open a Log window and set it to full screen size and use that as a backdrop to open other windows on top of that.
One click in the wrong place and the Log window is the top window and all others are gone.
I would like to "lower" the Log window e.g. via Windows->Log->Right-Click so all the others re-appear.
However, with a couple of F6 presses it also sort of works and is a bit easier than going along all other windows to raise them.

- fix the bug in skin handling where the menu buttons hidden in webfig skin still appear in winbox

still a thing? works for me

Try to hide the MPLS menu. It has several sub-menus. When (in Webfig) MPLS is removed (and even when all sub-menus are removed), in Webfig the MPLS item is completely gone, but in winbox it remains visible but when clicked it shows an "empty" (small) submenu.
When an item like Quick Start, which has no sub-menus, is removed it correctly disappears from the menu bar.

If any GUI improvements to winbox...

1/ BIG THANKS FOR KEEPING the old=archaic=great=reliable=clean=GOLDEN_STYLE of GUI without any "modern improvements"
2/ ...to ...
100/ repeat of the (1/) ... no joking. I am just that thankful ...

About welcome improvements not mentioned yet in this thread.

101/ better definition of three/four Alt-hotkeys in main menu -- as e.g. now there is a lack of resolution for Session/Settings as shown below.
(Suggestion is based on my experience fixing such things in MS dev center 20+ years ago.)

Collision = (black+bold=to_keep) vs (red+bold=to_change),
Solution+Suggestion = (blue+bold=changed-fixed)
now: | &Session | &Settings | &Dashboard
new: | &Session | S&ettings | &Dashboard

now <&Session>: | &New | &Open | &Save | &Save As | &Autosave on Close | &Close All Windows | &Disconnect | &Exit |
new <&Session>: | &New | &Open | &Save | Save &As | A&utosave on Close | &Close All Windows | &Disconnect | E&xit |

And of course underscores for Alt-hotkeys in menus to be shown when it is set so in OS (or maybe better - always...)

102/ EDIT: reworded -- making more clear:
Wondering why there is <Exit> button on the left pane on one click with no confirmation,
when the same can now user do safer by two clicks via main menu (Session > Exit).
WHY IMPORTANT?: Because misclicking on the <New WinBox>
cause immediate/without_confirmation <Exit> (hopefully not exitus in some stress situation).
So maybe a NEW main menu item <S&ettings> --> <Deactivate-Hide Exit button> as is for <Hide Passwords>

103/ Would appreciate <NewWinBox> and <Windows> as NEW main menu items:
now main menu = &Session | &Settings | &Dashboard |
new main menu = &Session | S&ettings | &Dashboard | &NewWinBox | &Windows |

---
And if none of that will happen ... never mind. WinBox is one of my favorite sw helping me to keep a good mood.

If any GUI improvements to winbox...

1/ BIG THANKS FOR KEEPING the old=archaic=great=reliable=clean=GOLDEN_STYLE of GUI without any "modern improvements"
2/ ...to ...
100/ repeat of the (1/) ... no joking. I am just that thankful ...

+1

Thanks! I did not know that.

ur welcome

Try to hide the MPLS menu. It has several sub-menus. When (in Webfig) MPLS is removed (and even when all sub-menus are removed), in Webfig the MPLS item is completely gone, but in winbox it remains visible but when clicked it shows an "empty" (small) submenu.
When an item like Quick Start, which has no sub-menus, is removed it correctly disappears from the menu bar.

oh i just tested it again and it does not work at all ... webgui yes, winbox no.
like winbox totally ignores the skin settings. but i remember it working some time in the past. did not test this any further so no idea since WHEN it doesn't work any longer

@spippan

try viewtopic.php?p=1015720#p1015720

@spippan

try viewtopic.php?p=1015720#p1015720

if i had not pressed SAVE it also would not work in the webGUI.
did that.
but thanks for the hint

oh i just tested it again and it does not work at all ... webgui yes, winbox no.
like winbox totally ignores the skin settings. but i remember it working some time in the past. did not test this any further so no idea since WHEN it doesn't work any longer

Remember it only works from some v7.x version, not before and not on v6.
Here it does something, but with a bug: not able to hide menu entries when there are sub-menus.

Tools, Check for updates.
Error: Upgrade file was corrupted.

Tools, Check for updates.
Error: Upgrade file was corrupted.

Read everything on the first post including the 2nd part of the important note.

Important note!!!

Upgrade from older WinBox versions might not work due to the new digital signature. Manual WinBox upgrade is required.

Tools, Check for updates.
Error: Upgrade file was corrupted.

it is literally the first thing the "important note" section states.

Would really appreciate if Auto reconnect on RoMON connections became really usable. If Address list is protected by master password, then connection loss will lead to "Error. disconnected from RoMON" - awaiting re-entry of master password. This happens even when connections is lost to RoMON neighbour while RoMON agent itself is accessible all the time. It looks like address and therefore RoMON agent list cannot be accessed because address list is locked by master password.

For straight connections (MAC or IP based) this problem does not occur and even when reconnect is canceled, address list stays unlocked until Winbox is closed.

Would really appreciate if Auto reconnect on RoMON connections became really usable.

I have quickly given up on "auto reconnect"... too many issues.
Instead I would prefer when sessions do not disconnect so easily.

It has almost always worked on straight IP connections - connection is re-established even after rebooting the device. Something is borked in case of RoMON connections because address list gets locked...

Well, one problem I have with it is that I use workspaces (virtual desktops) and when a connection is closed and auto-reconnected the window opens on the currently visible workspace instead of the one it originally lived on.
That could be fixed by not closing and re-creating the window in case of an auto reconnect.

Well, one problem I have with it is that I use workspaces (virtual desktops) and when a connection is closed and auto-reconnected the window opens on the currently visible workspace instead of the one it originally lived on.
That could be fixed by not closing and re-creating the window in case of an auto reconnect.

I essentially gave up on MikroTik fixing Winbox for these 'usability bugs'. These issues with multiple monitors/virtual desktops, started (at least for me) after v3 winbox. v2 worked perfectly fine on multiple monitors, it remembered each session on which monitor to load, etc. As one would expect really.

I mentioned them a couple of times in the first versions of v3, but I got thoroughly ignored, so I ended up using a 3rd party app (DeskSoft Window Manager) that forcefully moves windows wherever I want depending on various factors (executable name, window title, etc).

Unfortunatelly this doesn't solve another bug with winbox, that is, when it loses connection to a router and reconnects, sometimes the window will load on the top left corner at around 1024*768 (or smth) size, essentially destroying all windows placements within winbox. Window Manager will resize the window after the fact, so it doesn't really solve the problem.
Again, I resorted to a 3rd party solution, by keeping all my sessions on my Nextcloud, so when they get messed up, I simply revert the affected ones to a previous version.

I am running Winbox on Linux with Xfce. There are capabilities like that (pinning windows to certain workspaces) but my use of Winbox is too varied to make that work.
Although it now is a lot better due to the availability of BFD in v7, there still are occasional interruptions in the network that take long enough for Winbox to disconnect from a router (that does not take long!) and when I have auto-reconnect it re-opens on the workspace where I am currently working and I risk clicking on something I do not want. Or, when I come back to my system I find a number of Winbox windows (that normally are on different workspaces) opened all on top of eachother on the currently active workspace.
So I just disabled auto-reconnect...

The reason I ask for "- change the .viw files from binary to some user readable and editable format (JSON, XML, text, whatever)." is that I have .viw files that A LOT of work have been spent on to get everything correct, and then they build minor corruptions that probably could be fixed by removing a paragraph describing some particular window, but the file cannot be edited. Like you, I of course have regular snapshots and backups of .viw files, but corruptions may sneak in over time. Some windows won't remember the position/width of one particular column anymore, for example. Starting fresh with a new session fixes it, but means a lot of work is lost.

Also There is no "Make static" item in the DHCP Leases menu.

Why is it important?

It is important because it blinds people at night with this white theme.

Also There is no "Make static" item in the DHCP Leases menu.

Yes there is.
Used it several times yesterday.

Also There is no "Make static" item in the DHCP Leases menu.

Yes there is.
Used it several times yesterday.

It used to be there on right click menu of lease and it was gone at some point recently, you need to open lease to see Make Static button.

It used to be there on right click menu of lease and it was gone at some point recently, you need to open lease to see Make Static button.

Oh I see ... I never used that right click menu.

I do not understand why "invalid" when setting the time

What day ?

What day ?

it doesn't matter if I set the day of the week or not

It used to be there on right click menu of lease and it was gone at some point recently, you need to open lease to see Make Static button.

Oh I see ... I never used that right click menu.

It used to be a "Make Static" button between the Filter button and "Check Status" button.
At some point this got removed, for no apparent reason, and was put in the context menu of each lease.
Recently, the context menu option was removed and the old "Make static" button got re-instated.

So for years it was a button, we got used to that, then it was moved to the context menu, we got used to that, and now it's back as a button.
Dumb UI decisions that ruin muscle memory...

I am running Winbox on Linux with Xfce. There are capabilities like that (pinning windows to certain workspaces) but my use of Winbox is too varied to make that work.
Although it now is a lot better due to the availability of BFD in v7, there still are occasional interruptions in the network that take long enough for Winbox to disconnect from a router (that does not take long!) and when I have auto-reconnect it re-opens on the workspace where I am currently working and I risk clicking on something I do not want. Or, when I come back to my system I find a number of Winbox windows (that normally are on different workspaces) opened all on top of eachother on the currently active workspace.
So I just disabled auto-reconnect...

The reason I ask for "- change the .viw files from binary to some user readable and editable format (JSON, XML, text, whatever)." is that I have .viw files that A LOT of work have been spent on to get everything correct, and then they build minor corruptions that probably could be fixed by removing a paragraph describing some particular window, but the file cannot be edited. Like you, I of course have regular snapshots and backups of .viw files, but corruptions may sneak in over time. Some windows won't remember the position/width of one particular column anymore, for example. Starting fresh with a new session fixes it, but means a lot of work is lost.

I agree, a editable format is much preferred. I have the exact same problems you describe with old sessions that have grown too much and gotten corrupted over the time to the point that even viewing the routing table may randomly completely crash winbox (it simply exits, no error, no exception, no nothing).
But it is so much work to rebuild everything from scratch that I just put up with it....

Having a readable format, will allow for creating a basic template and use that to incorporate to multiple sessions in a semi automatic way with scripting.

I know I can do the same now, by having a basic preconfigured session and build on top of that for each router, but, when having literally hundreds of routers on winbox, it not feasible.

I agree, a editable format is much preferred. I have the exact same problems you describe with old sessions that have grown too much and gotten corrupted over the time to the point that even viewing the routing table may randomly completely crash winbox (it simply exits, no error, no exception, no nothing).
But it is so much work to rebuild everything from scratch that I just put up with it....

That is the exact problem I have too! "IP->Routes" sometimes just exits winbox.
And: in IP->Firewall->Mangle (for example), a column "New Packet Mark" can be added but it does not "stick", every time I close that window and re-open it, the column is gone and when I re-add it, it appears beyond "Comments" and I have to drag it into view.

I think it is partly related to migrating a .viw file along too many RouterOS versions, where features appear and disappear and/or change name.
I know that both of these problems can be fixed by starting a new session file, but that is just too much work.
When I could read the .viw file and look for the sections pertaining to "IP->Routes" and "IP->Firewall->Mangle", maybe I could see what is wrong or at least I could remove these sections and have to reconfigure only those particular windows instead of everything.

MikroTik: PLEASE consider doing this. It should be easy to auto-detect the format on read, and on write change to a new format.

+1 (or *100 maybe) for readable&editable config
Registry is so out of fashion... well, at least in Linux

Another feature request: when enabling a "filter" in winbox, after adding one or more filter rules, then disabling the filter, please remember the filter rules so that when filter is enabled again the last-used rules re-appear, and not a blank new filter.
Also when changing the filter topic on an existing filter line, e.g. from Src.Address to Dst.Address, please do not clear the match condition and value.
(these should be kept when the topic is changed to another one of the same data type)

Is there a way to use QR feature for Wireguard peers? As in without BTH

Another feature request: when enabling a "filter" in winbox, after adding one or more filter rules, then disabling the filter, please remember the filter rules so that when filter is enabled again the last-used rules re-appear, and not a blank new filter.
Also when changing the filter topic on an existing filter line, e.g. from Src.Address to Dst.Address, please do not clear the match condition and value.
(these should be kept when the topic is changed to another one of the same data type)

also please add an option to choose between AND/OR matching for more than 1 filter rule

maybe also useful to add a "bind to interface" for winbox operation or discovery

maybe something like this

WinBox v3.40 is released.
viewtopic.php?t=200431