How do I fix wireless connecting using 802.1x protocol after Windows 10 Anniversary upgrade?

scennimo used Ask the Experts™
After upgrading my laptop to Windows 10 Anniversary edition, I can no longer connect wirelessly to my company's network. Windows 10 worked fine, but after the Anniversary edition, I can no longer connect. i can connect hard wired but not wirelessly. At home wireless works just fine. To connect at work I need to have 802.1x checked off. I have an HP Elitebook Revolve 810 G1 with Intel Centrino Advanced-N-6235 wireless adapter. All drivers on the system are up to date. The system bios is also the latest version. Any ideas? I sure appreciate any help you can give me. Thank you
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

I find the best way is to uninstall (remove) the wireless card in Device Manager, shut down, start up and install the newest driver. This almost always works.

You can also try TCP/IP Reset.

Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the computer

I have an Intel 6205 on my Windows 10 Anniversary machine and it works fine.
What errors are you getting when trying to connect to the company wireless?


Bigeven2002, I have just been using it on a docking station so I am not sure so I have not tried it in over a week. I believe I just get a message that says I cannot connect to this network and to contact the administrator. I will have to double check tomorrow when I get in. If it is different I will post it here.
John, I will try your recommendations and post the results.
Thanks guys for your help. Much appreciated.
OWASP Proactive Controls

Learn the most important control and control categories that every architect and developer should include in their projects.

Ok thanks for the update.  I would be curious to know if the company network uses WPA2 or something older.


bigeven2002 we are using WPA2 - Enterprise


By the way our network consist of Open Enterprise Server by Micro Focus formerly Novell, Zenworks Client. It is not a Microsoft Domain Network. Not sure if this information can help.
Seeing as wpa2 enterprises uses radius or a pki certificate, do you use either?  If radius, I wonder if the user account got locked out or if pki, the very was removed or invalidated on the win 10 machine.

Can you try logging in as a different user on the win 10 box to see if it can access?  Preferably use a user account that can connect on another machine.
IT Manager
Top Expert 2010
Try the workaround below.

"Open Network and Sharing Center
Click Set up a new connection or network a. Select Manually connect to a wireless network b. Enter ASI-NET for the Network name. (Please note that this is case-sensitive.)
Click on Change connection settings
Click on the security tab, then Settings to open the Protected EAP Properties window.
Deselect Validate Server Certificate
To the right of Secured password (EAP-MSChap v2), open Configure and deselect the Automatically use my Windows login name and password option (and domain, if any). (Figure 3)
Select OK to close this window, then click on OK to close the Protected EAP Properties window.
Click on OK to close the ASI-NET Wireless Network Properties window, and finally select Close for the Manually connect to a wireless network window option.
Finally, click on the internet access icon and connect to the ASI-NET232 network"

Danny ChildIT Manager
As this is a corporate device, you should be approaching your in-house IT first... Unless you are them, of course!

That update is fairly notorious for breaking WiFi drivers.
Here's a similar post, where they had to revert to a previous version of the driver (NOT the most recent). 

HP Support may also have some recommendations here.


Guys, I appreciate all your help with this issue. I have tried all suggestions except Jackie Man. No luck. I will try Jackie Man's suggestion sometime today. I will update results. Thanks again.


Jackie Man, I tried your suggestion and no luck. (EAP-MSChap v2), open Configure and deselect the Automatically use my Windows login name and password optionEAP-MSChap v2), open Configure and deselect the Automatically use my Windows login name and password option) This option was not available when selecting Configure. Window pops up and says that I cannot do this. Back to the drawing board. If anyone has any other ideas, please let me know. by the way, when trying to logon the error says the following, NCLOGINUI 802.1x Authentication failed. An RPC error occurred. Network Login not Attempted. Thanks


Just wanted to post what I found out today. I am not sure how but I got my system to login to our network wireless. We have an app called (OES) Client for Open Enterprise Server for Windows by Micro Focus. This was formerly known as the Novell Client. I logged in local. I right clicked on the app and selected Client Properties and then I just clicked on OK. Rebooted the computer and now I was able to login. I do not know why this corrected anything. We did not change anything. Just clicked OK. We will be looking into this further but to me it is a mystery. We will check out prior clients and see if it is because of this new client. We will also test it on multiple systems with different network adapters. Anyway, I just wanted to let you guys know what I found out. Thanks again for all your help.
Ok great, glad you got that figured out.  That makes sense as clicking ok in the properties vs cancel will refresh the adapter or client selected.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial