Windows Wireless LAN 802.11 Extensibility Framework using too much CPU power

I had the same problem today.  I killed the task and restarted Wifi and no longer have 30% cpu taken up by this program.  HOWEVER...

1. THIS IS NOT A SOLUTION.  If your car keeps stalling on the highway and the car manufacturer's solution is to tell you to re-start it, that is NOT a solution.
2. Answers that suggest dutifully running in safe mode are NOT A SOLUTION to a transient and randomly recurring problem.  There is about 0 chance it will recur exactly when you try running in safe mode.  THAT DOES NOT MEAN THE PROBLEM IS FIXED.
3. A general suggestion to update drivers is NOT ADDRESSING THE PROBLEM unless you have specific knowledge of a driver that is causing this problem.   Same with "clean boot" and all the other nostrums suggested by people who claim to represent

MS needs to review these reports and engage someone with the technical background needed to troubleshoot it.  That person can write up something telling us what they need to pinpoint this problem next time it happens.  And it will happen again, and again until it is actually fixed.

Just end the task. My computer works just fine without it and the CPU dropped back down to 30.

I worked in software development for 30 years and L3mB15w is correct. None of the solutions presented so far in this thread are permanent fixes. They might temporarily reset whatever started the problem, but they are not fixes. Windows Wireless LAN Extensibility Framework is clearly a key component in Windows 8 & 10 and 3rd party software very likely depends on it to function. Killing it in Task Manager just kills whatever the 3rd party software was doing (likely accessing the internet to retrieve or update something).

The real problem is that Microsoft has written a critical component that can be misused, and some 3rd party vendors are in fact misusing it. Since there is little or no supervision from Microsoft over this software, they are simply *hoping* developers follow the rules. That obviously doesn't always happen.

As users, we have no way of knowing which program causes the problem - and that's why Microsoft's solution is the clean boot in safe mode. If that solves the problem (and it will) then you start stepping through each and every program you've ever installed on your computer, and test until you drop to see if you can duplicate the issue. Of course, no user has that kind of time or expertise.

The true answer is for Microsoft to create APIs that enforce "playing nice", i.e. no 3rd party abuse of the system. That's complicated stuff - not solved overnight. But they've known about this issue for 3 years now and I'll bet there are 10 other topics that have the same underlying problem. They've had time, they probably don't want to change their API policies.

Which leads me to the *ultimate* solution: every year or two, reformat your system, reinstall Windows from scratch and then install one program at a time. Run it for a month and see if your system is misbehaving in any way. If it is, get rid of that program. If everything is fine, then move the next program you want on your system and see how that one works. This is, of course, a truly terrible way to use technology, but that's where we are. Option 2: Buy a Mac. Apple does enforce APIs that protect the system from abuse. Apple's problem is that software vendors don't like their heavy hand, so there is less creativity on Apple and users end up with fewer options. The best Apple can say is "well, at least it works". Not perfect, but not bad either.

Hi,

The Windows Wireless LAN 802.11 Extensibility Framework provides an interface to Windows wireless security and connectivity features for the drivers of wireless network adapters.

Let’s try these methods and check if it fixes the issue.

Method 1: Run System Maintenance troubleshooter and check.

a) Press Windows and X key together and select Control Panel.

b) Click on Troubleshooting.

c) Click on View all option on the left side of the Windows.

d) Click on System Maintenance option.

e) Click on Next and follow the onscreen instructions to troubleshoot the issue.

Method 2: C heck the functionality in safe mode with networking.

Step 1: Start your computer in safe mode with networking and check the CPU usage.

Refer this link to start the computer in safe mode.

http://windows.microsoft.com/en-IN/windows-8/windows-startup-settings-including-safe-mode

If it works fine in safe mode with networking, let’s place the computer in a clean boot state.

Step 2: Perform clean boot.

Clean boot will help us identify if any third party applications or startup items are causing the issue.

To do this, follow steps from this link:

http://support.microsoft.com/kb/929135

Note: After checking the functionality in clean boot, follow the suggestions under “How to reset the computer to start as usual after troubleshooting with clean boot”.

Keep us updated with the status of the issue to assist you further.

I wonder why a clean boot is mentioned as a reply on most issues. Is everyone supposed to have so much time as to reinstall the OS for every issue there is?