NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
No more 2.4 Wifi on R7000 Nighthawk after V1.0.9.14_1.2.25 update
Hi, Never had an issue before with the R7000, but after the V1.0.9.14_1.2.25 update I have no wireless 2.4Ghz devices connected to the router. 5Ghz works fine, but most of my devices do not suppo...
rudiklein wrote:
But honestly, a factory reset sounds like an advice from Microsoft on Windows.
Yes, it does, but it's well documented on this forum that certain firmware updates are incompatible with the settings from previous versions. Chalk it up to Netgear's unwillingness to fix their configuration subsystem to be backwards and forwards compatible.
Try the factory reset. You might want to write down or take screenshots of the settings.
As expected from the experiences of other forum members: no 2.4 wireless this morning.
But honestly, a factory reset sounds like an advice from Microsoft on Windows. Mhh, your start button doesn't work, just do a reinstallation. Never mind the amount of work it takes.
This should not be neccesary on a quality product such as the R7000. My router holds a lot of additional settings including port forwarding and it is a lot of work to redo it.
I just went back to firmware version .23 and the wireless came up fine.
I'll stick to that version for now.
Rudi
rudiklein wrote:
But honestly, a factory reset sounds like an advice from Microsoft on Windows.
Yes, it does, but it's well documented on this forum that certain firmware updates are incompatible with the settings from previous versions. Chalk it up to Netgear's unwillingness to fix their configuration subsystem to be backwards and forwards compatible.
TheEther wrote:
rudiklein wrote:But honestly, a factory reset sounds like an advice from Microsoft on Windows.
Yes, it does, but it's well documented on this forum that certain firmware updates are incompatible with the settings from previous versions. Chalk it up to Netgear's unwillingness to fix their configuration subsystem to be backwards and forwards compatible.
It's also well documented on this forum that a factory reset does nothing to remedy the issue being discussed here. I agree with rudiklein, and have often used the Microsoft analogy as well.
- I downgraded yesterday but did not help. Then i did factory reset on top of that and it has helped so far so it does seem necessary.
