Creators Update resets 802.1x config on network adaptors to default

Radu Tyrsina
by Radu Tyrsina
Founder & Editor-in-Chief
0 Comments
Download PDF

A perplexing problem which is equally troubling has emerged out of the Windows 10 update that has been recently released. The new Windows 10 Creators Update build seems to have had a problem with adapters, specifically 802.1x, so it broke them. The unfortunate users that have been put in this situation are now looking for help to identify what the problem is, but so far, there is no solution as to what could have happened that made the new Creators Update break the adapter.

On Reddit, the subject is heatedly debated as people are pretty upset with Microsoft and the fact that they didn’t properly optimize the new update for every scenario. User the_spad has submitted a thread post that details the problem they are encountering and asks for help so that the problem might be fixed. Here is what they said on the forums:

Ad

Just started testing the Creators update in the lab and aside from the usual “Nice settings you’ve got there, would be a shame if someone reset them all” behavior, it appears to be resetting 802.1x config on network adapters to default, which means PEAP.

This means that as we’re using EAP-TLS to authenticate all our clients, they drop off the network post-update and there’s no way for them to get the correct config because they can’t refresh group policy.

Other users have also chimed in, but only to add to the number of people who don’t know how to solve this problem, instead of offering a solution. So far, the gathering has united against Microsoft, but has yet to find a proper solution to fix the adapter.

This isn’t the first issue that has emerged since the Creators Update arrived. There are many users who are still searching for workarounds to fix various problems the build has brought despite its intensive testing period.

RELATED STORIES TO CHECK OUT:

Ad