Tp Link Update Drivers

[Tarja Rabito]

Ihave been trying various methods of installing the ST-Link USB drivers on my Windows 11 Laptop, with absolutely no success. Here is the output I see when I try to run the installation batch file from the stsw-link009 download:

When I open the properties on the ST-Link device, it (obviously) says that the drivers are not installed. Needless to say, if I try to run a program form the Cube IDE, I get a "No-ST-Link Detected" message. Also, if I open a project on the mbed IDE while the nucleo is plugged in, the board does get recognized. The board is the F091RC, although I am not sure that's relevant to my issues. The pre-loaded blinky program does work as well.

I am a beginner in this space, so please let me know if I'm doing something dumb. I've read and watched a lot of things to try and figure out, and everything I've found either completely skips over any issues with this (so presumably it isn't a normal issue) or they dive into writing custom INF, disabling Secure Boot, or other relatively extreme measures.

Advise already given in this forum quite long ago (besides of modification and signing the INF) was to manually install the in-box winusb driver for ST-Link in the Device manager. This maybe works for early adopters of Win11 but there's time for ST to recognize Win11 .

Thanks for the input. I had seen that some forum posters had gotten it to work on 11, but I couldn't achieve the same success. I guess I'll just hold out until driver support is updated for Win11! Fingers crossed for it to be soon!

@BarryA

I have 2 TP-Link Kasa devises a KP115 smart plug with energy monitoring and a HS105 smart plug (no energy monitoring). So I installed your TP-Link Edge driver to try and get local control and energy monitoring for the KP115 in ST.

I do remember TP-Link had started disabling local control on some of their devices a couple years ago with a firmware update, but I believe they reversed that decision shortly after. Verify the FW is up to date.

Sorry about that, I do not have a KP115 to test with at this time. If I can get my hands on one I can try to get it working. Since the TP-Link API is not documented, adding new devices/capabilities often requires manual inspection of the protocol from the device itself.

Perfect, going to give this a try this weekend =) thank you so much for sharing this with the community. I know there are many of us that have TP-Link switches that would love to have them run locally

I have the outdoor plug (KP400) with two outlets. I am able to find it but it only the master outlet that controls both plugs but there is no individual outlets found so I am unable to control each separately. Also, the status works the first time and then gets stuck in the off position.You can still control both (off/on) but status changes for a brief second and changes back to off.

Yeah, unfortunately there is still some work to be done for the multi-component devices like the dual plug outlet and the power strip. At the time I wrote the driver multi-component devices were not yet supported for Edge drivers. If there is now support I will look into getting that fixed.

@BarryA thank you for providing the link to enroll in the channel. Typically after installing a particular driver I do a scan and the driver comes up as a new device but that is not happening here. How do we add bulbs? I assume we will need to create a new device but how is that done?

You just need to install the driver in the usual manner. Then do scan nearby and it should pick up any TP-Link Kasa devices that you already installed on your network using the Kasa app. I have 1 device that I had to unplug and plug in during the discover process.

Here you can download drivers for DisplayLink USB graphics chipsets incorporated in your dock, adapter or monitor. We recommend to update to the latest driver to address any potential security issue, fix bugs, improve performance and add new features.

Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the This page contains the VCP drivers currently available for FTDI devices.

Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the same way as it would access a standard COM port.

If a custom vendor ID and/or product ID or description string are used, it is the responsibility of the product manufacturer to maintain any changes and subsequent WHCK re-certification as a result of making these changes.

CountryAfghanistanAlbaniaAlgeriaAmerican SamoaAndorraAngolaAnguillaAntarcticaAntigua and BarbudaArgentinaArmeniaArubaAustraliaAustriaAzerbaijanBahamasBahrainBangladeshBarbadosBelarusBelgiumBelizeBeninBermudaBhutanBoliviaBosnia and HerzegovinaBotswanaBouvet IslandBrazilBritish Indian Ocean TerritoryBrunei DarussalamBulgariaBurkina FasoBurundiCambodiaCameroonCanadaCape VerdeCayman IslandsCentral African RepublicChadChileChinaChristmas IslandCocos (Keeling) IslandsColombiaComorosCongoCook IslandsCosta RicaCote D'IvoireCroatiaCubaCyprusCzech RepublicDenmarkDjiboutiDominicaDominican RepublicEast TimorEcuadorEgyptEl SalvadorEquatorial GuineaEritreaEstoniaEthiopiaFalkland Islands (Malvinas)Faroe IslandsFijiFinlandFrance, MetropolitanFrench GuianaFrench PolynesiaFrench Southern TerritoriesGabonGambiaGeorgiaGermanyGhanaGibraltarGreeceGreenlandGrenadaGuadeloupeGuamGuatemalaGuineaGuinea-BissauGuyanaHaitiHeard and Mc Donald IslandsHondurasHong KongHungaryIcelandIndiaIndonesiaIran (Islamic Republic of)IraqIrelandIsraelItalyJamaicaJapanJordanKazakhstanKenyaKiribatiNorth KoreaSouth KoreaKuwaitKyrgyzstanLao People's Democratic RepublicLatviaLebanonLesothoLiberiaLibyan Arab JamahiriyaLiechtensteinLithuaniaLuxembourgMacauFYROMMadagascarMalawiMalaysiaMaldivesMaliMaltaMarshall IslandsMartiniqueMauritaniaMauritiusMayotteMexicoMicronesia, Federated States ofMoldova, Republic ofMonacoMongoliaMontserratMoroccoMozambiqueMyanmarNamibiaNauruNepalNetherlandsNetherlands AntillesNew CaledoniaNew ZealandNicaraguaNigerNigeriaNiueNorfolk IslandNorthern Mariana IslandsNorwayOmanPakistanPalauPanamaPapua New GuineaParaguayPeruPhilippinesPitcairnPolandPortugalPuerto RicoQatarReunionRomaniaRussian FederationRwandaSaint Kitts and NevisSaint LuciaSaint Vincent and the GrenadinesSamoaSan MarinoSao Tome and PrincipeSaudi ArabiaSenegalSeychellesSierra LeoneSingaporeSlovak RepublicSloveniaSolomon IslandsSomaliaSouth AfricaSouth Georgia & South Sandwich IslandsSpainSri LankaSt. HelenaSt. Pierre and MiquelonSudanSurinameSvalbard and Jan Mayen IslandsSwazilandSwedenSwitzerlandSyrian Arab RepublicTaiwanTajikistanTanzania, United Republic ofThailandTogoTokelauTongaTrinidad and TobagoTunisiaTurkeyTurkmenistanTurks and Caicos IslandsTuvaluUgandaUkraineUnited Arab EmiratesUnited KingdomUnited StatesUnited States Minor Outlying IslandsUruguayUzbekistanVanuatuVatican City State (Holy See)VenezuelaViet NamVirgin Islands (British)Virgin Islands (U.S.)Wallis and Futuna IslandsWestern SaharaYemenDemocratic Republic of CongoZambiaZimbabweMontenegroSerbiaAaland IslandsBonaire, Sint Eustatius and SabaCuracaoPalestinian Territory, OccupiedSouth SudanSt. BarthelemySt. Martin (French part)Canary IslandsAscension Island (British)Kosovo, Republic ofIsle of ManTristan da CunhaGuernseyJersey

***Windows 10 and Windows 11 only. Universal Windows Drivers enable developers to create a single driver package that runs across multiple different device types, from embedded systems to tablets and desktop PCs.

3a8082e126