TP-Link TL-WN8200ND problem on startup?

[Storaro]

I've got a TP-Link TL-WN8200ND USB adapter on a Win7 PC. When I start my PC, the adapter does not work even though it is connected. I have to disconnect it and connect it again after startup for the adapter to start working. I re-installed the drivers, but this did not help.

 

[g90814]

Have you tried a different USB port?

 

[FACUCBA86]

Just came across a posible solution, in my case it worked. I was also having constant disconnects/reconnects on windows 7, I had to unplug usb and connect again to make it work after suspending my OS or shutting it down.
I noticed I couldn´t rename my wireless connection (which after I replaced my old tp link wifi adapter, it was named "Wireless Connection 2", couldn´t rename it to "Wireless Connection" so I knew something was up, with a little help from Google I was able to come across this solution to delete the old network wireless connection (apparently it was causing confusion between connections):

1) Go to Start, enter "regedit" right click the application and run it with Administrator Priviliges (right click it to see the context menu option).
2) Go to Edit, Search, and here you would enter "Wireless Connection" or whatever your old connection was named.
3) You should find a first entry you can check the PnpInstanceID to see that it actually DOESN´T MATCH your current hardware id for the TP Link 8200nd which is what you´re now using. If it DOESNT, then you can safely erase the entry (you can check the "Name"property of the entry as well). You can also delete the folder that contains the "Connection" folder that you see on the left of my example image.

http://imgur.com/a/2stOH

4) Keep searching for more entries repeating the previous method until you get rid of every entry of your OLD wireless adapter.

5) Now you can go to Control Panel, Networks, Network connections and just rename your new "Wireless Connection 2" to "Wireless Connection" to make sure you got rid of it.

6) Restart your pc and see if this works (Hopefully it will).



The issue looks to be related to hardware CONFLICT and not driver issues or anything like that, so if this doesn´t work, keep looking because this problem CAN be sorted out for sure.

Cheers !