NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Feedback for R7000 New firmware 1.0.9.18
Hi All,
Please post here for any update/issue related to the latest firmware 1.0.9.18.
You should review this and maybe revert back to this recommended version of FW:
Alfikwrote:I've looked here again after a while and I can't belive the problem is still not solved....
Since I've flashed Tomato a few weeks ago I've forgotten that I have a router- it's working perfectly getting dust because i do not touch it at all :-)...
Parental control works perfectly, 0 drops, strong signal - save your time and do a similar thing!
896 Replies
After receiving zero support from Netgear to fix a situation I should never have been in in the first place I decided to move to dd-wrt on the advice of a friend.
It works perfectly and is stable. The sad part of this is a firmware that only 2 guys write is more stable than the manufacturers recommended firmware.
Feedback for Netgear:
1. Now that I've seen you try and charge $50 for tech support on products older than 1 year I won't ever buy a netgear product until this changes. For the price of the router and the fact that this issue was of Netgears own making thanks to their own automatic update support for this should be free. If the issue was "I tried to custom flash the firmware and it failed and now I want to go back to Netgears firmware" then yes charge away for that support. If the device was no longer being produced and therefore it was more difficult to be supported due to needing to know older technology then yes charge for this. But this is an active router still being sold, updated with netgears own auto-update code, there should never be a charge for this support.
2. As soon as problems occurred with the firmware it should have been removed so that other users didn't find themselves in similar situations.
3. I understand the point of community forums, but community forums for manufacturers can only be successful if members of the manufacturer actually take an active role in the forum. Give feedback, provide estimates, as a developer I typically know how long some work will take and find people will be reasonable if they are given timelines, and yes you can add the caveat of "the developer anticipates a 3 day fix but if further issues are found this may slip, we will keep you advised".
Hi bobgodfrey,
Have you tried to reset the router after the update?
Hi hurricane28,
Please confirm if you already tried the hot fix firmware. We may need your feedback on this.
Hi Robb_H,
When you update the firmware, did you reset after?
Do you have any google home devices on your network?
Hi mated,
How many device on your LAN network that were having disconnection?
When using the hot fix firmware, did you encounter disconnection on wireless devices specifically on 2.4GHz?
Have you performed a factory reset?
Hi Peet45,
Which firmware works with port forwarding?
What error message did you encounter on the devices?
Please provide the port numbers that did not work.
Hi pfarmerca,
Are you still using the latest firmware? Hows the performance after the one drop? Please try to reset after the update if you are still experiencing disconnection.
Hi,
Sorry, i haven't tested the new firmware yet, i was quite busy with my PC. I am stil on V1.0.9.14_1.2.25 and have no issues that i know of.
I am not sure if i am comfortable flashing the new firmware bu if there are more positive feedback from users i might give it a try.
I may have been wrong about 5 GHz drops occuring with 1.0.9.26. They did occur, but may have been unrelated. But now some of the familiar 2.4 GHz problems are returning, including connections with no internet access. Back to 1.0.7.12 for now and thinking seriously about dd.wrt.
I tried the new beta firmware 1.0.9.26 .... but created disconnects on Lan ..... I guess that's why it is still beta. Back to 1.0.7.10_1.2.3 that works flawlessly.
I also tried the new beta firmware 1.0.9.26 (was on 1.0.9.20) -- still getting drops on 2.4 GHz
Stange, I have been on for over 60 hours and no disconnects on 2.4 or 5 GHZ
Can one still get the1.0.7.10_1.2.3 somewhere?
I had had v1.0.9.18_1.2.27 for a few weeks without issue. Today it started giving the intermittent connectivity issues. The devices (laptop, phone) would show connection to the wireless network but have no internet connectivity. The router's internet connectivity light is white and not orange. Internet connectivity is fine when router is bypassed. I just manually upgraded to v1.0.9.26_10.2.31_beta in hopes of fixing the issue. I just had one connectivity drop already with the new router so pessimistic.
Model: R7000
Firmware: 1.0.9.26
Updated to .26 last night, did a full paper-clip factory reset. Now I'm experiencing that my Sonos speakers are not being detected on the network. I've rebooted the speakers, and they will come up for a bit then disappear. They all run on the 2.4GHz channel. .20 did not exhibit this behavior. I'll roll back to that version.
It breaks Samsung smart TVs.
No - I didn't do a factory reset. WTF should anyone have to factory reset these days - It's 2018.
I rolled up to 1.0.9.18 & the TV stopped working.
I rolled back to 1.0.7.12 & the TV worked.
I rolled up to 1.0.9.26 & the TV worked.
I rolled back to 1.0.9.18 & the TV stopped working.
I rolled back up to 1.0.9.26 & the TV works.
Not once did I perform a factory reset.
Conclusion - a factory reset is BS & 1.0.9.18 is borked.
You have no idea what you are talking about dude.. Seriously..
If you have problems a factory reset can help in certain situations, i speak out of experience. I had a problem once with Netgear firmware and a factory reset solved the issues.. So NO a factory reset is NOT BS...
When i update to the latest BIOS on my motherboard i also have to do factory reset becaus if you don't you can get errors or issues so its best to do it forehand, its common sense actually..
You've totally missed the point hurricane28. You can talk about experience & common sense all you like, but a factory reset is total BS. It's BS coz some **bleep**ty coder can't process an out of range or re-used variable from an old configuration. Just because it may fix it, doesn't mean its the right answer. It's like if I ask you to be quiet, and you keep dribbling **bleep** ... and then I rip your arms off & beat you around the head a bit just to shut you up - it may work, but it's probably no the right way to go about it.
- Speed is 27 mbps. On a 100mbps plan any help with that
- So, I have been following this thread for a long time now. My take is that TerryPH has it right that it is a memory issue due to volume and introduced at some point after v1.07. So, the latest beta hotfix release notes from netgear seem to indicate that they have now agreed that this is the issue (instead of blaming it on Android) and tried to fix it. But, I am stuck in the following state:
1. Many of you seem to have updated to the latest beta and still experience the issue. Is this true?
2. I don’t like betas and am scared to move off of 1.07 for fear the issue will come back with the latest release
3. I am unclear what risks and security holes exist in 1.07 and am worried about being on this old version too long
4. I have seen nothing from netgear that officially admits to the problem, explains the root cause, and communicates to all of us when an official fully 100% tested release will be available
Do any of you have any answers here? Netgear, are you still out there? Do you still care? Will you be releasing an official version that solves the issue and communicate with transparency to all of us?Hi Redtarheelhawk ,
1. Many of you seem to have updated to the latest beta and still experience the issue. Is this true? -Many users have confirmed that the issue has been fix with the latest hotfix. You have to check as well if you have google home devices or chromecast or any other device the uses casts feature that contributes to the issue. There is a known issue with those devices.
2. I don’t like betas and am scared to move off of 1.07 for fear the issue will come back with the latest release. - This is considered as official firmware since it is released in official website.
3. I am unclear what risks and security holes exist in 1.07 and am worried about being on this old version too long. - Then you might have to consider upgrading to the latest firmware. Please take note that not all users have the same environment and network setup.
4. I have seen nothing from netgear that officially admits to the problem, explains the root cause, and communicates to all of us when an official fully 100% tested release will be available. - It has been confirmed by NETGEAR that it is an issue that is why the firmware was released.
1. Many of you seem to have updated to the latest beta and still experience the issue. Is this true? -Many users have confirmed that the issue has been fix with the latest hotfix. You have to check as well if you have google home devices or chromecast or any other device the uses casts feature that contributes to the issue. There is a known issue with those devices.
The hotfix is by no means a complete solution as evidenced by those with continuing problems. I used screen cast on an earlier firmware without problems. It's Netgear that has the problem, trying to pass it to others is pretty poor.
2. I don’t like betas and am scared to move off of 1.07 for fear the issue will come back with the latest release. - This is considered as official firmware since it is released in official website.
If it is considered official firmware why does the broken 1.0.9.18 remain as the first download available?
3. I am unclear what risks and security holes exist in 1.07 and am worried about being on this old version too long. - Then you might have to consider upgrading to the latest firmware. Please take note that not all users have the same environment and network setup.
Or you may consider moving to a third party frimware that does not have the issues provided by Netgear
.
4. I have seen nothing from netgear that officially admits to the problem, explains the root cause, and communicates to all of us when an official fully 100% tested release will be available. - It has been confirmed by NETGEAR that it is an issue that is why the firmware was released.
Has it been admitted by Netgear that they have not completely fixed the problem, because they can't find what they did to break it? I've seen no explanatory communication from them, has anyone? An apology would be a start.
The WIFI performance is still terriable on this router. Please have your 'software engineers' actually release something that works for such an expensive router.
I am so mad right now. I figured out that a 11 year old router does better than this stupid router. R7000
I have no problems with Wifi to be honest, nor with the rest of the network and i stream 4K video's through my network via Wifi...
I have 500/500 Internet connection and in speed test i get 515/515..
Almost 4 weeks I've been watching this thread. Have owned my R7000 a few years now. Has been one of the best routers I've owned. But I'm still waiting for the smoke to clear before updating. If .26 is still questionable, I'm waiting for .30 or later. I've been through the pitfalls and instability of bad FW. I've never seen Netgear take this long to rectify a bad FW release. So for now, I continue to wait.
Wifi still drops on patch V1.0.9.26_10.2.31. Hard reboot every single day. Devices lose connection and are unable to rejoin the wireless networks. Channels are properly set to avoid interference. This has been going on for quite some time now. When will it be fixed? Is it a hardware issue that firmware cannot fix?
