New Posts  All Forums:Forum Nav:

Unable to install/use any wi-fi adapters

post #1 of 17
4/19/10 at 9:17am
Thread Starter 
Hi,

I have Asus A6 laptop with a built in WLAN card. Unfortunately, all drivers for the card were deleted. I downloaded WLAN drivers from Asus but I get an error "file not found" during installation. Also, this adapter can not be deleted from the device manager list because "it is necessary for the functioning of the system".*

Out of desperation, I bought a USB wi-fi dongle and tried to install the drivers. Again, I received "file not found" error during installation.

So, it seems that something is wrong with a windows component or file and I can not use any wi-fi device on my notebook.*I'm running XP Pro with SP3.

Any help in understanding what's going on and how to fix it (without reinstalling windows and everything) will be appreciated.
Reply
Reply
post #2 of 17
4/19/10 at 9:57am
Try running a chkdsk first? Then download the files and reinstall?

cheers ...
Reply
Reply
post #3 of 17
4/19/10 at 1:07pm
Thread Starter 
I did that, chkdsk found no errors and Im still unable to install internal or external WLAN adaptor
Reply
Reply
post #4 of 17
4/19/10 at 1:33pm
Download and run Crap Cleaner from filehippo.com - tick all the boxes apart from the bottom one about freeing up space... After that select the fix issues and it will fix a lot of issues within the system like orphaned .dll's...

If that doesn't work, what flavour of windows are you running? It looks like a bit of file corruption which system file checker may fix...

Is the wifi card physically switched on in the laptop? Most wifi cards have to have drivers installed first, then plugged in/switched on....
Reply
Reply
post #5 of 17
4/19/10 at 2:04pm
Thread Starter 
If you mean CCleaner, I have it and cleaned everything I could. I'm not sure what flavour means, it's XP Pro for Asus notebooks, at least that's what original CD says.

The point is that I can not also install an external wi-fi D-link donkey I bought with the same error so I think it's not a problem with the internal asus adaptor, whether is is switched on or not
Reply
Reply
post #6 of 17
4/19/10 at 2:51pm
From Asus' support site, it seems your wireless card is made by Intel. have you tried downloading drivers from Intel?
Reply
Reply
post #7 of 17
4/19/10 at 3:51pm
Thread Starter 
In fact, it's made by Broadcom so I use bcm43xx drivers
Reply
Reply
post #8 of 17
4/20/10 at 1:53am
Thread Starter 
I have tried to clean all registry entries related to the internal adaptor. It was only partly successful because some entries can not be deleted. Anyway, after rebooting Windows finds the adaptor and tries to install the drivers but it still results in an error "file not found".
Reply
Reply
post #9 of 17
4/20/10 at 3:56am
If it is Windows trying to install the driver and giving the "File not found" error, then it should also list the file that it is trying to find.

Check to see if that file is a Windows file or a driver file and locate the file source that way.
Reply
Reply
post #10 of 17
4/20/10 at 4:11am
Thread Starter 
Quote:
Originally Posted by Revenent View Post
If it is Windows trying to install the driver and giving the "File not found" error, then it should also list the file that it is trying to find.

Check to see if that file is a Windows file or a driver file and locate the file source that way.
I wish it did. First, windows asks for the driver files location and then shows the copy window with flying folders and then switches back to installation screen showing installation error and saying "file not found".

It happens when I try to install drivers for internal adaptor and for external one from a different manufacturer so I'm sure it's not a specific driver file problem.
Reply
Reply
post #11 of 17
4/20/10 at 12:37pm
Go to your Windows directory and look for a file called "setupapi.log".

Try the installation again and after it fails, open that file and scroll to the bottom. It will show the log for the driver installation, and hopefully show you the file that it is looking for.
Reply
Reply
post #12 of 17
4/20/10 at 4:11pm
Quote:
Originally Posted by alikim View Post
If you mean CCleaner, I have it and cleaned everything I could. I'm not sure what flavour means, it's XP Pro for Asus notebooks, at least that's what original CD says.

The point is that I can not also install an external wi-fi D-link donkey I bought with the same error so I think it's not a problem with the internal asus adaptor, whether is is switched on or not
So its XP pro - stick the disc in the ROM drive once booted into windows... Go to start, run and type in SFC /SCANNOW This will check all system files and repair any corrupted ones...
Reply
Reply
post #13 of 17
4/22/10 at 5:50pm
Thread Starter 
Quote:
Originally Posted by Revenent View Post
Go to your Windows directory and look for a file called "setupapi.log". Try the installation again and after it fails, open that file and scroll to the bottom. It will show the log for the driver installation, and hopefully show you the file that it is looking for.
Thank you! I found that file, deleted it so it was recreated after my next installation attempt. Here is what I did: I turned off the internal adaptor and tried to install the external one since I'm pretty sure it has all the right drivers and the device is brand new. First I run the installer from the supplied CD, it does some work and then it asks me to insert the device into USB. At this moment Windows runs its own installer which results in "File not found error" in the installator window. I close that window and continue running manufacturer installer. It does some job again and then finishes saying that the USB adaptor can not be found. Since my laptop language is not english I translated the log where possible keeping all numbers and codes intact. Here is what I have in the log:
Code:
[SetupAPI Log]
OS Version = 5.1.2600 Service Pack 3
Platform = 2 (NT)
Service Pack = 3.0
Set = 0x0300
Product type = 1
Architecture = x86
[2010/04/23 05:37:53 2340.136]
#-198 Command line processed: "C:\\Program Files\\D-Link\\DWA-125 revA\\Drivers\\DeviceInst.exe"  -install config.dat
#E412 Digital signature parameters on this computer have been changed. Error 13. Wrong data.
#W413 Default value "1" is set for the registry parameter "Policy" in HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Driver Signing.
[2010/04/23 05:38:09 472.4]
#-198 Command line processed:: C:\\WINDOWS\\system32\\services.exe
#W383 MIgration "certclas.PNF": language PNF = 0c09, Thread = 0419.
[2010/04/23 05:38:08 472.3 Driver Install]
#-019 Searching device IDs: usb\\vid_07d1&pid_3c0d&rev_0101,usb\\vid_07d1&pid_3c0d
#-018 Searching matching IDs: usb\\class_ff&subclass_ff&prot_ff,usb\\class_ff&subclass_ff,usb\\class_ff
#-198 Command line processed: C:\\WINDOWS\\system32\\services.exe
#W383 Migration "oem13.PNF": languge PNF = 0c09, Thread = 0419.
#I022 Found "USB\\VID_07D1&PID_3C0D" in C:\\WINDOWS\\inf\\oem13.inf; Device: "D-Link DWA-125 Wireless 150 USB Adapter"; Driver: "D-Link DWA-125 Wireless 150 USB Adapter"; Supplier: "D-Link Corporation"; Manufacturer: "D-Link Corporation"; Section: "RTWLANSB.ndi"
#I023 Active installation section: [RTWLANSB.ndi.NT]. Rate: 0x00000001. Driver data: 04/15/2009.
#-166 Device installation function: DIF_SELECTBESTCOMPATDRV.
#I063 Instalation of the selected river from section [RTWLANSB.ndi] in "c:\\windows\\inf\\oem13.inf".
#I320 Device class GUID remains equal {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Selected driver installation.
#I058 The most compatible driver is chosen.
#-166 Device installation function: DIF_INSTALLDEVICEFILES.
#I124 Processing copying installation only "USB\\VID_07D1&PID_3C0D\\1.0".
#-011 Section installation [RTWLANSB.ndi.NT] from "c:\\windows\\inf\\oem13.inf".
#W383 Migration "drvindex.PNF": language PNF = 0c09, Thread = 0419.
#-166 Device installation function: DIF_REGISTER_COINSTALLERS.
#I056 Compatible installers are registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [RTWLANSB.ndi.NT.Interfaces] from "c:\\windows\\inf\\oem13.inf".
#I054 Interfaces have been installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Running full installation "USB\\VID_07D1&PID_3C0D\\1.0".
#I121 Device installation "USB\\VID_07D1&PID_3C0D\\1.0" has been successfully finished.
#E154 Class installator error. Error 2: Specified file not found.
[2010/04/23 05:38:13 2440.3]
#-199 Running "C:\\WINDOWS\\system32\undll32.exe" command line: rundll32.exe newdev.dll,ClientSideInstall \\\\.\\pipe\\PNP_Device_Install_Pipe_0.{FC824794-E88F-498A-81C8-434F3AC90B21}
#W383 Migration "certclas.PNF": language PNF = 0419, Thread = 0c09.
[2010/04/23 05:38:12 2440.2]
#-199 Running "C:\\WINDOWS\\system32\undll32.exe" command line: rundll32.exe newdev.dll,ClientSideInstall \\\\.\\pipe\\PNP_Device_Install_Pipe_0.{FC824794-E88F-498A-81C8-434F3AC90B21}
#I060 Selected driver installation.
#-019 Searching device ID: usb\\vid_07d1&pid_3c0d&rev_0101,usb\\vid_07d1&pid_3c0d
#-018 Searching compatible IDs: usb\\class_ff&subclass_ff&prot_ff,usb\\class_ff&subclass_ff,usb\\class_ff
#W383 Migration "oem13.PNF": language PNF = 0419, thread = 0c09.
#I022 Found "USB\\VID_07D1&PID_3C0D" in C:\\WINDOWS\\inf\\oem13.inf; Device: "D-Link DWA-125 Wireless 150 USB Adapter"; Driver: "D-Link DWA-125 Wireless 150 USB Adapter"; Supplier: "D-Link Corporation"; Manufacturer: "D-Link Corporation"; Section: "RTWLANSB.ndi"
#I023 Active installation section: [RTWLANSB.ndi.NT]. Rank: 0x00000001. Driver data: 04/15/2009.
#-166 Driver installation function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installation from section [RTWLANSB.ndi] in "c:\\windows\\inf\\oem13.inf".
#I320 Device class GUID remains equal {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Selected driver installation.
#I058 MOst compatible driver selected.
#-124 Running copy only installation "USB\\VID_07D1&PID_3C0D\\1.0".
#-166 Device installing function: DIF_INSTALLDEVICEFILES.
#-011 Installing section [RTWLANSB.ndi.NT] from "c:\\windows\\inf\\oem13.inf".
#W383 Migration "drvindex.PNF": language PNF = 0419, Thread = 0c09.
#-166 Device installation function: DIF_REGISTER_COINSTALLERS.
#I056 Compatible installers have been registered.
#-166 Device installation function: DIF_INSTALLINTERFACES.
#-011 Installing section [RTWLANSB.ndi.NT.Interfaces] from "c:\\windows\\inf\\oem13.inf".
#I054 Interfaces have been installed.
#-166 Device installation function:: DIF_INSTALLDEVICE.
#I123 Running full installation "USB\\VID_07D1&PID_3C0D\\1.0".
#I121 Device installation "USB\\VID_07D1&PID_3C0D\\1.0" has been successfull.
#E154 Class installator error. Error 2: Specified file not found.
[2010/04/23 05:42:37 2592.136 Driver Install]
#-019 Searching device IDs: usb\\vid_07d1&pid_3c0d&rev_0101,usb\\vid_07d1&pid_3c0d
#-018 Searching compatible IDs: usb\\class_ff&subclass_ff&prot_ff,usb\\class_ff&subclass_ff,usb\\class_ff
#-198 Command line processed:: "C:\\Documents and Settings\\alikim\\Local Settings\\temp\\{45DBE053-A7E1-47E0-BA74-BD2AC4FAD61A}\\{5EE83279-5FEA-4885-823A-B90C23A72DF0}\\DeviceInst.exe"  -find
#I063 Selected driver installation from section [RTWLANSB.ndi] in "c:\\windows\\inf\\oem13.inf".
#I320 Device class GUID remains equal {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Selected driver installation.
[2010/04/23 05:43:19 2992.136 Driver Install]
#-019 Searching device IDs: usb\\vid_07d1&pid_3c0d&rev_0101,usb\\vid_07d1&pid_3c0d
#-018 Searching matching IDs: usb\\class_ff&subclass_ff&prot_ff,usb\\class_ff&subclass_ff,usb\\class_ff
#-198 Command line processed: "C:\\Program Files\\D-Link\\DWA-125 revA\\Drivers\\DeviceInst.exe"  -find config.dat
#I063 Selected driver installation from section [RTWLANSB.ndi] to "c:\\windows\\inf\\oem13.inf".
#I320 Device class GUID remains equal {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Selected driver installation.
I think here is the error which is the reason behind the whole issue:
Code:
 
#E154 Class installator error. Error 2: Specified file not found.
I'm still not sure what to do to fix it so if you have any ideas please let me know.
Reply
Reply
post #14 of 17
4/23/10 at 3:05am
It seems like something is seriously borked.

Windows is saying that it doesn't know what a wireless network adaptor is - that's what the error message basically means.

You can try nuking the relevant registry keys so the NIC setup program can try to rebuild it.

(Something like the following: http://www.tomshardware.com/forum/14...dapter#t536179)

It's registry hacking, but it might get you going again.
Reply
Reply
post #15 of 17
4/23/10 at 1:27pm
Thread Starter 

Re

Quote:
Originally Posted by Revenent View Post
It seems like something is seriously borked.

Windows is saying that it doesn't know what a wireless network adaptor is - that's what the error message basically means.

You can try nuking the relevant registry keys so the NIC setup program can try to rebuild it.

(Something like the following: http://www.tomshardware.com/forum/14...dapter#t536179)

It's registry hacking, but it might get you going again.
well, I can try to do that but I do not see a happy resolution in the thead you've mentioned, I already played with registry in a similar manner without any success. Besides, I can not delete some registry entries using regedit, like the one with the vendor code {VEN_14E4...}. Windows says it can not be deleted.

Above all, it's wild guessing, I don't know what exactly I'm doing and why...
Reply
Reply
post #16 of 17
4/23/10 at 2:33pm
Check this out.....
Quote:
I experienced this exact problem and spent many many hours trying to resolve it. All Internet searches revealed many things to try but nothing short of reinstalling Windows resolved the problem. I gave up and called MS for after hours support ($515). They were able to give me the fix within minutes. If the solution below helps you, please help me defray my out of pocket costs for the support call by sending a buck or two to my paypal account - lancesjunk 'at' comcast.net
Background of my problem. I accidentally installed symantec endpoint protection with network threat protection (the firewall) on my exchange server. This hosed up all network communication. I uninstalled the product, but it left the "teefer2" network drivers in the hidden device manager (seen by running "set DEVMGR_SHOW_NONPRESENT_DEVICES=1" and setting Show Hidden Devices from the view menu of device manager.
The network communication problem still existed after going through the lengthy manual removal process found here: http://service1.symantec.com/SUPPORT...07073018014248
I was not able to uninstall or replace the drivers for the network cards to get them working correctly. It would always give me the error about the device being needed for booting.
Throughout this process, I have continually received the error, "#E154 Class installer failed. Error 2: The system cannot find the file specified.", while trying to get the drivers installed/updated for the cards. This was in the file c:\windows\setupapi.log I tried every driver known to man for these cards. At the end of every driver installation or update, I would get an error from the Hardware Update Wizard, which says:
"Cannot install this hardware"
There was a problem installing this hardware
Broadcom NetXtreme Gigabit Ethernet
An error occurred during the installation of the Device
The system cannot find the file specified
The actual process looks correct, as in, it is showing the files getting copied and I get the signed driver error on some that I tried, but the error is always the same.
Without much hope left, and facing a possible restore, I went through the entire registry and deleted anything that was associate with the broadcom cards and teefer2. This removed the nics and teefer2 from device manager and I was confident reinstalling "from scratch" would work, but it did not -I got all the problems mentioned above from the hardware wizard, and in setupapi.log.
This was my breaking point and decided to seek Microsoft's help. I am glad I did as their solution was simple, yet very obscure.
Backup and then delete the REG_BINARY value 'CONFIG' (not the "network" key from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network
You then restart the computer and either Windows will install the card automatically, or you will have to kick it off. If it is already in Device Manager, you may have to update the driver. This time it will work like magic.
A MS knowledge base article can be found here: http://support.microsoft.com/kb/937056
Although, it is for a slightly different issue, the underlying problem of holding onto incorrect information is the same. It also lists only win2000 and 2003sp1 having been affected, but my problem was on SP2 of 2003 server.
After the headache I got from endless google searches and deadends, I hope this helps somebody before going through all the trouble. Please forgive the reposting on other threads experiencing the same problem.
~Lance Smith
Reply
Reply
post #17 of 17
4/23/10 at 2:44pm
Thread Starter 
Thanks!
I've just found this link on a different forum, this is it, it works, I'm happy, case closed :-)
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home