NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Qabodan
May 22, 2022Aspirant
RBR750 new firmware version
when I download the newest version, the file ends with .chk. which is not accepted by the manual update of the router, it should be .img. what to do? and the automatic update also is not working
FURRYe38
May 23, 2022Guru - Experienced User
Is this system retail or some thing given by an ISP?
I don't see v3.2.0.20 listed on NG site...
What browser are you using?
What happens if you try to install v4.6.3.7.chk from the unpacked .zip file.
All Orbi systems use .chk files.
Be sure to update any RBS first, then the RBR lastly.
CrimpOn
May 23, 2022Guru - Experienced User
FURRYe38 wrote:
All Orbi systems use .chk files.
Image file names illustrate the inconsistent nature of Netgear software engineering.
- The original Orbi '50' series continues to use *.img for the router and satellite.
- The Orbi Pro, which has hardware identical to the original Orbi, is also *.img
- Subsequent products in the AC product line also used *.img.
- The RBS50Y also uses *.img for both Orbi and Extender mode firmware files.
- However, the RBW30 firmware is a *.chk file.
- The RBS40V (Voice) satellite, is also a *.chk file.
- When the AX product lines came out, they are all *.chk files. (not having one, I have not had much experience with them)
There is a similar pattern in the Nighthawk line:
- R7000 uses a *.chk file
- R7800 uses a *.img file
This is not the sort of thing that companies explain, so one is left to speculate what could cause some products to have *.img firmware files and other products have *.chk files.
- Maybe it is based on characteristics of the processor chip used in specific products?
- Maybe different software teams prefer one format or the other?
- Maybe they changed development platforms?
- Maybe NSA surveillance required a change to enhance snooping on customers? (LOL)
- FURRYe38May 23, 2022Guru - Experienced User
Ya I agree, NG's extension naming conventions are out of the ordinary across there products. Can be confusing. NG seems to be the only with this kind of planning. Most other Mfrs I've seen only use one extension naming convention.
User should using the extension that comes with in the packed .zip files and not modifying them at all. They work as there seen when unpacked from the .zip file.