NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New R7000 Firmware Version 1.0.11.100
It's been a while but finally NG has released a new firmware for R7000! :smileyhappy: R7000 Firmware V1.0.11.100_10.2.100 Download: https://kb.netgear.com/000061805/R7000-Firmware-Version-1-0...
Back on .42 and the issues I was having have been resolved... no reboots, no disconnects and inability to reconnect to the network has disappeared.
Whilst it is obviously good for you that your router is back to its former self, potentially, it could be security compromised because it won't have the latest security fixes. I guess it's trying to strike a balance, a stable router or running out of date firmware with potential security holes. Just make sure you've got decent anti-virus etc.
It is 6 yrs old and Made In China
I totally agree with you.. I try to keep all my devices with the latest firmware, including this router, for the very reasons you outline. Unfortunately, like others, the firmwares after .42 have been nothing but problems for me and I have no idea why.
If the firmware makes my internet useless, it doesn't matter if it fixes security issues or not .
It is unforunate that Netgear is unresponsive to firmware issues that they create unless you pay them for support after 90 days.
I'd actually be really interested to know when Netgear switched production of the R7000 from China to Vietnam and whether or not ultimately, this has had an effect on the success or failure of firmware updates.
It would be interesting to know if a manufacturing location or chipset versions created issues or not....but you would also think that Netgear could easily determine that by determining which users are having issues and narrowing down the issues from user errors to actual firmware issues.
The interesting thing with my router on the latest firmware was that it seems to detect one of my devices attempting to connect to the network and recognizing it as an intrusion of sorts...blocking and/or rebooting the router....which is what I have seen in the logs...which usually erase after the reboot as well.