D Link Dwa 140 Driver

1 view

Skip to first unread message

Mrx Wylie

unread,

Aug 3, 2024, 5:50:54 PM8/3/24

to prodernanca

@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.

Everytime it's stopped working I check Device Manager and the TP-Link Adapter has changed itself to a Realtek adapter (with a driver from 2008?) I have tried disabling Hardware Driver updates from Windows, Changing my Group Policy to disable Driver updates and even stopping the Windows Update Service. I'm honestly not sure what is happening, all I know is that everytime it stops it becomes a Realtek Device instead of saying "TP-Link Wireless Adapter"

We were looking to purchase around 1100 various TP-Link Access Points, Switches & Routers for our offices nationwide but based on this compatibility & level of support we have advised our service provider to offer us another quote with Ubiquiti products. Funny how this seemingly minor issue has caused us to rethink purchasing over half a million dollars of TP-Link gear.

Thank you for being interested in TP-Link products, it's a pity we failed to notice your case in first time, the moderators are active and monitoring the forum, but we might not be able to respond in a timely manner. For any urgent help, you could try to contact our local support via hotline or email from here:

I'd like also to emphasize a lack of compatibility with a new build of win10 (21H2 build). I also purchased T2E a month ago to this date I can't get a stable connection to it. Both drivers given from TP-Link official page are unstable.

3. How does the connection recover e.g. disconnect for 30 secs and reconnect by itself
4. What is the model number of your Wi-Fi router?
5. Please send us a photo of the driver version and computer system information as FAQ here : -link.com/support/faq/2722/

I have been gifted an AX1800, ARCHER TX20U Plus wireless usb adaptor, for my pc (Currently using Pop Os linux). Ive been searching for drivers but i cant find does anyone has a solution for that? I do not have a recipt so changing not an option. ( sorry for any wrong information ive given if you see the module ive been looking you will get the point)

I have 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!

It is worth mentioning that Intel does not support wireless integrations (installing a different wireless adapter into your system/laptop). We recommend you speak to the Manufacturer of your equipment for support on wireless integrations and replacement parts to ensure compliance with the regulatory requirements of your country and support. It is important to check for compatibility with the System Manufacturer, as there could be certain cards that will not work with the system.

Besides, Intel doesn't support and is not aware of the support or drivers of third-party products such as the Archer wireless cards. If you need assistance with this product specifically, contact the proper manufacturer of this card.

Thanks for your response! Yes I removed the old wireless card and disconnected the connector, inserted the new wireless card into the same PCIe slot and plugged the new card into the motherboard. The old card is no longer in the computer.

@Jocelyn_Intel Thanks for your response as well! That is all good information to know. To be honest I did think it was weird that their driver pack brought me to the intel site. The card came with a CD installation, but my PC does not have a CD rom so their instructions send you to their home page, and when you click on the driver download for that model card it redirects to the intel driver download site. I guess my whole problem is that I'm weirded out that its using the intel drivers, that it works with different intel drivers than the ones it had me download, and mainly that my PC isn't recognizing it as the card that it is but as an intel wireless Adapter. All very strange, but I appreciate the info.

@Podaen Thanks for that link! I will try that. Those steps look very similar to what I have tried a couple times except for using a different PCIe slot and trying to show hidden devices, I'll have to look around for that, but I thought I could see my wireless adapter, and I was selecting uninstall while also checking "remove associated drivers" and then when I was reinstalling the drivers it was showing up as the same wireless adapter rather than the new one of the different brand. But anyway thanks a bunch for taking time to post that help, much appreciated!

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

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