Cannot Enable WiFi Adapter in Windows 8.1

Toggle sidebar Toggle sidebar
P

pastorerik

Reputable
Dec 13, 2014
7
0
4,510
Logged on to my laptop the other morning and it was doing a Windows update (not sure if related to my problem). After it booted up I noticed that I had no WiFi. I restarted and still no WiFi. When I go to settings Windows says no wifi devices found. When I go to Control Panel>Network and Internet>Network Connections, it shows the WiFi Adapter (Realtek RTL8188EE Wireless LAN 802.11n PCI-E NIC), but there is a red X and it says not connected, when I click to disable, and the enable...it becomes grayed out and says "Disabled". When I disable and then enable it again, a small window appears that says WiFi in the title bar and it says "Enabling" then a few seconds later it says "Enabled" but it is still grayed out and says "disabled"....Sometimes when I click to enable it, it says "Enabling" then "Connection failed" and another error window pops up that says "It is not possible to connect at this time, no network was detected".....

What I have tried so far: Updating the driver, restoring to a point before the Windows update, doing the recommended bios update from Toshiba, going into the bios and making sure that wifi was enabled, rolling back the wifi adapter driver. I have also tried to install a separate usb wifi adapter. When I do this it also shows in the Network Connections window, but with the same results (Red X, Not Connected, grayed out, etc, all exactly the same).

Also when I click on "Properties" for the adapter....it says that it is working.

Thanks in advance for your help.

Toshiba Satellite S50-A Laptop, Windows 8.1
 
Sort by date Sort by votes
hmm,
Device Manager > Wireless Network Adapter > Update Driver Software > browse my computer > let me pick from a list > uncheck compatible drivers > browse the list and pick random driver (listed in realtek) .


 
Upvote 0 Downvote


Forgot to mention that I had tried that...just tried again. After doing so, I checked and still not WiFi...so I tried to disable the adapter and comp locked up.

I was doing some searching on the problem (might have been on here, earlier) ...one thing I found, that may or may not be relevant is that the
WLAN Autoconfig Service is not running (in the description it says that it can make your wifi devices unable to be seen by windows) It is set to automatic, when I click on "Start Service" it runs for a while, then I get an error that says it could not be started, I have tried it a couple of times and I get 2 different errors....one was Error 23, and I don't remember the other one, each time I try to start it, my comp locks up and I have to force it to power down using the power button. I ran a quick scan on Norton and it came up clean.

Thanks for your help.

 
Upvote 0 Downvote


Ran sfc /scannow and received the following error: "Windows resource protection found corrupt files but was unable to fix some of them. Details are included in the cbs.log ......Note that logging is currently not supported in offline servicing scenarios."

When trying to start WLAN AutoConfig Service in safe mode afterwards I received the following error: "Windows could not start the WLAN AutoConfig service on local computer Error 1068 - the dependency service or group failed to start" another time I received Error 1053: The service did not respond in a timely manner"


 
Upvote 0 Downvote


Thanks Paul...I read that and thought that has got to work...it is exactly my problem....tried it, but it didn't work...When I tried to start WLAN AutoConfig, I got one of the two errors that I always get...this time is was 1058, that the service did not start in a timely manner. I am wondering if the "Windows resource protection found corrupt files but was unable to fix some of them." Might have something to do with it?

I looked at the CBS.log file (not that I have a clue what I am looking at) and searched for "corrupt" and this is what I found:

CSI 0000047c [SR] Cannot repair member file [l:36{18}]"WLAN_policy_v1.xsd" of Microsoft-Windows-WlanSchemas, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-12-14 17:44:58, Info CSI 0000047d [SR] Cannot repair member file [l:36{18}]"WLAN_policy_v1.xsd" of Microsoft-Windows-WlanSchemas, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-12-14 17:44:58, Info CSI 0000047e [SR] This component was referenced by [l:326{163}]"Microsoft-Windows-Client-Features-Package-AutoMerged-net~31bf3856ad364e35~amd64~~6.3.9600.16384.Microsoft-Windows-Client-Features-Package-AutoMerged-net-Deployment"
2014-12-14 17:49:00, Info CSI 0000047f [SR] Could not reproject corrupted file [ml:520{260},l:48{24}]"\??\C:\WINDOWS\L2Schemas"\[l:36{18}]"WLAN_policy_v1.xsd"; source file in store is also corrupted.

Would it be helpful if I posted the whole CBS.log file? Any advice on what to try next? Thanks

 
Upvote -1 Downvote
Something is corrupt

Try this then

Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EapHost right click dependonservice" and deleted all entries.

Under same HKLM\SYSTEM\CurrentControlSet\Dhcp right click "dependonservice" and removed all entries except Afd saved changes rebooted and like magic everthing was working again {do not know why only that it worked) worth a try before wiping and reloading everything
 
Upvote 0 Downvote



That didn't work either. Wondering about "WLAN_policy_v1.xsd"; source file in store is also corrupted."

Had read somewhere about getting the file off of another good Windows 8 machine. That particular article said to do that if the value of that file was "0"....but that was not the case. Elsewhere in the CBS.log it said that file couldn't be repaired. I have not tried any kind of disk repair or anything like that yet.

 
Upvote 0 Downvote
Fixed it. Was thinking about that "WLAN_policy_v1.xsd"; source file in store is also corrupted." statement from the CBS.log. and decided to try to replace it with one off of my wife's Windows 8 laptop. So I copied it onto a flash drive and then put it in my Windows/L2Schema file. I tried to move the original one but I didn't have ownership/permission to do so, so rather than trying to figure that out, I just changed the name of the good one to 1WLAN_policy_v1.xsd. That didn't work either. So I tried to change the name again removing the "1" and it changed it to "WLAN_policy_v1(2).xsd. Tried to start WLAN AutoConfig and this time I got a different error code (23 I think). So I was about to go to bed and decided to run sfc /scannow again. I checked it when it was finished and this time it said that the file had been repaired successfully. Went in to start WLAN AutoConfig again and in about 5 seconds it said that it had started and my WiFi came back. I don't know the cause, but I had read somewhere that an OS update can cause this. This problem started right after a Windows update, so I guess that is possible.

Thanks to Paul and Patrick for all of your help, I really appreciate it.

 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom