Intel Wi-Fi 6E AX211 160MHz slow communicating with SQL

[TomHolm]

Hi!

Windows 11 Enterprise / Windows 10 Enterprise

Version 23H2 / 22H2

Wifi : Intel(R) Wi-Fi 6E AX211 160MHz

Driver Version :" Intel 23.80.1.3"

We have issues with all of our new laptops that have the latest Wi-Fi 6E AX211 network adapter.
When we are using our software that are communicating with a SQL server internally it takes forever to load.
Seems like there is an unexpected latency.
With a older driver (22.250.10.1) it takes around 5 seconds, with the latest driver the same procedure takes around 3-4 minutes.

We have tried to change all kinds of Advanced settings on the Network Adapter, and nothing seems to work.
We have also checked our AccessPoint settings and tried to tweak some things there without success..

We have tried the latest driver (23.80.1.3) and we had to go way back to the driver (22.250.10.1) for it to work like expected and without any delay or latency.
The same issue occurs on a newly formatted Windows PC aswell.

Seems like something happened after the 23.xx release of the network driver.

[EnricoZogno]

Hello,

@Cyrrhus solution works, and we use it as a workaround. We are waiting for the new driver to be released.

        E.

[bulbin]

But why does activating FIPS help? FIPS is a standard developed for US government agencies and contractors. Makes no sense to us as we are based in Sweden.

[RudyB]

Thanks!

[Tarjei99]

I have done some testing trying to work around the problem og installing a series 22 driver.

On "older" Lenovo PCs, I have a PowerShell script that add a series 22 driver and then removes the series 23 drivers.  This works fine.

The script "works" on newer PCs, but the driver is not loaded. The interface card is not shown in the list of network devices and it does not help to scan for devices.

I have successfully loaded the driver by hand on at least newer PCs. I just tried everything in the new driver dialogue. Repeatedly. Eventually, it does load the driver. When it is actually installed, the driver seems to work fine. 

I presume that it will be possible to hack the registry to load the driver. However I have not tried that.

Workarounds

Using a Microsoft VPN fixes the problem.

Running netsh capture seems to make the application run fine with a series 23 driver.

[i5202Help]

Just sharing. NOTICE: Solution Available for SQL Data Retrieval Slowness.

https://community.intel.com/t5/Wireless/NOTICE-Solution-Available-for-SQL-Data-Retrieval-Slowness/m-p/1663174#M58168

[Cyrrhus]

Thanks. This worked for me and does not require the FIPs work around.

[Marcel_]

Thank you - the new driver works perfectly.