First, please let me say that I'm a just casual user of Mikrotik Routerboards and not a networking pro of any sort. Apologies if this turns out to be a silly mistake on my part.

Routerboard
ROS 6.33.5 on RB951Ui-2HnD

Problem
Executing a /system reset-configuration results in an unconfigured router. It seems that the "default-configuration" script fails to run or complete even though the "RouterOS Default Configuration" popup displays.

Fortunately the router is still accessible via MAC & Winbox.

The following screenshots indicates what happens.

Was happening in at least 6.33.3 as well for the RB951G.

Was happening in at least 6.33.3 as well for the RB951G.

Didn't realize that. I wonder if it just happens to specific models.

It's not a problem to most of us who knows about Winbox and connecting with MAC. But just imagine if you're a new home user with a shiny new RB and you're trying to setup your internet connection. Most step-by-step guides asks you to reset to defaults before beginning. What you get after the reset is essentially a bricked router. Would be interesting to know how many unwarranted RMAs were caused by this.

Same on SXT LTE v6.33.5

EDIT: Tried two other releases:

v6.34rc36 - fail
v6.32.3 - works fine!

Didn't realize that. I wonder if it just happens to specific models.

Yes, my RB2011 without wireless reset's fine.

I'm guessing they're constantly adding/changing features that require changes to CLI commands that will sometimes cause script errors with certain hardware specific devices.

Sometimes the reset scripts get overlooked for a while.

I can confirm this reset-configuration bug exists in ROS 6.33.5 on a RB951G.

It is fixed for me in version 6.34rc41 on same RB951G.

I have the same issue with RB951G-2HnD after upgrade from 5.26 to 6.34.6 then I reset it. After reset, I can't connect using Winbox and its default IP 192.168.88.1

Thanks for the info on retrieving connection.

Have you ever used a branding package?

Please use latest stable or bugfix version. Default config script should be fixed in these versions.
If you changed wireless package to non factory default package without reinstalling the router, then script may also fail because of syntax differences between wireless packages.

Have you ever used a branding package?

I have no idea what is branding package. Thanks.

Excuse me for getting back to this issue. May I ask if there are any expectations on the next stable release timeframe ?