Gaai wrote

Import piece of information for Windows 10 users outside of the US who have problems with the TP-Link Archer T4U Wifi adapter.

Gaai, can you elaborate a bit more on the kind of problems you think of here ?

Myself, having a bad experience on other MediaTek OEM dongles (an Asus USB-AC51), shows that the 5GHz channels they use are only working on Channel 36.
The 802.11ac standard in Europe (DNK in my case), allows or dictates the use of Channels in the range from 36-140.

Since my AP (quite new Huawei 4G Broadband) delivers 5GHz on channels 100-140 only (I also reported this to Huawei, also without any response), I could not see the ssid, from the laptop using the usb dongle.
I reported, of course, to Asus but havent got any responses even I was an vip user on their support site. They are known for bad support, so I returned the adapter, after this thorough investigation.
I am now perusing other alternatives like the T4U (haven't bought one yet) but won't allow myself into a similar trap.

So this is why I'm asking, because I suspect the same issue is with TP2U and TP4U adapters as well, since they seem lso to use MediaTek as the chip/firmware vendor.
Looking inside the driver installation file (NETR28UX.INF) for the Asus 64-bit one, I saw a multitude of possible vendor for the it, for reference I name them here:
[CODE]%MediaTek% = MediaTek, NTAMD64.6.2
%Ralink% = Ralink, NTAMD64.6.2
%Asus% = ASUS, NTAMD64.6.2
%Sitecom% = Sitecom, NTAMD64.6.2
%Conceptronic% = Conceptronic, NTAMD64.6.2
%Planex% = Planex, NTAMD64.6.2
%D-Link% = D-Link, NTAMD64.6.2
%AL% = AL, NTAMD64.6.2
%Airlink% = Airlink, NTAMD64.6.2
%Corega% = Corega, NTAMD64.6.2
%Corega_TW% = Corega_TW, NTAMD64.6.2
%Allied% = Allied, NTAMD64.6.2
%Gigabyte% = Gigabyte, NTAMD64.6.2
%Sparklan% = Sparklan, NTAMD64.6.2
%SMC% = SMC, NTAMD64.6.2
%Arcadyan% = Arcadyan, NTAMD64.6.2
%ZCOM% = ZCOM, NTAMD64.6.2
%ZyXEL% = ZyXEL, NTAMD64.6.2
%EnGenius% = EnGenius, NTAMD64.6.2
%Philips% = Philips, NTAMD64.6.2
%Draytek% = Draytek, NTAMD64.6.2
%AzureWave% = AzureWave, NTAMD64.6.2
%Accton% = Accton, NTAMD64.6.2
%AMIT% = AMIT, NTAMD64.6.2
%Hawking% = Hawking, NTAMD64.6.2
%Siemens% = Siemens, NTAMD64.6.2
%Edimax% = Edimax, NTAMD64.6.2
%AboCom% = AboCom, NTAMD64.6.2
%BUFFALO% = BUFFALO, NTAMD64.6.2
%Gemtek% = Gemtek, NTAMD64.6.2
%Amigo% = Amigo, NTAMD64.6.2
%PEGATRON% = PEGATRON, NTAMD64.6.2
%LevelOne% = LevelOne, NTAMD64.6.2
%Quanta% = Quanta, NTAMD64.6.2
%Zinwell% = Zinwell, NTAMD64.6.2
%Logitec% = Logitec, NTAMD64.6.2
%AirTies% = AirTies, NTAMD64.6.2
%Motorola% = Motorola, NTAMD64.6.2
%Linksys% = Linksys, NTAMD64.6.2
%LinksysLLC% = LinksysLLC, NTAMD64.6.2
%DT% = DT, NTAMD64.6.2
%Ovislink% = Ovislink, NTAMD64.6.2
%Linktek% = Linktek, NTAMD64.6.2
%I-O% = I-O, NTAMD64.6.2
%Encore% = Encore, NTAMD64.6.2
%PARA% = PARA, NTAMD64.6.2
%Cisco% = Cisco, NTAMD64.6.2
%ALLWIN% = ALLWIN, NTAMD64.6.2
%IOMAGIC% = IOMAGIC, NTAMD64.6.2
%RadioShack% = RadioShack, NTAMD64.6.2
%KEEBOX% = KEEBOX, NTAMD64.6.2
%2L% = 2L, NTAMD64.6.2
%Belkin% = Belkin, NTAMD64.6.2
%TP-LINK% = TP-LINK, NTAMD64.6.2
%Sweex% = Sweex, NTAMD64.6.2
%AirLive% = AirLive, NTAMD64.6.2
%NETGEAR% = NETGEAR, NTAMD64.6.2
%Movistar% = Movistar, NTAMD64.6.2
%Hercules% = Hercules, NTAMD64.6.2
%TRENDnet% = TRENDnet, NTAMD64.6.2
%ELECOM% = ELECOM, NTAMD64.6.2
%BT_Group_Plc% = BT_Group_Plc, NTAMD64.6.2
%Treebear% = Treebear, NTAMD64.6.2
[/CODE]
And in my case, I was just having issue with the Win. 8.1 64 bit platform, I cannot think it will change for the Win 10, and the drivers there, did not make a difference for me on Win 8.1.
Remember we used to have upward and backward compatibility a few years back :mad:
So I am afraid we are only seeing the tip of the iceberg here ...:eek:

Exactly the same issue. Its driving me nuts. I really don't want to switch back to powerline -.-

None of the solutions worked, none of driver changing, nothing. And... I'm also afraid new "official" driver from TP-Link won't bring much to this problem either. ://

I just installed the latest Windows 10 64 bit drivers that were posted in January and am finding they are working very well. So far, no drop outs like I was having before with 5GHZ and WIFI AC. Windows still reports it as WIFI "N" for some strange reasons. I made changes in the Advanced adapter settings to force it to use USB3, 5GHZ and WIFI AC. So far - everything is working great. Fingers crossed. Let me know what you find out with the new drivers.

Digitaleagle12 wrote

I just installed the latest Windows 10 64 bit drivers that were posted in January and am finding they are working very well. So far, no drop outs like I was having before with 5GHZ and WIFI AC. Windows still reports it as WIFI "N" for some strange reasons. I made changes in the Advanced adapter settings to force it to use USB3, 5GHZ and WIFI AC. So far - everything is working great. Fingers crossed. Let me know what you find out with the new drivers.

hi.

can you tell me where did you find the Win10 drivers posted for T4U?

Digitaleagle12 wrote

I just installed the latest Windows 10 64 bit drivers that were posted in January and am finding they are working very well. So far, no drop outs like I was having before with 5GHZ and WIFI AC. Windows still reports it as WIFI "N" for some strange reasons. I made changes in the Advanced adapter settings to force it to use USB3, 5GHZ and WIFI AC.

Can you tell which Channels on 5GHz you are using ?
Hint ! Use the Admin Windows CMD to tell, for your SSID when connected:
netsh wlan show networks mode=bssid
Thanks

They were at the TPLINK website under the T4U adapter and on the drivers download tab. It was the top driver listed and had a date of January 2016.

Here's the link. http://www.tp-link.com/en/download/Archer-T4U.html#Driver

Sorry for the delay: On 5GHZ, I am using channel 157 and the bandwidth is set for Auto. I have it setup to only receive WIFI AC on 5GHZ. Hope this helps. I have now had the new drivers installed for two days and have not had a single dropout on either band. The only thing I still see that is strange is that Windows 10 reports the protocol used as WIFI "N" and not "AC" I know for a fact that it is using the "AC" protocol. This must be a bug within Windows 10.

Using the new Windows 10 driver I connect at 325 Mbps on the 5Ghz band. I dual boot with Ubuntu 15.10 which is using a Realtek driver rtl8812AU which connects the 5Ghz band at 867Mhz. Using USB 3.0. Is anyone connecting at 867Mhz and what's the secret?AC

ACGilbert wrote

Using the new Windows 10 driver I connect at 325 Mbps on the 5Ghz band. I dual boot with Ubuntu 15.10 which is using a Realtek driver rtl8812AU which connects the 5Ghz band at 867Mhz. Using USB 3.0. Is anyone connecting at 867Mhz and what's the secret?AC

I haven't updated the driver yet so my T4U is still on a USB2 port, but the connection shows 867 mbps. If you transfer a big file, what transfer rate does Win10 report? With USB3 on Win7 I used to get up to 32 MB/s if no contention for the bandwidth...