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.
HI, we have same problem. Problem was first detected 28.6.2024. After some days testing , I had change version driver back on number 22.250.1.2. Unfortinuly new version drivers ( tested the latest drivers 23.40.0.4 , 23.50.0.6 and 23.60.1.2) are very slow in comunication type sql server - client.
I hope, that Intel it doeas has repair!!!! Every actualization uploud new driver and I am still repairing .....
Hello I already recognized the problem at the beginning of 2024. I thought that this would be fixed over time. I became aware of the problem when opening the Windows Event Viewer remotely suddenly took an extremely long time. Unfortunately, the problem still exists. I opened a ticket with Microsoft and was then forwarded to Intel. I opened the ticket with Intel on 10/17/2024. Unfortunately, I don't have a solution yet, but the problem is in progress.
We currently have devices with newer Intel(R) Wi-Fi 6E AX211 160MHz where a driver downgrade to version 22.250.1, for example, is no longer possible. Presumably because the chip has a newer revision.
We have the same problem. Many clients in Azure SQL database and each windows update, we have to uninstall the driver. It's really a shame that Intel does not take this problem seriously.
Hello. Yes, i have a ticket/case with the Intel support and they are aware of the issue. Seems like the problem was bigger then they expected. Have not yet heard about a solution or workaround except the one i found with a really old driver.
But the thing is that our new HP laptops seems like they have a new revision that does not support 22.250.1 driver. So we are stuck here with no workaround or beta driver.
We have exactly the same problem. Also newer HP notebooks where an installation of an older driver is unfortunately no longer possible. I have not received any feedback from Intel regarding my ticket for weeks. I have already sent various logs.
Hi We have the same problem too. It occurs on several hardware distributers and computer models, but they all use the AX210 or AX211. The installation of an older driver solves the problem, but I am concerned to roll out an old driver on several machines.
I also opened a support ticket and hope for the best.
Try driver version 22.250.0.4, A35. Works for us (Dell Latitude 5540 with Intel AX211). We've been having horrendous performance issues accessing SQL databases over Wi-Fi on v23.x drivers.
Tried installing the 22.250.0.4 aswell, but it cannot be installed on our newer HP laptops with the new AX211 revision. It just says "Windows could not find drivers for your device".
We've been having the same exact issues. All the new Microsoft Surface Go 4s and Surface Pro 10s for business that we've purchased have this extra 500ms per sql query. We've seen this on AX211 and AX201 adapters. When we use an alternate wifi adapters, swap to a wired connection, or downgrade the driver to 22.220.0.4 the problem goes away. We've been buying alternate wifi adapters as a temporary measure until it gets resolved unfortunately.
Good news! I have received a new preview test version from Intel (23.110.0.1) and according to my tests the problem is fixed! I am currently in contact with Intel as to when the version will definitely be published.
All i've heard so far is that they are trying to resolve it and the only thing i got as suggestion so far has been to downgrade. But it's hard with the newer revisions when you can't downgrade the driver version.
Intel shared with me a setting change that fixed the issue for me. Hopefully it wont be necessary once they update the drivers, but maybe this will help others until then.
