NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

TomHM's avatar
TomHM
Aspirant
Dec 06, 2017
Solved

WNR2000v5 firmware update problem

I got an email about a firmware update and followed the instructions. I downloaded the file but have to browse to locate the file and nowhere does it tell me the file name to search for or what folder it downloaded to.  Please help. Running Windows 10 attached to the router

  • TomHM's avatar
    TomHM
    Dec 07, 2017

    I was following the instructions in the email and that was failing.  So I took your advice and downloaded the .zip file from the NetGear website - and extracted the .img - and uploaded that to the rouiter and it worked just fine.

     

    Thanks for your help.

     

    Thomas

5 Replies

  • > [...] I downloaded the file but have to browse to locate the file and
    > nowhere does it tell me the file name to search for or what folder it
    > downloaded to.

       What, exactly, did you download?  From where?  And to where?  Which
    browser are you using?  Did you look in your Downloads folder?

       From what I see for a WNR2000v5, the file should be named
    "WNR2000v5-V1.0.0.62.zip", from which you'll need to extract the file
    "WNR2000v5-V1.0.0.62.img" therein.  As the instructions at the target of
    the "Release Notes" link on the Downloads page say, the ".img" file is
    what you send to the router.

    • TomHM's avatar
      TomHM
      Aspirant

      I'm getting an error message on the download - MD5 Verify error

      • > I'm getting an error message on the download - MD5 Verify error

           "getting" from what, exactly?  What, exactly, does "download" mean?
        Send to the router?  (My D7000 (V1.0.1.50_1.0.1) says "Upload".)

           If so, then that sounds like a corrupt kit.  If the ".zip" archive
        were corrupt/incomplete, then you should get a complaint when its
        contents are extracted.  An MD5 complaint points to the ".img" file
        itself, which would most likely be Netgear's fault.  You might try
        re-extracting the ".zip" archive contents, but I wouldn't expect much to
        change.