WG311 v3 driver issue
Using 64-bit RC1, i'm using the above wireless card and have been using it in Vista 64-bit and all previous Win7 64-bit versions using the driver supplied by Windows Update with no issues. I installed clean each time with each beta and have installed clean with RC1 and let Windows Update grab the driver, only this time I'm getting a "Device cannot start" and no matter what I do, it will not work.What has changed from all previous beta versions that let this work with the windows update driver to RC1 where it is now unable to use it?I saw another thread concerning this same card and it was suggested it was the drivers installed from netgear, but since this is coming from windows update and it was working perfectly before, this is something related to RC1 and any such suggestion to contact netgear about this will be a copout and shows me just hownon-commital you guys are to helping support this new OS.
May 6th, 2009 11:01pm

Have you tried downloading the x64bit Vista driver from the netgear website and install it in compatibility mode to Windows Vista?
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2009 11:06pm

There is no x64 Vista driver on the website... just a Vista driver, and it has never worked, always had to use Windows Update and the drivers supplied by Marvell on theresince it's a marvell chip.
May 6th, 2009 11:08pm

Well OK that complicates the problem :) It might be possible for you to extract the drivers from an working Vista installation but that takes a lot of work and searching for the drivers however it might be worth it :)
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2009 11:26pm

I found a newer driver, but whenever I try to install it, I get this...Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)I just restarted and disabled driver signature stuff and then tried installing with newer marvell drivers... Still a Code 10, device cannot start
May 6th, 2009 11:34pm

Hello. I have been having exactly the same problem as you. I used the Windows Update get the drivers for the beta which worked fine and now trying the same thing with RC1 (64-bit)get the whole Code 10. I have also tried getting different versions of the NetGear drivers and also the marvell drivers aswell still getting the Code 10. It is quite annoying knowing that it worked fine with the Beta while not working with the RC.
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2009 1:00am

I'm in the exact same situation. Does anyone have any knowledge of ti working with the 32 bit version of RC1? I had it up and running on the 32 bit beta but switched to the 64 bit RC since I had the processor to do it this time. I can't even get the Netgear smart wizard to run even with UAC completely turned off and running in vista/XP mode. I also did a fresh install from a formatted drive. When I try to do windows updates on it I keep getting a failure, error code 80070103?
May 10th, 2009 4:06am

Hello, i resolved this problem. i had installed the driver 3.1 and when windows start i press F8 and i disable Driver Signing for the Wg311 will be enable. So its boring to do this manipulation all time. Sorry, im french, i have bad level in English^^ ++
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2009 3:21pm

Hello. I have been having exactly the same problem as you. I used the Windows Update get the drivers for the beta which worked fine and now trying the same thing with RC1 (64-bit)get the whole Code 10. I have also tried getting different versions of the NetGear drivers and also the marvell drivers aswell still getting the Code 10. It is quite annoying knowing that it worked fine with the Beta while not working with the RC. Hi. Same problem here ( Code 10) Did any one found a sollution for this ? I cannot use my mobile as a mobile for ages... Lukas
May 13th, 2009 7:11pm

I have the same problem. The card is not working in Windows 7 RC (Code 10). In Win 7 Beta, everything was fine. Please help!
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2009 4:54pm

Also have a WG311, trying to make it work on 64 bit vista, keep getting code 10 error, anyone have any advice on this?
May 23rd, 2009 5:16am

To everyone experiencing this problem, Is there perhaps a Windows XP x64 driver available? If not, and if anybody in this thread is still running the Windows 7 beta release, I'd recommend borrowing the verified working driver from that install and trying to use that exact file under the RC. If that fails, you may want to go back to the beta prior to the final release of Windows 7.-Alex
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2009 12:13am

exfelix, I am presuming you mean the files under C:\Windows\Inf\WG311v3 which contains folders "Vista32" and "Vista64".I know that there have always been driver issues with the Netgear WG311v3 Card, especially if you try to use 4Gig of RAM.I will be doing an install of Windows 7 RC within about a week, so I'll give it a go, I can always roll-back to Windows 7 Beta or Windows Vista.Noted that the Netgear (Australia) site (www.netgear.com.au) lists the current driver for the WG311v3 as;Windows XP/2000: 3.2.43.306Vista (32 Bit): 1.0.0.53.However at http://kb.netgear.com/app/answers/detail/a_id/2731/related/1/kw/311%2064%20bit/r_id/166they list the following; Adapters Vista x32 Vista x64 Driver Version WHQL Driver Version WHQL WG311v3 1.0.0.53 Y 1.0.0.53 Y Will report back success/failure, will also be trying 2Gig RAM vs 4Gig RAM as I would really like to install all the RAM rather than hobbling the system just for the WiFi card (really should just replace it, it is nothing special).
May 24th, 2009 8:16am

Hello. I have been having exactly the same problem as you. I used the Windows Update get the drivers for the beta which worked fine and now trying the same thing with RC1 (64-bit)get the whole Code 10. I have also tried getting different versions of the NetGear drivers and also the marvell drivers aswell still getting the Code 10. It is quite annoying knowing that it worked fine with the Beta while not working with the RC. Hi.Same problem here ( Code 10) Did any one found a sollution for this ? I cannot use my mobile as a mobile for ages...Lukas Yet another person with the same problem here!I have a Rosewill RNX-G300E but it uses a Marvell Libertas chip just like the Netgear.Just like everyone else my card works fine under the Beta (7000) after connecting to "Windows Update" but doesn't like the RC (Even after multiple tries at Update).Here are the things I have tried and the resulting outcome so anyone who reads this will not waste their time like I did:1. Rosewill Manufacturer drivers:Rosewill's installer does not work for 64 bit operating systems. It says to install the driver manually (I do not know if the Netgear installer has the same problem). Manually forcing Vista 64 bit driver results in Code 52. Manually forcing Win XP 64 bit driver results in system freeze during install.2. Manually use drivers from "Windows Update Catalog":Code 10.3. Install RC for 32 Bit system (Because 32 bit in better than no bit):Same result as 64 Bit system (Code 10, Code 52, System Freeze, etc.) even if I run the Vista installer in Compatibility Mode4. Use "cversion.ini" hack to upgrade form Beta to RC:Device works fine pre-upgrade but after restart shows Code 10.5. Exporting/Using the Windows 7 Beta Driver:DriverMax says the driver is not signaled (-1 entry value) and as far as I can tell the driver is the same anyway (MRVW13C.sys ~140 kb)I have also done about six or so clean re-installs and I know a corrupt install/iso/DVD is not the problem because I have used multiple DVD's and have downloaded the RC three times directly form Microsoft (Twice with the 64 bit and once with 32 bit).My current plan of action is to continue using the Beta and try again in a few weeks. Hopefully Microsoft is aware of this problem and will do a fix upgrade sometime in the near future (They read the forums right?).Rig set up for reference: Gigabyte GA-P35-DS3L, Q9300, Corsair Dominator 4x1GB, EVGA 8600GT, WD 320GB Sata/WD 40GB IDE, CoolerMaster 600W PS, Rosewill GNX-G300E, Built in Gigabyte LAN which works great when connected to the router using a 50' cable that threatens to clothsline you as you walk in the front door.*UPDATE:* I reinstalled the RC hoping that this would work for my RoswillRNX-G300E (Marvell chip):6. Using F8 to "Disable Driver Signing Enforcement" and then using the Vista 64 bit driver manually.Results in "The device can not start (Code 10)"Still waiting for that magical Windows Update to free me from this Cat 5 leash! Honeslty at this point I blame Rosewill for crappy drivers and lack of 64 bit installer that should have driver signing and/or actually work.
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2009 7:05pm

The driver 1.0.0.53 from netgear's website worked for me if I did the f8 -> disable driver signing enforcement.I followed the steps in this article on how to sign drivers to pass the 64bit signed driver checks. I made a codesigning certificate and signed the file mrv13c.sys, now I no longer need to do the f8 thing to get this driver to work.
May 31st, 2009 8:21am

Using 32bit Win7RC with the Netgear WG311v3 adapter. Finally got the software to install but have not been able to correct the Device error Code 10. Are there any other Wireless adapters that work with Win7RC?
Free Windows Admin Tool Kit Click here and download it now
June 6th, 2009 9:35pm

If they work on Windows Vista they should work in Windows 7. But until Windows 7 is official, don't expect any to flat out say compatible with Windows 7 on them.
June 13th, 2009 9:42pm

I got a D-Link DWA-547 Card and it works great with Windows 7 RC1 (64-Bit). Also works with Vista 32-Bit. Haven't tried it on Win 7 32-Bit or Vista 64-Bit.
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2009 5:19am

I have determined that your solution will work for me too. I have Win7 RC build 7137. No drivers work and I get the code 10 error like all the rest. I just tried the 1.0.0.53 driver and using the f8 method I get it to work! I also want to do the certificate thing like you did, but I don't have time now, or the technical know how. And my beta expires in 14 days. I was wondering if it is possible for you to email the certified driver to me? I would very much appreciate it! Thanks
June 18th, 2009 2:05pm

My email is daniellouwdj@gmail.com thanks again!
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 2:08pm

I've got this problem too, 7100 build. At what point do you press F8? before Windows starts up, or during or what?
June 18th, 2009 3:58pm

Just before it shows the splash screen. You want to go into the advanced startup options menu where you select safe mode, last known good config etc.
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 4:43pm

The driver 1.0.0.53 from netgear's website worked for me if I did the f8 -> disable driver signing enforcement.I followed the steps in this article on how to sign drivers to pass the 64bit signed driver checks. I made a codesigning certificate and signed the file mrv13c.sys, now I no longer need to do the f8 thing to get this driver to work. Hi Harolder,I've been following the article for the past few days, and couldn't get it to work.1. I've marvell 1.0.0.53 from http://www.station-drivers.com/page/marvell.htm, because it is no longer available from Netgear website.2. There are 2 files in the 64-bit driver package: netmw13c.inf and MRVW13C.sys3. Sucessfully signed and verified the signature in MRVW13C.sys following the article4. Verified that my self signed cert was in "Trusted Root Certification Authorities" for Current User & Local Machine, as per the article5. During driver installation - I picked "have disk" and pointed it to the directory containing the 2 files. At this point, a warning message came up saying the driver was not signed (?). Clicked "Install Anyway". Got a "Code 10". Driver not working.Then I tried some variations to the steps. 6. I used Inf2Cat to generate a catalog file from netmw13c.inf. 7. Signed the catalog file MRVW13C.cat following the same steps.8. Uninstalled driver and re-installed. This time, I didn't get the warning message about unsigned driver.9. Installation went smoothly with no warning/errortill the end...... and got "Code 52" now.Some questions1. Did you do it on Win 7 RC x64, or Beta?2. Did you have to reboot in Test Mode?3. What files do you have in your driver package?4. What other files did you have to sign other than the MRVW13C.sys?5. Could you pls share your signed driver filesand root cert?Thanks,Boleh
July 2nd, 2009 1:13am

After reading this and many other articles I ave come to tthe conclusion that this card is simply not going to work under the 64 bit RC1 release until Netgear or MSgets off they're lazy duff's and fixes the issue. I have tried all the above mentioned approaches and in numerous combinations, trys and re-trys. And The device will not start, error code 10, and 52 also!Fortunately I am using mainly my Desktop PC andI have 3 OS's installed: WinXP SP3 32 Bit, Vista SP1 32 Bit, and Win7 RC1 64 Bit. I am connected to my router via integrated NIC and cable and I obviously have access to the internets. This being said; and after reading and trying all these ideas I'm just going to forget about my wireless card until I find a simple, legit fix. One last thing: I do have another wireless card I am thinking about trying. It's an ENLWI-G. IF anyone knows anything bout this card and setup please let me know and, if I get it to work I will let you all know and how. I suspect I will have the same issue as well, but I hope not!Peas
Free Windows Admin Tool Kit Click here and download it now
July 3rd, 2009 4:16am

Update:Apparently all are documented clearly in MSDN: http://msdn.microsoft.com/en-us/library/aa906247.aspxThe last step to the procedure above is to enable test-signing by executing: Bcdedit.exe-setTESTSIGNINGON, and reboot. After that, I no longer had to do F8 -> Disable Driver Signature Enforcement. Butnow I get a small text caption "Test Mode"at the lower right corner on my desktop.This is probably the best it gets without a fully legit MS-signed driver.
July 3rd, 2009 6:10am

Even with the 1.0.0.53 drivers I'm still getting code ten half the time in Vista 32-bit, and my computer only has two gigs of ram. Does it matter if you use that Netgear software or not?
Free Windows Admin Tool Kit Click here and download it now
November 21st, 2009 8:40pm

Even with the 1.0.0.53 drivers I'm still getting code ten half the time in Vista 32-bit, and my computer only has two gigs of ram. Does it matter if you use that Netgear software or not? It will NOT matter at all, someitalian123. If the v1.0.0.53 drivers don't get the WG311v3 wireless card to work correctly under Win7, regardless of the Netgear software is installed or not, then the drivers itself are faulty. those drivers are based on the Marvell Libertas wireless network adapter. Marvell and Netgear should both write a newer driver for the WG311v3 adapter (aka. newer than 1.0.0.53) and send a copy of it to Microsoft so that MS can digitally sign and approve it (and maybe even make the newer WG311v3 adapter driver available on Windows Update). That would save a lot of users who use the WG311v3 adapter under Vista/Win7 from having a lot of headaches.
January 8th, 2010 9:45pm

I haven't experienced any code 10 erors since I swichted to the Marvell Libertas drivers, instead of the netgear ones. I'm not sure what version they are though. I can check when I get home if anyone needs to know.
Free Windows Admin Tool Kit Click here and download it now
January 10th, 2010 2:17am

I have Windows 7 Ultimate 32 bit with 4 GB RAM I have spent 9 hours and installed it atleast 100 times but no luck. Finally how it worked out is below: Do NOT install Netgear Software (CD or Downloaded one) as it only leads to Code 10 error. Downloaded 1.0.0.53 driver from Marvel (Vista drivers) and disable Driver Signing and then install them - It will work for advise mail me at ashkumar65@gmail.com Thanks alot and I feel happy now :-)
August 21st, 2010 7:22pm

Argh, I have same problem...I'd have thought by now that Win 7 issues might have settled down. New machine, 4 Gb RAM and fresh install of 64-bit Windows 7. I bought a cheap TP-link network card - that worked, but only at about 10% speed. Assumed it was the card at fault and decided to go for Netgear - after all I have a Netgear router. Same issue - either driver fails to install or I get a code 10. Does anyone know of a 54Mbps PCI (my graphics card covers my only PCIE2 slot) card tat will work on a 4Gb Windows 7 machine (and preferably for not too much money)?
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2010 7:38pm

м. Upgrade Bios fog Gigabite end wg311v3 dead [error 10]. Please help my.
December 22nd, 2010 12:02am

Best Wireless LAN Adapter for Desktops I've been using the irritating Netgear WG311v3 adapter. Its horrible, lots of driver issues. So I've decided to get a new Wireless Adapter. Which one does experts recommend?
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2011 8:01pm

First and foremost, what wireless router do you have at home? Your 311 is a "G" legacy adapter. Your best bet is to get a dual band N adapter, one of the newer models. But this won't really improve performance if you have an older G only router. On Sat, 25 Jun 2011 17:01:44 +0000, choudharypranay wrote: >Best Wireless LAN Adapter for Desktops >I've been using the irritating Netgear WG311v3 adapter. Its horrible, lots of driver issues. > >So I've decided to get a new Wireless Adapter. Which one does experts recommend? Barb Bowman http://www.digitalmediaphile.com
June 26th, 2011 12:38pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics