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-11-100
Security Fixes:
- Fixes security issues.
Bug Fixes:
- Fixes the issue where disconnected devices still display as connected after a period of time.
- Fixes the issue where the system default time displays as 2015 when the NTP sync up fails.
- Fixes the system crash or out of memory issue
- Fixes the issue where incorrect data displays under the attached devices list.
- Fixes the issue where devices under the attached devices list can’t be edited.
- Fixes typos in the GUI.
Both automatically update and 'Search for update' did not work. But downloading the .zip file and updating manually worked like a charm.
Bandwidth-test of my 200/200 line:
| 201.29Mbps | 201.34Mbps |
So far, so good. I will update post if meeting any issues or problems.
Happy quarantine time! :heart:
182 Replies
Please make sure you reboot your router before updating to this firmware.
Various security and bug fixes were addressed. We recommend that you restart your router before starting the update to ensure a successful update.
Thanks
Darren
Ok, so I took the plunge and I've successfully installed the latest firmware 1.0.11.100
I skipped the v.1.0.9.88 update.I bought my R7000 at the end of January 2020, it came with v.64 installed from the factory.
I had no issues whatsoever updating to v.1.0.11.100. This was my first time ever updating the firmware on any router as previously my ISP supplied router auto updated OTA.
I decided against updating the router via the Netgear Nighthawk App. In any case, I would personally never carry out a firmware update over wireless.
This was the procedure I carried out:
I downloaded the firmware update file from Netgear support
Extracted the ZIP file to a folder on my desktop
I turned off Wireless on 2.4 and 5ghz
I disconnected all four of my ethernet cables from the router then connected the router to my computer via ethernet.
I turned off my VPN
I turned off my Bitdefender anti-virus
I rebooted the router from the admin page on my computer
Via the admin page, I uploaded the file from my desktop folder and hit the upgrade button
Router did its thing, upgraded itself from the firmware update file, took about 3 minutes and rebooted itself.
After the update I just reconnected my ethernet cables, turned on my wireless, VPN and anti-virus and everything just works.
My router admin page now shows Netgear Armor in the menu setup, but as I have a Bitdefender subscription and a VPN, I'm not interested.
I'm hoping I won't get any issues. If I do, I'll be sure to let it be known.
Excellent update/upgrade.
A fine example of a pure clean upgrade.
DarrenM wrote:Please make sure you reboot your router before updating to this firmware.
Various security and bug fixes were addressed. We recommend that you restart your router before starting the update to ensure a successful update.
Thanks
Darren
ReBoot (power cycle) or Reset (erase all settings) prior to update?
Thx
Netgear's instruction for the firmware are quite clear, reboot before upgrading the firmware, nothing about erase all settings. There shouldn't be any need to complicate matters.
I'm not saying anyone should follow the method I listed in my previous post, but it worked first time for me and it's been several hours now since I carried out the firmware update and no problems whatsoever so far.
My only recommendation which I didn't mention before, is that if you have the Netgear Nighthawk App and like me you choose to upgrade the firmware via ethernet, I was prompted to sign out of my App before the firmware update actually happened.
I have to say, I've read some absolutely dire things that have apparently happened with users attempting firmware upgrades and bricking their routers or claiming that upgrading the firmware has left their R7000 unusable or unstable, but this just hasn't been the case with this update for me....so far!
The only thing that has got my back up over this update, is that afterward, I did a Bitdefender Home Scan and just as before on my previous firmware, everything came back as safe, all except for the router itself which came back highlighted as 'potentially at risk'. It is of course in my opinion, utter carp, there's nothing wrong with the router and it doesn't take a rocket scientist to work out why that result came back as it did. Enough said.
This is exciting! I sure hope it fixes all the problems encountered after 1.0.9.42!
Has anyone observed if this fixes the R7000 5g dropping connection issue in .88? I rolled back to .42. Thank you.
- Well, I installed it today and then this evening my wife and I each ran a zoom with friends for almost 4 hrs and both my kids played fortnite online. No drops so far. 🤞🏻
Well it's been 24 hours since I carried out the firmware upgrade and thus far I've encountered zero problems. I've checked my logs, no dropped connections, absolutely rock solid. But then all this said, I had no issues on v.64.
If anything, for me, upgrading the firmware was just the sensible thing to do from a security point of view, especially as in my locale, we're in lockdown and I'm spending a huge amount of time online. If Netgear have done security and GUI tweaks to the R7000 and they work, then that's good enough for me. I suspect for the vast majority of us who upgrade, we will experience few issues, if any. I'm not going to lie, I had serious reservations about upgrading the firmware, but I put all of the bad stuff I've read on this community about other firmwares to one side and cracked on. For the sake of a couple of minutes preparation for personal preference on disabling WiFi, anti-virus, VPN and unnecessary cabling and rebooting prior to upgrade, it was a painless process if I'm honest.
At the end of the day, it's all about choices and no one is forcing or preaching to anyone to upgrade from their present firmware if that is what they're happy with.
I've update to 1.0.11.100 this morning and it seems to be stable. However, I have come across twos issues.
1) I can't seem to disable WPS. When I uncheck "Enable Router's PIN (disabled because an attack is detected)" on the "Wireless Settings" page under "WPS Settings" and then click "Apply" it reverts back to checked.
Is there some other way to disable WPS?
2) I have 200Mbps service from Comcast. I ran the same speed tests from a gigabit wired desktop PC and from a phone via WiFi.
On Wifi the test reported 237.6 down and 11.7 up.
The wired connection 136.4 down 11.1 up.Can anyone explain why the wired connection isn't at least as fast as the wireless connection?
I took the plunge this morning and upgraded to .100 and will see if this is as stable as .42 on my unit. Many thanks for the previous posters observations.
DoctorX wrote:I've update to 1.0.11.100 this morning and it seems to be stable. However, I have come across twos issues.
1) I can't seem to disable WPS. When I uncheck "Enable Router's PIN (disabled because an attack is detected)" on the "Wireless Settings" page under "WPS Settings" and then click "Apply" it reverts back to checked.
Is there some other way to disable WPS?
2) I have 200Mbps service from Comcast. I ran the same speed tests from a gigabit wired desktop PC and from a phone via WiFi.
On Wifi the test reported 237.6 down and 11.7 up.
The wired connection 136.4 down 11.1 up.Can anyone explain why the wired connection isn't at least as fast as the wireless connection?
#1 - Dont see what you are talking about - I only see the WPS Wizard button (I dont use WPS, so I have not clicked it).
** Update - I see Advanced Wireless Settings - Yes, You uncheck it, apply, and it is still checked!#2 - I have the same comcast service. On my wired connection I am getting 240 Down and 6 Up (normal for comcast). I would like your upload speed, about 6 is the best I get with comcast's Half-Fast crappy upload speed.
I've just done a Google search on this issue and it brings up several threads on the Netgear Community about the subject. Might be worth having a read through.
I haven't bothered to try unchecking WPS because I just manually add devices anyway.
Here is a thread explaining more about the WPS issue.
https://community.netgear.com/t5/Nighthawk-WiFi-Routers/Can-t-disable-WPS/td-p/495976
Greetings,
I remember seeing this behavior a few times on FW revisons between 1.0.7 and 1.0.9. I skipped 1.0.8 branch all together because it was so bad.
My R7000 is on our boat so I don't have it here to test with. After making the change, and applying, have you tried gracefully restarting?
I think I finally got it to turn off, but do not remember how, sorry.
Thanks for the responses.
I think this issue is different than the one described in the link provided by Thornado.
The posts in that thread indicate the checkbox is disabled (grayed out) when SSID broadcast is disabled. In my case, SSID broadcast is enabled and so is the checkbox. When I uncheck the checkbox and click apply the setting doesn't stick.
And as Additude has suggested, I've tried multiple browsers (IE, Chrome, Chrome mobile, Samsung mobile browser) All behave the same.
And finally, as Shadowsports has recommended, I have rebooted the router a couple of times since updating the firmware.
Does anyone think Netgear will release any more updates for this aging model?
None of us know whether or not Netgear will release any more updates for the R7000. This is a Community Forum with as far as I know, zero input from Netgear themselves. It's seemingly taken long enough for Netgear to update from V1.0.9.88, an update I did not bother to upgrade to from my factory installed version, v.64 because I've only owned my router for two months before this new firmware arrived.
This latest firmware update is not causing me any issues whatsoever and my update went without a hitch. I get it that not everyone has an easy time of firmware updates, but anyone can mitigate certain issues just by carrying out some basic preparation prior to committing and pressing that upgrade box. I'm not even sure why anyone would need to carry out multiple reboots either, prior to or after updating. That said, I suppose this model has been out for some time and undoubtedly models manufactured in the last couple of years may well contain different chips/components than models manufactured a few years previously, and these factors may or may not have an influence. My R7000 was only manufactured in March last year, so perhaps it's in better shape than a model several years older.
Updated to this yesterday day from V1.0.9.42_10.2.44 and all was running fine until I had a random reboot earlier today which is the same issue I had with all previous versions. I ended up rolling back to V1.0.9.42_10.2.44.
I just found this thread and saw that you were supposed to reboot before updating so I did that and now trying the new firmware again. Hopefully the issue will be resolved now.
- You rolled back for one random reboot? 😆
For me a resetbeas important also. Reboot, update, reset, then perform all my settings manually. Not one blip is 48 hrs.I installed the .100 yesterday morning and about 630pm this evening we lost 5G network availability. Only 2.4G network was available. I rebooted the router and 5G available again. Same behavior with my equipment on the .88 firmware upgrade. Any ideas?
czonin wrote:Updated to this yesterday day from V1.0.9.42_10.2.44 and all was running fine until I had a random reboot earlier today which is the same issue I had with all previous versions. I ended up rolling back to V1.0.9.42_10.2.44.
I just found this thread and saw that you were supposed to reboot before updating so I did that and now trying the new firmware again. Hopefully the issue will be resolved now.
Alright thanks for taking the plunge for me. Still on 1.0.9.42, won't upgrade I guess!!! Any other firmware would send my R7000 into a reboot loop.
I threw salt over my shoulder before starting the upgrade, and it worked, so highly recommend.
**rolls eyes**
- I thought after netgear released 1.0.10.xx and crashed some r7000.. they took the time to get this firmware correct. I was so eager to upgrade to this fw hoping the 5g crashing issue would be fixed sigh
- Yea it sucks.... I did go 72hrs before it croaked which is more than any other after 1.0.9.42.... I guess that's a positive. 🙄. I'll digress and see what the next 72hrs brings.
1.0.11 lasted one day without any problem. But then it started having disconnection issue again. Rolled back to 42. I think 42 is the last stable firmware for the router.
- I didn't have to reboot the whole router.... I just went in a unchecked WPS then hit apply and it cycled the wireless. It's been almost 24 hours since that reboot. If it keep happening I'll be getting a Tp-link Archer A20. I'm done running a 2 year old firmware with security holes.
To the people that have downgraded back to .42. At this point that is really no longer a option. There are some security issues that the new firmware has patched. Rolling back is no good anymore. Maybe it's time to throw in the hat and get a new router. And i recommend it's not a Netgear. The Asus RT-AX58U can be found at Best buy fot 159.00 and this router works very well. Highly supported by Asus and Merlin. Firmware updates are frequent way more so then Netgear. Good Luck with your R7000.
- Yup that's it, I'm done.
I have had issues with firmware updates on this router in the past. The key seems to be to reset everything before and after the udate. I unplugged all ethernet cables except the one for the pc doing the update. This disconnects my wired devices as well as my MOCA network. I then reset the router using the hole on the router and a paper clip, unfolded. I then rebooted the PC and went right into the browser to install the new firmware. After the firmware update I give the router a few minutes to completely reboot. I then re-apply my router settings, and reboot the router again. Then again wait for the router to completly boot up. I then connect the moca bridge and wait a couple minutes. Then I reboot every network device one at a time, to force a new dhcp and/or wireless connection.
It has been several days now, network sppeds are good, no dropped devices, no issues. On the network I have Android, IOS, Windows, MOCA bridges, moca conected tivos, doorbell, water heater, tablets, phones, etc... I will update this post if I have an issue.
That's how I applied the update over a wired connection and a brand new stock setup from factory defauts. For me the router really started having issues after i tried to enable the guest network.
I was having to reboot at least once a day, amost so regularily that I could have set my sundial to it. Sometimes I had to reboot twise a day.
I was extremely excited to see this update and Netgear having fixed memory leaks which could cause a hang.I followed the install instructions, rebooting before I updated and then just had it download and update the firmware late yesterday.
Well lo and behold, we have already had to reboot it once today. Not the same time as usual, so probably a different mechanism, or they changed something to move the time.
If only there were a way to provide debugging/logging feedback to Netgear.
Being a firmware developer myself, I understand how hard it can be to fix problems like this.
I'll monitor for changes and look for yet another update. Perhaps the next one will be golden.
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.
I have not had to reboot my R7000 in about a week now. I just happened to notice in the logs that it was failing to connect to the default netgear NTP server. I pointed my device to a public NTP server and have not had to reboot it since doing this. I hope this helps others who are having similar problems.
Yes fixed my issues too... I went back to .42 :smileytongue:
No reboots or errors since I downgraded.
- After installing 1.0.11.100 my 2.4 and 5ghz would stop working daily. A hard reboot of the router would fix the problem temporarily. I ended up downgrading to .88. I'm also starting to hate this security software Netgear is pushing. Maybe it's time to move on..
It's entirely hypothetical, but the firmware issues might be affecting older routers disproportionately. From what users on this forum have indicated, these R7000 units have been made in different factories in different countries, some in China, some in Vietnam.
Just because one router looks identical to another doesn't necessarily mean that the components used inside are identical. Over the years, electronics and components change. I'd be surprised if a router made 5 years ago and one made within the last 12 months stripped down side by side, would be utilizing exactly the same electronic components. There have been advancements in WiFi tech and components over the years. Who's to say that the wireless components used haven't altered between batches built between 2014 and 2020? This may or may not have a bearing on whether firmware updates will have the same degree of success between identical models of different manufacturing years from different factories. Maybe this is the reason why my own router for example, isn't suffering any ill effects at all from the latest firmware update.
Portwey84 wrote:It's entirely hypothetical, but the firmware issues might be affecting older routers disproportionately. From what users on this forum have indicated, these R7000 units have been made in different factories in different countries, some in China, some in Vietnam.
Just because one router looks identical to another doesn't necessarily mean that the components used inside are identical. Over the years, electronics and components change. I'd be surprised if a router made 5 years ago and one made within the last 12 months stripped down side by side, would be utilizing exactly the same electronic components. There have been advancements in WiFi tech and components over the years. Who's to say that the wireless components used haven't altered between batches built between 2014 and 2020? This may or may not have a bearing on whether firmware updates will have the same degree of success between identical models of different manufacturing years from different factories. Maybe this is the reason why my own router for example, isn't suffering any ill effects at all from the latest firmware update.
The fact there are routers like the R7000 that allow you to choose which OS to run on it, like you would any other computer is something I enjoy.
I may like the hardware spects of both a computer, or even a router in this case, but may have issues, or just not like the stock firmware/ os.
The issue I have with most consumer routers has mainly been, the quality of the hardware, and / or firmware / os.
In the case of the R7000 I first tried FreshTomato firmware, as suggested on this thread, but that wasn't a good fit, and I had issues with speed. So, I went back to DD-WRT, which I had run on my R7000 last year for several months straight. After going back, I regained great speed and stability, and because DD-WRT doesn't support WPS, I don't even have that functionality anymore to deal with, which was another ocmplaint here on this thread. At the end of the day, for me, I considder my issues resolved at no cost to me, other than time, to manually configure settings stock firmware either doesn't have, or try to do for you, and also reading about settings and how to set them.
With this said, I plan to do this the more professional way when I needs a physical new router, by getting a wired only router, and a seperate asccess point so I don't have to depend on one device for both, especially if there are wireless problems than it won't take down the whole network to fix. (At least, it shouldn't)
