Hello MikroTik Community,

I am facing an issue with downgrading my MikroTik hAP ax3 ARM 64 router from RouterOS version 7.18beta2 to 7.16.2. I have tried multiple methods but have been unable to get the desired version to install successfully.

Steps Taken:

Verified the correct .npk file: I confirmed that I am using the correct routeros-7.16.2-arm64.npk file for my router’s architecture (ARM 64).

Uploaded the .npk file: I uploaded the file to the "Files" directory by dragging and dropping the .npk file using Winbox.

Rebooted the router: After uploading the .npk file, I rebooted the router.

Checked the packages: I verified that the file was present in the "Files" directory using /file print. I also checked the installed packages with /system package print, but the 7.16.2 package does not appear, and the router continues to show 7.18beta2.

Attempted to remove the 7.18beta2 packages: I used the following commands to remove all components of the newer version:
/system package disable wifi-qcom routeros rose-storage
/system package remove wifi-qcom routeros rose-storage

However, the system continues to show 7.18beta2 packages as installed.
Checked logs for errors: I checked the logs with /log print where message~"package", and the following warning appeared:
omitting package system-7.16.2: newer package system-7.18beta2 is already installed
Re-uploaded the .npk file: I re-uploaded the file and rebooted, but the issue persists.

What further steps should I take to downgrade to RouterOS 7.16.2?
would greatly appreciate any guidance or suggestions.
Thank you for your help!

Is this a very new router?
Check System > RouterBoard and see what the factory firmware version is. You can't downgrade to anything lower than that version.

Not that new!

[admin@MikroTik] /system> routerboard/print
routerboard: yes
board-name: hAP ax^3
model: C53UiG+5HPaxD2HPaxD
serial-number: ********
firmware-type: ipq6000
factory-firmware: 7.6
current-firmware: 7.17
upgrade-firmware: 7.18beta2

For minimum ROS version you have to check this:
Sometimes it can be different than routerboot (I have a wAP ax with factory-firmware: 7.15.2 and factory-software: 7.15.1).

Anyway, proper way for downgrading is to

1. get list of installed packages (disabled as well)
2. upload all corresponding package files but for older version (e.g. routeros, wifi-qcom, rose, etc.)
3. execute /system/package/downgrade
4. reboot

Bullet #3 is different from upgrading ROS via otherwise identical way.

It could be the new 'security' feature introduced in 7.17 - /system device-mode has been changed.

By default install-any-version is set to no which prevents installation of anything with a lesser version than listed in allowed-versions, see https://help.mikrotik.com/docs/spaces/R ... evice-mode

It could be the new 'security' feature introduced in 7.17 - /system device-mode has been changed.

By default install-any-version is set to no which prevents installation of anything with a lesser version than listed in allowed-versions ...

Right, but default setting for allowed-versions is 7.13+ ... so downgrade to 7.16.2 should be possible.

"Rebooted the router: After uploading the .npk file, I rebooted the router." : To downgrade, you don't have to reboot, but click on the specific downgrade button on winbox (system/package)


AND you have maybe, to configure the fu...ing device-mode to allow downgrade, if you see a message about that in logs.

I'm trying upgrade to beta and downgrade with an hap ax3 on my lab....

success for theses versions changes : 7.17 >> 7.16.2 >> 7.18b2 >> 7.16.2 >> 7.17

In less than 15min, with only routeros+wifi-qcom packages and the last backup restored to avoid problems.

Thank you so much for testing this in your lab.
I will try again when I get home.
The new OS messed up my smb clients and I need fo downgrade for now.
This time I’m going to copy all 3 packages and try again.

I Will update this post…

No problem, i have a lab with rb5009, hex, hap ax3, hap ac3, cap ax and an old crs125 (capricious psu problem i think) if necessary.

Copying all three files together did the trick!
Damn! I was rebooting and rebooting, lmao!
Thank you so much for the help, as well as the other guys who commented.