If possible, h ave you checked if this issue happens testing only the PC/laptop and the router/Access Point? (no other wireless devices connected to the wireless network during this test).Īlso, please run the Intel® System Support Utility (Intel® SSU) and attach the report to this thread to gather more details about your system.ġ- Download the Intel® SSU and save the application on your computer.Ģ- Open the application, check the "Everything" checkbox, and click "Scan" to see the system and device information. 802.1X authentication type (WEP, TKIP, CCMP):ġ0.Encryption Type (Open, RC4, TKIP, AES):.How many systems do you have affected by this behavior? Network SSID stealth mode: hidden or broadcast?Ĩ. Computer power source: plugged in or battery?ħ. Have you tried a different router or Access point for testing purposes?Ħ. Router/Access point brand, model, and firmware version:ĥ. Have you checked if this issue happens on different networks? Could you please provide an example of other networks or non-TLS network when it is working fine for reference purposes?Ĥ.
Is the Intel® Wireless-AC 9260 the original wireless adapter that came pre-installed in your system or did you install it on it?ģ.
Are you having issues with Wi-Fi only or with Bluetooth too (both)?Ģ. In order to check this further, could you please provide the following information?ġ. Thank you for posting on the Intel® communities. Maybe reference this forum URL and the Intel case # 04714529 with any new opened support cases?
More clearly, disabling 802.11w Management Frame Protection (MFP) is a work-around for this issue, which I was just able to confirm as successful at least in my initial testing.Īnyone experiencing the same issue here with Windows 10 version 2004 is encouraged to open their own support cases with Microsoft - especially in that apparently this is not yet seen as a serious issue and not prioritized for a fix.
Other drivers that do not support WPA3 are apparently not affected. This happens despite having WPA3 disabled or not supported on the AP, and not selecting anything for WPA3 in the client config. This is specific to Windows 10 version 2004, likely as a consequence of the introduced WPA3 support. The only workaround shared so far has been the following:ĭon’t use WPA2/3-Ent + MFP (CCMP128+AKM SHA256) Microsoft confirmed that there can be a MIC error in Msg2 of the EAPOL 4-way Handshake during authentication.
It's almost as if in Windows 10 version 2004, this "success" message is never making it from the driver to Windows.Īs part of the Intel case # 04714529 opened with this, they opened an engineering case with Microsoft. There are no errors included, other than EAP successes, and even a momentary STA association and connection. I've also reviewed the logs on the WAP, including packet captures of the RADIUS traffic. So why is the connection immediately stopping after receiving an authentication succeeded? I.E., why was the operation cancelled? Interface GUID: Ĭonnection Mode: Automatic connection with a profileįailure Reason:The operation was cancelled. Network Adapter: Intel(R) Wireless-AC 9260 160MHz
What I do see are many repeats of the following sequence of Event Logs under WLAN-AutoConfig: Can anyone else confirm working or non-working scenarios here under Windows 10 version 2004? This seems to clearly show an issue with WPA2-Enterprise within the Intel drivers under Windows 10 version 2004. Using a cheap Realtek RTL8188CU Wireless LAN 802.11n USB 2.0 adapter works (albeit without the AC speeds, or 5 GHz).However, then upgrading that Windows installation to Windows 10 version 2004 breaks any WPA2-Enterprise connections, only allowing for PSK. This works with both the 8265NGW and the 9260, using either the 21.80.2 or 21.90.3.2 driver version, both before and after all Windows Updates are applied. Performing a clean re-install of Windows 10 version 1909.The following, however, allow for successful connections: Performing a clean re-install of Windows 10 version 2004, both before and after all Windows Updates are applied.Changing the wireless card to a 8265NGW.
I've spent a few hours trying all combinations of the following, without success:
At present, I am using an Intel Wireless-AC 9260 with driver version 21.90.3.2. I am unable to connect to WPA2-Enterprise (or WPA3-Enterprise) using TLS networks (any and multiple) after upgrading from Windows 10 version 1909 to 2004 (OS Build 19041.329).