WLAN Service will not start

MobileTechie

Well-Known Member
Reaction score
32
Location
UK
Anyone know anything about this?

The WLAN autoconfig service won't start and when you try to start it manually you get "Windows could not start WLAN Autoconfig on this Local Computer" Error : 0xc00ce508"

Various fixes exist - SFC, restore a reg key but none make any difference. Reinstalling the driver etc does nothing. There is no further info the logs as to why the service won't start. I've tried turning Norton off but not uninstalling it so far

I've been looking at this for a few days but I'm not solving it.
 
Last edited:
Try the adapter with another box to ensure it is working. If it works elsewhere I see a nuke and pave in your future.
 
The "0xc00ce508" error indicates an XML parsing error. WLAN autoconfig uses 3 xml files located in \Windows\L2Schemas. One of these is probably corrupt. Try to replace with files from a known good installation with a working WLAN. You may need to take ownership/alter permissions of the files to do this.

edit: See here for more in-depth info. Hope this helps.
 
Last edited:
In the meantime I've already swapped the schema files. No effect.

However MS Office is giving an XML related error so I wonder if it could be related? When you try to save any document, or open Outlook you get the error that it needs MSXML 6 to do it. MSXML 6 is installed and indeed I've reinstalled/repaired the bits of it I can. No effect.

Given the number of hours spent I think I'll try an in place repair install.
 
In the meantime I've already swapped the schema files. No effect.

When in doubt just open the .XSD files in notepad and slowly scan them from top to bottom. You don't need to understand the language just look for normal formatting and a normal end of code. If it looks weird, garbage or like it truncates early then you got a bad .XSD.
 
I had a quick look. They looked to be valid code rather than garbage. So possibly nothing to do with them.

The repair install seems to have sorted out everything. working fine now.
 
Have you tried running a CHKDSK? Sometimes its the one thing we overlook.

Andy

DOH! I need new glasses. Obviously the other thing we overlook is the answer that is written before us!:D
 
Back
Top