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 1.0.11.116 failure to update
Just found the latest firmware updated here: https://www.netgear.com/support/product/r7000.aspx#download Unzipped the download, and tried to update the firmware *.chk file using the Upload butto...
Netgear must have updated the 1.0.11.116 download, because this week I tried again, and this time it installed successfully. Not sure what the issue is, but clearly Netgear updated the patch. Darn I wish I had kept the old download, could've checked sized and diffed it against the new one.
A user trying to install the patch, first time, does exactly what I did: download, browse to the .chk file, and select "upload" in the router update UI. They see exactly the same error message, try it a few more times to eliminate user error, same result, so they search on the error message and end up at this thread.
Diffing a file in THEIR case isn't going to help at all--because they don't HAVE 2 versions of the v1.0.11.116 firmware file yet. They have ONE version--which gives them an error.
All I'm doing in my resolution post is saying that "Try again later" is something that resolved it for me. It's not satisfying, but it did actually work and updated my firmware, and it might help somebody else to know that and try again, despite getting the error.
So stop pretending like your smug post added anything to resolve the original issue--it wouldn't help a single user that has the original error message I had.
If you have other actual solutions to try, I'm all ears. Otherwise, STFU and stop beating a dead horse to boost your lame ego.
ng_husker wrote:
A user trying to install the patch, first time, does exactly what I did: download, browse to the .chk file, and select "upload" in the router update UI.
That is not the process you described in your earlier message.
You said there:
First time: browsed to firmware update file, and click ok.
That could have described a very different process, and a mistake that many people have made over the years. Some people try to "run", or "ok", that chk file.
You would be surprised by how many people screw up that process, partly because Netgear's instructions ain't great.
That's why it is important to describe what you did in detail. Otherwise we are left guessing as to what went wrong.
I have seen no sign here of any change to the firmware file. That sort of thing gets widely reported, especially for something like the R7000, probably Netgear's best seller.
That is why some people might think that it was user error rather than Netgear's file that failed at your end.
Not what happened here. No user error, zero. Updated firmware many times over the last 7 years--ON THIS ROUTER. Just used the update UI. I know how to update firmware. And even to make sure, I had retried the download/install sequence several times on the first date I tried the patch.
Michaelkenward fair enough, no way of knowing what process users follow and I did say clicked 'ok' at one point. My bad on that confusing comment.
But it doesn't change what ACTUALLY happened. It's definitely not user error, the standard router UI-based upload process was used--same as has been used probably 30 to 40 times before in the years I've had this router.Screens showing the simple update sequence:
Tried downloading the bits, then installing as above, 3x on the January attempt. Same error all 3x, no way this is user error with my background and such a simple UI-based operation. And I've seen this report from other users online.
This week, it occurred to me to check if perhaps they had a new version of the patch. The auto-update checks in the router don't always work anyway. I saw version was the same, but thought maybe they could've patched the patch, since some including me had issues with it earlier. So I reran the process and it works. Something changed--it wasn't the user process for the update, and apparently it wasn't the bits either. Best guess in that case is that perhaps it could've been something specific to my environment: router, home network, etc. At this point it's moot. But I'd maintain that absent any more detailed cause-and-solution type of explanation, which I still haven't seen anywhere, it doesn't hurt to try installing again if you tried and failed earlier. The main motive I had for trying again was I wanted the security update.