Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
What's new in 7.25.1 (2026-11-02):
bridge - fix BPDUs leaking to the wrong dual-connected bond in MLAG (introduced in v7.24);
bridge - improve FDB synchronization between MLAG peers when VLANs are added;
console - fix custom SSH client login parameters being ignored (introduced in v7.25);
dhcpv4-client - fix packet length calculation (introduced in v7.25);
dude - fix missing outage times and graph background scaling (introduced in v7.25);
fetch - fix HTTP fetch getting stuck in a "bad HTTP response" state;
ipsec - fix XFRM interfaces staying down until a reboot;
ipv6 - fix from-pool address lifetimes not updating after a prefix renewal (introduced in v7.25);
pim - fix IGMP/MLD querier being disabled after upgrade (introduced in v7.25);
ptp - fix PTP support on CRS804-4DDQ;
routing-filter - fix host matching in address lists with more than 64 ranges;
sfp - fix DAC EEPROM corruption when disabling 400G ports on CRS804 and CRS812 switches;
ssh - fix packet alignment when SHA-1 is used (introduced in v7.25);
system - improve stability (includes CVE-2026-98432);
webfig - fix multi-value fields being displayed as empty (introduced in v7.25);
wifi - fix virtual interface restart loop when reselect-interval and reselect-time are configured (introduced in v7.25);
To upgrade, click Check For Updates under System/Packages menu and select the stable Channel in RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download
Everything went smoothly
I encountered an issue after the update (please post about the device, configuration, and unexpected symptoms)
I encountered an issue, but solved it (please post the solution)
0voters
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. The file must be generated while a router is not working as suspected or after some problem has appeared on the device
Please keep this forum topic strictly related to this particular RouterOS release.
My hap be lite getting Capsman from RB5009 was fine on 7.25 and also fine on 7.25.1.
RB5009, CRS310, hap be lite, hap be3 media all upgraded without any issues (other than the CRS310 takes ages to reboot to the point of making me feel twitchy that something bad has happened)
Depending what you need from it, switch the crs310 to switchOS its gonna reboot/boot in literal seconds, if u dont need l3hw, swOS would suffice and its way less demanding + it boots in a reasonable time.
Show me which settings for hap be lite you use.
I tried using hap be lite with capsman and as an independent point. in all variants, the devices are not connected.
After upgrading the router CCR2004-1G-12S+2XS to RouterOS 7.25.1 and then updating RouterBOOT, the device did not boot. All LEDs were lit, and the fan was running at maximum speed. It only came back up after I manually power-cycled it (unplugged and reconnected the power).
Here's my full slightly redacted Hap be Lite config which was running fine on 7.25 and continues to run fine on 7.25.1. I'd PM it rather than post it here, but this forum doesn't appear to have PMs.
Capsman is running on an RB5009. It has my vlan config in it, primarily for the wired ports, and has an emergency access off bridge port configured in case of vlan messups. If you have Capsman in the lan, you should be able to boot the Hap into cap mode using "Keep holding the reset button until the LED turns solid, then release it to enable CAP mode. The device will then start searching for a CAPsMAN server." which will load the CAP default config.
