Can't connect to Wi-Fi 7 with TBE400E

Can't connect to Wi-Fi 7 with TBE400E

Can't connect to Wi-Fi 7 with TBE400E
Can't connect to Wi-Fi 7 with TBE400E
Monday - last edited Yesterday
Model: Archer TBE400E  
Hardware Version:
Firmware Version:

So, this is basically my question. Not long ago I bought Wi-Fi 7 router Cudy WR3600H. It can run 2.4GHz and 5Ghz (no idea if hardware can 6GHz, but probably not at least until it will be allowed in my country).
 

As adapter I bought TP-LINK TBE400E. It's also Wi-Fi 7, supports MLO.
 

To confirm at least something, I used moblie app WiFiman that highlighted, that my network indeed is Wi-Fi 7 and using MLO. The issue is that for some reason my Windows still uses protocol 802.11ax (Wi-Fi 6) instead of 802.11be (Wi-Fi 7) when I connect to my network. I updated windows from 22h2 to 25h2. I installed the latest driver. I set network to use WPA3-Personal. But windows still for some reason uses Wi-Fi 6 protocol. I'm out of ideas why. I want to use MLO. Why can't I?
 

Just to clarify, netsh wlan show drivers shows that it supports 802.11be

P.S. Just now I noticed that there are different driver versions for different regions, but I have no clue right now which one I need. At the very least I see no warnings in the Device Manager.

  0      
  0      
#1
Options
4 Reply
Re:Can't connect to Wi-Fi 7 with TBE400E
18 hours ago - last edited 18 hours ago

Hello @xwolkx ,

Welcome to our community.

 

According to my research, the Cudy WR3600H is a dual-band WiFi 7 router. But it does support MLO network.

 

Could you share your PC's motherboard model number and other relevant details?

 

 

Are you unable to find the MLO Network on your PC? Or are you able to see it but couldn't connect? 

Please confirm that the built-in Wi-Fi adapter is disabled on the PC.

Please forget the wireless network on the PC, then try searching for it and reconnecting.

 

On the router, please try to change the channel and channel width. 

 

The latest version driver is Archer TBE400E(UN)_V1_20251011_Win11. Did you install it?

Please confirm the old driver is removed correctly. How to remove old and useless drivers in Windows

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: △Pre-release Firmware for Archer AX50 Introduces New Parental Control Features and Enhancements △Introducing AI QoS: Elevate Your Gaming Experience on the Archer GE800 Gaming Router △Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN △Tether KidShield Test Recruitment - Safeguarding Children's Online Experience If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
  0  
  0  
#2
Options
Re:Can't connect to Wi-Fi 7 with TBE400E
10 hours ago

  @xwolkx 

 

Hi,

 

Don't worry about regions. The drivers for all modern Wi-Fi cards that I know of are universal. (i.e. they are meant for use in all regions)

 

Does Windows also show "Wi-Fi 6" when you connect to the non-MLO SSIDs of the Cudy router?

 

If you'd like to try, there are drivers available that are still slightly newer (version 5.7.0.4755) than the ones available on the TP-Link website.
https://www.elevenforum.com/t/drivers-amd-mediatek-wifi-bluetooth.11384/

 

  0  
  0  
#3
Options
Re:Can't connect to Wi-Fi 7 with TBE400E
10 hours ago - last edited 7 hours ago

  @woozle Hello. So far I tried on 5GHZ and on MLO networks. In both cases windows tells me Wi-Fi 6, yeah.

  0  
  0  
#4
Options
Re:Can't connect to Wi-Fi 7 with TBE400E
7 hours ago

  @Joseph-TP Hello
My motherboard is ASUS PRIME B450M-A

It lacks any Wi-Fi. So, basically, to fix this issue I bought TBE400E, yeah...


I can see all the networks from my Cudy WR3600H device. One 2.4GHz, one 5GHz and one MLO.

I tried enabling Smart Connect. Then disabled it. I switched to WPA2/WPA3. Then to just WPA3. I changed 5GHz channel width to 160 MHz. Still the same result.

I installed the latest driver as I wrote in first post and installation program removes previous driver by itself (I checked because I reinstalled it several times and the program itself tells that).

I tried to attach netsh returns, but for some reason forums doesn't allow me to :/

  0  
  0  
#5
Options