I cannot get the Support Page to work to request the new driver... can some one explain to me how to get the new driver?

That's what I told you... The current official driver doesn't work and the email form does not work as well.....

Kevin_Z wrote

@Bilbao 

 

Click here to get the official driver for the T2U.

 

If you have installed the official driver but still the same, you can email our tech support to get some help then. 

https://www.tp-link.com/support/contact-technical-support/#E-mail-Support  

First half of the Contact page works... on the second half i get the following message which means Send failed in German... treid it multiple times...

I dont understand why i have to tell you this a bunch of times... as other already said the same thing that the contact page doesnot work properly...

Bilbao, yeah they have pretty messed website, contact part does not work properly and login system is kind of messed up too. So I am not surprised anymore that Archer T2U drivers do not work. 

Also, these drivers what you will send you is not going to work either. Also pretty outdated driver.

I suggest that TP-Link would STOP selling faulty product and call it back! It's kind of pointless to sell a product which does not work in Europe and after months you still have no clue how to make it work, how to fix it. At the moment selling it in Europe is just damaging your company reputation every day.

I wish do return that product, since it clearly does not work with Windows 10 and I do need working product today, not in somewhere next year. It's pretty clear now that you have no clue why it does not work and how to fix it and when you are able to fix it.

I was also having similar problems (slow 2.4g connection and the 5g connection would connect but the internet would drop). I am currently running the latest version of Windows 10 (1903). The solution for me was to turn off "Projecting to this PC". It can be found in All settings -> System -> Projecting to this PC, then selecting "Always off" from the top drop down box. From what I can tell from comparing my various machines (some running 1809 and some running 1903), it was a feature that existed in previous versions, but was possibly defaulted to enabled with 1903. The feature itself does not seem to play well at all with the tp-link Archer T2U regardless of driver version; however, turning of the project feature fixed the problem for me.