Newer WinBox versions shouldn’t break client’s routers running stable, older ROS versions, disconnecting CAPs or whatever else the current version is able to kill or mess up with.
Or atleast there should be some warning regarding this, when it encounters unsupported (anymore) ROS versions instead of the current unfortunate behaviour.
I won’t upgrade to 6.47.2 just to be able to use the latest WinBox unless there’s some serious security issue with the older ROS.
I’m skeptic about the 6.47.x versions so far to put them in production.
I do play with two routers running 7.1beta2 but those aren’t in production environment and I don’t care that much at home if my Netflix hiccups for some reason.
I’ll keep an eye for autosupouts. If I don’t encounter them anymore than this settles that WB 3.25 was the cause for those also (in 6.46.6 and 7.1beta2).
LE: now that I think of it, could this WB version be the cause for the issue I’ve posted here? http://forum.mikrotik.com/t/v7-1beta2-development-is-released/142356/1