NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jwong84
Sep 11, 2015Aspirant
R7000 2.4ghz not working but 5ghz is fine
Firmware 1.0.4.30 and 1.0.4.28 tried for weeks at a time.
Wireless devices connected to 5ghz band are all working perfectly and have been since i purchased this router at the beginning of June ...
- May 25, 2016
Good news! We now have a production version of firmware that should resolve the 2.4 GHz issue, v1.0.5.64. You may download this firmware from our R7000 page here: http://downloadcenter.netgear.com/en/product/R7000#searchResults
As IrvSp correctly notes, this version of firmware fixes the 2.4 GHz issue and reinstates the new features, such as Kwilt, Smart Connect, and WiFI Transmit Power Control. It does not support Arlo. We hope to have a beta version that supports Arlo in the next two weeks.
We welcome any feedback you provide on this new firmware, and appreciate your patience as we resolved these issues. Thank you all for supporting the R7000 and NETGEAR!
stuckincube
Jan 28, 2016Apprentice
KazzMANIA wrote:
Hate to say it fellows but this is not likely a firmware issue. You need to get a more recent version via RMA.
I'm not sure about that; many ran this router for a long time without issues until recently. The problem seemed to start with the change of firmware; even though others report downgrading firmware doesn't fix the issue.
Let's hope Netgear fixes this very soon!
Kernald
Jan 29, 2016Guide
As downgrading the firmware doesn't help, I can see two obvious possibilities:
- a firmware (probably 1.0.4 or 1.0.5 regarding the date they were published) broke some component (or at least a specific variant used in some R7000 batches),
- a component used in some R7000 batches has a limited life duration (manufacturing problem happens), that we reached
The fact that flashing an old firmware doesn't solve the issue, coupled with the fact that many R7000 broke at pretty much the same time is clearly disturbing.
- Kang2Jan 29, 2016Aspirant
I had this problem after installing 1.0.6.28 and I fixed it by wiping the settings and going back to to 1.0.5.48.
I NEVER had this problem (router is 2 years old) until I installed 1.0.6.28 and yes I wiped the settings before and even after installing the new firmware.