Ok there is definitely an issue when upgrading an RB running 4.16 with the NV2 package running to V5.0. I have tried it on three separate RB’s now and every single one of them lost the wireless package after the upgrade. If you enable the standard wireless package on the 4.16 instead of the NV2 package before the upgrade it will upgrade fine but if you try it with the NV2 package enabled it has lost the wireless package and settings every time I have tried.
Did you try upgrading from 4.17 to 5.0?
No these boards were all running 4.16. If I have to go through the hassle of doing two upgrades it is easier to just go back to the standard wireless package first and upgrading straight to 5.0
The same problem. After upgrade from 4.16 to 5.0. The wireless package was disabled 
please contact to support@mikrotik.com about this issue.
We need info (what packages were enabled/installed in v4.16), what hardware you used and what package you used for upgrade.
Same problem here, from 4.16 to 5.0 with a RB433AH all wireless settings (also WDS, virtual interfaces) are lost.
I made a backup before upgrade and i can recover all settings pasting it again in the console.
What packages you had installed on the v4.16? did you have the bundle package installed in v4.16 or you had only specific packages installed?
Uldis,
The boards I have were running the routeros-mipsbe-4.16.npk or routeros-mipsle-4.16.npk and had the NV2 wireless package enabled. I upgraded to the routeros-mipsbe-5.0.npk or routeros-mipsle-5.0.npk. Version dependent on the RB I have had the issue with both RB133 and RB411’s. From what I have seen it this will happen 100% of the time if I try to upgrade a board from the above software version to 5.0 if the NV2 package is enabled. If I enable the standard wireless package “instead of NV2” before the upgrade the upgrade works fine, but this is not an ideal situation having to convert parts of the network back to nstreem or 802.11 before I can upgrade it to V5.0.
I have an spout file I can send from a 411 that failed to enable the wireless package after the upgrade, it is on another PC I will try to send it to you later today.
Chadd
I think the problem could present itself if you disabled the regular wireless package before enabling the nv2 package when you were using it in v4. The correct method of installing the nv2 package in v4 is to simply enable it, and not do anything to the regular package. Maybe this was what happened?
Not the case here. The NV2 enabled not the other way around.
Two of these were remote links disabling the standard wireless package would have not been possible.