NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
JerryPar
Dec 20, 2018Aspirant
problems after upgrading to V1.0.9.60_10.2.60
Ever since I updated to the latest firmware I have had to reboot the router daily after loosing wi-fi. How do I solve this?
JerryPar
- Dec 21, 2018
Go back to the .42 firmware release. .60 is troublesome for many.
IrvSp
Dec 21, 2018Master
Go back to the .42 firmware release. .60 is troublesome for many.
beepee
Dec 21, 2018Aspirant
I downloaded an earlier version as per instructions to my desktop but when I try to add this and run the router kicks it out each time.
Can anybody give me an idiots guide to show how to revert to an older version, PLEASE.
Thanks,
BP
- IrvSpDec 21, 2018Master
beepee wrote:
I downloaded an earlier version as per instructions to my desktop but when I try to add this and run the router kicks it out each time.
I'd love to help you but I have no idea what happened? What does 'kicks it out' mean? Surely you can provide better details like an error or what actually you saw happen?
Which intructions did you follow? None were listed here?
Suspect you NEVER unzipped the file and didn't point the router to the proper .CHK file, but without more details I can't tell.
- beepeeDec 21, 2018Aspirant
Hi,
Thanks for the reply.
At the router update page I did add the correct downloaded and unzipped chk file BUT...... I had ticked a box at the bottom of the page when originally setting up to not allow automatic upgrades. I unticked that and it loaded the old firmware fine.
Cheers,
BP
- IrvSpDec 21, 2018Master
beepee wrote:
I had ticked a box at the bottom of the page when originally setting up to not allow automatic upgrades. I unticked that and it loaded the old firmware fine.Hmm, would expect that to be the problem? They should not be connected if it turns off ALL updating/loading of firmware.
No surprise I guess, they didn't even update the HELP for the page which has no 'help' for the last 2 choices on the router page.
Seems like another bug not discovered by NG? Auto-Update was fairly new. NG, testing, designing new features, implementing correctly, FAIL!!!