Firmware V1.12.0.18 Discussion

---

RogerSC wrote:

---

---

Hmmm...I replied to this posting already, my reply seems to have disappeared. So I'll try again *smile*.

 

Sometimes when a router is flashed, memory corruption can result. What the user sees is problematic behavior, and if they were to get in touch with Netgear support, one of the first things that's suggested is to reset to factory defaults, and re-enter the user's configuration. It is common practice with consumer routers that if problems arise after a firmware update flash, manual or automatic, that the router is reset and reconfigured. While Netgear would like this not to happen, I'm sure, it really does happen and there's not much that Netgear can do about it. Kind of a random occurance for the level of hardware that consumers are willing and able to pay for.

 

So your experience, while not fun, is part of the normal course of long term hardware use. I really hope that your router will be fine from here on out, but I've had to reset my Orbi units here once or twice as well due to problematic behavior, and that's just life. Most times when I do a factory default reset, it's because that's the most expedient way to fix a serious problem. And things are usually good for quite a while after that. I really hope that's the case for you.

---

There is no reason for memory to become "corrupted" during a software update, nor is there any reason for settings to get broken or changed, beyond poor programming practices and/or quality assurance. If changes are big enough that old settings are incompatible then the update should reset settings, not just leave the router half-working The reason we continue to see this so much in consumer routers is the bar has already been set pretty damn low, and we've come to accept that it's normal.

To be clear, the issue nxc is having happens every single time you upgrade to 1.2 or 2.X from an earlier version. It's a defect in the update process that should be obvious if they were testing correctly and it's an issue that I raised with them well over a month ago. It also requires a NVRAM reset, not just a factory reset to resolve.