I confirm that in RB433UAH version 4.16 the CPU 100% problem is NOT present after 5 days of tests. 
I am now upgrading one 433AH with the same version and see if the problem is also solved there.
advantz:
I can manually change tx-power.Haven’t tested changing tx-power up.Only down to regulative domain.
Established backhaul link and works ok.I can ping the other side.
Firmware upgrade (from v.28 on RB493AH) caused router not to startup (no status lights on any eth port, blue light on). I had it powered off manually and it started up, sys routerboard shows v.29 installed.
EDIT3: I may have been premature in my diagnosis. Yesterday, I observed one of the queue tree leafs downloading at burst speed for over an hour (it should be 10minutes max). I also saw queue tree reseting which coincided with scripts making changes to a disabled interface. Today, 16 hours, later I see burst working just fine…and no queue tree resets. The only difference is 50% less traffic as far as I can tell…
Still having issues with the NV2 wireless package, I did some more testing tonight and here are a few problems I still have. Some clients have no connection stability while running NV2. Good signal strengths, fair CCQ but client continually disconnects with various errors in the log related to time outs in control frame, synchronization and medium-access. Another issue that I am seeing with NV2 is that with 4.16 I have been unable to manually set data rates even though frequency mode and country are set. When you set the data rates to configured rates clients disconnect and won’t reconnect unless you set rates to default. Also if you are running the NV2 package and running the AP in 802.11 mode clients randomly stop passing data, they are still associated with the AP but you can’t ping, mac ping or telnet to the clients unless you disable and re-enable the AP interface. The clients will then work normal for a random period of time.
Roll the AP back to standard wireless package and the issues go away.
I will send SPouts from one of the clients and the AP while running NV2.
I upgraded several 411 CPE’s tonight from 3.x to 4.16 and one of them has lost the software key. This is a unit that is over 30 miles away and I really don’t want to have to do a truck roll for this. Can you please send me a new key for this unit, I have about 22 hrs to get it installed. I sent an email to support with the software ID and attached the spout from the unit also.
Thanks,
Chadd
chadd,
Which version was installed previously on your router, where you lost the license key?
Please, contact support about such questions (support@mikrotik.com).
Sergejs,
I was upgrading several routers at the same time so I can’t be 100% sure what version of 3.x it was but I am pretty sure it was V 3.10 that was upgraded from. I sent the supout file from the upgraded RB to support with my request for a new software key.
Thanks,
Chadd
do you updated the license key before upgrade ?
License updates were not supported in v3.10, this feature was added only in v3.28
Also, its’ recommended to upgrade to v4.16 first, and only then issue the license upgrade command.
I upgraded from 3.x to 4.16 as I have on ~ 75 clients and for some reason this one client lost its license without giving me the option after the upgrade to update the key. This was the only client that I had the issue with.
I’ve just installed 4.16 on a RB112 - seems fine except that I can’t get a working ‘new terminal’ either from within Winbox or telnet from outside, so can’t upgrade the firmware. (I think it was from v3.30.)
“New teminal” brings the terminal screen up and the MT logo after a 5 sec. hang but the command prompt never materialises.
I had that issue and solved it by downgrading then upgrading.
Thanks. I managed after an hour or so to successfully downgrade it back to 3.30 and decided to leave it there. I’ve learned in the past that trying to keep up with the latest RouterOS ‘stable’ release is for those who like living dangerously.
i have the same problem rb433 ros 4.16 when update bios fro 2.20 to 2.29 the router did not come back ,and now what can i do ?
chrismarine Do you have local access to the router?
It would be great you can provide us with console output, which is shown after firmware upgrade reboot.
The 2.29 is the correct firmware in 433 ,I say this because the site of routerboard .com the correct firmware for 433 is 2.25? 
RouterBOOT booter 2.17
RouterBoard 433
Authorization: Passed
CPU frequency: 300 MHz
Memory size: 64 MB
Press any key within 2 seconds to enter setup..
loading kernel from nand… OK
setting up elf image… OK
jumping to kernel code
Kernel panic - not syncing: Attempted to kill init!
chrismarine,
what is the version, that was installed before on your router?
The problem was solved when I enter to console and I reset the (bios) bootloader! from the bootloader menu .
to get the console had to push a switch on 433 and simultaneously attach the power plug in ,
I understand that I joined Alternatively bootloader 2.17
the previus software version is ros 4.10
chrismarine, do you have any other RB433 with the same behavior. I tried on mine upgrade to v4.16, it seems to work fine for me.
this issue comes up on several 133C’s I have. On the 112’s the problem is less.
When I try to open terminal locally cpu shows 100%. Only the welcome screen comes up after a while and then termina seems to stall. CPU stays 100% until I close the terminal window.
Remote telnet session log in and then after a sec or so dissconnect. Sometimes when I try even a running winbox connection to that rb drops off.
Usually one or two (yes, sometimes it is needed twice!) powercycles solve the issue. Sometimes the problem is more persistent, even after a power cycle some units still have the issue.
I noticed that the problem is worse when a full ROS install is done so hardly any memory is left on the rb112 or 133C.
By removing the not needed packages things improve.
I also noticed that disable NV2 package and enable the normal wireless the problem is less and the rb starts up and works faster.
The rb112 is faster with 4.16 version in all winbox commands anyway then the rb133c. That last one regurlarly takes ages to start a session or show alterations I performed. Weird, you should expect otherwise.