I spent last week testing a hAP Lite with firmware 7.20.1. My understanding is the hAP Lite and your two devices use the “wireless” package although they are different architectures. I connected an iPhone 11 Pro and a tablet with an Intel AC card. Both held stable connections and I don’t recall seeing any messages about disconnection in the log.
Do the devices reconnect to the same wAP/hAP ac lite or are they attempting another station?
In environments with wAPs, phones tried to reconnect to the same AP. In environments with hAP ac lite, Brother printers were completely unable to connect. I couldn't do much testing because these were production environments, so I reverted to version 7.19.6, which previously worked without any Wi-Fi issues.
In RouterOS 7.20.1, the MTU is incorrectly assigned to a VRRP interface if the parent VLAN interface is created on a bonding interface. The MTU for the VRRP interface is taken from the bonding interface, not the VLAN interface.
What's new in 7.20 (2025-Sep-29 12:33):
*) vrrp - make MTU property read-only;
Just dropping a message with my 5 cents.
Yesterday evening I’ve upgraded my home setup to 7.20.1. My home setup is fairly simple:
The upgrade was pretty straightforward for me, the Chateau was as usual faster to upgrade. I’m still puzzled why I need a second restart to upgrade the firmware as well, but I’m used to it. I usually perform the upgrades when my wife and kids are asleep, and there’s zero need for home WiFi.
So far my setup is stable, WiFi is fine, I have a STB connected to the 5GHz streaming throughout the day.
Version 7.20.2 has been released:
What is happening with the RouterOS versions this month?
It’s like a third stable release in a matter of weeks. I could not keep up with this pace 
remember to have proper validation, update and rollback procedures in place, also read thoroughly changelogs before deploying a new release into production
No, they definitely come to the forum and read "something" right when it crashes or doesn't work...
Tip: Looking for a way to keep the hardware updated but in a stable state?
When MikroTik starts to release the release candidate versions (ex.: 7.21rc1), they stop working on the minors of the version before (ex.: 7.20.2), so you can update to the latest stable minor version without surprise.
I afraid I dont agree that just because they’ve stopped working on a release there will be no surprises in it. Well, maybe no new surprises, but only if you’ve carefull read through all the issues folks have reported. Theres no guarantees (or often even notifications) that they are fixed.
Just my 2 cents.
I got your point, and I agree. The latest minor version doesn’t mean that it won’t have issues.
Anyway, when I had said “surprise” I meant a new minor version. Mikrotik won't release a new one. IMO this is the best approach to keep the hardware updated with the most stable state.
@mfilipe Thanks for a rational and reasoned response. I can see your angle here and would agree it’s a valid approach for most.
The last few releases have soured my personal opinion on this method, and my acceptance of risk has fallen. Luckily there are no new features i need, and no security flaws I think Im exposed to, so Im not in the position of having to upgrade.
I would really like it if there was an errata entry in releases noting open issues .
fwiw: it’s fixed in 7.20.2
(post deleted by author)
All problems with WiFi disappeared, for some 'unexplained reason' 
, after installing ROS 7.20.2.
Regards, G.
