NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
EdFerreira
Sep 14, 2021Apprentice
New V4.6.3.16
Hi all, Installed yesterday the new beta firmware V4.6.3.16. Got some improvements in the wireless connections but totally broke my lan wired stability. I have been quiet and reading the feedback bu...
tak1313
Sep 15, 2021Luminary
Haven't poked in here in awhile, since I put my AX in AP mode because my Asus is better at routing (also blocked updates some time ago because of this type of debacle after it was forced to update to a version I didn't want).
Just curious if they re-enabled the ability to downgrade with the beta, or if they're holding fast to their "we know what's good for you" mentality.
AggedwNG
Sep 15, 2021Apprentice
They're holding fast.. Its likely apart of the model they've decided to take with this product. Which is why it was likely disabled in the first place.
- tak1313Sep 16, 2021Luminary
AggedwNG wrote:
They're holding fast.. Its likely apart of the model they've decided to take with this product. Which is why it was likely disabled in the first place.So another curiosity. Since the cat is out of the bag, and they know that some have figured out the F12 key method of enabling the "YES" button in the update page (if someone REALLY wanted to downgrade to stable), did the dark forces bork that ability in the 16 update, or did they leave it be?
- AggedwNGSep 17, 2021Apprentice"Dark forces"... lol. More like shady business practices.. It's likely still hidden in the html. As the previous poster confirmed, he was able to downgrade. I personally tossed mine in the closet and have been running on an old router with stable firmware. Seeing as they felt the need to hide it in the first place, shows their intentions of where they plan on going with this.. I might pull mine out and do some testing this weekend but I wouldn't hedge any bets on them reversing course on that.
- vmieleSep 17, 2021Guide
Well, probably, if they had released a working and well tested firmware, we wouldn't be here arguing about whether or not it is correct to hide a button.
- tak1313Sep 17, 2021Luminary
vmiele wrote:Well, probably, if they had released a working and well tested firmware, we wouldn't be here arguing about whether or not it is correct to hide a button.
That's why I decdided to move on awhile ago. After mine was updated without permission, I decided to put it behind my Asus router in AP for multiple reasons.
1. Asus gives FAR more control in routing
2. Asus does things for FREE that Netgear charges for.
3. To fully block updates
At this point, I am especially glad I did #3 when I did as it apparently saved a lot of grief.
Netgear just doesn't seem to have the most capable coders and they apparently don't sufficiently understand their own products. ALL tech products have issues, but the lack of proficiency, capability, and most importantly, customer support response is undeniably lacking. It's ridiculous that they maintain a pay wall and/or make it difficult for users to get support for a problem THEY created.
I got the Orbi because I needed a good mesh. I was going to stick with Asus, but decided to try Orbi since I had great experiences with Netgear stuff in the past. The Orbi is great at wifi, but nothing else (hence running it in AP mode).
Netgear - never again. When it's time to upgrade, it'll be anything but.
- vmieleSep 17, 2021Guide
I've had a rbk20 for a year and a half with no problems.
I decided to upgrade and opted for the rbk753...I wasn't expecting this nightmare.
I still have time to return everything and opt for something else.
Let's see how this evolves... but given netgear's poor responsiveness.... I'm afraid I'll have to decide before they come out with a solution (assuming there will be one) - AggedwNGSep 17, 2021ApprenticeNo arguing here lol.. Fully agree with all sentiments expressed in this thread. It is a joke and one of the worst I've seen in a long time. I wouldn't hold your breath on anything productive coming from this.. If my return policy hadn't lapsed, I would have taken it back in a heartbeat. Whether it be due to poor implemented coding, Product Management or Release Support, for me they've shown their hand and I'm done with this brand.
- EdFerreiraSep 17, 2021Apprentice
AggedwNG wrote:
"Dark forces"... lol. More like shady business practices.. It's likely still hidden in the html. As the previous poster confirmed, he was able to downgrade. I personally tossed mine in the closet and have been running on an old router with stable firmware. Seeing as they felt the need to hide it in the first place, shows their intentions of where they plan on going with this.. I might pull mine out and do some testing this weekend but I wouldn't hedge any bets on them reversing course on that.Let me know how that goes... Mine is staying in the garbage bag until something happens. Probably in another 2 months, since they took 2 months to release a final beta version of the fw (this isn't even RC).
- tak1313Sep 17, 2021Luminary
vmiele wrote:I've had a rbk20 for a year and a half with no problems.
I decided to upgrade and opted for the rbk753...I wasn't expecting this nightmare.
I still have time to return everything and opt for something else.
Let's see how this evolves... but given netgear's poor responsiveness.... I'm afraid I'll have to decide before they come out with a solution (assuming there will be one)Return it. Look at it this way, you can see all the problems this ruckus is causing already. Let's say they are able to fix things before your return window is up, so you decide NOT to return it.
Netgear has shown their ineptitude in this type of situation, so you know at some point, your then working system (now past the return period) will be borked by another update/forced update and you'll be stuck with a bunch of network bricks.
I have already advised everyone I know that even IF NG can get passed this, you can depend on another "event" down the road with similar results.
I'm not knocking them for updating - ALL brands HAVE to update periodically, especially if it's a security issue. The difference is HOW problems with updates are handled by the back office.