Netgear WG311v3 working in Windows 7 64 bit

I spent about 4 hours trying to get this damn Netgear WG311v3 to work this afternoon with my new install of Windows 7 64 bit. Either there’s an issue with it working with > 2gb of ram, or it’s an unsigned driver, or both. Anyways, after several hours of furious googling and finding nothing but people talking about the problem, I found an excellent writeup on the solution here. It works! I’m going to quote it in case it goes down, as this seems to be the only solution currently. The files you need are here. In short, you are installing the Win7 Netgear drivers, then “updating” them from inside the System Manager with an old unsigned Vista 64 driver (driver linked to above) for the same wifi chipset (Marvell 8335). Relevant information is after the cut:

This is his text, cleaned up a little and fixed some spelling. It’s worth noting that running unsigned drivers opens up a security hole on your computer so be very careful who you get them from. But at least you have wifi now.

*Disclaimer: I take no responisiblity if this stuffs up your machine*

Ok, well I had some troubles getting my Netgear WG311v3 working in Windows 7  64-bit with more than 2Gb of RAM (I’m using 8Gb). It would run fine using official Netgear v3.1 drivers if I only had 2Gb of RAM, but I was getting sick and tired of having to turn off, then restart my computer to add more RAM to play games at their potential (but then also not being able to play online unless I got my network cable out). So I searched for a fix and never really found anything that worked. I ended up fixing it myself by combining a few answers. Here is how you too, can get your WG311v3 working with more than 2Gb of RAM.

First you’ll need to download and extract the Marvell v1.0.0.53 driver.

Marvell v1.0.0.53 Driver: DOWNLOAD HERE

or got to THIS page and go to Libertas 802.11a/b/g Wireless (MRV-8335) and select Version 1.0.0.53 beta under the headingWindows Vista 32/64bits

Next you’ll need to manually force Windows to install this driver as it will not do it automatically. So go Start -> Control Panel -> Device Manager. Here you’ll see a list of all your devices. You should see a little exclaimation mark next to your Netgear WG311v3. Right click on this and select “Update Driver Software…”. Now select “Browse my computer for driver software”. Choose “Let me pick from a list of drivers on my computer”. Click “Have Disk…” and browse for the file MRVW13B.sys (32-bit) or MRVW13C.sys (64-bit).

Unfortunately these drivers are not signed so it will ask you if you really want to install it, so click yes.

Now, since Windows Vista RC1 and forward require all drivers to be signed, we need a work around. This is easy, but tedious. What you need to do is… When booting your computer, press F8 before Windows loads. Between the BIOS boot screen and the Windows logo, you must furiously pound the F8 key.  Then select Disable Driver Signature Enforcement. Done!

There is an alternative though. It is called ReadyDriverPlus and it pretty much presses the F8 button for you and selects the Disable menu automatically

credit: By Brendon Pilt

If Microsoft ever makes it so you can run unsigned drivers without having to stab the F8 key at boot, leave me a note so I can update this. I am shocked that Netgear sold this WG311v3 card into December of 2009 without any functioning Windows 7 64 bit drivers. Hope this helps.

This entry was posted in computing and tagged , , , , , , , , , , , , . Bookmark the permalink.

6 Responses to Netgear WG311v3 working in Windows 7 64 bit

  1. jim says:

    Why are saying to navigate to the .sys file? You cannot even load that filetype as a driver. You should be looking for a .inf file

  2. Tom says:

    ^^yea, what is the correct solution? How do you choose .sys file?

  3. Justin says:

    Thanks for the help. This got my PC back online after an OS update.

  4. anonymous says:

    This actually works! Thanks dude. This will help a lot of people..

  5. Johnd215 says:

    It is also possible that Zynga’s chosen advertising network is to blame if we akeecfabkadf

  6. Dave says:

    This worked great and got me out of a bind where the onboard NIC failed. Thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>